Skip to content
Snippets Groups Projects
Select Git revision
  • main
  • renovate/kubernetes-go
  • renovate/prometheus-json-exporter-0.x
  • renovate/kubernetes-sigs-cluster-api-1.x
  • renovate/redis-22.x
  • renovate/mariadb-22.x
  • renovate/hcloud-exporter-4.x
  • renovate/docker.io-library-nextcloud-31.x
  • renovate/cloudflare-5.x
  • renovate/docker.io-syncthing-syncthing-2.x
  • renovate/siderolabs-kubelet-1.33.x
  • renovate/docker.io-bitnami-kubectl-1.x
  • renovate/kubernetes-kubernetes-1.x
  • renovate/docker.io-library-debian-13.x
  • renovate/go-1.x
  • renovate/rancher-system-upgrade-controller-0.x
  • renovate/quay.io-shivering-isles-koolbox-2025.x
  • renovate/longhorn-1.x
  • renovate/github.com-prometheus-client_golang-1.x
  • renovate/siderolabs-talos-1.10.x
  • v25.08
  • v25.07
  • v25.06
  • v25.05
  • v25.04
  • v25.03
  • v25.02
  • v25.01
  • v24.12
  • v24.11
  • v24.10
  • v24.09
  • v24.08
  • v24.07
  • v24.06
  • v24.05
  • v24.04
  • v24.03
  • v24.02
  • v24.01
40 results

kustomization.yaml

Blame
  • Sheogorath's avatar
    Sheogorath authored
    This patch introduces the general tier-1 to tier-3 priorities to all
    deployed applications, HOWEVER it does not apply these to helm generated
    resources, which can result in wonky behaviour, e.g. that some tier-1
    and tier-2 applications act like tier-3 applications when the
    priorityClassName is not populated through helm. This needs some further
    over time.
    e80dda87
    History
    kustomization.yaml 476 B