I thought Docker was supposed to make life easier.... Instead, it's giving me imposter syndrome all over again because I can't seem to wrap my fucking mind around it.

There are some great interactive docker and kubernetes tutorials on https://www.katacoda.com/learn for free. Within 30 minutes you're up to speed. 🙂

@heyheni will give this a look. I'm sure the complexity of our code base and our dev environments are contributors to the frustration.

@88elabb

This 2 hour video on docker is really good.

https://youtube.com/watch/...

Warning : Some of the information on the video is out of date.

Docker is easy. Integrating stateful applications with docker is hard. That's why k8s has stateful sets.

Don't look into k8s.

Yet.

@SortOfTested

Do you find any way for the local IP to be allocated for the service in minikube? I am just testing k8s on my local machine.

Every blog say it is not possible but something tell me that it possible. How would having minikube make sense if it cannot allocate a local IP to test with?

It's random on cluster start. Using hyperkit you can kind of pin it via uuid.

https://github.com/kubernetes/...

The problem they note is there isn't a consistent configuration support among the drivers they support for networking.

@SortOfTested

My mistake I mean the LoadBalancer is not giving IP to test it locally. (https://kubernetes.io/docs/...)

In docker there is IP assign to the each container. LoadBalancer cannot give IP to connect to the service in k8s.

📌 So i can look into thoses resources when I'm on my computer.

@mr-user
If you want to use minikube that way, you'll need to lean into the tunnel approach:
https://minikube.sigs.k8s.io/docs/...

If you want the service IP, use nodeport.

Or look into something like k3s
https://rancher.com/docs/k3s/...

Took me a while to get my head around AIX workloads too :) after that docker was easy.

It's alright, just don't give up halfway there