You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.
Bug Description
I'm unable to create an IAMPartialPolicy resource with the latest version (1.54.0) of Config Connector.
The Go client throws an error, as IAMPartialPolicySpec does not match the CRD schema def.
Solution:
Use IAMResourceRef type in IAMPartialPolicySpec.
type IAMPartialPolicySpec struct {
/* Optional. The list of IAM bindings managed by Config Connector. */
// +optional
Bindings []PartialpolicyBindings `json:"bindings,omitempty"`
/* Immutable. Required. The GCP resource to set the IAM policy on (e.g. organization, project...) */
ResourceRef v1alpha1.IAMResourceRef `json:"resourceRef"`
}
Additional Diagnostic Information
Kubernetes Cluster Version
v1.19.9-gke.1900
Config Connector Version
1.54.0
Config Connector Mode
cluster
Log Output
E0627 20:28:36.073935 1 iam.go:33] Unable to create IAM Policy abc-iam-role-admin: IAMPartialPolicy.iam.cnrm.cloud.google.com "abc-iam-role-admin" is invalid: spec.resourceRef.kind: Required value
Steps to Reproduce
Steps to reproduce the issue
Create a new iamv1beta1.IAMPartialPolicy resource with the Go client.
The text was updated successfully, but these errors were encountered:
Checklist
Bug Description
I'm unable to create an
IAMPartialPolicy
resource with the latest version (1.54.0
) of Config Connector.The Go client throws an error, as IAMPartialPolicySpec does not match the CRD schema def.
Solution:
Use IAMResourceRef type in
IAMPartialPolicySpec
.Additional Diagnostic Information
Kubernetes Cluster Version
v1.19.9-gke.1900
Config Connector Version
1.54.0
Config Connector Mode
cluster
Log Output
Steps to Reproduce
Steps to reproduce the issue
Create a new
iamv1beta1.IAMPartialPolicy
resource with the Go client.The text was updated successfully, but these errors were encountered: