website VS Pulumi

OpenGitOps group has defined 5 principles, and while I won't delve into them, here, you can read more. If you take a look at those principles you will see that they are, in some sense related to some Kubernetes concepts.

What is OpenGitOps?

The OpenGitOps standards group defines GitOps using a set of four principles:

On top of Talos, I'm running a Kubernetes cluster with everything deployed using GitOps principles. GitOps is a development methodology that uses Git as the single source of truth for infrastructure and application deployments. It's a great way to manage infrastructure changes, and it means that I can easily roll back any changes if something goes wrong.

opengitops.dev is the GitOps working group created by Amazon, GitHub and even Weaveworks which coined the "GitOps" term in their 2017 blog post.

Having "GitOps" on its own doesn't sound right when I say it. Based on the OpenGitOps Principles, we are architecting the GitOps Agent in this discussion, so I'd include that too.

GitOps principles differ from the traditional CI & CD pipeline approach. In the last few years, the GitOps working group under CNCF formalized all the ideas developed around GitOps into a cohesive set of principles that have become the GitOps Principles.

There are four principles of GitOps, and according to Open GitOps, they are:

The Gitops definition

If you are following this blog series, you should already know the benefits of using Terraform to define and deploy your AWS resources and configuration. Other IaC solutions such as AWS CloudFormation, AWS CDK, and Pulumi work the same way but differs in the programming or configuration language.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.

funny, to me systemd == no docker, no containers, just a VM.

it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up an scale down with: https://www.pulumi.com/

Pulumi — Modern infrastructure as a code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure.

A move like this may have an impact in other open source projects. Take Pulumi, for instance, people might avoid choosing it now that the Linux Foundation have its own IaC tool, and for newer, smaller projects it will probably be impossible to compete with a project under the Linux name.

Another alternative to writing an operator would be to rely on kustomize or https://www.pulumi.com/.

Pulumi

Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?

[1]: https://www.pulumi.com/

Infrastructure as Code (IaC): Define your infrastructure using code (IaC) to automate the provisioning of resources such as virtual machines, load balancers, and databases. Tools like Terraform, Pulumi, and AWS CloudFormation can help.