02f400e442
Allow Calico resources such as NetworkPolicy, GlobalNetworkPolicy,
WorkloadEndpoint, etc to be specified using values.
To avoid the complexities of list management with helm we use a
dictionary that contains a relative priority and set of objects
(called rules).
For example:
network:
policy:
someName:
priority: 0
rules:
- apiVersion: projectcalico.org/v3
... some useful resource object ...
- apiVersion: projectcalico.org/v3
... some other useful resource object ...
someOtherName:
priority: 1
rules:
- apiVersion: projectcalico.org/v3
... rules that come later ...
lastSetOfRules:
priority: 9
rules:
- apiVersion: projectcalico.org/v3
... rules that come last ... maybe hostendpoints ...
By having named groups of rules each with it's own priority you can
update, delete and amend individual sets of rules without provided you
set the appropriate "priority" value.
Change-Id: Id441350bcc8b95a91ef4d1b89d1bc3c417f50b13
|
||
|---|---|---|
| .. | ||
| bin | ||
| bird | ||
| etc | ||
| configmap-bin.yaml | ||
| configmap-bird.yaml | ||
| configmap-etc.yaml | ||
| daemonset-calico-etcd.yaml | ||
| daemonset-calico-node.yaml | ||
| deployment-calico-kube-controllers.yaml | ||
| job-calico-settings.yaml | ||
| job-image-repo-sync.yaml | ||
| secret-etcd-certificates.yaml | ||
| service-calico-etcd.yaml | ||