-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Register UnauthenticatedHTTP2DOSMitigation into kube components #121224
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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/test-infra repository. |
/sig architecture previous PR(s) - https://github.com/kubernetes/kubernetes/pulls?q=is%3Apr+UnauthenticatedHTTP2DOSMitigation /approve |
LGTM label has been added. Git tree hash: 5d23436445ccf8947b16056c7b3752c55b2fd82d
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…226-upstream-release-1.25 Automated cherry pick of #121224: Register UnauthenticatedHTTP2DOSMitigation into kube
…224-upstream-release-1.28 Automated cherry pick of #121224: Register UnauthenticatedHTTP2DOSMitigation into kube
…226-upstream-release-1.26 Automated cherry pick of #121224: Register UnauthenticatedHTTP2DOSMitigation into kube
…225-upstream-release-1.27 Automated cherry pick of #121224: Register UnauthenticatedHTTP2DOSMitigation into kube
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224.
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224.
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224.
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224.
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224.
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224. Co-authored-by: Tim Usner <tim.usner@sap.com>
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224. Co-authored-by: Tim Usner <tim.usner@sap.com>
The feature gate was added retrospectively to versions `1.25`, `1.26`, `1.27` and `1.28`, see kubernetes/kubernetes#121224. Co-authored-by: Tim Usner <tim.usner@sap.com>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Ensures the UnauthenticatedHTTP2DOSMitigation gate is register for all kube components, so deployments that manage feature gates homogenously across all components can use it.
Does this PR introduce a user-facing change?
/cc @enj @dims @jeremyrickard