Our agent is able to communicate directly with the
Kubernetes API Server to get more details about containers and pods. This optional feature can be given to the agents when deploying the
DaemonSet by setting up a
ServiceAccount and limit the access by using a
Additional information is provided by `
Our central platform prepares this additional information and uses it to identify new potential targets. Thus it is possible to attack a dedicated Kubernetes
Deployment or to cause failures in a
deployment rollout status
Check the rollout status of the deployment. The check succeeds when no rollout is pending, i.e., kubectl rollout status exits with status code 0.
rollout restart deployment
execute a rollout restart for a Kubernetes deployment
Verify system unavailability status during Redis latency
Verify that an increased latency in a Redis cache is handled by your application properly by having increased processing time but still being able to maintain the throughput.
Verify system unavailability status during Redis downtime
Check that your application handles a Redis cache downtime gracefully and continues to deliver its intended functionality. The cache downtime may be an unavailable Redis instance or a complete cluster.
Verify system unavailability status when Microsoft SQL Server database can't be reached
An unavailable Microsoft SQL Server database might be too severe for suitable fallbacks and requires your system to indicate unavailability appropriately.