Skip to content

Commit 3f3b7a6

Browse files
committed
BZ-2061452: Removing removed annotation in favor of using priority class
1 parent db9b1b8 commit 3f3b7a6

File tree

2 files changed

+4
-9
lines changed

2 files changed

+4
-9
lines changed

modules/psap-special-resource-operator-using-configmaps.adoc

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -141,14 +141,10 @@ spec:
141141
app: {{.Values.specialresource.metadata.name}}-{{.Values.groupName.driverContainer}}
142142
template:
143143
metadata:
144-
# Mark this pod as a critical add-on; when enabled, the critical add-on scheduler
145-
# reserves resources for critical add-on pods so that they can be rescheduled after
146-
# a failure. This annotation works in tandem with the toleration below.
147-
annotations:
148-
scheduler.alpha.kubernetes.io/critical-pod: ""
149144
labels:
150145
app: {{.Values.specialresource.metadata.name}}-{{.Values.groupName.driverContainer}}
151146
spec:
147+
priorityClassName: system-node-critical
152148
serviceAccount: {{.Values.specialresource.metadata.name}}-{{.Values.groupName.driverContainer}}
153149
serviceAccountName: {{.Values.specialresource.metadata.name}}-{{.Values.groupName.driverContainer}}
154150
containers:
@@ -280,7 +276,7 @@ To remove the simple-kmod kernel module from the node, delete the simple-kmod `S
280276

281277
.Verification
282278

283-
The `simple-kmod` resources are deployed in the `simple-kmod` namespace as specified in the object manifest. After a short time, the build pod for the `simple-kmod` driver container starts running. The build completes after a few minutes, and then the driver container pods start running.
279+
The `simple-kmod` resources are deployed in the `simple-kmod` namespace as specified in the object manifest. After a short time, the build pod for the `simple-kmod` driver container starts running. The build completes after a few minutes, and then the driver container pods start running.
284280

285281
. Use `oc get pods` command to display the status of the build pods:
286282
+
@@ -322,4 +318,4 @@ simple_kmod 16384 0
322318
[TIP]
323319
====
324320
The `sro_kind_completed_info` SRO Prometheus metric provides information about the status of the different objects being deployed, which can be useful to troubleshoot SRO CR installations. The SRO also provides other types of metrics that you can use to watch the health of your environment.
325-
====
321+
====

modules/psap-special-resource-operator-using-crd.adoc

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -175,11 +175,10 @@ spec:
175175
app: {{ printf "%s-%s" .Values.specialResourceModule.metadata.name .Values.kernelFullVersion | replace "." "-" | replace "_" "-" | trunc 63 }}
176176
template:
177177
metadata:
178-
annotations:
179-
scheduler.alpha.kubernetes.io/critical-pod: ""
180178
labels:
181179
app: {{ printf "%s-%s" .Values.specialResourceModule.metadata.name .Values.kernelFullVersion | replace "." "-" | replace "_" "-" | trunc 63 }}
182180
spec:
181+
priorityClassName: system-node-critical
183182
serviceAccount: {{.Values.specialResourceModule.metadata.name}}
184183
serviceAccountName: {{.Values.specialResourceModule.metadata.name}}
185184
containers:

0 commit comments

Comments
 (0)