<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Infrastructure as Code - OpsX DevOps Team Forum				            </title>
            <link>https://opsx.team/community/infrastructure-as-code/</link>
            <description>OpsX DevOps Team Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Tue, 07 Apr 2026 20:38:14 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Our journey from Jenkins to GitHub Actions - lessons learned</title>
                        <link>https://opsx.team/community/infrastructure-as-code/our-journey-from-jenkins-to-github-actions-lessons-learned-78/</link>
                        <pubDate>Tue, 04 Nov 2025 08:34:42 +0000</pubDate>
                        <description><![CDATA[After extensive evaluation, we&#039;re considering our journey from jenkins to github actions - lessons learned for our production environment.

Current stack:
- Infrastructure: ECS Fargate
- CI/...]]></description>
                        <content:encoded><![CDATA[After extensive evaluation, we're considering our journey from jenkins to github actions - lessons learned for our production environment.

Current stack:
- Infrastructure: ECS Fargate
- CI/CD: GitLab CI
- Monitoring: Prometheus + Grafana

Requirements:
✓ Support for 109 microservices
✓ Multi-region deployment
✓ GDPR compliance
✓ Cost under $9k/month

Has anyone used this at scale? What are the gotchas we should know about?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>David Jenkins</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/our-journey-from-jenkins-to-github-actions-lessons-learned-78/</guid>
                    </item>
				                    <item>
                        <title>Monitoring stack comparison: Prometheus vs Datadog vs New Relic</title>
                        <link>https://opsx.team/community/infrastructure-as-code/monitoring-stack-comparison-prometheus-vs-datadog-vs-new-relic-77/</link>
                        <pubDate>Mon, 20 Oct 2025 03:58:42 +0000</pubDate>
                        <description><![CDATA[Monitoring stack comparison: Prometheus vs Datadog vs New Relic - our team is split on this decision.

Pro arguments:
- Proven at scale
- Excellent documentation
- Cost-effective

Con argume...]]></description>
                        <content:encoded><![CDATA[Monitoring stack comparison: Prometheus vs Datadog vs New Relic - our team is split on this decision.

Pro arguments:
- Proven at scale
- Excellent documentation
- Cost-effective

Con arguments:
- Complex configuration
- Poor error messages
- Migration will be painful

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Evelyn Lewis</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/monitoring-stack-comparison-prometheus-vs-datadog-vs-new-relic-77/</guid>
                    </item>
				                    <item>
                        <title>Service mesh showdown: Istio vs Linkerd vs Consul Connect</title>
                        <link>https://opsx.team/community/infrastructure-as-code/service-mesh-showdown-istio-vs-linkerd-vs-consul-connect-72/</link>
                        <pubDate>Thu, 16 Oct 2025 20:40:42 +0000</pubDate>
                        <description><![CDATA[After extensive evaluation, we&#039;re considering service mesh showdown: istio vs linkerd vs consul connect for our production environment.

Current stack:
- Infrastructure: ECS Fargate
- CI/CD:...]]></description>
                        <content:encoded><![CDATA[After extensive evaluation, we're considering service mesh showdown: istio vs linkerd vs consul connect for our production environment.

Current stack:
- Infrastructure: ECS Fargate
- CI/CD: ArgoCD
- Monitoring: CloudWatch

Requirements:
✓ Support for 407 microservices
✓ Multi-region deployment
✓ GDPR compliance
✓ Cost under $6k/month

Has anyone used this at scale? What are the gotchas we should know about?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Robert Stewart</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/service-mesh-showdown-istio-vs-linkerd-vs-consul-connect-72/</guid>
                    </item>
				                    <item>
                        <title>ArgoCD vs FluxCD in 2025 - which GitOps tool wins?</title>
                        <link>https://opsx.team/community/infrastructure-as-code/argocd-vs-fluxcd-in-2025-which-gitops-tool-wins-73/</link>
                        <pubDate>Fri, 10 Oct 2025 09:04:42 +0000</pubDate>
                        <description><![CDATA[ArgoCD vs FluxCD in 2025 - which GitOps tool wins? - our team is split on this decision.

Pro arguments:
- Easy to learn
- Enterprise features
- Security-first design

Con arguments:
- Vendo...]]></description>
                        <content:encoded><![CDATA[ArgoCD vs FluxCD in 2025 - which GitOps tool wins? - our team is split on this decision.

Pro arguments:
- Easy to learn
- Enterprise features
- Security-first design

Con arguments:
- Vendor lock-in risk
- Limited features in free tier
- Migration will be painful

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Sara Pike</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/argocd-vs-fluxcd-in-2025-which-gitops-tool-wins-73/</guid>
                    </item>
				                    <item>
                        <title>Infrastructure drift detection tools - what actually works?</title>
                        <link>https://opsx.team/community/infrastructure-as-code/infrastructure-drift-detection-tools-what-actually-works-75/</link>
                        <pubDate>Tue, 30 Sep 2025 23:16:42 +0000</pubDate>
                        <description><![CDATA[Infrastructure drift detection tools - what actually works? - our team is split on this decision.

Pro arguments:
- Easy to learn
- Active development
- Cloud-agnostic

Con arguments:
- Reso...]]></description>
                        <content:encoded><![CDATA[Infrastructure drift detection tools - what actually works? - our team is split on this decision.

Pro arguments:
- Easy to learn
- Active development
- Cloud-agnostic

Con arguments:
- Resource-intensive
- Breaking changes between versions
- High operational overhead

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Tom Chack</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/infrastructure-drift-detection-tools-what-actually-works-75/</guid>
                    </item>
				                    <item>
                        <title>Terraform vs Pulumi vs CloudFormation - real production experience</title>
                        <link>https://opsx.team/community/infrastructure-as-code/terraform-vs-pulumi-vs-cloudformation-real-production-experience-76/</link>
                        <pubDate>Sun, 28 Sep 2025 00:08:42 +0000</pubDate>
                        <description><![CDATA[Terraform vs Pulumi vs CloudFormation - real production experience - our team is split on this decision.

Pro arguments:
- Industry standard
- Enterprise features
- Cloud-agnostic

Con argum...]]></description>
                        <content:encoded><![CDATA[Terraform vs Pulumi vs CloudFormation - real production experience - our team is split on this decision.

Pro arguments:
- Industry standard
- Enterprise features
- Cloud-agnostic

Con arguments:
- Complex configuration
- Debugging is hard
- Better alternatives exist

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Mark Murphy</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/terraform-vs-pulumi-vs-cloudformation-real-production-experience-76/</guid>
                    </item>
				                    <item>
                        <title>Deep dive: Kubernetes networking deep dive: CNI, Services, and Ingress</title>
                        <link>https://opsx.team/community/infrastructure-as-code/deep-dive-kubernetes-networking-deep-dive-cni-services-and-ingress-180/</link>
                        <pubDate>Mon, 22 Sep 2025 03:21:13 +0000</pubDate>
                        <description><![CDATA[Solid work putting this together! I have a few questions: 1) How did you handle security? 2) What was your approach to rollback? 3) Did you encounter any issues with costs? We&#039;re considering...]]></description>
                        <content:encoded><![CDATA[Solid work putting this together! I have a few questions: 1) How did you handle security? 2) What was your approach to rollback? 3) Did you encounter any issues with costs? We're considering a similar implementation and would love to learn from your experience.

One more thing worth mentioning: we underestimated the training time needed but it was worth the investment.

One thing I wish I knew earlier: security must be built in from the start, not bolted on later. Would have saved us a lot of time.

Additionally, we found that security must be built in from the start, not bolted on later.

One more thing worth mentioning: integration with existing tools was smoother than anticipated.

Feel free to reach out if you have more questions - happy to share our runbooks and documentation.]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Alexander Smith</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/deep-dive-kubernetes-networking-deep-dive-cni-services-and-ingress-180/</guid>
                    </item>
				                    <item>
                        <title>Practical guide: Implementing SLOs and error budgets for reliability</title>
                        <link>https://opsx.team/community/infrastructure-as-code/practical-guide-implementing-slos-and-error-budgets-for-reliability-305/</link>
                        <pubDate>Thu, 18 Sep 2025 20:21:13 +0000</pubDate>
                        <description><![CDATA[Exactly right. What we&#039;ve observed is the most important factor was the human side of change management is often harder than the technical implementation. We initially struggled with scaling...]]></description>
                        <content:encoded><![CDATA[Exactly right. What we've observed is the most important factor was the human side of change management is often harder than the technical implementation. We initially struggled with scaling issues but found that drift detection with automated remediation worked well. The ROI has been significant - we've seen 3x improvement.

I'd recommend checking out relevant blog posts for more details.

For context, we're using Grafana, Loki, and Tempo.

For context, we're using Istio, Linkerd, and Envoy.

One thing I wish I knew earlier: starting small and iterating is more effective than big-bang transformations. Would have saved us a lot of time.

Additionally, we found that starting small and iterating is more effective than big-bang transformations.

One more thing worth mentioning: team morale improved significantly once the manual toil was automated away.]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Joseph Peterson</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/practical-guide-implementing-slos-and-error-budgets-for-reliability-305/</guid>
                    </item>
				                    <item>
                        <title>Docker BuildKit vs Podman - performance benchmarks</title>
                        <link>https://opsx.team/community/infrastructure-as-code/docker-buildkit-vs-podman-performance-benchmarks-79/</link>
                        <pubDate>Tue, 09 Sep 2025 00:31:42 +0000</pubDate>
                        <description><![CDATA[Docker BuildKit vs Podman - performance benchmarks - our team is split on this decision.

Pro arguments:
- Industry standard
- Good performance
- Cost-effective

Con arguments:
- Vendor lock...]]></description>
                        <content:encoded><![CDATA[Docker BuildKit vs Podman - performance benchmarks - our team is split on this decision.

Pro arguments:
- Industry standard
- Good performance
- Cost-effective

Con arguments:
- Vendor lock-in risk
- Limited features in free tier
- Overkill for our use case

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Maria Rodriguez</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/docker-buildkit-vs-podman-performance-benchmarks-79/</guid>
                    </item>
				                    <item>
                        <title>CI/CD for microservices - our multi-repo vs mono-repo strategy</title>
                        <link>https://opsx.team/community/infrastructure-as-code/cicd-for-microservices-our-multi-repo-vs-mono-repo-strategy-74/</link>
                        <pubDate>Mon, 08 Sep 2025 13:50:42 +0000</pubDate>
                        <description><![CDATA[CI/CD for microservices - our multi-repo vs mono-repo strategy - our team is split on this decision.

Pro arguments:
- Easy to learn
- Active development
- Cloud-agnostic

Con arguments:
- C...]]></description>
                        <content:encoded><![CDATA[CI/CD for microservices - our multi-repo vs mono-repo strategy - our team is split on this decision.

Pro arguments:
- Easy to learn
- Active development
- Cloud-agnostic

Con arguments:
- Complex configuration
- Breaking changes between versions
- High operational overhead

Would love to hear from teams who've made this choice - any regrets or wins?]]></content:encoded>
						                            <category domain="https://opsx.team/community/infrastructure-as-code/">Infrastructure as Code</category>                        <dc:creator>Tom Chack</dc:creator>
                        <guid isPermaLink="true">https://opsx.team/community/infrastructure-as-code/cicd-for-microservices-our-multi-repo-vs-mono-repo-strategy-74/</guid>
                    </item>
							        </channel>
        </rss>
		