Sridhar Gaddam d4a0bc4d15 Update Submariner Engine to a DaemonSet ...

Currently, the Submariner Engine is a deployment with nodeSelector
(for submariner.io/gateway=true). It is seen that when the label
is removed from the node after SM engine is deployed, SM engine
continues to run on that node. This behavior is not in Sync with
the DaemonSet (used by GlobalnetController) behavior where the POD
is immediately terminated when the label is removed from the node.
This PR updates SM engine as DaemonSet so that we have consistent
behavior between the SM Engine POD and GlobalnetController POD.

Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>

2020-01-28 19:23:32 +05:30

..

_helpers.tpl

Add globalnet service account creation

2020-01-22 16:50:32 +02:00

crd.yaml

initial commit, adding v0.0.1 helm charts

2019-03-11 17:14:39 -07:00

engine-deploy.yaml

Update Submariner Engine to a DaemonSet

2020-01-28 19:23:32 +05:30

globalnet.yaml

Remove GLOBALCIDR, empty yaml if disabled

2020-01-21 11:49:45 +02:00

NOTES.txt

initial commit, adding v0.0.1 helm charts

2019-03-11 17:14:39 -07:00

rbac.yaml

Added clusters to rbac

2020-01-28 08:27:25 +02:00

route-agent-ds.yaml

k8s 1.16.x support

2019-11-25 15:23:22 +02:00

svc-acct.yaml

Add globalnet service account creation

2020-01-22 16:50:32 +02:00