The config connector is calling the api with the project id taken from the namespace field of the yaml file, instead of the actual GCP project id.
If the namespace field is left empty it takes the default namespace (default).
However if I add the annotation cnrm.cloud.google.com/project-id and set it to my project id the correct endpoint is called and my resource is created. As of now this field seems to be required to set for this resource to work, either there is information missing in the documentation or this is a bug in the implementation.
Checklist
Bug Description
The documented yaml specification does not work out of the box for SecretManagerSecret, seen here: https://cloud.google.com/config-connector/docs/reference/resource-docs/secretmanager/secretmanagersecret
The config connector is calling the api with the project id taken from the namespace field of the yaml file, instead of the actual GCP project id.
If the namespace field is left empty it takes the default namespace (default).
However if I add the annotation
cnrm.cloud.google.com/project-id
and set it to my project id the correct endpoint is called and my resource is created. As of now this field seems to be required to set for this resource to work, either there is information missing in the documentation or this is a bug in the implementation.Additional Diagnostic Information
none
Kubernetes Cluster Version
1.29
Config Connector Version
1.115.0
Config Connector Mode
cluster mode
Log Output
Steps to reproduce the issue
Apply the yaml file in the cluster without adding the annotation
cnrm.cloud.google.com/project-id
YAML snippets