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][opensearch-dashboard] add protocol TCP for metricsPortName #588

Closed
dmpe opened this issue Sep 3, 2024 · 2 comments · Fixed by #589
Closed

[BUG][opensearch-dashboard] add protocol TCP for metricsPortName #588

dmpe opened this issue Sep 3, 2024 · 2 comments · Fixed by #589
Assignees
Labels
bug Something isn't working

Comments

@dmpe
Copy link
Contributor

dmpe commented Sep 3, 2024

Describe the bug

When using server side apply, argocd says

Failed to compare desired state to live state: failed to calculate diff: error calculating server side diff: serverSideDiff error: error removing non config mutations for resource Service/opensearch-dashboards: error reverting webhook modified fields in predicted live resource: .spec.ports: element 1: associative list with keys has an element that omits key field "protocol" (and doesn't have default value)

Using latest version, helm chart is missing protocol property for metrics port

  - name: {{ .Values.service.metricsPortName | default "metrics" }}
    port: {{ .Values.service.metricsPort }}

To Reproduce

Steps to reproduce the behavior:

  1. Deploy Opensearch dashboard to k8s cluster via ArgoCD
  2. observe the error message

Expected behavior

Add protocol: TCP to the helm chart

Chart Name

opensearch-dashboard

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • Kubernetes Version: v1.28.11+rke2r1
  • argocd: 2.12.1
@dmpe dmpe added bug Something isn't working untriaged Issues that have not yet been triaged labels Sep 3, 2024
@prudhvigodithi
Copy link
Collaborator

This bug is coming from the PR #581, adding @VILJkid and @eyenx to please take a look.
Thank you

@VILJkid
Copy link
Contributor

VILJkid commented Sep 4, 2024

Thanks @dmpe, @prudhvigodithi for pointing this one out!
Looking into this and raising a PR with the fix shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

4 participants