-
Bug
-
Resolution: Done
-
Blocker
-
Logging 5.5.0
Logging 5.5 create PriorityClass/cluster-logging different from the old. It create PriorityClass during operator deployment. if we create clusterlogging/instance with an invalid log type, the CLO will delete PriorityClass/cluster-logging and never create it again. Without PriorityClass/cluster-logging, the ds/colllector can not be deployed.
$oc get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE collector 0 0 0 0 0 kubernetes.io/os=linux 100m
- links to
- mentioned on
(3 mentioned on)