Use CEL rule to validate field immutability for direct Compute resources #3193
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.
Change description
b/377531379
Checked all three direct compute resources(forwarding rule, firewall policy rule, target tcp proxy), added CEL rule on the immutable and required fields, following https://github.com/GoogleCloudPlatform/k8s-config-connector/blob/master/docs/develop-resources/api-conventions/validations.md#option-2
Note: We haven't turned on direct reconciliation for those compute resources yet, instead, we use the "alpha.cnrm.cloud.google.com/reconciler: "direct"" annotation to opt-in. So they are still protected by the immutable webhook for now.
Tests you have done
make ready-pr
to ensure this PR is ready for review.