Great video, we should chat about once you have this data in or out of the Kubernetes cluster, how do we protect it and provide mobility for that data. Operators generally have backup built in but if you have several operators and several databases then it becomes challenging to manage. We have an answer to that and a simple way to orchestrate backup, recovery and mobility of those stateful workloads.
Great episode! Thank you for having our Maksim, and sharing this helpful information regarding the authentication in Kubernetes and K8s community involvement!
Thank you to Maksim and the larger team at Palark (and Flant) for always sharing knowledge with the community, contributing back, and making cloud native a better place. The community is truly lucky to have you.
You can find all the links here: kube.fm/docker-compose-migration-vasily-ronald The original article is available here: medium.com/@loovatech/application-migration-from-docker-compose-to-kubernetes-how-why-and-what-problems-b2d1c695c42b
Need your advise how we can upgrade all deprecated charts and what would be best way to upgrade and stabilise environment. We have our apps running on AWS eke cluster and our terraform and helm is also quite old versions also we have eke cluster not upgraded it’s still in 1.19. All charts are applied using terraform
What kubernetes version you are aiming for ? I believe you would want to go to 1.25. If yes then you should check for all deprecated api version’s running by running kubent tool which will give all deprecated apis being used. Update the api version then after upgrading the cluster
It's done! Find us on: Apple Podcast: kube.fm/apple Spotify: kube.fm/spotify and a few others. You can find them listed here: kube.fm/planternetes-grace-nguyen
