Update dependency GoogleCloudPlatform/k8s-config-connector to v1.115.0 #190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.114.0
->v1.115.0
Release Notes
GoogleCloudPlatform/k8s-config-connector (GoogleCloudPlatform/k8s-config-connector)
v1.115.0
Compare Source
v1.114.1
: 1.114.1Compare Source
(Version 1.114.0 contained a minor regression discovered after tagging, and was not published; we recommend 1.114.1 instead)
Stop merging sensitive fields in SQLInstance and ComputeBackendService
Fix resource deletion of
AlloyDBInstance
andEdgeContainerNodePool
when their "parent objects" no longer exist.Initial support (alpha stability) for pausing reconciliation, by setting
spec.actuationMode: Paused
in the ConfigConnectorContext.Initial support (alpha stability) for defaulting state-into-spec to absent (the recommended setting),
by setting
spec.stateIntoSpec: Absent
in the ConfigConnectorContext.Experimental "powertools" area of the CLI, containing experimental/dangerous functionality that should not be
part of normal operation, but can sometimes nonetheless be useful.
Special shout-outs to @Hamzawy63, @hkundag, @katrielt for their
contributions to this release.
Resources promoted from alpha to beta:
When resources are promoted from alpha to beta, we (generally) ensure they follow our best practices: use of refs on fields where appropriate,
output fields from GCP APIs are in
status.observedState
.AccessContextManagerServicePerimeterResource
New Resources:
Added support for
ComputeNetworkFirewallPolicyAssociation
(v1beta1) resource.Added support for
APIKeysKey
(v1alpha1) resource.New Fields:
BigQueryDataSet
access[].iamMember
field.ComputeAddress
status.observedState.address
field.ComputeTargetHttpsProxy
spec.certificateManagerCertificates
field.DNSRecordSet
spec.routingPolicy
field.GKEHubFeatureMembership
spec.policycontroller
field.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.