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

Disabling ingress does not remove the created ingress objects #2651

Closed
Starefossen opened this issue Feb 19, 2024 · 2 comments · Fixed by #2575
Closed

Disabling ingress does not remove the created ingress objects #2651

Starefossen opened this issue Feb 19, 2024 · 2 comments · Fixed by #2575
Assignees
Labels
bug Something isn't working needs triage

Comments

@Starefossen
Copy link
Contributor

Component(s)

collector

What happened?

Description

If you disable a previously enabled ingress for a Collector the ingress resource will not be deleted from the cluster.

Steps to Reproduce

  1. Create a collector with an ingress
  2. Remove the ingress and apply the collector to the cluster

Expected Result

The previously created ingress resource should be removed.

Actual Result

The previously created ingress is not removed.

Kubernetes Version

v1.28.3-gke.1286000

Operator version

0.93.0

Collector version

n/a

Environment information

Environment

Cloud: GKE

Log output

No response

Additional context

No response

@Starefossen Starefossen added bug Something isn't working needs triage labels Feb 19, 2024
@jaronoff97
Copy link
Contributor

Thanks for opening this, we are actively working on a fix. CC @yuriolisa this is the bug for #2575

@yuriolisa
Copy link
Contributor

Thank you, @jaronoff97, for pointing this out. I'm just waiting for @pavolloffay to review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants