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
The ask from the customer is to use trusted F5 NGINX container registries.
The goal is that the operator is easy for customers that are offline.
And the installation of the operator cannot dynamically pull from registries because of corporate security policy.
In this case each image registry needs to be expressly trusted and approved by the security team.
To add to this, is there a way to point to a private registry that is hosting the necessary images for the operator? I am having to host the kube-rbac-proxy image in our private repo and everywhere I change it, the operator reverts to the gcr.io registry.
Review all the container registries that we use in the operator project and consolidate them to use Quay when possible.
Examples:
nginx-ingress-helm-operator/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml
Line 418 in 61bf1f3
nginx-ingress-helm-operator/config/default/manager_auth_proxy_patch.yaml
Line 34 in 61bf1f3
Related issue, #336, was closed by issuer as "self resolved. the changes persisted."
Tasks
The text was updated successfully, but these errors were encountered: