kubespy VS kube-fledged

lang="en"> charset="utf-8"> Hello, world! Hello, world! 👋 Deployed with 💜 by new href="https://pulumi.com/">Pulumi.

Pulumi IaC will help us bring up our infrastructure on the AWS Cloud. Check out pulumi.com if you still need to become familiar with it. You can deploy this demo stack using the Pulumi button below.

There are other infrastructure as code tools that take secrets seriously. Pulumi encrypts all values in state and you can even bring your own key from your cloud provider

*Codifying the deployment of the OTel Collector *(to Nomad, Kubernetes, or a VM) using tools such as Terraform, Pulumi, or Ansible. The Collector funnels your OTel data to your Observability back-end. ✅

KubeSpy - to see what's going on a deployment real time. https://github.com/pulumi/kubespy

it takes too much time, terraform configs are not easy to use also. Pulumi is much better to maintenance. Cloudy is good enough for launching a production-ready cluster in 5-10 minutes. It could be an alternative to kops

Just wanted to mention a Terraform alternative I really like, especially cause it's infrastructure as code (IaC) http://pulumi.com/, though I'm not sure about their approach on multi cloud, haven't used it in quite a while

That is the entire point of Pulumi, you should give it a try

pulumi.com if you are interested in doing anything dynamic inside of your templates (i.e. conditions) take a look at pulumi

Exactly. Part of the appeal to consolidate all of our container images to use Debian-slim is the ability to optimise the caching of layers, both in our container registry but also on our kubernetes cluster’s nodes (which can be done in a consistent manner with kube-fledged[1]).

[1] https://github.com/senthilrch/kube-fledged

If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.

Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.

https://github.com/senthilrch/kube-fledged

https://github.com/dragonflyoss/Dragonfly2

https://github.com/uber/kraken

https://nydus.dev/

kube fledged - pre pull containes in nodes: https://github.com/senthilrch/kube-fledged

kube-fledged is a kubernetes add-on or operator for creating and managing a cache of container images directly on the worker nodes of a kubernetes cluster. It allows a user to define a list of images and onto which worker nodes those images should be cached (i.e. pulled). As a result, application pods start almost instantly, since the images need not be pulled from the registry. kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and supports several configurable parameters in order to customize the functioning as per one’s needs. (URL: https://github.com/senthilrch/kube-fledged)

I found recently this tool kube-fledged that should do what you want..

I recommend you also look at kube-fledged this is more appealing IMHO.