3 ms·

You can use k8s on $2/mo digital ocean projects. It probably even works on the free tier of a lot of providers. And there's zero setup. Just a deployment yaml

by echelon 6mo ago

You can use k8s on $2/mo digital ocean projects. It probably even works on the free tier of a lot of providers. And there's zero setup. Just a deployment yaml that specifies exactly what you want deployed, which has the benefit of easy version control. I don't get why people are so bent on hating Kubernetes. The mental cost to deploy a 6-line deployment yaml is less than futzing around with FTP and nginx. Kube is the new LAMP stack. It's easier too. And portable. If you're talking managed kube vs one you're taking the responsibility of self-managing, sure. But that's no different than self-managing your stack in the old world. Suddenly you have to become Sysadmin/SRE.

throwawaypath 6mo ago
>And portable. This made me audibly guffaw. Kubernetes is a lot of things, but "portable" is not one of them. GKE, EKS, AKS, OCP, etc., portability between them is nowhere near guaranteed.
- cortesoft 6mo ago
  It is if you stick to standard Kubernetes resources, and it has gotten even easier with better storage class and load balancer support. All of the cloud providers now give you default storage classes and ingresses when you provision a cluster on them, so you can use the exact same deployment on any of them an automatically get those things provisioned in the right way out of the box.
  - throwawaypath 6mo ago
    >It is if you stick to standard Kubernetes resources "If you stick to standard C..." No one does, that's the issue. Helm charts that only support certain cloud providers, operators and annotations that end up being platform specific, etc. >now give you default storage classes and ingresses Ingress is being deprecated, it's Gateway now! Welcome to hell, er, Kubernetes.
    - cortesoft 6mo ago
      I use Kubernetes every day, and have worked with dozens of helm charts, and have yet to encounter cloud specific helm charts. Are these internal helm charts for your company? Obviously you can lock yourself in if you choose, but I have yet to see third party tools that assume a specific provider (unless you are using tools created BY that provider). At my previous spot, we were running dozens of clusters, with some on prem and some in the cloud. It was easy to move workloads between the two, the only issue was ACLs, but that was our own choice. I know they are pushing the new gateway api, but ingresses still work just fine.
      - throwawaypath 6mo ago
        Tell me you haven't managed Kubernetes at scale without telling me you haven't managed Kubernetes at scale. Helm charts may not support a cloud platform like Rancher, Azure, etc. or may have platform specific issues. First one I checked: https://docs.jfrog.com/installation/docs/helm-chart-requirements_general-system-requirements https://docs.jfrog.com/installation/docs/helm-chart-requirem... "When deploying a JFrog application on an AWS EKS cluster, the AWS EBS CSI Driver is required for dynamic volume provisioning. However, this driver is not included in the JFrog Helm Charts." "JFrog validates compatibility with core Kubernetes distributions. Some Kubernetes vendors apply additional logic or hardening (for example, Rancher), so JFrog Platform deployment on those vendor-specific distributions might not be fully supported."
    - vbezhenar 6mo ago
      > Ingress is being deprecated Do you have any links about Ingress being deprecated? Official docs here: https://kubernetes.io/docs/reference/kubernetes-api/service-resources/ingress-v1/ https://kubernetes.io/docs/reference/kubernetes-api/service-... There are no mentions about this API being deprecated.
      - 0x457 6mo ago
        Ingress resource is bassicaly "implementation specific" and isn't portable. It's not deprecated now, but there plans to retire ingress-nginx: https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/ https://kubernetes.io/blog/2025/11/11/ingress-nginx-retireme... Anyway, Ingress resource been in "Migrate to Gateway" state for awhile.
  - SOLAR_FIELDS 6mo ago
    I'm a Kubernetes user and advocate but to call it "portable" just tells me you've never actually tried to deploy the similar thing on multiple different clouds. Even the standardized kubernetes resources behave differently due to various cloud idiosyncracies. You can of course make the situation easier, but to call it entirely portable is probably a misnomer.
subhobroto 6mo ago
> Suddenly you have to become Sysadmin/SRE I don't you made that argument but could a valid conclusion of your comment be that, because Kubernetes is so ubiquitous, using it frees you from being a Sysadmin/SRE?
- 0x457 6mo ago
  Frees you from being a sysadmin, but burndens you with being a k8s operator, still an SRE.
