Engineering Reliability for Developers

Reliability as Code

Surface Reliability issues and make your users happy with our powerful, open-core, developer-centric tools.

Get Started

reliably scan kubernetes --format table
Results:
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0007  Setting a high cpu request may render pod scheduling difficult or starve other pods 
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0009  Not setting a cpu requests means the pod will be allowed to consume the entire available CPU (unless the cluster has set a global limit)
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0013  A rollout strategy can reduce the risk of downtime 
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0014  Without the 'minReadySeconds' property set, pods are considered available from the first time the readiness probe is valid. Settings this value indicates how long it the pod should be ready for before being considered available.
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0001  You should specify a number of replicas 
■  manifests/pod.yaml         Kubernetes:Pod                K8S-POD-0001  You should not use the default 'latest' image tag. It causes ambiguity and leads to the cluster not pulling the new image
■  manifests/pod.yaml         Kubernetes:Pod                K8S-POD-0003  Only images from an approved registry can be run 
■  manifests/deployment.yaml  Kubernetes:Deployment         K8S-DPL-0012  Image pull policy should usually not be set to 'Always' 
■  test-manifest.yaml:92:1    Kubernetes:PodSecurityPolicy  K8S-PSP-0001  Enabling privileged can lead to unwanted escalation from the container's process 
■  test-manifest.yaml:92:1    Kubernetes:PodSecurityPolicy  K8S-PSP-0007  To reduce risk of accessing files outside of an allowed paths, it's best to make them read only 
Summary:
  10 suggestions found
  ■ 3 info - ■ 5 warning - ■ 2 error

reliably slo report
                                       Current  Objective  / Time Window     Type             Trend    
  Service #1: http-api                                   
  ✅ 99% availability over 1 hour      100.00%        99%  / 1h0m0s          Availability     ✓ ✓ ✓ ✓  
  ✅ 99.5% availability over 1 day     100.00%      99.5%  / 1d              Availability     ✓ ✓ ✓ ✓  
  ❌ 99% of requests under 300ms        73.91%        99%  / 1d              Latency          ✕ ✕ ✕ ✕  
  ❌ 99.9% of requests under 1s         98.55%      99.9%  / 1d              Latency          ✕ ✕ ✕ ✕  
                                                         
  Service #2: products-api                               
  ✅ 99% availability over 1 day       100.00%        99%  / 1d              Availability     ✓ ✓ ✓ ✓  
  ✅ 99.5% of requests under 200ms     100.00%      99.5%  / 1d              Latency          ✓ ✓ ✓ ✓