K8s deployer

[rgrandl]

In this PR we are adding a kubernetes deployer, that enables Service Weaver applications to run on standard Kubernetes environments (e.g., GKE, AWS, on-prem).

deploy_collatz_k8s.webm Run app.webm

How it works:

• build a docker image that contains the weaver k8s command, and the app binary
• push the image to docker hub (you just need to set an env variable with your docker hub id)
• for each replica set
  • build a container and associate it with a deployment
  • build a service for each public listener (a load balancer)
• once the pods are started, a babysitter service is running
• the babysitter will manage the components hosted by the pod
• to interact with the application, you should access the external listeners services
• added a new section [k8s] in the app config that contains the listeners for the application

[rgrandl]

Looks great, Robert. Very simple and clean.

Thanks

[mwhittaker]

I talked with Robert offline about this a bit, but what do you both think about renaming everything to weaver-kube and weaver kube instead of weaver-k8s and weaver k8s? I find kube a bit easier to say and type. I know k8s is pretty ubiquitous though, so happy either way.

[spetrovic77]

weaver kube sounds great to me!

On Wed, Jun 7, 2023 at 9:08 AM Michael Whittaker @.***> wrote:

I talked with Robert offline about this a bit, but what do you both think about renaming everything to weaver-kube and weaver kube instead of weaver-k8s and weaver k8s? I find kube a bit easier to say and type. I know k8s is pretty ubiquitous though, so happy either way.

— Reply to this email directly, view it on GitHub https://github.com/ServiceWeaver/weaver-k8s/pull/1#issuecomment-1581132251, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJSQ6SCSSIQSRXH6DZ2GC3XKCRO3ANCNFSM6AAAAAAYYU7TYE . You are receiving this because your review was requested.Message ID: @.***>