This taskset collects information on your redis workload in your Kubernetes cluster and raises issues if any health checks fail.
Tasks:
-
Ping `DEPLOYMENT_NAME` Redis Workload
Show More
Common scenarios that might relate to this command or script:
1. Troubleshooting a Kubernetes CrashLoopBackoff event for a specific Redis deployment to see if the server is running properly and responding to commands.
2. Performing routine health checks on Redis deployments within the Kubernetes cluster to ensure that the servers are operational and responsive.
3. Checking the status of the Redis server after a recent deployment or upgrade to ensure that it is functioning as expected within the Kubernetes environment.
4. Verifying the status of the Redis server in response to user-reported issues or errors related to data storage or retrieval.
5. Investigating performance or latency issues within the Kubernetes cluster by inspecting the responsiveness of the Redis servers using the redis-cli PING command.
-
Verify `DEPLOYMENT_NAME` Redis Read Write Operation
Show More
Common scenarios that might relate to this command or script:
1. Troubleshooting application performance issues related to Redis in a Kubernetes environment.
2. Investigating and resolving connectivity issues between a Kubernetes deployment and the Redis database.
3. Monitoring and diagnosing potential data inconsistencies or corruption in the Redis database within a Kubernetes cluster.
4. Analyzing and troubleshooting CrashLoopBackoff events related to the Redis deployment in Kubernetes.
5. Providing support for developers by retrieving specific key values from the Redis database within a Kubernetes environment for debugging purposes.
2 Troubleshooting Commands
Contributed by jon-funk
Codecollection: 
Source Code
Discoverable
Raises Issues