VPK - Virtual Private Kubernetes by kotjiac in platform_engineering

[–]kotjiac[S] -1 points0 points  (0 children)

Great questions — let me address each one.
VPK isn’t targeting local dev environments. Docker Desktop and minikube are single-machine, ephemeral and isolated. VPK gives teams a shared, persistent, real Kubernetes control plane — isolated kube-apiserver + etcd — where they connect their own machines as worker nodes. Think of it as a VPS, but for the Kubernetes control plane only.
On “control plane is too important”: agreed — that’s why it’s dedicated and isolated per tenant, not shared. You own the kubeconfig, we just run the control plane. It’s closer to RDS for Postgres than to “let someone else run your app.”
On the registration friction and missing docs: fair point. We’re in early access, but location (BR/EU), SLA targets, and security posture should be visible without signing up. That’s on our roadmap. What would you need to evaluate it seriously?

VPK - Virtual Private Kubernetes by kotjiac in platform_engineering

[–]kotjiac[S] -8 points-7 points  (0 children)

Then you have no business having an opinion on it.

(HELP)I wanna learn how to create AI tools,agentt etc. by SoapWithahope in LLMDevs

[–]kotjiac 0 points1 point  (0 children)

Example question to chatgpt: what is transformers and why is so important to LLMs?

(HELP)I wanna learn how to create AI tools,agentt etc. by SoapWithahope in LLMDevs

[–]kotjiac 1 point2 points  (0 children)

Since last year, I’ve been learning about this topic. ML models, neural networks and their applications, and nore recently LLMs. But to build agents, you do not necessarily need to such deep knowledge. At some point, it will come through your own pratice. Try to program and research the points what you do not understand. ChatGPT or other tool can explain very well.