-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.10
-
None
-
Important
-
None
-
Proposed
-
False
-
Description of problem:
openscap pods don't schedule due to nodeSelector w/o fully qualified hostname
Version-Release number of selected component (if applicable):
0.1.53
How reproducible:
once so far
Steps to Reproduce:
1. openscap-pods crashloopbackoff with x509 certificate expired due to scans taking over 1 day 2. `oc delete compliancescan rhcos-moderate-worker`
Actual results:
openscap-pod pods don't schedule `spec.nodeSelector.kubernetes\.io/hostname` is only bare hostname and not FQDN
Expected results:
openscap-pod pods schedule and `spec.nodeSelector.kubernetes\.io/hostname` is full hostname
Additional info:
