-
Notifications
You must be signed in to change notification settings - Fork 567
Add IngressControllerConfig API for cluster-level ingress management #2485
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?
Add IngressControllerConfig API for cluster-level ingress management #2485
Conversation
Hello @danielmellado! Some important instructions when contributing to openshift/api: |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cc @joseorpa |
8a27613
to
8d3af3a
Compare
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.
New APIs should be gated and introduced as v1alpha1 in the first instance, can you please add a feature gate, and move this initially to v1alpha1
8d3af3a
to
329d2a6
Compare
@JoelSpeed would I need to create an enhancement to use a new FeatureGate or would it be ok to use legacyFeatureGateWithoutEnhancement? I assume it won't after 4.18 but would like an ack here. Thanks xD |
@joseorpa would you be the contact person for this? |
Yes, I will be the owner |
An enhancement would be expected as well yes |
Currently, OpenShift cluster administrators lack a unified way to configure operational settings for ingress controllers across the cluster. This introduces a new config/v1/IngressControllerConfig CRD that provides cluster-wide configuration for resource management, node scheduling, operational controls, and performance tuning. Signed-off-by: Daniel Mellado <[email protected]>
329d2a6
to
d5cc1da
Compare
/assign |
@danielmellado: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
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.
Leaving an initial high-level question
Feel free to ignore if the enhancement will answer it and let me know when the enhancement is ready for a read (the context helps in API reviews).
// +kubebuilder:resource:path=ingresscontrollerconfigs,scope=Cluster | ||
// +kubebuilder:subresource:status | ||
// +kubebuilder:metadata:annotations="description=Ingress Controller configuration API" | ||
type IngressControllerConfig struct { |
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.
Who/what is going to create this resource?
Currently, OpenShift cluster administrators lack a unified way to
configure operational settings for ingress controllers across the
cluster. This introduces a new config/v1/IngressControllerConfig CRD
that provides cluster-wide configuration for resource management,
node scheduling, operational controls, and performance tuning.
Signed-off-by: Daniel Mellado [email protected]