-
Notifications
You must be signed in to change notification settings - Fork 107
CFE-885:Feature route external certificate validation #407
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
Changes from all commits
a23830d
00e9a02
baedcfe
74f2fc1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -103,7 +103,7 @@ func (o *OpenShiftAPIServer) Validate() error { | |
|
|
||
| // RunAPIServer takes the options, starts the API server and waits until stopCh is closed or initial listening fails. | ||
| func (o *OpenShiftAPIServer) RunAPIServer(stopCh <-chan struct{}) error { | ||
| if err := features.InitializeFeatureGates(feature.DefaultMutableFeatureGate, configv1.FeatureGateRouteExternalCertificate); err != nil { | ||
| if err := features.InitializeFeatureGates(feature.DefaultMutableFeatureGate, configv1.SelfManaged, configv1.FeatureGateRouteExternalCertificate); err != nil { | ||
|
Contributor
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. Assuming Hypershift runs this instance of the API server, how does it specify its own profile?
Member
Author
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. @deads2k suggested always using self-managed here.
Contributor
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. please add a comment explaining
Contributor
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.
Arbitrary choice since this binary doesn't care and teaching the operand about hypershift is not likely to end well. |
||
| return err | ||
| } | ||
|
|
||
|
|
||
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.
I don't understand how these adapters (with empty
RouteValidationOptions{}) relate to the strategy (which initializes itsRouteValidationOptionsobject), so I have to defer to the openshift-apiserver maintainers to verify that the register code and the strategy code are correctly handlingRouteValidationOptions.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.
I checked that all other resources in this file are also getting registered with an empty struct. e.g
I'm also unsure whether they are used somewhere or only meant to check whether all validators are correctly registered through unit tests. I'll wait for apiserver team's suggestion on this.
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.
@stlaz could you check if these changes look good from openshift-apiserver viewpoint?
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.
Used by units in
openshift-apiserver/pkg/api/validation/validation_test.go
Line 1 in 12686d8