Bug 1954892
Summary: | Add necessary priority class to ingress-canary | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ravig <rgudimet> |
Component: | Networking | Assignee: | Stephen Greene <sgreene> |
Networking sub component: | router | QA Contact: | jechen <jechen> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | amcdermo, aos-bugs, hongli, ravi.gouda |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 23:04:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ravig
2021-04-29 02:45:55 UTC
@ravig is there any guidance for which priority class to use for daemonsets? @rgudimet can you help us determine which priority class to use for the canary daemonset? Verified in 4.8.0-0.nightly-2021-06-01-043518 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-06-01-043518 True False 16m Cluster version is 4.8.0-0.nightly-2021-06-01-043518 $ oc -n openshift-ingress-canary get ds -oyaml <-- snip--> spec: containers: - command: - ingress-operator - serve-healthcheck image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bbd856bec22173b7026d2c086a175a3576dca4b8905c48bd2734d7ee6ca7db2f imagePullPolicy: IfNotPresent name: serve-healthcheck-canary ports: - containerPort: 8080 protocol: TCP - containerPort: 8888 protocol: TCP resources: requests: cpu: 10m memory: 20Mi terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError dnsPolicy: ClusterFirst nodeSelector: kubernetes.io/os: linux priorityClassName: system-cluster-critical <-----verified the fix from https://github.com/openshift/cluster-ingress-operator/pull/620 restartPolicy: Always schedulerName: default-scheduler securityContext: {} terminationGracePeriodSeconds: 30 tolerations: - effect: NoSchedule key: node-role.kubernetes.io/infra operator: Exists <--snip--> Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 |