Add information about SSO & OIDC issues on k3d #498
Description
What type of suggestions?
Wrong Information
What page is concerned?
No response
What version of the docs?
ALL
What is the issue?
Add information about SSO & OIDC issues on k3d as right now (either in the FAQ or the user creation page, it's not implemented correctly like with any other clouds. See konstructio/kubefirst#1509 for the created issue about it.
if you create a new developer using terraform/atlantis:
✅ the also can log into vault
✅ they should be restricted in vault from being able to delete secrets
❌ they cannot access argocd with their vault user (workaround is logging in with admin)
when you provision k3d we do create a kbot user who:
✅ can log into vault
❌ cannot log into argocd (even though there’s a login with vault button) - the workaround for access is to use the admin user with a password pulled from the argocd namespace
✅ can technically get to argo workflows, but that’s because there’s ❌ no auth on argo workflows so anyone can reach workflows without any auth - it’s not technically using sso or anything though
Code of Conduct
- I agree to follow this project's Code of Conduct