Springing into Kubernetes

[@simonboland]

Can you share a link to a repository for this?

[@hayrullahyasar]

Thank you for sharing. I could not run the ingress on port 80 so instead I am able to run with the command "skaffold dev --port-forward" than one of the localhost port is opening to open on browser. (port 4503) Looking for more examples about the topic.

[@hayrullahyasar]

After executing the command ingress got working, web page became reachable on localhost port 80 , kubectl create ingress project-localhost --class=nginx --rule="localhost/*=project_name:80"

[@ChristopherWarmbold]

would you say you should use config maps instead of config server?

[@habuma]

I would not say that. I would say that ConfigMaps and Secrets are more "Kubernetes native" and are a more natural way to work with configuration if you're deploying to Kubernetes. But you can certainly choose to use Config Server in a Kubernetes world. Just know that Config Server comes with certain things you'll need to do to ensure production-readiness (security comes to mind) where as Secrets (and I suppose ConfigMaps) can be secured with built-in K8s mechanisms. Of course, Spring Cloud Services for Tanzu Application Service (TAS) handles those production-ready things for you, so if you're deploying to TAS, then Config Server is great (and ConfigMaps/Secrets aren't even an option). But I'm not going to tell you that you should use ConfigMaps/Secrets instead of Config Server. You'll have to make that decision for yourself. I'll just say that ConfigMaps/Secrets are a natural choice when deploying to K8s and Config Server is a great choice when not.

[@ChristopherWarmbold]

@@habuma i feel honored getting an answer from such a legend! 🤩

[@skootdiggity1301]

8:50