-
Notifications
You must be signed in to change notification settings - Fork 239
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
Why is iam_v1beta1_iampolicymember.yaml CRD missing gcp category? #286
Comments
Hi @MarkD43 , thank you for bringing our attention to this. We are aware that our IAM Policy/IAM Policy Member CRDs don't have "gcp" category and shortnames the way the rest of our resources do. The short explanation is that our IAM resources are generated a little differently and we haven't yet added those fields/indicators into it. I will mark this as a bug and we will look into fixing this! |
Hi @MarkD43, this has now been fixed in KCC 1.24.0. |
When executing kubectl get gcp -n {namespace}, iam policy members are not returned. IAM policy member CRD is missing gcp category and short names.
We are currently using kcc version 1.19.1 but I see the latest CRD version is missing gcp category as well.
The text was updated successfully, but these errors were encountered: