Dustin C. Hatch
bed5ed5767
The *dch-webhooks* server now has a _POST /host/online_ hook that can be triggered by a new machine when it first comes online. This hook starts an automatic provisioning process by creating a Kubernetes Job to run Ansible and publishing information about the host to provision via AMQP. Thus, the server now needs access to the Kubernetes API in order to create the Job and access to RabbitMQ in order to publish the task parameters.
40 lines
663 B
YAML
40 lines
663 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
labels:
|
|
- pairs:
|
|
app.kubernetes.io/instance: dch-webhooks
|
|
includeSelectors: true
|
|
includeTemplates: true
|
|
- pairs:
|
|
app.kubernetes.io/part-of: dch-webhooks
|
|
|
|
resources:
|
|
- ../dch-root-ca
|
|
- dch-webhooks.yaml
|
|
- certificate.yaml
|
|
- ingress.yaml
|
|
|
|
configMapGenerator:
|
|
- name: dch-webhooks
|
|
envs:
|
|
- dch-webhooks.env
|
|
- name: host-provisioner
|
|
files:
|
|
- ansible-job.yaml
|
|
options:
|
|
disableNameSuffixHash: true
|
|
|
|
secretGenerator:
|
|
- name: firefly-token
|
|
files:
|
|
- firefly.token
|
|
|
|
- name: paperless-token
|
|
files:
|
|
- paperless.token
|
|
|
|
- name: step-ca-password
|
|
files:
|
|
- provisioner.password
|