Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 62 posts

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

#51

Post by Reitet00 »

jaguar75 wrote: post #47
Reitet00 wrote: post #38

Earlier quoted context omitted.

Looks okay but I was looking for something that wouldn't require learning yet another config language and would rather take k8s yamls that I already have (or require minimal modifications).

Check out https://www.signadot.com/ . Full disclosure, I'm the founder, but it could help with what you’re looking for.

> Define Sandboxes using a simple YAML file, specifying customizations relative to the baseline environment. Maintain these YAML files in your git repository and standardize Sandboxes across your organization.

It looks like these yaml files are not k8s files that I already have?

Also, is it open source? (I couldn't find a link to source on mobile)

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

#52

Post by Reitet00 »

omniglottal wrote: post #48
Reitet00 wrote: post #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.

Minikube

Minikube is just one piece but it's not functionally equivalent to `docker compose run` since I'd still have to build and push docker images and edit k8s yamls manually (compose run will build containers and start them, no need to edit anything) .

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

#53

Post by edwardmcfarlane »

coxley wrote: post #43

YAML hell. It's very difficult to have standard, company (or org) wide "templates" for creating resources. And I don't mean literal templates. In my ideal world, everything would be defined within Starlark. And we could build our own abstractions. Do we want every resource to be associated with a team or cost-center label? Cool - this is now a required argument for the make_service() function. Even with Kustomize, th…

Maybe try https://github.com/emcfarlane/kubestar ?

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

#54

Post by jaguar75 »

Reitet00 wrote: post #51
jaguar75 wrote: post #47

Earlier quoted context omitted.

Check out https://www.signadot.com/ . Full disclosure, I'm the founder, but it could help with what you’re looking for.

> Define Sandboxes using a simple YAML file, specifying customizations relative to the baseline environment. Maintain these YAML files in your git repository and standardize Sandboxes across your organization. It looks like these yaml files are not k8s files that I already have? Also, is it open source? (I couldn't find a link to source on mobile)

Yes, these are our (thin) YAML files via which you describe the Sandboxes in terms of deltas from the baseline env. The K8s yaml files remain as the source of truth for your standard deployments. The operator is not open source. Some components like the CLI and Resource plugins are. We do have a free tier, however.

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

#55

Post by Reitet00 »

jaguar75 wrote: post #54
Reitet00 wrote: post #51

Earlier quoted context omitted.

> Define Sandboxes using a simple YAML file, specifying customizations relative to the baseline environment. Maintain these YAML files in your git repository and standardize Sandboxes across your organization. It looks like these yaml files are not k8s files that I already have? Also, is it open source? (I couldn't find a link to source on mobile)

Yes, these are our (thin) YAML files via which you describe the Sandboxes in terms of deltas from the baseline env. The K8s yaml files remain as the source of truth for your standard deployments. The operator is not open source. Some components like the CLI and Resource plugins are. We do have a free tier, however.

Okay, thanks for the explanation!

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

#56

Post by ojhughes »

Reitet00 wrote: post #38
potatocannon wrote: post #25

Earlier quoted context omitted.

tilt.dev

Looks okay but I was looking for something that wouldn't require learning yet another config language and would rather take k8s yamls that I already have (or require minimal modifications).

Checkout Skaffold and kustomize as well

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

#57

Post by spion »

spion wrote: post #13

The fact that you need a container registry drastically increases the barrier for initial adoption.

I see the downvotes. I can't stress how important this has been when talking to people trying to test the waters with k8s. microk8s goes a long way of making this as simple as possible, but having a super-simple out of the box secure (!) registry solution would simplify things a lot.

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

#59

Post by peterbecich »

Reitet00 wrote: post #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.

It would be very useful IMO to be able to easily move a service outside of Kubernetes.

The goal is to move the "fast loop" development outside of any container, onto the native system.

If I am not mistaken, all of the tools which help this either rebuild a container, or rebuild inside a container, right?

Given a Kubernetes application with service names, port forwards, etc., I would like to have an option to automatically convert these configurations into `ExternalName`, external port forwards, etc. This would be transparent to all services, inside and outside Kubernetes.

I think it can be done manually today. My colleagues at my last job wrote a helper script; credit to them for the idea. I think it could be built into `kubectl`. i.e. `kubectl apply --externalize serviceA`

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

#60

Post by simiones »

epilogue wrote: post #15
simiones wrote: post #5

One thing I just hit is that there doesn't seem to be any way to ask from a Pod to get a TLS certificate signed by the cluster itself (that would only be valid inside the cluster, of course) that is valid for the IP(s) and DNS names associated by Kubernetes itself with the pod (and to automatically rotate etc such certs). Since the infrastructure already knows (and controls) this information, it would be the ideal pl…

We’ve been using Linkerd as our service mesh which does this without really much effort at all required on our part. They bind the certs to the ServiceAccount identity of each pod, which is apparently more secure than doing it via IP. https://linkerd.io/2.13/features/automatic-mtls/

Unfortunately this would probably not work for my purposes - the issue on my side is that I want to enable MinIO to use server-side encryption; however, MinIO doesn't support SSE unless TLS is enabled inside MinIO itself - so it's ultimately MinIO that needs these certificates, it doesn't help that the Linkerd proxy is actually encrypting the traffic if MinIO doesn't know about it.

There may be a way to tell MinIO to use the the proxy certificates though, since those may be somewhere in the pod FS if I understand the docs correctly, I can try to investigate that, thanks for the link!

Post reply on HN