create an htpasswd per grafana stack component, and per tenant, including our default current cluster; prepare to deprecate bitwarden as an ESO provider #123

Merged
jessebot merged 6 commits from add-per-tenant-htpasswd-generation into main 2026-10-17 10:20:44 +00:00
Owner

Changes

  • create an htpasswd per grafana stack component per tenant, which always includes the current cluster name as a tenant
  • always put the grafana stack component htpasswd secrets in both the monitoring and alloy (OpenBao or k8s) namespaces
  • stops referring to loki, tempo, and mimir as "sub apps" of the LGTM stack and starts referring to them as "components"
  • support custom_namespace parameter for OpenBao.kv_put method
  • upgrade zensical 0.0.71 (closes #113)
  • Closes #121
  • Relates to oeng/argocd-apps#133
  • cleans up all references to bitwarden to be strictly a local password manager, except for the migration path to get off of Bitwarden as your ESO provider and start using OpenBao

Warning

This will be the last release in which we support Bitwarden as a Kubernetes Secrets manager. Going forward, you can still use Bitwarden as your local password manager, but as Bitwarden may be changing their licensing, we can't keep providing the Kubernetes service. OpenBao has very FOSS friendly licensing and as it's a fork of Vault, was build with Kubernetes in mind, and therefore supports many great quality of life features. Over time, we will slowly begin removing support for using Bitwarden as your ESO provider.

# Changes - create an htpasswd per grafana stack component *per tenant*, which always includes the current cluster name as a tenant - always put the grafana stack component htpasswd secrets in both the monitoring and alloy (OpenBao or k8s) namespaces - stops referring to loki, tempo, and mimir as "sub apps" of the LGTM stack and starts referring to them as "components" - support `custom_namespace` parameter for `OpenBao.kv_put` method - upgrade zensical `0.0.71` (closes #113) - Closes #121 - Relates to https://git.open.engineering/oeng/argocd-apps/pulls/133 - cleans up all references to bitwarden to be strictly a local password manager, except for the migration path to get off of Bitwarden as your ESO provider and start using OpenBao > [!Warning] > This will be the *last* release in which we support Bitwarden as a Kubernetes Secrets manager. Going forward, you can still use Bitwarden as your *local* password manager, but as Bitwarden may be changing their licensing, we can't keep providing the Kubernetes service. OpenBao has very FOSS friendly licensing and as it's a fork of Vault, was build with Kubernetes in mind, and therefore supports many great quality of life features. Over time, we will slowly begin *removing* support for using Bitwarden as your ESO provider.
create an htpasswd per grafana stack component, and per tenant, including our default current cluster
Some checks failed
Test smol-k8s-lab / test_k3s (pull_request) Failing after 1m32s
a2097eebc7
Signed-off-by: JesseBot <jessebot@linux.com>
jessebot added this to the WAF project 2026-10-17 07:28:11 +00:00
update grafana stack docs to also note you need the very first sync wave of alloy
All checks were successful
Test smol-k8s-lab / test_k3s (pull_request) Successful in 6m19s
ea70aca4ed
make sure that we also populate the k8s or openbao alloy namespaces with the remoteWrite credentials
Some checks failed
Test smol-k8s-lab / test_k3s (pull_request) Failing after 3m4s
74d101acc1
Signed-off-by: JesseBot <jessebot@linux.com>
upgrade zensical and make sure we update the BOTH openbao namespaces with the tenant secrets
Some checks failed
Test smol-k8s-lab / test_k3s (pull_request) Failing after 3m58s
93b1cf9f9e
make custom_namespace optional for the OpenBao.kv_put method
All checks were successful
Test smol-k8s-lab / test_k3s (pull_request) Successful in 6m47s
da1d7f6d18
get ready to deprecate bitwarden as an ESO provider down the line
All checks were successful
Test smol-k8s-lab / test_k3s (pull_request) Successful in 6m48s
22038ba8db
jessebot changed title from create an htpasswd per grafana stack component, and per tenant, including our default current cluster to create an htpasswd per grafana stack component, and per tenant, including our default current cluster; prepare to deprecate bitwarden as an ESO provider 2026-10-17 10:14:55 +00:00
jessebot deleted branch add-per-tenant-htpasswd-generation 2026-10-17 10:20:45 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
oeng/smol-k8s-lab!123
No description provided.