grucloud VS kops

I wrote an open source tool called grucloud that can also list the asset inventory, check it out at www.grucloud.com

Check it out at https://www.grucloud.com/

I wrote a birectional infrastructure as code, where the code is generated automatically from a live infrastructure (aws, azure, gcp). Let me know your feedback on this open source tool, available at www.grucloud.com

Yes indeed, yaml and json are not suited for describing infrastructure. Off the self programming languages provide conditionals, loops and so on. I wrote an alternative to CDK/terraform called www.grucloud.com, check it out.

Dig into www.grucloud.com, an alternative to terraform/cdk/pulumi. However, the code is generated automatically forme your current live infrastructure, no need to manually write infrastructure as code.

Have a look at www.grucloud.com, an alternative to Terraform/CDK/pulumi. Instead of manually writing the code, grucloud can generate code from live infrastructures: AWS, Azure and GCP.

The local module defining the app on the k8s side is located at base.

The command gc graph generates this diagram from the code iac.js.

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.