Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate the rbac-proxy in stunner-gateway-operator #47

Open
rg0now opened this issue Jan 30, 2025 · 0 comments · May be fixed by #48
Open

Deprecate the rbac-proxy in stunner-gateway-operator #47

rg0now opened this issue Jan 30, 2025 · 0 comments · May be fixed by #48

Comments

@rg0now
Copy link
Member

rg0now commented Jan 30, 2025

We no longer deploy the kube-rbac-proxy: it was never really needed to begin with, plus it's now deprecated (see l7mp/stunner#185). The operator kustomize pipeline has been changed so that we no longer deploy the rbac-proxy (see l7mp/stunner-gateway-operator@79212a8). This change needs to be carried over here.

The major difference is that we have disabled the manager_auth_proxy_patch.yaml kustomize patch. This effectively removes the kube-rbac-proxy sidecar container in the controller-manager Deployment. The simplest way to see the effects is to run kustomize build config/default in the stunner-gateway-operator repo and compare the output with the Helm templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant