Scenario 1: Operands Remain Stable Without restart-date Annotation

Objective: Verify CNO does not spuriously restart operands when no restart-date annotation is present.

Maps to: Regression — ensure no unintended side effects

Cluster: brcox-88531-hc on Azure dev mgmt cluster — HCP namespace: clusters-brcox-88531-hc

Release image: registry.build10.ci.openshift.org/ci-ln-1qhpr62/release:latest (CNO PR #3030 + HyperShift PR #8751)

Overall Scenario 1: PASS

Step	Check	Result	Evidence
1	Verify no `restart-date` annotation on HC or HCP	PASS	No restart-date annotation found on either resource
2	Verify no `restart-date` annotation on CNO operand deployment pod templates	PASS	All 4 deployments at generation 1, no restart-date in pod template annotations
3	Record CNCC and all CNO operand pod names and creation timestamps	PASS	All 4 pods running with 0 restarts since cluster creation
4	Confirm pods remain stable (no rollouts triggered)	PASS	All deployments generation 1 = observedGeneration 1; 0 restarts

Evidence

Step 1 — No restart-date annotation on HC or HCP

$ oc get hostedcluster brcox-88531-hc -n clusters \
    -o jsonpath='{.metadata.annotations}' | jq 'with_entries(select(.key | contains("restart")))'
{}

$ oc get hostedcontrolplane brcox-88531-hc -n clusters-brcox-88531-hc \
    -o jsonpath='{.metadata.annotations}' | jq 'with_entries(select(.key | contains("restart")))'
{}

Step 2 — No restart-date on deployment pod templates

$ oc get deployment -n clusters-brcox-88531-hc \
    cloud-network-config-controller multus-admission-controller \
    network-node-identity ovnkube-control-plane \
    -o jsonpath='{range .items[*]}Deployment: {.metadata.name}
  restart-date annotation: {.spec.template.metadata.annotations.hypershift\.openshift\.io/restart-date}
  generation: {.metadata.generation}
  observedGeneration: {.status.observedGeneration}
{end}'
Deployment: cloud-network-config-controller
  restart-date annotation:
  generation: 1
  observedGeneration: 1
Deployment: multus-admission-controller
  restart-date annotation:
  generation: 1
  observedGeneration: 1
Deployment: network-node-identity
  restart-date annotation:
  generation: 1
  observedGeneration: 1
Deployment: ovnkube-control-plane
  restart-date annotation:
  generation: 1
  observedGeneration: 1

Step 3 — Baseline pod state

$ oc get pods -n clusters-brcox-88531-hc \
    -o custom-columns='NAME:.metadata.name,READY:.status.containerStatuses[0].ready,RESTARTS:.status.containerStatuses[0].restartCount,CREATED:.metadata.creationTimestamp' \
    | grep -E "multus|network-node-identity|ovnkube-control-plane|cloud-network-config"
cloud-network-config-controller-5c7997f74f-7hllb     true    0          2026-06-17T11:13:20Z
multus-admission-controller-6d7b6dfc49-mgxlc         true    0          2026-06-17T11:13:27Z
network-node-identity-b5d5546d8-kdgb7                true    0          2026-06-17T11:13:42Z
ovnkube-control-plane-6c56d86876-ksfc5               true    0          2026-06-17T11:13:36Z

← Dashboard Scenario 2 →