A Helm chart for deploying spire-server and spire-agent. > :warning: Please note this chart requires Projected Service Account Tokens which has to be enabled on your k8s api server. > :warning: Minimum Spire version is `v1.0.2`. To enable Projected Service Account Tokens on Docker for Mac/Windows run the following command to SSH into the Docker Desktop K8s VM. ```bash docker run -it --privileged --pid=host debian nsenter -t 1 -m -u -n -i sh ``` Then add the following to `/etc/kubernetes/manifests/kube-apiserver.yaml` ```yaml spec: containers: - command: - kube-apiserver - --api-audiences=api,spire-server - --service-account-issuer=api,spire-agent - --service-account-key-file=/run/config/pki/sa.pub - --service-account-signing-key-file=/run/config/pki/sa.key ```
Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.
.png)
2 occurrences:
💡 Missing property object `livenessProbe` - add a properly configured livenessProbe to catch possible deadlocks
Learn how to fix the issue here
1 occurrences:
💡 Incorrect value for key `namespace` - use an explicit namespace instead of the default one (`default`)
Learn how to fix the issue here
1 occurrences:
💡 Incorrect value for key `kind` - raw pod won't be rescheduled in the event of a node failure
Learn how to fix the issue here
4 occurrences:
💡 Missing property object `requests.memory` - value should be within the accepted boundaries recommended by the organization
Learn how to fix the issue here
2 occurrences:
💡 Missing property object `readinessProbe` - add a properly configured readinessProbe to notify kubelet your Pods are ready for traffic
Learn how to fix the issue here
4 occurrences:
💡 Missing property object `limits.memory` - value should be within the accepted boundaries recommended by the organization
Learn how to fix the issue here
1 occurrences:
💡 Incorrect value for key `image` - specify an image version to avoid unpleasant "version surprises" in the future
Learn how to fix the issue here
3 occurrences:
💡 Missing property object `allow-snippet-annotations` - set it to "false" to override default behaviour
Learn how to fix the issue here
4 occurrences:
💡 Missing property object `requests.cpu` - value should be within the accepted boundaries recommended by the organization
Learn how to fix the issue here
4 occurrences:
💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization
Learn how to fix the issue here
