Make a better YAML

[kitarp29]

Make a better YAML

The idea started with this issue: - #52
Why not use all my learnings as a DevOps Engineer to build a better YAML to install Kube-ez.
I will keep this open, to keep building on it.
The File I am referring to is here: - one-to-rule-them-all.yaml

[kitarp29]

Add a Service to the YAML

I will add a Service in the YAML so that if any pod restart happens user won't be needed to port-forward each time.

Problem:

The deployment will restart the pod if it fails or is deleted, but the pod is ephemeral and has a random name, so the port-forward will need to be re-established each time.....Ahhh I bored myself writing this!

Solution:

Make a Service! It sits on top of the pod. And we expose the port of this resource.

A service is a Kubernetes object that exposes a pod or group of pods to the network. When you create a service, you can specify the ports that you want to expose. The service will then create a load balancer that distributes traffic to the pods.

If you port forward a service, the port forwarding will continue to work even if the pods that are backing the service restart. This is because the service will always be pointing to the latest pods that are backing it.

---

Me to Kube-EZ Pods now:

[github-actions]

Stale issue message

[github-actions]

Stale issue message

[github-actions]

Stale issue message

[github-actions]

Stale issue message

[github-actions]

Stale issue message