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

[BUG]Unable to define a static IP address for the service type LoadBalancer in dashborad configuration strict decoding error: unknown field "spec.dashboards.service.LoadBalancer" #945

Closed
febi881 opened this issue Jan 23, 2025 · 1 comment
Labels
bug Something isn't working untriaged Issues that have not yet been triaged

Comments

@febi881
Copy link

febi881 commented Jan 23, 2025

What is the bug?

[BUG]Unable to define a static IP address for the service type LoadBalancer

How can one reproduce the bug?

Use the following config in dashboard section

dashboards: enable: true service: #externalTrafficPolicy: Local type: LoadBalancer LoadBalancerIP: "10,x,x,x"

What is the expected behavior?

As per the https://artifacthub.io/packages/helm/opensearch-project-helm-charts/opensearch-dashboards/1.26.0 given chart details the above confi should provision a LoadBalance type service and assign the defined IP

What is your host/environment?

RockyLinux 9,
LAB Kubernetes
opensearch-operator chart version 2.7.0
Openserach Version installed: 2.18.0

Do you have any screenshots?

Error: strict decoding error: unknown field "spec.dashboards.service.LoadBalancer"

Do you have any additional context?

The Opensearch cluster ins installed and currently up and running but patching with a static LoadBalancer IP creates the problem, I am manually able to edit the dashboard service and set the LoadBalancer IP

@febi881 febi881 added bug Something isn't working untriaged Issues that have not yet been triaged labels Jan 23, 2025
@swoehrl-mw
Copy link
Collaborator

Hi @febi881. The operator does not expose the full range of configuration options available for services. The helm chart you have linked is not for the operator, so what is possible there is irrelevant.
The intended usage is to expose opensearch and dashboards via an ingress controller for proper certificate and routing handling. If you want to really expose Dashboards directly via service type Loadbalancer please create and apply your own service manifest alongside the cluster spec.

@swoehrl-mw swoehrl-mw closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2025
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Engineering Effectiveness Board Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issues that have not yet been triaged
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants