Advice in “Configuring Redis using a ConfigMap” not quite correct

[olekszhel]

The configuration values have not changed because the Pod needs to be restarted to grab updated values from associated ConfigMaps.

This is not correct really and leads to confusion. As configmap is mounted as a volume it automatically updates appropriate config file inside pod. But redis application itself is not configured to update config automatically. It really creates wrong imagination about core topic (configmap). That's why I believe redis is not a good example to demonstrate that configmap automatically updates config inside pod and it doesn't required pod recreation.

[Shubham82]

Page to update: https://kubernetes.io/docs/tutorials/configuration/configure-redis-using-configmap/

[sftim]

/retitle Advice in “Configuring Redis using a ConfigMap” not quite correct
/language en

[sftim]

The configuration values have not changed because the Pod needs to be restarted to grab updated values from associated ConfigMaps.

This sentence is true, but we could explain more about the context that makes it true.

[RA489]

/triage accepted

[yashodhanmohan]

Would it help here to add an additional demonstration step that the underlying redis.conf did indeed update but that the Redis configuration didn't change because it needs to restart to pick the new values? I can pick it up @sftim if the change is acceptable. Let me know if there might be a simpler update to this.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale