<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infra as Code on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/infra-as-code/</link><description>Recent content in Infra as Code on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 15 Sep 2020 07:00:57 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/infra-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Create a local Kubernetes cluster with Vagrant</title><link>https://tferdinand.net/en/create-a-local-kubernetes-cluster-with-vagrant/</link><pubDate>Tue, 15 Sep 2020 07:00:57 +0000</pubDate><guid>https://tferdinand.net/en/create-a-local-kubernetes-cluster-with-vagrant/</guid><description>&lt;p&gt;Testing Kubernetes is quite easy thanks to solutions such as Minikube.&lt;/p&gt;
&lt;p&gt;However, when you want to test cluster-specific features, such as load balancing or failover, it is not necessarily suitable anymore.&lt;/p&gt;
&lt;p&gt;It is possible to build your Kubernetes infrastructure on servers, or by using managed services from a cloud provider (Kapsule at Scaleway, AKS at Azure, GKE at GCP or EKS at AWS for example).&lt;/p&gt;
&lt;p&gt;Nevertheless, these solutions cost money. When you just want to test functionalities or self-training, it&amp;rsquo;s not necessarily appropriate.&lt;/p&gt;</description></item><item><title>Terraform VS CloudFormation: Which tool to deploy on AWS?</title><link>https://tferdinand.net/en/terraform-vs-cloudformation-which-tool-to-deploy-on-aws/</link><pubDate>Fri, 13 Dec 2019 11:00:00 +0000</pubDate><guid>https://tferdinand.net/en/terraform-vs-cloudformation-which-tool-to-deploy-on-aws/</guid><description>&lt;p&gt;Terraform or CloudFormation, the two tools are often pitted against each other, asking DevOps to decide and choose one tool or the other. However, from my point of view, these two tools do not necessarily address the same needs.&lt;/p&gt;
&lt;h2 id="asking-the-question-of-ones-exact-need"&gt;Asking the question of one&amp;rsquo;s exact need&lt;/h2&gt;
&lt;p&gt;Before knowing which tool to go to, it is important to know the exact need to be addressed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do I want to deploy only on AWS?&lt;/li&gt;
&lt;li&gt;Do I need to interface with existing tools (especially CI/CD)?&lt;/li&gt;
&lt;li&gt;Do I want to host the deployment solution myself or depend on a managed service?&lt;/li&gt;
&lt;li&gt;Do I already use other tools from the HashiCorp ecosystem (Nomad, Packer, Consul or Vault for example)?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Indeed, with these questions you can already target the tool you want to use more easily.&lt;/p&gt;</description></item><item><title>Migrate your infrastructure to AWS in an optimal way</title><link>https://tferdinand.net/en/migrate-your-infrastructure-to-aws-in-an-optimal-way/</link><pubDate>Fri, 12 Apr 2019 12:39:56 +0000</pubDate><guid>https://tferdinand.net/en/migrate-your-infrastructure-to-aws-in-an-optimal-way/</guid><description>&lt;p&gt;The Cloud appears to be an Eldorado for many companies: simpler application deployment, cost reduction, use of innovative technologies, so many advantages that Amazon promises to its potential customers, but is it that simple?&lt;/p&gt;
&lt;p&gt;AWS, and the cloud more generally, can be an excellent lever on the points mentioned above, however it is quite easy to lose feathers. In this article, I will list what, for me, seems to be the mistakes to avoid.&lt;/p&gt;</description></item></channel></rss>