Live data from Hacker News

Ask HN: What tools would make your Kubernetes development experience better?

news.ycombinator.com

21–30 of 62 posts

Re: Ask HN: What tools would make your Kubernetes development experience better?

#21
post #6

Earlier quoted context omitted.

The firm I work at developed an internal library (open source soon hopefully!) that does all our templating in Python, example: import os """ Imports redacted, but this imports our library """ NAME = "my_app" PORT = 5000 DEPLOY_ENV = os.environ["DEPLOY_ENV"] deploy_all( create_stateful_service( NAME, http_port=PORT, cpu=2000, memory=500 ), create_ingress( NAME, service_name=NAME, service_port=PORT, hostnames=["myapp.…

Nice, I've seen similar setups like this with Go before. Maybe that's the better way to do it, use a proper language instead of yamls for config.

It should be like that from the very beginning, any and all configuration management systems that chose YAML as base instead of DSL (even if DSL is just a subset of Python or Lua) have same problems.

Re: Ask HN: What tools would make your Kubernetes development experience better?

#22
post #6

Better templating, example https://github.com/emcfarlane/kubestar which uses starlark for kubernetes config.

The firm I work at developed an internal library (open source soon hopefully!) that does all our templating in Python, example: import os """ Imports redacted, but this imports our library """ NAME = "my_app" PORT = 5000 DEPLOY_ENV = os.environ["DEPLOY_ENV"] deploy_all( create_stateful_service( NAME, http_port=PORT, cpu=2000, memory=500 ), create_ingress( NAME, service_name=NAME, service_port=PORT, hostnames=["myapp.…

I wrote something similar using Ruby a while back. https://github.com/matsuri-rb/matsuri

I even have a helm plugin that would let you specify all the command line options and values so that it can be tracked in git and consistently applied

There’s also tools for transforms on raw manifests so you can track changes (in code) from upstream manifests

Re: Ask HN: What tools would make your Kubernetes development experience better?

#24
Having a tool that'd make it easy to run the app locally for development and at the same time have roughly the same files used in production. Docker compose got this mostly right, compare compose with the complexity of running locally service in micro Kubernetes cluster.

Re: Ask HN: What tools would make your Kubernetes development experience better?

#25

Having a tool that'd make it easy to run the app locally for development and at the same time have roughly the same files used in production. Docker compose got this mostly right, compare compose with the complexity of running locally service in micro Kubernetes cluster.

tilt.dev

Re: Ask HN: What tools would make your Kubernetes development experience better?

#26
- A tool to create a Kubernetes YAML from a "docker run" command :-)

- A kubernetes YAML explainer playground where you can paste a YAML file in and it explains what the YAML does.

- Diagram generation from Kubernetes namespace(s)

I am interested in devops tooling. The space is incredibly complicated and I find other people's workflows and tooling to be confusing.

I wrote a tool that configures terraform/chef/ansible/packer/shellscript and other tools by graph/diagram files: https://devops-pipeline.com/ It's not ready for usage by other people but the idea is there.

If you could make configuring traefik, istio, service mesh, sidecars, storage easier that would be amazing. I am inclined to run Postgres outside of kubernetes.

Re: Ask HN: What tools would make your Kubernetes development experience better?

#27
post #23

I see that there are often things people ask for, but it turns out, someone had alreadt made it. Maybe an Awesome Kubernetes is what we need

Kubernetes that automatically toasts a bagel and makes a cup of tea during compilation. Sets slack status to away just before a coworker messages me. Swipes tinder matches based on biometric data on my behalf. Sky's the limit!

Re: Ask HN: What tools would make your Kubernetes development experience better?

#29
post #3

I understand that this is contrary to your question, but I might suggest a different approach to your inquiry. Instead of asking people for their dev tool ideas, ask them what problems they have with Kubernetes that aren't yet solved well for them. With that information you can iterate on dev tool ideas that could potentially solve those problems. In my experience people understand their problems better than the pote…

In addition to this, I've found that many people answer the question "what tools would you like?" but if you actually build those tools most people who answered can't be bothered to try them.
Post reply on HN