-
Notifications
You must be signed in to change notification settings - Fork 235
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
SecretManagerSecret automatic replication no longer working #1081
Comments
Have you tried removing the whole replication section and see if the resource can be acquired successfully?
|
Sorry, I meant to include the new non-deprecated field "auto" rather than "automatic". yaml update to reflect. |
@sthomson-wyn Are you able to determine the actual configurations of the existing resource? For example does the existing resource have |
yielded
|
I have the same issue when attempting to create a new SecretManagerSecret using the following YAML
Attempting to apply fails with The SecretManagerSecret docs states that replication.auto.customerManagedEncryption should be valid. I can repro this on a new cluster built on Friday last week using a cnrm image |
Checklist
Bug Description
A SecretManagerSecret resource with
.spec.replication.auto = {}
yieldsUpdate call failed: cannot make changes to immutable field(s): [Field Name: replication.0.auto.#, Got: 0, Wanted: 1];
Additional Diagnostic Information
Unclear if this happens on a brand new resource, but this is happening for an existing resource
Kubernetes Cluster Version
v1.27.4-gke.900
Config Connector Version
1.112.0
Config Connector Mode
cluster mode
Log Output
No response
Steps to reproduce the issue
Create yaml below, for an existing secret in GSM
YAML snippets
The text was updated successfully, but these errors were encountered: