You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Korrel8r instance is created with default configuration from the Operator v0.5.10 against OpenShift 4.15 the Korrel8r pods get into CrashLoopBackOff state. When we do oc get korrel8rs.korrel8r.openshift.io -n korrel8r korrel8r -o yaml to check the status then it states the status as True and type as Available. Ideally, it should show the correct status in the case of pods being in CrashLoopBackOff state it can state something like This instance of Korrel8r is invalid
oc get pods -n korrel8r
NAME READY STATUS RESTARTS AGE
3438e8acc38f112533a0bfe423e3bdcda7e582350881fbda5870f9cdfefvjkp 0/1 Completed 0 5h37m
korrel8r-77c85c64f6-lh4zb 0/1 CrashLoopBackOff 70 (2m13s ago) 5h35m
korrel8r-controller-manager-57db65fdbf-p6drh 2/2 Running 0 5h37m
quay-io-korrel8r-operator-bundle-0-5-10 1/1 Running 0 5h38m
When the Korrel8r instance is created with default configuration from the Operator
v0.5.10
against OpenShift 4.15 the Korrel8r pods get intoCrashLoopBackOff
state. When we dooc get korrel8rs.korrel8r.openshift.io -n korrel8r korrel8r -o yaml
to check the status then it states the status as True and type as Available. Ideally, it should show the correct status in the case of pods being inCrashLoopBackOff
state it can state something likeThis instance of Korrel8r is invalid
The text was updated successfully, but these errors were encountered: