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

[Helm] Gateway CRs not removed when disabling proxy in Helm values file. #9369

Open
DuncanDoyle opened this issue Apr 16, 2024 · 0 comments
Open
Labels
Area: Gloo Gateway Issues related to the Gloo Gateway project Area: Helm Type: Bug Something isn't working

Comments

@DuncanDoyle
Copy link
Contributor

Gloo Edge Product

Enterprise

Gloo Edge Version

1.16.6

Kubernetes Version

1.27.8

Describe the bug

When you have deployed a Gateway using Helm, and you later disable that Gateway in the Helm values file by setting:

gatewayProxies:
  myCustomGateway:
    disabled: true

the gateway deployment, service, replicaset, etc. are correctly removed from the namespace. However, the Gloo Proxy CRs for that specific Gateway, both the standard and ssl one, are not removed.

Expected Behavior

All resources of my disabled GW are properly cleaned up.

Steps to reproduce the bug

  1. Deploy a GE Gateway with Helm.
  2. Disable the gateway by setting its disabled: true flag in your Helm values file.
  3. Run a helm upgrade
  4. Observe that the Gateway CRs are not properly cleaned up.

Additional Environment Detail

No response

Additional Context

No response

@DuncanDoyle DuncanDoyle added Type: Bug Something isn't working Area: Helm Area: Gloo Gateway Issues related to the Gloo Gateway project labels Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Gloo Gateway Issues related to the Gloo Gateway project Area: Helm Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant