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

FEATURE: Decomission hashicorp-vault and create certificates signed by CSM CA and create users in gitea #26

Open
Masber opened this issue Feb 12, 2024 · 1 comment

Comments

@Masber
Copy link
Collaborator

Masber commented Feb 12, 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

@miguelgila
Copy link
Collaborator

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 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants