-
Notifications
You must be signed in to change notification settings - Fork 397
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
[Bug]: unable to create ingress object in openshift #1484
Comments
@alexlionnel do you want to use ingress, or do you actually want to use OCP routes? If I remember correctly, we have more or less removed the possibility to create an ingress from OCP users without thinking of it. |
In fact, i want to use an ingress with tls config, using cert manager ingress:
metadata:
cert-manager.io/cluster-issuer: letsencrypt-issuer
spec:
ingressClassName: openshift-default
tls:
- hosts:
- <my_domain.com>
secretName: secret-cert-tls
rules:
- host: <my_domain.com>
http:
paths:
- backend:
service:
name: grafana-service
port:
number: 3000
path: /
pathType: Prefix But ingress is not created |
With our current implementation, that is not possible.
As a workaround, I recommend that you setup an ingress separately from the operator. Sorry for the inconvenience. |
Describe the bug
Ingress resource is not created when i create a grafana instance using grafana operator
Version
I am using grafana-operator v5.8.0 and openshift 4.12.53
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ingress resource should be created but it isn't
Same result with
ingressClassName: nginx
The text was updated successfully, but these errors were encountered: