Select Git revision
kustomization.yaml
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.
kustomization.yaml 456 B
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: mail
resources:
- ../../base/mail
- certificate.yaml
- mail-values.yaml
components:
- ../../../shared/components/resourcequota-default
- ../../../shared/components/priority-tier-1
configMapGenerator:
- name: mail-grafana-dashboards
files:
- ./dashboards/logs.json
- ./dashboards/aws-ses.json
options:
labels:
grafana_dashboard: mail