search

sassoftware / viya4-monitoring-kubernetes

Provides simple scripts and customization options to deploy monitoring, alerts, and log aggregation for Viya 4 running on Kubernetes
Apache License 2.0
56 stars 32 forks source link

Opensearch Dashboard 502 Bad gateway #551

Closed Vergr0 closed 1 year ago

Vergr0 commented 1 year ago

Hello,

I've deployed logging compontents using deploy_logging.sh script. I used user-values-opensearch.yaml and user-values-osd.yaml files from samples/azure-deployment directory to set path based ingress.

Deployment went fine, but when I try to access my.host/dashboards I get 502 Bad Gateway. There are no errors in osd pod logs. In ingress-nginx pod logs I see that when I try to access my.host/dashboards I get the following error:

obraz

Viya is deployed on AKS. Could you please help me resolve this issue? Best Regards

gsmith-sas commented 1 year ago

@Vergr0 Thank you for reporting this issue; I'm sorry to report that you have found a bug. Evidently, the azure-deployment sample was not updated to reflect our recent change to enable TLS (and, HTTPS) by default. Please use the user-values-opensearch.yaml and user-values-osd.yaml files in the samples/ingress/path-based-ingress sub-directory instead of the ones in the azure-deployment sample.

If you are using a custom storageClass for the OpenSearch PVCs (as recommended in the azure-deployment sample), you will need to copy the persistence stanza (i.e. the two lines setting the persistence and storageClass keys) from the azure-deployment/logging/user-values-opensearch.yaml file to your user-values-opensearch.yaml.

Thanks again for reporting this, please let us know if this resolves your issue. We will correct the azure-deployment sample in the soon.

Vergr0 commented 1 year ago

@gsmith-sas Thank you for quick reply. I followed your instructions and it worked, now I can access opensearch dashoboards without any issues.

I'm closing the issue, thank you for help.