Edvin N
When https://github.com/aquasecurity/trivy-operator/pull/979 gets merged we should be able to go over to trivy-server from the trivy-operator. Thus we can remove one helm chart from our terraform solution.
This feature is currently in preview but it looks like the way you would think how the original spot instances actually would work... https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/spot-priority-mix When this comes out of preview...
Use the new PDB rule to make sure that a user can't define a PDB minAvliable bigger then an HPA/deployment number.
Recently we started to use x509 helm chart. At the time it didn't have prirotiyClass in it, https://github.com/enix/x509-certificate-exporter/pull/91 The new helm chart containing the change is currently in beta. Waiting...
Implement Cilium in Azure and AWS Tasks - [X] Linkerd verification - [ ] Node-local dns - [X] monitoring - [ ] Documentation - [ ] Disable kube-proxy - [...
This crd make prometheus and grafana agent to fight. This can be seen at: https://github.com/grafana/helm-charts/tree/main/charts/agent-operator/crds
In some cases it might be nice to still have the separation of application in namespaces but still want to use the same tenant in the cloud aka AWS account...
Trying to get controller metrics in to prometheus using the ingress chart. My values file looks like this and I'm using helm chart [ingress-0.12.0](https://github.com/Kong/charts/releases/tag/ingress-0.12.0) ```yaml controller: serviceMonitor: enabled: true podAnnotations:...
When using ArgoCD and the ingress helm chart you will get the following error `RepeatedResourceWarning Resource apiextensions.k8s.io/CustomResourceDefinition//ingressclassparameterses.configuration.konghq.com appeared 2 times among application resources. `  I think this is because...