-
Notifications
You must be signed in to change notification settings - Fork 828
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
Operator docs may require enhancement #3963
Comments
Sounds good to me. @calvin0327 can you help to confirm that? |
@RainbowMango That's sure. /assign |
@Vacant2333 Thanks pointing this, there is a better way to get the karmada config: kubectl get secret -n <KARMADA_NAMESPACE> $(kubectl get karmada -n <KARMADA_NAMESPACE> <KARMADA_NAME> -ojsonpath='{.status.secretRef.name}') -ojsonpath='{.data.config}' | base64 -d > config |
yes its better,and is there something we can add to the file too? |
@calvin0327, @Vacant2333 might want to help on this :) |
ah no, I mean if there something can update to this file too that I didnt mention. And it's ok Calvin to do this |
Except for this, I didn't think of anything else to update to the README. |
we may can add a example for |
What would you like to be added:
Operator docs may require enhancement
https://github.com/karmada-io/karmada/blob/master/operator/README.md
Why is this needed:
for example:
we can add the the usage to get the karmada-apiserver's kubeconfig
kubectl get secret -n {namespace} karmada-demo-admin-config -o jsonpath='{.data.config}' | base64 --decode > kubeconfig.yaml
The text was updated successfully, but these errors were encountered: