[Bug] Ingress - Bad servicePort

[pbrissaud]

Describe the bug
When upgrading to 3.10.4 version, I can't access to Grafana via Ingress (I can via port-forward). When I look to the Ingress spec, the servicePort is set to 'http' but the grafana-service don't have a 'http' port (only 'grafana'). When I downgrade to 3.10.3 version, the servicePort is setup to '3000' and it works.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade CRDs
2. Upgrade operator deployment and roles settings
3. Apply grafana CR
4. Pod is running but no access via Ingress

Expected behavior
The servicePort field in Ingress is set to 'grafana' or '3000'

Suspect component/Location where the bug might be occuring
unknown

Screenshots
Ingress in 3.10.3:

...
spec:
  rules:
  - host: xxx.yyy.zz
    http:
      paths:
      - backend:
          serviceName: grafana-service
          servicePort: 3000
        path: /
        pathType: ImplementationSpecific
...

Ingress in 3.10.4:

spec:
  rules:
  - host: xxx.yyy.zz
    http:
      paths:
      - backend:
          serviceName: grafana-service
          servicePort: 'http'
        path: /
        pathType: ImplementationSpecific

Service (even in 3.10.3 and 3.10.4):

spec:
  clusterIP: 10.43.90.160
  ports:
  - name: grafana
    port: 3000
    protocol: TCP
    targetPort: grafana-http
  selector:
    app: grafana
  sessionAffinity: None
  type: ClusterIP

Runtime (please complete the following information):

• OS: Linux
• Grafana Operator Version: 3.10.4
• Environment: Kubernetes 1.19.14
• Deployment type: Deployed

[NissesSenap]

This should now be solved, we will cut a release as soon as we can with this fix. Thanks for reporting it

[willthames]

@NissesSenap when will that release cut happen - it's been over a month since this issue was closed, and yet 3.10.4 is still the latest available 3.10 version.

[pbrissaud]

Hi, The v4 release fix this issue ! Regards, Paul Le lun. 22 nov. 2021 à 08:56, Will Thames ***@***.***> a écrit :

…

@NissesSenap <https://github.com/NissesSenap> when will that release cut happen - it's been over a month since this issue was closed, and yet 3.10.4 is still the latest available 3.10 version. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#554 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGPRHGGFL7PTWZPL2N7RS73UNHZUVANCNFSM5FOCJUVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[NissesSenap]

@willthames we are stuck with k8s-operatorhub/community-operators#265.
We would love to get some help to debug this if you feel up for it.

None of the maintainers is getting paid to manage/develop this operator so we haven't had time to prioritize this. Sorry for the delay.

[js-timbirkett]

I'm guessing that not bringing the fix to v3 is a polite way of saying: move to v4 😄 😬

[NissesSenap]

No we want this feature to be released under 3.10.4 using OLM and as explained we are stuck in the CI process and no one have prioritised to solve it: #554 (comment)

@js-timbirkett if you are not using OCP and OLM 3.10.4 version image is built and available and you should be able to use it in helm. You can find 3.10.4 release here: https://github.com/grafana-operator/grafana-operator/releases/tag/v3.10.4

[js-timbirkett]

Hmmm... the ingress in 3.10.4 is definitely broken as per the initial issue: https://github.com/grafana-operator/grafana-operator/blob/v3.10.4/pkg/controller/model/grafanaIngress.go#L66-L69