c12s-kubespray/roles/kubernetes-apps/policy_controller/calico/defaults/main.yml

---
# Limits for calico apps
calico_policy_controller_cpu_limit: 100m
calico_policy_controller_memory_limit: 256M
calico_policy_controller_cpu_requests: 30m
calico_policy_controller_memory_requests: 64M

# SSL
calico_cert_dir: "/etc/calico/certs"
canal_cert_dir: "/etc/canal/certs"
Adding yamllinter to ci steps (#1556) * Adding yaml linter to ci check * Minor linting fixes from yamllint * Changing CI to install python pkgs from requirements.txt - adding in a secondary requirements.txt for tests - moving yamllint to tests requirements 2017-08-24 09:09:52 +00:00			`---`
Move calico-policy-controller into separate role By default Calico CNI does not create any network access policies or profiles if 'policy' is enabled in CNI config. And without any policies/profiles network access to/from PODs is blocked. K8s related policies are created by calico-policy-controller in such case. So we need to start it as soon as possible, before any real workloads. This patch also fixes kube-api port in calico-policy-controller yaml template. Closes #1132 2017-03-13 15:04:31 +00:00			`# Limits for calico apps`
			`calico_policy_controller_cpu_limit: 100m`
			`calico_policy_controller_memory_limit: 256M`
			`calico_policy_controller_cpu_requests: 30m`
			`calico_policy_controller_memory_requests: 64M`

			`# SSL`
			`calico_cert_dir: "/etc/calico/certs"`
			`canal_cert_dir: "/etc/canal/certs"`