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.

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

Cannot create dashboard on cluster with custom name #959

Closed
ciomaire opened this issue Mar 23, 2023 · 4 comments · Fixed by #962
Closed

Cannot create dashboard on cluster with custom name #959

ciomaire opened this issue Mar 23, 2023 · 4 comments · Fixed by #962
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on. v5 A v5 specifc issue/feature

Comments

@ciomaire
Copy link

Describe the bug

On a k8s cluster with a custom cluster-name, grafana-operator is attempting to reconcile a dashboard using an incorrect service fqdn which includes .svc.cluster.local

Looks like the issue that was originally reported in #592 and fixed in #791

Version
v5.0.0-rc0

Suspect component/Location where the bug might be occurring
'.cluster.local' is hardcoded in the service fqdn in https://github.com/grafana-operator/grafana-operator/blob/master/controllers/reconcilers/grafana/grafana_service_reconciler.go#L49-L53

Runtime (please complete the following information):

  • Grafana Operator Version v5.0.0
@ciomaire ciomaire added bug Something isn't working needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 23, 2023
@NissesSenap NissesSenap added the v5 A v5 specifc issue/feature label Mar 24, 2023
@NissesSenap
Copy link
Collaborator

Hmm so there is nothing that you can't change when it comes to how the ingress and service should look like, but the status field will not adapt to this, and it will probably be rather painful to do...

As a workaround, I would set prefer ingress config to true so you can use the operator. And to be honest it's not impossible that's the solution we will recommend in the future.
To be honest, the number of users that sets custom cluster names should be extremely limited since it's an antipattern.
But at the same time we could probably remove the svc.cluster.local from the status since it should be enough with the namespace.

@NissesSenap NissesSenap added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 24, 2023
@pb82
Copy link
Collaborator

pb82 commented Mar 24, 2023

@NissesSenap Yes, the original fix did exactly that, remove .svc.cluster.local. If it works without that, we could do the same, would that work on a cluster with a custom domain?

@weisdd
Copy link
Collaborator

weisdd commented Mar 24, 2023

Yeah, I think we should reintroduce the change. Should work just fine.

@weisdd
Copy link
Collaborator

weisdd commented Mar 25, 2023

@ciomaire the fix will be included in the next RC version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage/accepted Indicates an issue or PR is ready to be actively worked on. v5 A v5 specifc issue/feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants