-
Notifications
You must be signed in to change notification settings - Fork 819
OCPBUGS-74511: Remove RouteExternalCertificate feature gate #2962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -422,7 +422,7 @@ type RouterShard struct { | |
| // TLSConfig defines config used to secure a route and provide termination | ||
| // | ||
| // +kubebuilder:validation:XValidation:rule="has(self.termination) && has(self.insecureEdgeTerminationPolicy) ? !((self.termination=='passthrough') && (self.insecureEdgeTerminationPolicy=='Allow')) : true", message="cannot have both spec.tls.termination: passthrough and spec.tls.insecureEdgeTerminationPolicy: Allow" | ||
| // +openshift:validation:FeatureGateAwareXValidation:featureGate=RouteExternalCertificate,rule="!(has(self.certificate) && has(self.externalCertificate))", message="cannot have both spec.tls.certificate and spec.tls.externalCertificate" | ||
| // +kubebuilder:validation:XValidation:rule="!(has(self.certificate) && has(self.externalCertificate))", message="cannot have both spec.tls.certificate and spec.tls.externalCertificate" | ||
|
Comment on lines
422
to
+425
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1. Undocumented tlsconfig xvalidation rule TLSConfig has a new +kubebuilder:validation:XValidation rule without a plain-language Go comment explaining the cross-field constraint. This reduces API clarity and violates the requirement to document XValidation rules in comments. Agent Prompt
|
||
| type TLSConfig struct { | ||
| // termination indicates the TLS termination type. | ||
| // | ||
|
|
@@ -475,7 +475,6 @@ type TLSConfig struct { | |
| // The router service account needs to be granted with read-only access to this secret, | ||
| // please refer to openshift docs for additional details. | ||
| // | ||
| // +openshift:enable:FeatureGate=RouteExternalCertificate | ||
| // +optional | ||
| ExternalCertificate *LocalObjectReference `json:"externalCertificate,omitempty" protobuf:"bytes,7,opt,name=externalCertificate"` | ||
| } | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Stale test gating docs
🐞 Bug⚙ MaintainabilityAgent Prompt
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools