-
Notifications
You must be signed in to change notification settings - Fork 838
Open
Labels
bugSomething isn't workingSomething isn't working
Description
I've tried to deploy the helm chart in my kubernetes cluster, but my cluster is not able to pull the container images.
The maintainers of cri-o changed the behavior of unqualified container images names (short-names). They will not automatically use docker.io. This leads to an deployment issue.
I've tried to modified the values.yaml and added the registry host. For example
postUpgrade:
labelNamespace:
image:
- repository: openpolicyagent/gatekeeper-crds
+ repository: docker.io/openpolicyagent/gatekeeper-crdsNevertheless, there is one helm hook job which can't be deployed, because the environment is not able to pull the container image: kubectl get jobs.batch gatekeeper-update-crds-hook.
Please adapt the values.yaml and introduce a dedicated property to set the registry for all kind of deployments:
postUpgrade:
labelNamespace:
image:
+ registry: docker.io
repository: openpolicyagent/gatekeeper-crdsFurther information:
$ kubectl version
Client Version: v1.34.2
Kustomize Version: v5.7.1
Server Version: v1.34.2Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working