mats
64abb69c26
build / build-push (push) Successful in 34s
The ingress still sent the UI and admin API to the resolver after the console split. Route both paths through the console so OIDC callbacks and Kubernetes edits reach their owner, while keeping DoH on the resolver. Include the console resources in Kustomize so GitOps deploys its configuration, permissions, workload and Service alongside the resolver.
29 lines
671 B
YAML
29 lines
671 B
YAML
# kustomize build deploy/k8s | kubectl apply -f -
|
|
#
|
|
# The files are numbered so a plain `kubectl apply -f deploy/k8s/` in
|
|
# alphabetical order also lands in a working order: namespace and config
|
|
# first, then identity, then the workload, then the networking.
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
namespace: dns
|
|
|
|
resources:
|
|
- 00-config.yaml
|
|
- 05-serviceaccount.yaml
|
|
- crds/crds.yaml
|
|
- crds/rbac.yaml
|
|
- 10-deployment.yaml
|
|
- 20-service.yaml
|
|
- console/console.yaml
|
|
- 30-ingress.yaml
|
|
|
|
labels:
|
|
- includeSelectors: false
|
|
pairs:
|
|
app.kubernetes.io/part-of: fancy-dns
|
|
|
|
images:
|
|
- name: fancydns/fancy-dns
|
|
newTag: latest
|