4 ms·

Are you assuming the workloads have to use K8s APIs? Where is this coming from? If that’s not the case can you actually explain with a concrete example?

• ttymck 2y ago
  Any cluster extension. Helm is a good example. https://helm.sh/docs/topics/version_skew/ https://helm.sh/docs/topics/version_skew/ Istio: https://istio.io/latest/docs/releases/supported-releases/#support-status-of-istio-releases https://istio.io/latest/docs/releases/supported-releases/#su... Literally every kubernetes manifest that hits the server uses a k8s api: apiVersion: apps/v1
  • epgui 2y ago
    You mean operators? (genuine tone, not rhetorical)
    • ttymck 2y ago
      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.
  • Too 2y ago
    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.
    • ttymck 2y ago
      99% of users don't need kubernetes. Just deploy to heroku, and you'll have a much better developer experience.
      • 5Qn8mNbc2FNCiVV 2y ago
        My wallet says otherwise