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

Why is iam_v1beta1_iampolicymember.yaml CRD missing gcp category? #286

Closed
MarkD43 opened this issue Sep 25, 2020 · 2 comments
Closed

Why is iam_v1beta1_iampolicymember.yaml CRD missing gcp category? #286

MarkD43 opened this issue Sep 25, 2020 · 2 comments
Labels
bug Something isn't working question Further information is requested

Comments

@MarkD43
Copy link

MarkD43 commented Sep 25, 2020

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.

@MarkD43 MarkD43 added the question Further information is requested label Sep 25, 2020
@caieo caieo added the bug Something isn't working label Sep 28, 2020
@caieo
Copy link
Contributor

caieo commented Sep 28, 2020

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!

@jcanseco
Copy link
Member

jcanseco commented Oct 7, 2020

Hi @MarkD43, this has now been fixed in KCC 1.24.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants