-
Bug
-
Resolution: Not a Bug
-
Major
-
Logging 5.4.0
-
None
-
False
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
-
-
Logging (LogExp) - Sprint 214
LokiStack components are not restarted on config map changes.
| [kbharti@cube ~]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE loki-operator.v0.0.1 Loki Operator 0.0.1 Succeeded [kbharti@cube ~]$ oc edit cm/loki-config-lokistack-dev configmap/loki-config-lokistack-dev edited [kbharti@cube ~]$ oc get pods NAME READY STATUS RESTARTS AGE ca62d525248e797cf94ed1f067021020d655a54cf961251d1ec0983c39mkfc7 0/1 Completed 0 3h10m loki-compactor-lokistack-dev-0 1/1 Running 0 177m loki-distributor-lokistack-dev-fc5d45c4c-r4wjk 1/1 Running 0 177m loki-index-gateway-lokistack-dev-0 1/1 Running 0 177m loki-ingester-lokistack-dev-0 1/1 Running 0 177m loki-operator-controller-manager-7667bf9c6c-j6ffj 2/2 Running 0 3h10m loki-querier-lokistack-dev-cb499c59b-r9mxj 1/1 Running 0 177m loki-query-frontend-lokistack-dev-767df9d744-bt5tl 1/1 Running 0 177m lokistack-gateway-lokistack-dev-7c9cd565d7-mp6pd 2/2 Running 0 177m quay-io-rhn-support-kbharti-loki-operator-bundle-v0-0-1 1/1 Running 0 3h10m |
Steps to Reproduce:
1) Deploy Loki Operator and Loki stack components.
2) Edit loki-config-lokistack-dev configmap and change values under limits_config for config.yaml.
3) Save the configMap.
Expected Result:
LokiStack Components must restart after configmap change
Actual Result:
Components do not restart.