Current Behavior
Integration tests are failing on master because gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0
has been removed from the registry. The meshery-operator pod gets stuck in
ImagePullBackOff, causing the deployment to time out and integration test setup to fail.
Confirmed failing on master across CI runs and verified locally.
Desired Behavior
Integration tests should set up successfully and the meshery-operator pod
should start without image pull errors.
Implementation
Update the kube-rbac-proxy image reference in
config/default/manager_auth_proxy_patch.yaml to a newer available version
from gcr.io/kubebuilder or migrate to quay.io/brancz/kube-rbac-proxy
which is the actively maintained registry.
Acceptance Tests
make integration-tests-setup completes without errormeshery-operator pod starts with both containers (kube-rbac-proxy and manager) in Running state- Integration Tests CI passes on master
Contributor Guides and Resources
Current Behavior
Integration tests are failing on master because
gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0has been removed from the registry. The
meshery-operatorpod gets stuck inImagePullBackOff, causing the deployment to time out and integration test setup to fail.Confirmed failing on master across CI runs and verified locally.
Desired Behavior
Integration tests should set up successfully and the
meshery-operatorpodshould start without image pull errors.
Implementation
Update the
kube-rbac-proxyimage reference inconfig/default/manager_auth_proxy_patch.yamlto a newer available versionfrom
gcr.io/kubebuilderor migrate toquay.io/brancz/kube-rbac-proxywhich is the actively maintained registry.
Acceptance Tests
make integration-tests-setupcompletes without errormeshery-operatorpod starts with both containers (kube-rbac-proxyandmanager) in Running stateContributor Guides and Resources