Closed knelasevero closed 7 months ago
The actual operand doesn't need it as it is static pod and it has Operator:Exists Toleration
@knelasevero: This pull request references WRKLDS-1015 which is a valid jira issue.
/retest
/retest
@knelasevero: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-gcp-operator-single-node | a448c4c6820f42742ef6fc67a293707e739dfe94 | link | false | /test e2e-gcp-operator-single-node |
ci/prow/e2e-aws-operator-disruptive-single-node | a448c4c6820f42742ef6fc67a293707e739dfe94 | link | false | /test e2e-aws-operator-disruptive-single-node |
Full PR test history. Your PR dashboard.
/retest-required
/lgtm
have you forgot to apply the toleration to kube-apiserver
's manifest ?
have you forgot to apply the toleration to
kube-apiserver
's manifest ?
Core static pods already tolerate every taint.
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/:
An empty key with operator Exists matches all keys, values and effects which means this will tolerate everything.
have you forgot to apply the toleration to kube-apiserver's manifest ?
@ingvagabund pointed me to https://github.com/openshift/cluster-kube-apiserver-operator/blob/master/bindata/assets/kube-apiserver/pod.yaml#L268-L269 which means that kas
tolerates all taints.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ingvagabund, knelasevero, p0lyn0mial
The full list of commands accepted by this bot can be found here.
The pull request process is described here
[ART PR BUILD NOTIFIER]
This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.16.0-202404221110.p0.g65eb450.assembly.stream.el9 for distgit ose-cluster-kube-apiserver-operator. All builds following this will include this PR.
Required to be able to advise customers to follow workflow described in https://github.com/openshift/enhancements/pull/1583. If they want to taint control-plane nodes to avoid any other thing to run there (while enforcing it further with validating admission policies), control plane workloads need to tolerate that taint.