This message was deleted.
# general
a
This message was deleted.
s
That’s a good question - following
❤️ 1
r
kubectl get authconfigs
m
You may also be looking into: GlobalRoleBinding.management.cattle.io to give permission RoleTemplate.management.cattle.io to setup roletemplate that used on downstream cluster Setting.management.cattle.io to customize certain part of the auth parameters Project.management.cattle.io in the cluster namespace (obs, part of the name random) to create project) ClusterRoleTemplateBinding.management.cattle.io in cluster namespace)to give clusterpermission, and ProjectRoleTemplateBinding.management.cattle.io in the cluster-project namespace to give project roles
We have some setup in ArgoCD to create our downstream clusters and set permission in them
s
Oh interesting, has the worked well for you/your team?
m
It's good for setting up clusters, projects and onboarding, but when you need to change groups you can't update without removing old
When I did the first version (a year ago) the cards wasn't documented so you need to read the API/terraform doc. I have tried to let our contact know that really need to improve the doc of the crds so kubectl explain works
We are also having argocd to create clusters for pull request validation, mostly throught Kubernetes objects
Some parts like doing integration to hashicorp vault and ipam is call to terraform currently
The hard part was to understand that the cluster is random, even if old code says that it was a checksum of some parts