-
Notifications
You must be signed in to change notification settings - Fork 15
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
ingressclass is hardcoded to nginx #224
Labels
Milestone
Comments
Can you create the Nexus instance without the Ingress and manually create yours as a workaround? |
Sure. That's what I'm doing. |
Hmm, this is a bug, should not delete it if it's not owned by the operator. Many thanks for reporting it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The created ingress resource is annotated with: "kubernetes.io/ingress.class: nginx".
I use traefik, not nginx. The nexus-operator is unusable with a non-nginx ingress.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ingress should be created without any annotation. It is up to the cluster operator to set the desired default ingress.class. If needed a custom ingress can be set via a custom annotation or allow setting the spec.ingressClassName somehow.
Environment
Behaves the same no matter what the env is.
The text was updated successfully, but these errors were encountered: