Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

Commit

Permalink
WIP: add CAPI controller manifest
Browse files Browse the repository at this point in the history
Doesn't work yet because the code is parsing and re-emitting a single object.
  • Loading branch information
bboreham committed May 7, 2020
1 parent 2b969ef commit 4a08ebf
Showing 1 changed file with 40 additions and 0 deletions.
40 changes: 40 additions & 0 deletions pkg/apis/wksprovider/controller/manifests/yaml/04_controller.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,43 @@ spec:
requests:
cpu: 100m
memory: 20Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: capi-controller
namespace: system
labels:
name: capi-controller
spec:
replicas: 1
selector:
matchLabels:
name: capi-controller
template:
metadata:
labels:
name: capi-controller
spec:
tolerations:
# Allow scheduling on master nodes. This is required because during
# bootstrapping of the cluster, we may initially have just one master,
# and would then need to deploy this controller there to set the entire
# cluster up.
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
# Mark this as a critical addon:
- key: CriticalAddonsOnly
operator: Exists
# Allow running on nodes with low disk space: useful for demos
- effect: NoExecute
key: node.kubernetes.io/disk-pressure:NoSchedule
operator: Exists
containers:
- name: controller
image: us.gcr.io/k8s-artifacts-prod/cluster-api/cluster-api-controller:v0.3.5
resources:
requests:
cpu: 100m
memory: 20Mi

0 comments on commit 4a08ebf

Please sign in to comment.