Skip to content

cri-o v1.34: changed default: failed to pull images #4288

@volker-raschek

Description

@volker-raschek

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-crds

Nevertheless, 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-crds

Further information:

$ kubectl version
Client Version: v1.34.2
Kustomize Version: v5.7.1
Server Version: v1.34.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions