31–40 of 62 posts
However looking at the pods and checking their env vars has helped me a bit.
Better templating, example https://github.com/emcfarlane/kubestar which uses starlark for kubernetes config.
What do you use templating for that made you not want to use Helm? Granted it's buggy as hell, but the fact that it automates so much operational process makes it save way more time over templating, in my experience.
What tools I need as a jr dev with no docker experience vs a dev ops admin is going to be vastly different.
As a software engineer who has tried to build a business with their own app as a solo dev using Docker/Helm/Kubernetes to host in DigitalOcean I found all the tooling super complex and time consuming to learn.
Frankly my "job to be done" was to publish an app to a remote server and if it crashed automatically restart. Hiring someone to set this up didn't help much because once they set it up, I needed to run it on my own and it was a lot to pick up in addition to the other 4-5 technologies I wanted to utilize.
I honestly don't care about serverless and I don't want to learn yet another technology, I just wanted to publish my damn app, focus on new features and try to make some money. This was easier with a VM, but you have to share that with another app that might not play nice and take the whole server down. Then the site is down and you won't know or can't restart it until you get off work.
If you can build a tool where I can take an app and push to a server with https enabled, without being an expert in kubernetes or helm or whatever. That'd be awesome.
Prd has high traffic during the day; low traffic at night. Pods must be manually right-sized based on the model and expected traffic. Each model gets its own pod. 20 models = 20 pods = 20 cpu and ram configurations per env.
Stg has low traffic (50 queries per day). Hosting a container per pod is expensive. Stg hosting per pod costs ~20% of the production cost (if prd cost $10k/mo, staging costs $2k/mo to service a 1% the traffic).
I think this can be fixed in the application layer with 2 very different configurations per env, but it would be nice if this was abstracted away from us so we could focus on tuning the models, not configuring proxies and hosting environments.
- 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…
https://docs.podman.io/en/latest/markdown/podman-generate.1....
> kubernetes YAML explainer playground
GPT4 can probably do this just in the way you describe. The other thing that came to mind is yaml-language-server
> Diagram generation from Kubernetes namespace(s)
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!
K9s - https://k9scli.io/ CLI UI for k8s. Saves me a ton of typing while checking k8s pods/logs.
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
- 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…
I have used it to get 80/20 of the work done when converting from docker-compose to k8s.