Run weave node agent in a daemonset and use it to configure the pod network

[mikedanese]

It should use kubelet cni plugin and be deployed as an addon in phase3.

[colemickens]

Is this being pushed instead of using native cloudprovider? Permanently? Temporarily? Is it because of Terraform not being able to cleanup routes/routetables/lbs?

I'm personally interested in having a native cloudprovider option. (Cleanup for Azure is a lot easier because each cluster gets a resource group that can be trivially deleted without needing to necessarily teach Terraform about cloudprovider-created resources.)

[mikedanese]

This will be a proof of concept that we can run the pod network as an addon. It proves that we can deploy kubernetes-anywhere in environments that don't by default support the routing that the pod network requires without sacrificing simplicity.

[aaronlevy]

Is this (theoretically) possible today, or is there more work that needs to happen? I'm not super familiar with the kubelet/CNI coordination points.

[mikedanese]

@aaronlevy I think this should work after kubernetes/kubernetes#28178 is merged but I need to do some testing.

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[errordeveloper]

/close