Project: Polaris (Provisioning / Security & Compliance)
File: reliability.md

meta: name: description content: "Fairwinds Polaris | Make sure your Kubernetes workloads are always available, and are running the correct image." These checks help to make sure your workloads are always available, and are running the correct image. key | default | description -|| `readinessProbeMissing` | `warning` | Fails when a readiness probe is not configured for a pod. `livenessProbeMissing` | `warning` | Fails when a liveness probe is not configured for a pod. `tagNotSpecified` | `danger` | Fails when an image tag is either not specified or `latest`. `pullPolicyNotAlways` | `warning` | Fails when an image pull policy is not `always`. `priorityClassNotSet` | `warning` | Fails when a priorityClassName is not set for a pod. `deploymentMissingReplicas` | `warning` | Fails when there is only one replica for a deployment. `missingPodDisruptionBudget` | `warning` | Fails when PDB is missing. `metadataAndInstanceMismatched` | `warning` | Fails when label `app.kubernetes.io/instance` and `metadata.name` mismatch `topologySpreadConstraint` | `warning` | Fails when there is no topology spread constraint on the pod Readiness and liveness probes can help maintain the health of applications running inside Kubernetes. By default, Kubernetes only knows whether or not a process is running, not if it's healthy. Properly configured readiness and liveness probes will also be able to ensure the health of an application. Readiness probes are designed to ensure that an application has reached a "ready" state. In many cases there is a period of time between when a webserver process starts and when it is ready to receive traffic. A readiness probe can ensure the traffic is not sent to a pod until it is actually ready to receive traffic. Liveness probes are designed to ensure that an application stays in a healthy state. When a liveness probe fails, the pod will be restarted. Docker's `latest` tag is applied by default to images where a tag hasn't been specified. Not specifying a specific version of an image can lead to a wide variety of problems. The underlying image could include unexpected breaking changes that break your application whenever the latest image is pulled. Reusing the same tag for multiple versions of an image can lead to different nodes in the same cluster having different versions of an image, even if the tag is identical. Related to that, relying on cached versions of a Docker image can become a security vulnerability. By default, an image will be pulled if it isn't already cached on the node attempting to run it. This can result in variations in images that are running per node, or potentially provide a way to gain access to an image without having direct access to the ImagePullSecret. With that in mind, it's often better to ensure the a pod has `pullPolicy: Always` specified, so images are always pulled directly from their source. By default, the Kubernetes scheduler uses a bin-packing algorithm to fit as many pods as possible into a cluster. The scheduler prefers a more evenly distributed general node load to app replicas precisely spread across nodes. Therefore, by default, multi-replica is not guaranteed to be spread across multiple availability zones. Kubernetes provides topologySpreadConstraint configuration in order to better ensure pod spread across multiple AZs and/or Hosts. Example of a topologySpreadConstraint spreading across zones: ``` apiVersion: apps/v1 kind: Deployment metadata: name: demo-basic-demo spec: selector: matchLabels: app.kubernetes.io/name: basic-demo app.kubernetes.io/instance: demo template: metadata: labels: app.kubernetes.io/name: basic-demo app.kubernetes.io/instance: demo spec: topologySpreadConstraints: maxSkew: 1 topologyKey: "topology.kubernetes.io/zone" whenUnsatisfiable: ScheduleAnyway ```