Hey HN - I am working on a terraform automation tool [1] and have been observing that a lot of our users are now using coding agents in their workflows, even for infra tasks. Obviously, this means a lot of terraform is being generated by coding agents, and while this is great for greenfield setups, most teams already have conventions in place. My colleague was speaking to a friend earlier today, who mentioned that... - Source: Hacker News / 9 months ago

None of these are a replacement of Terraform Cloud (recently rebranded to HCP Terraform). For example, when you create a PR, it could affect multiple workspaces. The new experimental version of TFC/TFE (I refuse to call it HCP!) implements Stacks, which is something like a workflow, and links one workspace output to other workspace inputs. None of the open-source solutions, including the paid Digger [0], support... - Source: Hacker News / over 2 years ago

I'm part of the founding team at Digger, an Open Source Terraform Enterprise alternative. For the past few days, I have been wanting to talk about why the usual metrics in Commercial Open Source just don't cut it anymore. Source: about 3 years ago

Depending on the organisation, it is not always a good idea to make assumptions on what another team will be doing to use your module. Don't get me wrong, there are attempts at making cross-platform workflows like digger.dev, or RedHat who have recently released an ansible playbook that runs terraform (so in theory you'd only need ansible then) but at the very minimum, be aware if you tightly integrate your... Source: over 3 years ago

We are building an open source terraform cloud alternative (https://digger.dev/) and are looking to start a bounty program. Source: over 3 years ago

For kubeadm , kubetlet , kubectl should same version package in this lab I used v1.31 to have 1.31.7 References: Https://kubernetes.io/docs/reference/networking/ports-and-protocols/ Https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ Https://github.com/opencontainers/runc/releases/... - Source: dev.to / over 1 year ago

Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc. - Source: dev.to / almost 2 years ago

Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. Containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes. - Source: dev.to / almost 2 years ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / almost 3 years ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 3 years ago