gitea-admin/simple-private-codecollection
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Crossplane GCP Bucket generation rules to use preferred API version

Browse Source 
Modified the generation rules for Crossplane GCP Buckets to omit the version in resource type definitions, allowing the use of the API server's preferred version (currently v1beta2). Updated documentation to reflect this change and clarify version pinning for schema stability.

Changes include:
- Updated YAML generation rules to remove explicit versioning.
- Revised documentation to explain the implications of omitting versioning and the preferred version usage.

This enhances resilience across CRD upgrades and simplifies the configuration for users.
This commit is contained in:
stewartshea
2026-06-30 21:55:36 -04:00
parent eb8160e659
commit 31ac475c97
3 changed files with 20 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
codebundles/gcp-bucket-crossplane-health/.runwhen/generation-rules/gcp-bucket-crossplane-health.yaml
+6 -3
View File
@@ -4,12 +4,15 @@ spec:
platform: kubernetes
generationRules:
# Discover every Crossplane GCP Bucket in the cluster.
# Resource type syntax: plural.group/version
# Resource type syntax: plural.group[/version]
# plural = buckets (from `kubectl api-resources | grep storage.gcp.upbound.io`)
# group = storage.gcp.upbound.io
# version = v1beta1 (omit /version to use the API server's preferred version)
# version = omitted (use the API server's preferred version — currently v1beta2)
#
# Pin an explicit version like `buckets.storage.gcp.upbound.io/v1beta1`
# if you need schema stability across CRD upgrades.
- resourceTypes:
- buckets.storage.gcp.upbound.io/v1beta1
- buckets.storage.gcp.upbound.io
matchRules:
# Match every Bucket by name. Swap this regex to scope by naming
# convention (for example `^prod-.*` to only cover prod buckets) or