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 operator is not powering up dashboard pods #746

Open
euruba opened this issue Mar 4, 2024 · 4 comments
Open

[BUG] Opensearch operator is not powering up dashboard pods #746

euruba opened this issue Mar 4, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@euruba
Copy link

euruba commented Mar 4, 2024

I have this configuration:

apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: my-cluster
  namespace: monitoring
spec:
  general:
    version: "2.12.0"
    httpPort: 9200
    vendor: opensearch
    serviceName: my-cluster
    monitoring:
     enable: true
    pluginsList: ["repository-s3"]
  dashboards:
    version: "2.12.0"
    enable: true
    replicas: 2
    resources:
      requests:
         memory: "1Gi"
         cpu: "500m"
      limits:
         memory: "1Gi"
         cpu: "500m"
    opensearchCredentialsSecret:                                                                                                                                                                                                                
      name: admin-credentials-secret  # The secret with the admin credentials for the operator to use
  confMgmt:
    smartScaler: true
  security:
    config:
      adminCredentialsSecret:
        name: admin-credentials-secret  # The secret with the admin credentials for the operator to use
      securityConfigSecret:
       name: securityconfig-secret  # The secret containing your customized securityconfig
    tls:
      transport:
        generate: true
      http:
        generate: true
  nodePools:
    - component: masters
      replicas: 3
      diskSize: "30Gi"
      nodeSelector:
      resources:
         requests:
            memory: "2Gi"
            cpu: "500m"
         limits:
            memory: "2Gi"
            cpu: "500m"
      roles:
        - "master"
        - "data"      
    - component: nodes
      replicas: 1
      diskSize: "30Gi"
      nodeSelector:
      resources:
         requests:
            memory: "2Gi"
            cpu: "500m"
         limits:
            memory: "2Gi"
            cpu: "500m"
      roles:
        - "data"
    - component: coordinators
      replicas: 1
      diskSize: "30Gi"
      nodeSelector:
      resources:
         requests:
            memory: "2Gi"
            cpu: "500m"
         limits:
            memory: "2Gi"
            cpu: "500m"
      roles:
        - "ingest"

And when I boot the cluster, the dashboard never boot.

I don´t know how to search what is failling.

Best regards

@euruba euruba added bug Something isn't working untriaged Issues that have not yet been triaged labels Mar 4, 2024
@VincSch
Copy link

VincSch commented Mar 6, 2024

I am experiencing the exact same behaviour.

@VincSch
Copy link

VincSch commented Mar 6, 2024

Hey @euruba,
In my case the problem was that I turned on

monitoring:
enable: true

but no prometheus monitoring crs where installed causing the operator to fail reconciling which leads to the point that dashboard pod wills never be spawned.

Try to disable monitoring or install the proper CRDs in your cluster.

As a hint its always worth checking the logs of the oprator :) thats my personal learning

@dhawaldenny
Copy link

@VincSch Thanks. Disabled Monitoring and it created the dashboards.

@prudhvigodithi
Copy link
Collaborator

[Triage]
Hey @euruba @VincSch @dhawaldenny, this should also work when monitoring is enabled, did you all follow the instructions listed here https://github.com/opensearch-project/opensearch-k8s-operator/blob/main/docs/userguide/main.md#adding-opensearch-monitoring-to-your-cluster, can you please confirm?

@prudhvigodithi prudhvigodithi removed the untriaged Issues that have not yet been triaged label Mar 26, 2024
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
None yet
Development

No branches or pull requests

4 participants