Skip to content

migrate monitoring stack to argocd - #1515

Open
iamvigneshwars wants to merge 4 commits into
mainfrom
migration/monitoring-argocd
Open

migrate monitoring stack to argocd #1515
iamvigneshwars wants to merge 4 commits into
mainfrom
migration/monitoring-argocd

Conversation

@iamvigneshwars

Copy link
Copy Markdown
Contributor

No description provided.

@iamvigneshwars iamvigneshwars self-assigned this Aug 6, 2026
@iamvigneshwars iamvigneshwars added the helm Pull request that updates Helm charts label Aug 6, 2026
valuesObject: {}

monitoring:
enabled: false

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason why it’s switched off in staging?

@iamvigneshwars iamvigneshwars Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SInce we don't have a sealedsecret controller inside the vcluster in pollux, thought it might be better to wait for your openbao migration

metadata:
name: grafana-oauth
namespace: workflows
namespace: monitoring

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has to be workflows (referring to the namespace the vcluster is installed in). It is then mapped in both the values.yaml and staging-values.yaml to its destination namespace within the vcluster

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The monitoring chart is rendered inside the vcluster, with monitoring namespace as the destination. So, this template must be in the monitoring namespace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

helm Pull request that updates Helm charts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants