Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Draft]: Integrate HashiCorp Vault Support in Splunk Operator #1387

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/PasswordManagement.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
- [Secrets on Docker Splunk](#secrets-on-docker-splunk)
- [SmartStore Access using AWS IAM Role for Service Account](#smartstore-access-using-aws-iam-role-for-service-account)
- [Support for AWS IAM Role for Service Account in Splunk Operator Deployment](#support-for-aws-iam-role-for-service-account-in-splunk-operator-deployment)
- [Support for Hashicorp Vault](#support-for-hashicorp-vault-in-splunk-operator-deployment)

## Global kubernetes secret object
A global kubernetes secret object acts as the source of secret tokens for a kubernetes namespace used by all Splunk Enterprise CR's. It's name follows the format `splunk-<namespace>-secret` where `<namespace`> represents the namespace we are operating in. The contents of this object are volume mounted on all the pods within a kubernetes namespace.
Expand Down Expand Up @@ -153,4 +154,7 @@ spec:
persistentVolumeClaim:
claimName: splunk-operator-app-download
...
```
```

## Support for Hashicorp Vault in Splunk Operator Deployment
TODO
Loading