Check you have set readiness probes across Kubernetes clusters to ensure reliability with Fairwinds Insights.
Hey, y'all. Adam Zahorscak here, working with Fairwinds Insights to resolve the readiness probe should be configured action item. Here I have a cluster with a workload, and as you can see the readiness probe should be configured action item is firing for this specific workload.
If we click on the action item we'll get extra detail. First seen, last reported, the namespace and so on. Particularly of interest is the description, references to relevant documentation, steps to remediate the problem, and examples of a remediation.
In our case, we're just going to do a simple HTTP check to let the kubelet know when the application is ready to receive traffic. I'll go to my cluster. As you can see, I have a deployment, with three pods running. I'm going to edit the deployment live in the cluster.
We'll go down to the container spec, and we'll find a good section to add our readiness probe. In this example, just do an httpGet. We'll write a path and a port. You can use a numbered port or a named port. Save our changes, make sure that's been deployed, and roll the deployment to ensure this configuration is live in the cluster.
Once all the pods have rolled and some time has passed, Fairwinds Insights reports have been run, we can go back to Insights and see that the readiness probe should be configured action item is no longer present on this workload. That is how you resolve the readiness probe should be configured action item in Fairwinds Insights.
