Skip to content

Fix incorrect kubectl exec command in Redis ConfigMap tutorial #53091

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Nov 6, 2025
Merged

Fix incorrect kubectl exec command in Redis ConfigMap tutorial #53091

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/docs/tutorials/configuration/configure-redis-using-configmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ redis-config:
Use `kubectl exec` to enter the pod and run the `redis-cli` tool to check the current configuration:

```shell
kubectl exec -it redis -- redis-cli
kubectl exec -it pod/redis -- redis-cli
```

Check `maxmemory`:
Expand Down Expand Up @@ -173,7 +173,7 @@ maxmemory-policy allkeys-lru
Check the Redis Pod again using `redis-cli` via `kubectl exec` to see if the configuration was applied:

```shell
kubectl exec -it redis -- redis-cli
kubectl exec -it pod/redis -- redis-cli
```

Check `maxmemory`:
Expand Down Expand Up @@ -213,7 +213,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes/website/main/conte
Now re-check the configuration values one last time:

```shell
kubectl exec -it redis -- redis-cli
kubectl exec -it pod/redis -- redis-cli
```

Check `maxmemory`:
Expand Down