How we migrated onto K8s in less than 12 months

Re:How we migrated onto K8s in less than 12 months by ttymck on Friday August 09, 2024 @09:10PM (#41206647)

Any cluster extension. Helm is a good example.

https://helm.sh/docs/topics/version_skew/

Istio: https://istio.io/latest/docs/releases/supported-releases/#su...

Literally every kubernetes manifest that hits the server uses a k8s api:

    apiVersion: apps/v1

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by epgui on Friday August 09, 2024 @09:57PM (#41206778)

You mean operators?

(genuine tone, not rhetorical)

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by ttymck on Friday August 09, 2024 @10:47PM (#41206949)

Sure, an operator is likely to use a wide array of APIs.

But, to reiterate, everything uses APIs. The *betavX APIs are of course likely to be deprecated and replaced with stable APIs after a few versions.

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by Too on Saturday August 10, 2024 @01:35AM (#41207559)

Man, you don't need to use service mesh just because you use k8s. Istio is a very advanced component that 99% of users don't need.

So if you are going to compare with a managed solution, compare with something equivalent. Take a bare managed cluster and add a single Deployment to it, it will be no more complex than ECS, while giving you much better developer ergonomics.

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by ttymck on Saturday August 10, 2024 @02:03AM (#41207648)

99% of users don't need kubernetes. Just deploy to heroku, and you'll have a much better developer experience.

[ Parent | on HN ]

Re:How we migrated onto K8s in less than 12 months by 5Qn8mNbc2FNCiVV on Monday August 12, 2024 @11:09AM (#41225342)

My wallet says otherwise

[ Parent | on HN ]