itielshwartz's comments

On: K8s vs. DeepSeek: When Production Chaos Met AI Promises

[itielshwartz]

TBH it didn't really crash, but enter endless loop with our prompt and instruction , the script itself crashed :)

On: Show HN: The Kubernetes for Humans Podcast

[itielshwartz]

Focus around platform engineering in kubernetes, basically how to do you make kubernetes from a cool technology into something the org can really use!

On: Show HN: Helm-dashboard: the missing UI for Helm

[itielshwartz]

Really looking for feedback/ issues or PRS

On: Show HN: Helm-dashboard: the missing UI for Helm

[itielshwartz]

I think helm has become more popular then everyone thought, the fact is that the CPI is hard to use , and doesn't provide an easy way for most daily commands

[k8s_Hero → itielshwartz]

like when do you absolutely need it and can't settle for version control with GitHub?

[itielshwartz → k8s_Hero]

Oh I meant CLI*

GitHub in general really lacks the viability of what is happening in the cluster right now and how does it really changed, it is a bit more wishful thinking

On: Show HN: Helm-dashboard: the missing UI for Helm

[itielshwartz]

Op here :)

On: Show HN: ValidKube – Validate, Clean and Secure Your K8s YAML

[itielshwartz]

We are looking for more suggestions for cool kubernetes yamls tools to wrap, if anyone know one :)

On: Ask HN: How do you keep track of releases/deployments of dozens micro-services?

[itielshwartz]

Founder of https://Komodor.com here, we track changes and alerts across your complete K8s-based stack, analyzing their ripple effect and then providing devs, DevOps and SRE teams the context they need to troubleshoot efficiently. Independently.

Feel free to ask question or reach out :)

On: Why on earth did we choose Jenkins for 2019?

[itielshwartz]

I wrote the "only reasons" as I see them, feel free to correct me.

Also we use scripted pipeline all the way

[nuclx → itielshwartz]

I guess the reasons depend on the environment, in my case a multi-platform embedded product. E.g. in my case I don't have a use for dynamic node instantiation. Testing partly requires fiddling with hardware and diverse system architectures, so these parts have to be done manually. Delivery bundling isn't fully automatable as well, so there isn't a place for Jenkins in the go-to delivery pipeline I have in mind. It would just complicate things imho. So what's left is SCM-based triggering of builds, unittests, dynamic tests (valgrind, sanitizers) and system tests.

On: Why on earth did we choose Jenkins for 2019?

[itielshwartz]

Mmm actually you are right, did you try https://jenkins.io/doc/book/architecting-for-scale/ ?

On: Why on earth did we choose Jenkins for 2019?

[itielshwartz]

We choose it a few months ago , jenkins is just old...

[craftyguy → itielshwartz]

Ah. In that case, the wording is just really weird.