Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release-4.7] bug 1937916: add a flowschema to ensure that probes never get 429s #1083

Closed
wants to merge 1 commit into from
Closed

[release-4.7] bug 1937916: add a flowschema to ensure that probes never get 429s #1083

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
28 changes: 28 additions & 0 deletions manifests/0000_20_kube-apiserver-operator_08_flowschema.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,3 +73,31 @@ spec:
serviceAccount:
name: kube-apiserver-operator
namespace: openshift-kube-apiserver-operator
---
# probes need to always work. If probes get 429s, then the kubelet will treat them as probe failures.
# Since probes are cheap to run, we won't rate limit these at all.
apiVersion: flowcontrol.apiserver.k8s.io/v1beta1
kind: FlowSchema
metadata:
name: probes
spec:
distinguisherMethod:
type: ByUser
matchingPrecedence: 2
priorityLevelConfiguration:
name: exempt
rules:
- nonResourceRules:
- nonResourceURLs:
- '/healthz'
- '/readyz'
- '/livez'
verbs:
- 'get'
subjects:
- group:
name: system:authenticated
kind: Group
- group:
name: system:unauthenticated
kind: Group