-
Notifications
You must be signed in to change notification settings - Fork 100
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add example to show how to use external secrets (#744)
Signed-off-by: Pete Wall <pete.wall@grafana.com>
- Loading branch information
Showing
8 changed files
with
70,886 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# External Secrets | ||
|
||
Using external secrets allows you to store the hostnames, usernames, passwords and other sensitive data in a pre-made | ||
Kubernetes Secret object. This example shows how to reference that secret, as well the keys within it: | ||
|
||
```yaml | ||
cluster: | ||
name: external-secrets-test | ||
externalServices: | ||
prometheus: | ||
hostKey: prom_hostname | ||
secret: | ||
create: false | ||
name: alloy-secret | ||
namespace: monitoring | ||
basicAuth: | ||
usernameKey: prom_username | ||
passwordKey: password | ||
|
||
loki: | ||
hostKey: loki_hostname | ||
secret: | ||
create: false | ||
name: alloy-secret | ||
namespace: monitoring | ||
basicAuth: | ||
usernameKey: loki_username | ||
passwordKey: password | ||
``` | ||
here is the secret object itself: | ||
```yaml | ||
apiVersion: v1 | ||
kind: Secret | ||
metadata: | ||
name: alloy-secret | ||
namespace: monitoring | ||
type: Opaque | ||
stringData: | ||
prom_hostname: "https://prometheus.example.com" | ||
prom_username: "12345" | ||
loki_hostname: "https://loki.example.com" | ||
loki_username: "12345" | ||
password: "It's a secret to everyone" | ||
``` |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.