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.

Sign up for GitHub

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

Jump to bottom

Support ingressClassName in collector spec #1268

Closed
avadhut123pisal opened this issue Nov 21, 2022 · 0 comments · Fixed by #1269
Closed

Support ingressClassName in collector spec #1268

avadhut123pisal opened this issue Nov 21, 2022 · 0 comments · Fixed by #1269
Labels
area:collector Issues for deploying collector

Comments

@avadhut123pisal
Copy link
Contributor

Ingress controller implementations use this field (ingressClassName) to know whether they should be serving the Ingress resource.

Before the IngressClass resource and ingressClassName field were added in Kubernetes 1.18, Ingress classes were specified with a kubernetes.io/ingress.class annotation on the Ingress. This annotation was never formally defined, but was widely supported by Ingress controllers.

The newer ingressClassName field on Ingresses is a replacement for that annotation

https://kubernetes.io/docs/concepts/services-networking/ingress/#deprecated-annotation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:collector Issues for deploying collector
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

adds ingressClassName field to collector spec avadhut123pisal/opentelemetry-operator
2 participants
@pavolloffay @avadhut123pisal