v1.119.0
- This release adds options to configure the reconciliation of the ConfigConnector
- This release adds several new resources and fields.
- Special shout-outs to @acpana, @anhdle-sso, @barney-s, @cheftako, @gemmahou, @hankfreund, @jasonvigil, @jingyih, @justinsb, @maqiuyujoyce, @varsharmavs, @xiaoweim, @yuwenma, @zicongmei, @ziyue-101 for their
contributions to this release.
New features:
-
Add options to configure the reconciliation of the ConfigConnector controller
- Added a new
ControllerReconciler
CRD (v1alpha1). See example - This feature allows users to customize the client-side kube-apiserver request rate limit.
- Added a new
-
Continue moving towards Direct Actuation as our preferred mechanism.
- The default reconciler now uses Direct Actuation, if the ConfigConnector CRD does not have a
cnrm.cloud.google.com/tf2crd: "true"
orcnrm.cloud.google.com/dcl2crd: "true"
label.
- The default reconciler now uses Direct Actuation, if the ConfigConnector CRD does not have a
New Resources:
CloudBuildWorkerPool
- Added
CloudBuildWorkerPool
(v1alpha1) resource for servicecloudbuild
. - This resource uses Direct Actuation.
- Added
New Fields:
-
ComputeForwardingRule
- Added the
spec.target.serviceAttachmentRef
field, allowing aComputeForwaringRule
to target aComputeServiceAttachment
.
- Added the
-
ContainerCluster
- Added previous output-only spec fields to
status.observedState
- Added
status.observedState.masterAuth.clusterCaCertificate
- Added
status.observedState.privateClusterConfig.privateEndpoint
- Added
status.observedState.privateClusterConfig.publicEndpoint
- Added
- Added previous output-only spec fields to