gzread 6mo ago
> And there's zero setup. Just a deployment yaml that specifies exactly what you want deployed Writing this yaml is hours and hours of setup if you can't ctrl+c/v from your last project
- turtlebits 6mo ago
  AI is especially good at writing IaC. Most small projects I let it write a Dockerfile too.

by echelon 6mo ago

throwawaypath 6mo ago

>And portable. This made me audibly guffaw. Kubernetes is a lot of things, but "portable" is not one of them. GKE, EKS, AKS, OCP, etc., portability between them is nowhere near guaranteed.

cortesoft 6mo ago
It is if you stick to standard Kubernetes resources, and it has gotten even easier with better storage class and load balancer support. All of the cloud providers now give you default storage classes and ingresses when you provision a cluster on them, so you can use the exact same deployment on any of them an automatically get those things provisioned in the right way out of the box.
- throwawaypath 6mo ago
  >It is if you stick to standard Kubernetes resources "If you stick to standard C..." No one does, that's the issue. Helm charts that only support certain cloud providers, operators and annotations that end up being platform specific, etc. >now give you default storage classes and ingresses Ingress is being deprecated, it's Gateway now! Welcome to hell, er, Kubernetes.
  - cortesoft 6mo ago
    I use Kubernetes every day, and have worked with dozens of helm charts, and have yet to encounter cloud specific helm charts. Are these internal helm charts for your company? Obviously you can lock yourself in if you choose, but I have yet to see third party tools that assume a specific provider (unless you are using tools created BY that provider). At my previous spot, we were running dozens of clusters, with some on prem and some in the cloud. It was easy to move workloads between the two, the only issue was ACLs, but that was our own choice. I know they are pushing the new gateway api, but ingresses still work just fine.
    - throwawaypath 6mo ago
      Tell me you haven't managed Kubernetes at scale without telling me you haven't managed Kubernetes at scale. Helm charts may not support a cloud platform like Rancher, Azure, etc. or may have platform specific issues. First one I checked: https://docs.jfrog.com/installation/docs/helm-chart-requirements_general-system-requirements https://docs.jfrog.com/installation/docs/helm-chart-requirem... "When deploying a JFrog application on an AWS EKS cluster, the AWS EBS CSI Driver is required for dynamic volume provisioning. However, this driver is not included in the JFrog Helm Charts." "JFrog validates compatibility with core Kubernetes distributions. Some Kubernetes vendors apply additional logic or hardening (for example, Rancher), so JFrog Platform deployment on those vendor-specific distributions might not be fully supported."
  - vbezhenar 6mo ago
    > Ingress is being deprecated Do you have any links about Ingress being deprecated? Official docs here: https://kubernetes.io/docs/reference/kubernetes-api/service-resources/ingress-v1/ https://kubernetes.io/docs/reference/kubernetes-api/service-... There are no mentions about this API being deprecated.
    - 0x457 6mo ago
      Ingress resource is bassicaly "implementation specific" and isn't portable. It's not deprecated now, but there plans to retire ingress-nginx: https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/ https://kubernetes.io/blog/2025/11/11/ingress-nginx-retireme... Anyway, Ingress resource been in "Migrate to Gateway" state for awhile.
- SOLAR_FIELDS 6mo ago
  I'm a Kubernetes user and advocate but to call it "portable" just tells me you've never actually tried to deploy the similar thing on multiple different clouds. Even the standardized kubernetes resources behave differently due to various cloud idiosyncracies. You can of course make the situation easier, but to call it entirely portable is probably a misnomer.

subhobroto 6mo ago

> Suddenly you have to become Sysadmin/SRE I don't you made that argument but could a valid conclusion of your comment be that, because Kubernetes is so ubiquitous, using it frees you from being a Sysadmin/SRE?

0x457 6mo ago
Frees you from being a sysadmin, but burndens you with being a k8s operator, still an SRE.

gzread 6mo ago

> And there's zero setup. Just a deployment yaml that specifies exactly what you want deployed Writing this yaml is hours and hours of setup if you can't ctrl+c/v from your last project

turtlebits 6mo ago
AI is especially good at writing IaC. Most small projects I let it write a Dockerfile too.