Hacker News new | past | comments | ask | show | jobs | submit login

K8S is not easy.

  It helps standardize:
    - deployments of containers
    - health checks
    - cron jobs
    - load balancing
What is the "old way" of doing things?

Is it same/similar across teams within and outside your organization.

If not, what would it cost to build consensus and shared understanding?

How would you build this consensus outside your organization?

For small organizations, one should do whatever makes them productive.

However, as soon as you need to standardize across teams and projects, you can either build your own standards and tooling or use something like K8S.

  Once you have K8S, the extensibility feature kicks in to address issues such as:
   - Encrypted comms between pods
   - Rotating short lived certificates
I don't love K8S.

However, if not K8S then, what alternative should we consider to build consensus and a shared understanding?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: