helm-diff VS kube-score

#!/usr/bin/env bash set -euo pipefail cd "$(dirname "$0")/.." source scripts/common.sh green "Installing Kubectl" install_kubectl green "Installing helm version => ${HELM_VERSION}" install_helm green "Setting up Kong Helm Repo" helm repo add kong https://charts.konghq.com helm repo update green "Installing Helm Diff Plugin" helm plugin install https://github.com/databus23/helm-diff || true green "Setting up AWS Auth" setup_aws_auth green "Set the current namespace" kubectl config set-context --current --namespace=${KONG_NAME}-kong green "Validating VPA Config => ${KONG_NAME}-kong-vpa" kubectl diff -f ${KONG_NAME}/vpa.yaml || true if [[ "${KONG_NAME}" == prd ]]; then green "Validating Ingress => ${KONG_NAME}-kong-ingress" kubectl diff -f ${KONG_NAME}/ingress.yaml || true fi green "Validating Kong => ${KONG_NAME}" helm diff upgrade \ --install \ "${KONG_NAME}" \ kong/kong \ --namespace "${NAMESPACE}" \ -f ${KONG_NAME}/kong.yaml \ --set-file dblessConfig.config=${KONG_NAME}/declarative.yaml \ --version 2.6.3

helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets

helm-diff plugin to see differences about what will be deployed.

There's Helm plugin (https://github.com/databus23/helm-diff) that show diff results for you, for example

    helm diff upgrade   --namespace 

So helm secrets is a helm plugin, not quite native. It requires the helm diff plugin as well.

This is taken from: https://github.com/zegl/kube-score/blob/master/README_PROBES.md and I have read the same opinions elsewhere.

A developer's workflow should anyway deploy to a real, or close-to-production Kubernetes cluster before opening a merge request with the finished change. That means the developer definitely sees upfront if the manifest is super wrong. Tools like kube-score (which is quite opinionated), kubeval or OPA rules can help in addition to keep things consistent and secure. For such a developer workflow, I recommend Skaffold since it mostly just wraps Docker, kubectl and the templating tool you're using (e.g. kustomize/helm).

apps/v1/Deployment semaphore-demo-ruby-kubernetes 💥 [CRITICAL] Container Resources · semaphore-demo-ruby-kubernetes -> CPU limit is not set Resource limits are recommended to avoid resource DDOS. Set resources.limits.cpu · semaphore-demo-ruby-kubernetes -> Memory limit is not set Resource limits are recommended to avoid resource DDOS. Set resources.limits.memory · semaphore-demo-ruby-kubernetes -> CPU request is not set Resource requests are recommended to make sure that the application can start and run without crashing. Set resources.requests.cpu · semaphore-demo-ruby-kubernetes -> Memory request is not set Resource requests are recommended to make sure that the application can start and run without crashing. Set resources.requests.memory [CRITICAL] Container Image Pull Policy · semaphore-demo-ruby-kubernetes -> ImagePullPolicy is not set to Always It's recommended to always set the ImagePullPolicy to Always, to make sure that the imagePullSecrets are always correct, and to always get the image you want. [CRITICAL] Pod NetworkPolicy · The pod does not have a matching NetworkPolicy Create a NetworkPolicy that targets this pod to control who/what can communicate with this pod. Note, this feature needs to be supported by the CNI implementation used in the Kubernetes cluster to have an effect. [CRITICAL] Pod Probes · Container is missing a readinessProbe A readinessProbe should be used to indicate when the service is ready to receive traffic. Without it, the Pod is risking to receive traffic before it has booted. It's also used during rollouts, and can prevent downtime if a new version of the application is failing. More information: https://github.com/zegl/kube-score/blob/master/README_PROBES.md [CRITICAL] Container Security Context · semaphore-demo-ruby-kubernetes -> Container has no configured security context Set securityContext to run the container in a more secure context. v1/Service semaphore-demo-ruby-kubernetes-lb ✅

Link : https://github.com/zegl/kube-score