You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create an nexus instance with networking.exposeAs: Ingress
See that the ingress is created with a annotation: "kubernetes.io/ingress.class: nginx"
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:
Sure. That's what I'm doing.
I configure my nexus instance with networking.expose=false and create an ingress with a different name myself.
If my custom ingress has the same name as the nexus instance your operator deletes it.
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: