Live data from Hacker News

Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

getkloak.io

11–20 of 55 posts

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#11
post #3

Hey, we're the spinning-factory team, the folks behind Kloak. Kloak runs as a Kubernetes controller. It swaps the secrets in your workloads for harmless placeholders we call kloaked secrets, then uses eBPF to substitute the real secrets back in at the last moment — right when your app makes a request to an allowed host. Today, Kloak works with any app using OpenSSL 3.0–3.5 (statically or dynamically linked) or go-tls…

This is fantastic! I need this. however, for my self-hosted home projects that are containerized but where I don't use Kubernetes, is there a way for me to use a version of Kloak that does the same eBPF magic on docker-compose or LXC/QEMU (Incus) stacks? It's perfectly fine for you to say non-Kubernetes isn't either your focus or on your 90 day roadmap :)

Yeah you might have to go talk to incus folks on how to integrate this together.. They are fairly capable, might have some good direction.

https://discuss.linuxcontainers.org/t/how-to-best-ask-questi...

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#14

You should split your controller - it is running in both the control and data planes. Idea is good though, wish you luck.

Aiui the controller is only running in the control plane, and the ebpf programs are in the data plane?

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#15

This is pretty awesome. Super relevant for the time because AI controlled workflows are desperate for a out of band solution like this. The main thing I wonder is how well supported is it in cloud environements? AKS/EKS/etc?

It should work in cloud environments, We tested it on EKS and digital ocean cloud so far, and it works. The kloak controller is deployed as privileged daemonset that have access to the underlying host and can perform eBPF attachment operations on all the pods on that host.

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#16

You should split your controller - it is running in both the control and data planes. Idea is good though, wish you luck.

Thank you! Not really, the controller is not doing dataplane per-say, it only pushes eBPF programs to the kernel for the relevant apps/cgroups so that could be considered control-plane. The full data-plane run in eBPF.

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#17
post #6
post #4

Yeah, so Kloak is Danish for sewer.

I guess we are the secrets sewers then! :D We would love to hear what you think about it beyond the name though.

I think it is funny that it's sewer, because a sewer is also a underground way around things, which is a good description of the out of band solution here. So the name checks out.

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#18
post #14

You should split your controller - it is running in both the control and data planes. Idea is good though, wish you luck.

Aiui the controller is only running in the control plane, and the ebpf programs are in the data plane?

yes, that's right!

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#19
post #11

Earlier quoted context omitted.

This is fantastic! I need this. however, for my self-hosted home projects that are containerized but where I don't use Kubernetes, is there a way for me to use a version of Kloak that does the same eBPF magic on docker-compose or LXC/QEMU (Incus) stacks? It's perfectly fine for you to say non-Kubernetes isn't either your focus or on your 90 day roadmap :)

Yeah you might have to go talk to incus folks on how to integrate this together.. They are fairly capable, might have some good direction. https://discuss.linuxcontainers.org/t/how-to-best-ask-questi...

Thank you! We will reachout and see what can be done

Re: Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

#20
post #6

Earlier quoted context omitted.

I guess we are the secrets sewers then! :D We would love to hear what you think about it beyond the name though.

I think it is funny that it's sewer, because a sewer is also a underground way around things, which is a good description of the out of band solution here. So the name checks out.

It was not intended! We were trying to make it sound like a cloak with a kubernetes K but I guess this explanation actually checkout better!
Post reply on HN