You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, we store k8s and gitea authentication details in a hashicorp-vault instance which can only be accessed through VPN, this make difficult for manta to be portable.
A solution would be creating an user certificate CSM k8s can accept and create individual users in gitea
The text was updated successfully, but these errors were encountered:
I think with CSM 1.3+ we can get this working without a lot of work on the mesa/manta side of things::
TAPMS brings functionality that allows K8s to use OIDC tokens
The version of Gitea installed can connect to an OIDC provider, we could set it up to use the one within CSM.
Masber
changed the title
decomission hashicorp-vault and create certificates signed by CSM CA and create users in gitea
FIX: Decomission hashicorp-vault and create certificates signed by CSM CA and create users in gitea
Feb 25, 2024
Masber
changed the title
FIX: Decomission hashicorp-vault and create certificates signed by CSM CA and create users in gitea
FEATURE: Decomission hashicorp-vault and create certificates signed by CSM CA and create users in gitea
Feb 26, 2024
currently, we store k8s and gitea authentication details in a hashicorp-vault instance which can only be accessed through VPN, this make difficult for manta to be portable.
A solution would be creating an user certificate CSM k8s can accept and create individual users in gitea
The text was updated successfully, but these errors were encountered: