-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use release branch for costallocation in Platform,C2 and Playground (#…
- Loading branch information
Showing
4 changed files
with
0 additions
and
286 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,2 @@ | ||
# Prometheus Operator | ||
|
||
## Table of contents | ||
|
||
- [Refresh secrets](#Refresh-secrets) | ||
|
||
### Refresh secrets | ||
|
||
Refreshing secrets for Prometheus Operator can be done in 2 steps: | ||
1. Update `prometheus-token` secret with new password in KV | ||
1. One way to generate a password is to use `openssl rand -base64 32`. This will generate a 32 character string. | ||
2. Run [configure.sh](./configure.sh) to update components in kubernetes cluster. | ||
3. After updating the secrets we need to run [apply_scrape_config.sh](https://github.com/equinor/radix-monitoring/blob/master/cluster-external-monitoring/scripts/kube-prometheus-stack/apply_scrape_config.sh) on `external monitor cluster` to restart the component pods and force it to read the updated k8s secret(s) |
This file was deleted.
Oops, something went wrong.