Issue #56: Adds vault-ui ingress #65
Conversation
Updated file name and created reference issue ai-cfia/github-workflows#105 |
…ause it currently doesnt have enough credentials to access vault
…-access-the-vault-ui-and-configure-secrets
I still see an uppercase PNG extension |
done |
…-access-the-vault-ui-and-configure-secrets
|
remaining task should provide us the ability to operate vault through kubernetes manifest. Problem is I am having problems giving proper authentication to the operator to manage vault. Since this is not a priority, it will be done in another issue. I also added the whitelisting source to allow access to vault only from vpn and internal. |
|
@rngadam We are having problems with our vault ui access since this pull request isn't merged. We have done fixing changes that would allow to fix these problems. The vite mgiration for nachet introduces updates to secrets. Since we arent able to access vault currently, we wont be able to deploy the new version of nachet. |
| @@ -0,0 +1,101 @@ | |||
| # Secret management | |||
There was a problem hiding this comment.
Create follow issue to turn this into an ADR to review by team and security.
There was a problem hiding this comment.
Opened ai-cfia/dev-rel-docs#117
| capabilities = [ "create", "update", "delete" ] | ||
| } | ||
| --- | ||
| apiVersion: redhatcop.redhat.io/v1alpha1 |
There was a problem hiding this comment.
future issue: document and explain reliance on redhat.io
There was a problem hiding this comment.
referenced in #99
We want to enable access to the vault-ui to enable the team to create secrets.
TODO before ready for merge:
- [ ] Find fix to enable vault config operator to have enough permissions to access and configure vault.Preceding task will be done in another issue since its to provide automation of vault configuration but we have problems enabling the operator to have proper permissions on the cluster to interact with vault. Since this is not a priority we will open an issue.