You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are setting up a kubernetes 1.5 test environment on Centos 7 (c7 vms with stock extras kube rpms installed, atomic maybe later) and ran into acessibility issues with container registry.access.redhat.com/rhel7/pod-infrastructure:latest. This container seems to require a rhel subscribers client cert which we dont have.
Is it save to substitute this pause image in the kubelet config with pod-infra-container-image=gcr.io/google_containers/pause-amd64:3.0 ?
Pods work with this pause container now, but we would like to know if we miss something by substituting rhel7/pod-infrastructure with google_containers/pause-amd64.
The text was updated successfully, but these errors were encountered:
KollegaDe
changed the title
Is it save to replace the pause container in pod-infra-container-image?
Is it save to replace the pause container in pod-infra-container-image? (Kubelet 1.5 in C7 Extras)
Mar 17, 2018
We are setting up a kubernetes 1.5 test environment on Centos 7 (c7 vms with stock extras kube rpms installed, atomic maybe later) and ran into acessibility issues with container registry.access.redhat.com/rhel7/pod-infrastructure:latest. This container seems to require a rhel subscribers client cert which we dont have.
Is it save to substitute this pause image in the kubelet config with pod-infra-container-image=gcr.io/google_containers/pause-amd64:3.0 ?
Pods work with this pause container now, but we would like to know if we miss something by substituting rhel7/pod-infrastructure with google_containers/pause-amd64.
This gave us the idea for the substitution:
https://trello.com/c/CA5zb4WE/169-default-kubernetes-to-use-rh-provided-pause-container-kube-containers
The text was updated successfully, but these errors were encountered: