Skip to content

Update gloo.solo.io settings_v1 schema from Gloo Edge 1.21.3 CRD - #942

Open
mkav-es wants to merge 1 commit into
datreeio:mainfrom
mkav-es:update-gloo-settings-v1-schema
Open

Update gloo.solo.io settings_v1 schema from Gloo Edge 1.21.3 CRD#942
mkav-es wants to merge 1 commit into
datreeio:mainfrom
mkav-es:update-gloo-settings-v1-schema

Conversation

@mkav-es

@mkav-es mkav-es commented Aug 14, 2026

Copy link
Copy Markdown

The current gloo.solo.io/settings_v1.json lags the Settings CRD shipped with recent Gloo Edge versions. Valid manifests fail strict kubeconform validation with e.g.:

at '/spec/gateway/validation': additional properties 'fullEnvoyValidation', 'warnMissingTlsSecret' not allowed
at '/spec/gloo': additional properties 'istioOptions', 'enableAutoWebsocketTransformationPassthrough' not allowed
at '/spec/gloo/awsOptions/serviceAccountCredentials': additional properties 'region' not allowed

Regenerated with this repo's Utilities/openapi2jsonschema.py from the settings.gloo.solo.io CRD installed by the gloo-ee 1.21.3 Helm chart (openAPIV3Schema, version v1).

Verified: a rendered gloo-ee 1.21.3 release (69 resources) that previously failed now passes kubeconform -strict against the updated schema.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant