rustshop VS kops

I was hoping to have https://github.com/rustshop/rustshop be like that, but I've got a Rust dayjob since then, and I have less time for Rust side projects now.

Many thanks to u/dpc_pw, whose notes on GitHub were my starting point for the flake definition. (I also just realized I unwittingly gave my article an almost-identical title by the time I was done refining it, so I’m more indebted to them than I thought.)

Since docker images are mentioned, I'd like to point out that using musl-linked images is often counterproductive, as docker layers with standard library can be shared between different projects and build versions. https://github.com/rustshop/rustshop/discussions/9

and here is the project in this area that I'm working on

rustshop is an attempt at building a template for developers to help them start their own cloud-based system, without much Ops experience.

The general problem of patching resource definitions that are not fully under your control has also been recognized for some time. This is true of default resources created and updated by cluster maintenance tools (e.g. kOps), or by public helm charts that you use to install common services and operators (e.g. nginx-ingress, cert-manager, and so on). High quality charts will allow you to override the configuration of important components such as service account references, but some simpler charts offer much less configuration.

The kops documentation is not very clear about this.

Very fast progress and great article with lots of useful information. I found myself nodding a lot having recently seen GitLab Dedicated https://docs.gitlab.com/ee/subscriptions/gitlab_dedicated/ being developed that had my similar challenges. I wonder what other people think of Kops https://kops.sigs.k8s.io/

note: I work with kube on a daily basis. All current clusters under my care use a managed backplane service though there are a number of small (3+ years-old) clusters that I still keep an eye on that were initialized using kops.

kOps with your own instances.

Companies run their own clusters (sometimes for cost reasons), using tools like kops, and kubeadm to set up their own clusters.

curl -Lo kops https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64 chmod +x kops sudo mv kops /usr/local/bin/

Kops is a cluster setup and management command line tool that deploys a Kubernetes cluster to AWS. It provides configuration abstractions such as manifest YAML files that facilitate node and components configuration. And like Ansible, it will provide dry-run capabilities and ensures idempotency of changing the nodes.