nginxinc/kic-reference-architectures

fail to deploy prometheus

xp2014 opened this issue · 5 comments

Describe the bug
Fail to deploy prometheus with ./bin/start.sh.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a stack with ./bin/start.sh
  2. View logs on terminal
  3. See error

error: Program failed with an unhandled exception:

Your environment

  • Version of the repo -v1.1.1
  • Version of infrastructure tooling (Pulumi)
  • Version of executing environment (Python)
  • OS and distribution: ubuntu 20
  • Details about containerization or virtualization environment: Microk8s

Additional context
fail to deploy prometheus.log

Hi @xp2014 ,

Can you let me know what version of microk8s you are running? we have known issues with 1.24 #182

Jay

@qdzlug

1.23/stable: v1.23.9

Thanks,
XP

@xp2014 - thanks, confirmed that I'm able to reproduce this locally. Looking into it now.

Found the issue; when we refactored to use the python based startup script and the secrets namespace we missed ensuring that the admin password for Grafana was added to the config. This wasn't impacting the automated testing since that builds the config automatically.

Working on a patch for the repo, but short term, you can get around this by adding the value manually

pulumi config set prometheus:adminpass "${MARA_PASSWORD}" --secret -C pulumi/python/kubernetes/secrets -s "${STACKNAME}"

where you substitute your values for the two variables.

Found the issue; when we refactored to use the python based startup script and the secrets namespace we missed ensuring that the admin password for Grafana was added to the config. This wasn't impacting the automated testing since that builds the config automatically.

Working on a patch for the repo, but short term, you can get around this by adding the value manually

pulumi config set prometheus:adminpass "${MARA_PASSWORD}" --secret -C pulumi/python/kubernetes/secrets -s "${STACKNAME}"

where you substitute your values for the two variables.

Thanks!