This is a known issue affecting the Harbor package in TKG 1.4. There is currently no resolution.Workaround:
To workaround this issue use the following procedure to patch the Harbor package.
- Create a file named overlay-notary-signer-image-fix.yaml with the following contents:
#@ load("@ytt:overlay", "overlay")
#@overlay/match by=overlay.and_op(overlay.subset({"kind": "Deployment"}), overlay.subset({"metadata": {"name": "harbor-notary-signer"}}))
---
spec:
template:
spec:
containers:
#@overlay/match by="name",expects="0+"
- name: notary-signer
image: projects.registry.vmware.com/tkg/harbor/notary-signer-photon@sha256:4dfbf3777c26c615acfb466b98033c0406766692e9c32f3bb08873a0295e24d1
- Issue a command similar to the following to create a secret from the file created in Step 1:
kubectl -n <Harbor namespace> create secret generic harbor-notary-singer-image-overlay -o yaml --dry-run=client --from-file=overlay-notary-signer-image-fix.yaml | kubectl apply -f -
Note: Replace <Harbor namespace> with the name of the namespace where the Harbor package is installed.
- Issue a command similar to the following to patch the Harbor package:
kubectl -n <Harbor namespace> annotate packageinstalls harbor ext.packaging.carvel.dev/ytt-paths-from-secret-name.0=harbor-notary-singer-image-overlay
Note: Replace <Harbor namespace> with the name of the namespace where the Harbor package is installed.