home.social

#infrastructureascode — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #infrastructureascode, aggregated by home.social.

  1. Platform Engineering Labs has announced a major update to formae - its platform.

    New capabilities include:
    ➤ Full Kubernetes support
    ➤ Native Helm integration
    ➤ Direct .tfvars compatibility
    ➤ A new public plugin hub

    More details on bit.ly/4dM6hKC

  2. Platform Engineering Labs has announced a major update to formae - its #opensource #IaC platform.

    New capabilities include:
    ➤ Full Kubernetes support
    ➤ Native Helm integration
    ➤ Direct .tfvars compatibility
    ➤ A new public plugin hub

    More details on #InfoQbit.ly/4dM6hKC

    #PlatformEngineering #DevOps #InfrastructureAsCode #Kubernetes #CloudNative

  3. "The question isn't whether #AI will replace #DevOps engineers. It's whether you understand your systems well enough to know when it's wrong. It will be wrong. And it won't tell you." - Heinan Cabouly

    Companies in regulated industries such as #TDBank, #Vega and #EY are proceeding with caution with #AIagents for #InfrastructureasCode -- but proceeding nonetheless. And a new developer interface for IT automation might be taking shape...

    Get all the details, including #Ansible by #RedHat 's approach to this shift, in my latest writeup here: techtarget.com/searchitoperati

  4. From zero to production-ready infrastructure – with an Ansible playbook. 🛠️ In his blog post, Tim shows how you can automatically provision a complete environment using our Nine API and nctl. No manual dashboard clicking, everything reproducible, as code, and everything hosted in Switzerland. 🇨🇭 What does that mean? Fewer careless mistakes and faster setups. For more info and details, read the full article: 👉 nine.ch/en/blog/from-zero-to-i #infrastructureascode #ansible #devops #automation #nine

  5. #OpenTofu 1.12 is out!

    This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.

    Find out more: bit.ly/3RY6AdU

    #InfoQ #DevOps #Terraform #InfrastructureAsCode

  6. 1.12 is out!

    This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.

    Find out more: bit.ly/3RY6AdU

  7. #OpenTofu 1.12 is out!

    This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.

    Find out more: bit.ly/3RY6AdU

    #InfoQ #DevOps #Terraform #InfrastructureAsCode

  8. #OpenTofu 1.12 is out!

    This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.

    Find out more: bit.ly/3RY6AdU

    #InfoQ #DevOps #Terraform #InfrastructureAsCode

  9. #OpenTofu 1.12 is out!

    This update isn’t a complete rewrite, but it does resolve some issues that infrastructure teams have faced for a while.

    Find out more: bit.ly/3RY6AdU

    #InfoQ #DevOps #Terraform #InfrastructureAsCode

  10. Pipeline-as-truth creates invisible drift. Declare intended state in versioned configuration files and treat the pipeline as an executor, not an authority. hackernoon.com/your-automation #infrastructureascode

  11. Terraform for the VMs and Ansible for the config are already paying off.

    I took my old Ansible playbook that initialized a cluster, joined the other control plane nodes, and then joined two workers which all still works.

    Now the really fun part comes about configuring the cluster entirely with some tool, which I might go back to Terraform for. I know I'll want to configure a CNI to start, and kube-vip for the control plane nodes, then I'll be able to get some workloads going.

    #homelab #kubernetes #ansible #terraform #infrastructureascode #pipelines

  12. Terraform for the VMs and Ansible for the config are already paying off.

    I took my old Ansible playbook that initialized a cluster, joined the other control plane nodes, and then joined two workers which all still works.

    Now the really fun part comes about configuring the cluster entirely with some tool, which I might go back to Terraform for. I know I'll want to configure a CNI to start, and kube-vip for the control plane nodes, then I'll be able to get some workloads going.

    #homelab #kubernetes #ansible #terraform #infrastructureascode #pipelines

  13. Terraform for the VMs and Ansible for the config are already paying off.

    I took my old Ansible playbook that initialized a cluster, joined the other control plane nodes, and then joined two workers which all still works.

    Now the really fun part comes about configuring the cluster entirely with some tool, which I might go back to Terraform for. I know I'll want to configure a CNI to start, and kube-vip for the control plane nodes, then I'll be able to get some workloads going.

    #homelab #kubernetes #ansible #terraform #infrastructureascode #pipelines

  14. Terraform for the VMs and Ansible for the config are already paying off.

    I took my old Ansible playbook that initialized a cluster, joined the other control plane nodes, and then joined two workers which all still works.

    Now the really fun part comes about configuring the cluster entirely with some tool, which I might go back to Terraform for. I know I'll want to configure a CNI to start, and kube-vip for the control plane nodes, then I'll be able to get some workloads going.

    #homelab #kubernetes #ansible #terraform #infrastructureascode #pipelines

  15. Terraform for the VMs and Ansible for the config are already paying off.

    I took my old Ansible playbook that initialized a cluster, joined the other control plane nodes, and then joined two workers which all still works.

    Now the really fun part comes about configuring the cluster entirely with some tool, which I might go back to Terraform for. I know I'll want to configure a CNI to start, and kube-vip for the control plane nodes, then I'll be able to get some workloads going.

    #homelab #kubernetes #ansible #terraform #infrastructureascode #pipelines

  16. I'm exploring how to handle the cluster creation now that I can provision nodes on demand and it seems to be the easiest way will be to use Ansible.

    I already have a playbook for that (which is great) I'll just need to adjust it to the new inventory and configurations. Should be easy enough?

    From there, I think I'll figure out how I want to deploy resources in some idempotent manner. This is where Terraform might come back into play.

    I also want to work on testing new versions of containers in a dev space as well as restoring from backups for my more important data, but that's an issue for another month.

    #homelab #kubernetes #terraform #ansible #infrastructureascode

  17. Of course, things like this are easy with Terraform. Here’s an inventory/config, go make it. This post was more about avoiding sunk cost fallacy with clusterctl.

    I even added Terraform configuring the DNS entries for the 5 nodes and figured that was enough for tonight.

    #homelab #terraform #kubernetes #infrastructureascode #automation

  18. Gave up on using clusterctl for the time being, figured out I can get a lot further with Terraform and the template from image-builder (with some minor modifications).

    In just over an hour, I already have Terraform provisioning 5 empty VMs preinstalled with the software I need. I'm 99% sure there are ways to provision k8s clusters in Terraform so I don't need to reinvent that wheel. Here are 3 control plane nodes, and 2 worker nodes, go build it.

    The only change I had to make with the image-builder template was to re-add a cloud-init disk.

    #homelab #terraform #kubernetes #infrastructureascode #automation

  19. 🚀 𝗤𝘂𝗶𝗰𝗸 𝗴𝘂𝗶𝗱𝗲 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗹𝗲

    Deploy 𝗥𝗘𝗟𝗜𝗔𝗡𝗢𝗜𝗗 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝘃𝟴 on 𝗔𝗪𝗦 with 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺 easily using the official module.

    ✔️ Ready-to-use infrastructure (VPC, subnet, security groups)

    ✔️ EC2 instance with RELIANOID AMI

    ✔️ SSH and Web GUI access

    ✔️ Clean teardown with terraform destroy

    👉 relianoid.com/resources/knowle

  20. “Migrations fail when visibility is stale, drift grows, and cutovers go manual.”

    Migrating Puppet environments doesn’t have to be painful.

    Tony Green shares hard‑won lessons from real-world migrations and how to stay in control when things get messy.

    If you’re planning a Puppet migration (or already in the middle of one), this is well worth a read:

    puppet.com/blog/puppet-mirgrat

  21. Setting up a self-hosted Mattermost Team Edition server does not have to be a complex infrastructure puzzle. ☁️

    You can deploy to Upsun with PostgreSQL 16 and OpenSearch 2, configured automatically from a single infrastructure-as-code file. ⚡

    Read our guide to see how this simple configuration works and get your deployment started today.

    👉 developer.upsun.com/posts/tuto

    #Mattermost #DevOps #CloudNative #InfrastructureAsCode

  22. Setting up a self-hosted Mattermost Team Edition server does not have to be a complex infrastructure puzzle. ☁️

    You can deploy to Upsun with PostgreSQL 16 and OpenSearch 2, configured automatically from a single infrastructure-as-code file. ⚡

    Read our guide to see how this simple configuration works and get your deployment started today.

    👉 developer.upsun.com/posts/tuto

    #Mattermost #DevOps #CloudNative #InfrastructureAsCode

  23. Setting up a self-hosted Mattermost Team Edition server does not have to be a complex infrastructure puzzle. ☁️

    You can deploy to Upsun with PostgreSQL 16 and OpenSearch 2, configured automatically from a single infrastructure-as-code file. ⚡

    Read our guide to see how this simple configuration works and get your deployment started today.

    👉 developer.upsun.com/posts/tuto

    #Mattermost #DevOps #CloudNative #InfrastructureAsCode

  24. I just added #Ubuntu 26.04 LTS to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @ubuntu

  25. I just added #Fedora 44 to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @fedora
    @ansible

  26. I just added #Fedora 44 to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @fedora
    @ansible

  27. I just added #Fedora 44 to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @fedora
    @ansible

  28. I just added #Fedora 44 to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @fedora
    @ansible

  29. I just added #Fedora 44 to our Integration Test Target (ITT) lineup:
    👉 github.com/orgs/foundata/repos

    🔍 Looking for #Linux #Containers for your CI/CD pipeline? We’ve built a collection of OCI images:

    ✅ fully functional systemd (not just a shim!)
    ✅ unprivileged execution support, perfect for tools like #Podman.
    ✅ ideal for #Ansible #Molecule testing, see them in action with a collection: github.com/foundata/ansible-co

    #Automation #DevOps #OpenSource #InfrastructureAsCode #foundata

    @fedora
    @ansible

  30. A lot of teams are being told to “use AI in ops” right now. The harder part is figuring out *where it actually helps* day to day without adding risk, noise, or another thing to babysit.

    If you’re curious (or skeptical 👀) about AI in ops, join Robin Tatam and Jason St-Cyr as they share their thoughts on where AI can realistically fit into infrastructure operations today. No magic, just using good tools to do better.

    👉 puppet.com/resources/events/we

  31. A lot of teams are being told to “use AI in ops” right now. The harder part is figuring out *where it actually helps* day to day without adding risk, noise, or another thing to babysit.

    If you’re curious (or skeptical 👀) about AI in ops, join Robin Tatam and Jason St-Cyr as they share their thoughts on where AI can realistically fit into infrastructure operations today. No magic, just using good tools to do better.

    👉 puppet.com/resources/events/we

    #Puppet #InfrastructureAsCode #AIOps

  32. A lot of teams are being told to “use AI in ops” right now. The harder part is figuring out *where it actually helps* day to day without adding risk, noise, or another thing to babysit.

    If you’re curious (or skeptical 👀) about AI in ops, join Robin Tatam and Jason St-Cyr as they share their thoughts on where AI can realistically fit into infrastructure operations today. No magic, just using good tools to do better.

    👉 puppet.com/resources/events/we

    #Puppet #InfrastructureAsCode #AIOps

  33. A lot of teams are being told to “use AI in ops” right now. The harder part is figuring out *where it actually helps* day to day without adding risk, noise, or another thing to babysit.

    If you’re curious (or skeptical 👀) about AI in ops, join Robin Tatam and Jason St-Cyr as they share their thoughts on where AI can realistically fit into infrastructure operations today. No magic, just using good tools to do better.

    👉 puppet.com/resources/events/we

    #Puppet #InfrastructureAsCode #AIOps

  34. A lot of teams are being told to “use AI in ops” right now. The harder part is figuring out *where it actually helps* day to day without adding risk, noise, or another thing to babysit.

    If you’re curious (or skeptical 👀) about AI in ops, join Robin Tatam and Jason St-Cyr as they share their thoughts on where AI can realistically fit into infrastructure operations today. No magic, just using good tools to do better.

    👉 puppet.com/resources/events/we

    #Puppet #InfrastructureAsCode #AIOps

  35. 📢 Puppet Continuous Delivery 5.15.0 available with improvements for stability, security, integrations, and usability.

    Highlights include:
    - New external_webhook_url support for proxy-based deployments
    - Impact Analysis updates for Pipelines as Code
    - Clearer GitLab commit status reporting
    - Amazon Linux 2023 support for Docker-based installs
    - Security and dependency updates addressing reported CVEs

    Full release notes:
    help.puppet.com/cdpe/current/C

  36. Puppet Security Compliance Management 3.7.0 is out!

    This release focuses on keeping compliance stable as environments scale:
    - New CIS benchmarks for modern Linux, macOS, and Windows 11
    - More predictable scan performance with tunable JVM memory
    - Stronger session and GraphQL API controls
    - Security fixes and dependency updates (CVE items in the release notes!)

    👇Check out the Release notes:
    help.puppet.com/scm/current/Co

  37. Follow-up to getnix.io/guides/nixos-auto-up — here's how I handle upstream tracking for packages like Netbird:

    1. Internal mirror syncs release tags from upstream source repository
    2. CI detects new tags, updates the Nix flake (version + related hashes), builds & commits
    3. Consumer repos pick up the change, open PRs with nvd diffs
    4. Human reviews & merges
    5. Hosts auto-deploy

    Full pipeline runs unattended — you only step in to review the PR.

    #nixos #nix #infrastructureascode #gitops

  38. Puppet Core 8.18.0 is out with macOS 15 support and security updates.

    This release includes CVE fixes across core dependencies:
    - libxml2 updated to 2.15.2
    - zlib gem updated to 3.0.1
    - curl updated to 8.19.0

    If you’re managing macOS fleets or operating with tight patch windows, this is a solid release to plan into your next upgrade cycle.

    Release notes:
    help.puppet.com/core/current/C