<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[DevOps for Zombies - Medium]]></title>
        <description><![CDATA[Articles about Devops Culture and Tools - Medium]]></description>
        <link>https://medium.com/devops-for-zombies?source=rss----91fddc6c6369---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>DevOps for Zombies - Medium</title>
            <link>https://medium.com/devops-for-zombies?source=rss----91fddc6c6369---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:21:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/devops-for-zombies" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Importância da Experiência do Desenvolvedor na Engenharia de Plataforma]]></title>
            <link>https://medium.com/devops-for-zombies/import%C3%A2ncia-da-experi%C3%AAncia-do-desenvolvedor-na-engenharia-de-plataforma-5fb932aac371?source=rss----91fddc6c6369---4</link>
            <guid isPermaLink="false">https://medium.com/p/5fb932aac371</guid>
            <category><![CDATA[devex]]></category>
            <category><![CDATA[engenharia-de-software]]></category>
            <dc:creator><![CDATA[Yros Aguiar]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 22:32:34 GMT</pubDate>
            <atom:updated>2024-02-16T23:16:42.560Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*9ZrwI2dyKHPvEHd-s8_tEw.png" /></figure><p><strong>Por que a DevEx é tão Importante para o Sucesso de uma Plataforma</strong></p><p>O DevEx é crucial para o sucesso de uma plataforma promovendo a inovação e garantindo o controle de qualidade, evitar o <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself#:~:text=%22Don&#39;t%20repeat%20yourself%22,redundancy%20in%20the%20first%20place."><strong>DRY (Don’t repeat yourself)</strong></a> e ajuda manter o <a href="https://en.wikipedia.org/wiki/Single_source_of_truth"><strong>SSOT (single source of truth)</strong> ou <strong>SPOT (single point of truth)</strong></a><strong> </strong>a nível de dependencias e reuso de código e ferramentas. Um dos determinantes mais importantes da eficácia e viabilidade de uma plataforma é a Experiência do Desenvolvedor (DevEx).</p><p>Neste post, descobriremos um pouco mais por que o DevEx desempenha um papel central na garantia do sucesso e da sustentabilidade de uma plataforma, bem como falaremos sobre os benefícios notáveis ​​que um DevEx estabelecido de forma eficiente pode trazer para o time de engenharia.</p><p><strong>Acelera o desenvolvimento de aplicativos.</strong></p><p>O DevEx de alto nível e qualidade simplifica todo o ciclo de vida de desenvolvimento de aplicações, reduzindo significativamente o tempo de configuração do ambiente de desenvolvimento e o tempo necessário para implementar novos recursos, além de resolver problemas. Com isso, as equipes de desenvolvimento podem trabalhar para entregar valor com mais rapidez, adaptando-se melhor às mudanças do mercado e superando os concorrentes.</p><p><strong>Aumenta a Produtividade da Equipe de Desenvolvimento</strong></p><p>A produtividade aprimorada entre os desenvolvedores é possível quando eles têm acesso a ferramentas fáceis de usar, diretrizes bem documentadas e mecanismos de suporte eficientes. O funcionamento de um sistema DevEx avançado é tal que abre caminho para os desenvolvedores, eliminando todos os obstáculos e distrações para que possam trabalhar no desenvolvimento ou melhoria de produtos de qualidade.</p><p><strong>Melhora a Satisfação dos Desenvolvedores</strong></p><p>A satisfação do desenvolvedor também melhora. Um DevEx positivo não apenas torna o trabalho dos desenvolvedores mais fácil e rápido, mas também contribui para a satisfação no trabalho. Desenvolvedores valorizados, apoiados e capacitados tendem a ter níveis mais elevados de engajamento, lealdade e motivação, o que pode levar a taxas de rotatividade reduzidas e maior coesão da equipe.</p><p><strong>Facilita a Colaboração e a Inovação</strong></p><p>A criação de comunicação sem barreiras e o estímulo à cooperação entre os desenvolvedores como resultado de uma experiência de desenvolvimento adequada levam à geração de novas ideias, invenções e criatividade. Tais sistemas permitem que os desenvolvedores troquem informações, encontrem soluções conjuntas para problemas, trabalhem juntos em tarefas difíceis, eventualmente produzindo soluções mais confiáveis ​​e originais.</p><p><strong>Impulsiona a Adoção da Plataforma</strong></p><p>Em última análise, a excelência DevEx é um fator crítico na adoção da plataforma pelas comunidades internas e externas de desenvolvedores. É mais provável que os desenvolvedores adotem e recomendem plataformas que proporcionem uma experiência de desenvolvimento tranquila, eficiente e agradável, o que, por sua vez, contribui para o crescimento e sucesso contínuos da plataforma.</p><p><strong>Conclusão</strong></p><p>Portanto, concluímos que o DevEx desempenha um papel fundamental no sucesso das plataformas digitais, impactando diretamente na velocidade de desenvolvimento, na qualidade das aplicações, na satisfação da equipe e na adoção pelo mercado. Investir na melhoria da experiência do desenvolvedor não é apenas uma estratégia inteligente, mas também uma necessidade para as organizações que procuram permanecer competitivas e inovadoras num ambiente digital em evolução.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fb932aac371" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-for-zombies/import%C3%A2ncia-da-experi%C3%AAncia-do-desenvolvedor-na-engenharia-de-plataforma-5fb932aac371">Importância da Experiência do Desenvolvedor na Engenharia de Plataforma</a> was originally published in <a href="https://medium.com/devops-for-zombies">DevOps for Zombies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Zero to the GitOps — Part 1]]></title>
            <link>https://medium.com/devops-for-zombies/from-zero-to-the-gitops-part-1-59b88124de46?source=rss----91fddc6c6369---4</link>
            <guid isPermaLink="false">https://medium.com/p/59b88124de46</guid>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[pipeline]]></category>
            <category><![CDATA[kustomize]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[gitops]]></category>
            <dc:creator><![CDATA[Yros Aguiar]]></dc:creator>
            <pubDate>Sun, 26 Jul 2020 16:40:03 GMT</pubDate>
            <atom:updated>2020-07-26T22:07:27.683Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Zero to the GitOps — Part 1</h3><p>A series of articles about GitOps</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*xR20TJhMNeHIdFhthHhu9A.png" /></figure><h3>GitOps operations by pull request, git as a source of truth</h3><p>What exactly is GitOps? Using Git as our source of truth, we can operate just about anything. For example, version control, history, peer review, and rollback take place in Git without having to touch tools like kubectl.</p><ul><li><strong>The provisioning of Cloud resources, third party services and the deployment of k8s could be declarative</strong></li><li><strong>The entire state of the system is under version control and described in Git repositories</strong></li><li><strong>Operational changes are made on merge requests (in addition to build and release pipelines)</strong></li><li><strong>The Diff tools detect any divergence and notify us via alerts; synchronization tools allow convergence Reversal and audit logs are also provided via Git</strong></li><li><strong>The monitoring and alerts could be created as a code level.</strong></li><li><strong>The Security layer could be implemented as a code.</strong></li><li><strong>The code itself is the documentation of the environment</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*CHCNrywh4CLDaAO5U-e1CA.png" /></figure><p>It is not about centrally managing the infrastructure/operations, having specific engineering teams to take care of operations, this is a bottleneck, in addition to having more risks and less knowledge dissemination, it is more difficult to obtain a continuous improvement process, we have to understand that in a self-service culture there can be no distinction between development, operations, testing, security, everyone may be able to create, or even change, we will have squads or teams that are more specialized in a given subject, but everyone can be able to propose and create improvements. Just as software development has evolved rapidly over the past few decades, think that infrastructure/operations configuration management needs to follow the same path to evolve quickly, that is, reusing infrastructure code is very important to obtain a process of continuous improvement, using pipelines, git flows, well-defined processes that can be improved through a pull request, so anyone on the team who is part of that product, environment, solution, can request a change, make a change, going through the review and process approval of others, and having great discussions on the subject in the comments of the Pull Request, and when approved we have tests and more tests that validate this change of infrastructure of the environment until delivery is the path to a continuous improvement process because we can easily have metrics and measure step times and always improve our lead time. The SRE team needs to create this process together with the other teams, develop self-service strategies so that engineers can achieve the continuous improvement of a certain product, they must be able to create and maintain items such as Pipeline as Code, Configuration as Code, Infrastructure as Code, Observability as Code.</p><p>Everyone is allowed to create/modify whatever they want in the environment, to ensure standards and things do not get out of control because everyone is allowed to create, modify, we create review strategies based on changes in specific directories (code owners), and the need approval by another engineer, in addition to pipelines with steps that guarantee quality delivery.</p><p>Another example is that you need to create and recreate or maintain hundreds of similar, but distinct environments, if we were to think of code in some programming language a good practice is DRY (Don’t repeat yourself), so we use dependencies and make references to libraries and code that is created by other developers, this is the essence of Open Source, the same applies to infrastructure/operations code, the less I repeat code the leaner my infrastructure/operations code is, the easier it will be maintained, test, modify. In addition to using components that are maintained by several people around the world and that is always in constant evolution, the time of the convergence is fast because we can apply the operations code for all environments, after tests, or if want to apply the new version of the infrastructure only for a part of the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*TnYiHk5PHVoN2XCsv1Wohg.png" /></figure><p>These are just examples of how GitOps can leverage your continuous improvement process. In this series of articles, I will describe and give examples of some technologies in which I have the experience to arrive at an effective GitOps strategy, I will give an overview of the technology and practical examples of how to implement it. The series will be divided into 7 parts, described below:</p><ul><li><strong>Pipeline as Code</strong></li><li><strong>Infrastructure as Code</strong></li><li><strong>Configuration as Code</strong></li><li><strong>Continuous integration</strong></li><li><strong>Continuous Delivery/Deployment</strong></li><li><strong>Security as Code</strong></li><li><strong>Observability as Code</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*6XtFA_-oainqIncKz0-Bzw.png" /></figure><p>Git has advanced the state of the art in development. A decade of best practice says that the configuration is code and the code must be stored in version control. Now it is bringing this benefit to Ops. Now we’ve found that we’d rather fix a production problem with a pull request than make changes to the running system.</p><p>None of this matters unless it makes it easier to understand and use application clusters. GitOps practices have made Kubernetes and native cloud applications much easier. I really think you will find that too. The tools themselves are very simple. And you can quickly reach a process of continuous improvement.</p><p>So that’s it, until the next article that will be about Pipeline as Code. Hugs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b88124de46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-for-zombies/from-zero-to-the-gitops-part-1-59b88124de46">From Zero to the GitOps — Part 1</a> was originally published in <a href="https://medium.com/devops-for-zombies">DevOps for Zombies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding k8s AutoScale]]></title>
            <link>https://medium.com/devops-for-zombies/understanding-k8s-autoscale-f8f3f90938f4?source=rss----91fddc6c6369---4</link>
            <guid isPermaLink="false">https://medium.com/p/f8f3f90938f4</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cluster-autoscaler]]></category>
            <category><![CDATA[hpa]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Yros Aguiar]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 01:48:13 GMT</pubDate>
            <atom:updated>2020-07-14T03:39:27.890Z</atom:updated>
            <content:encoded><![CDATA[<p>An HPA introduction</p><h3>What’s autoscaling?</h3><p>Auto-scaling is a way to automatically increase or decrease the number of computing resources that are being assigned to your application based on your needs at any given time. It emerged from cloud computing technology, which revolutionized the way computer resources are allocated, enabling the creation of a fully scalable server in the cloud. When an application needs more computing power, you can launch additional features on-demand and use them for as long as you want.</p><h3>What’s the HPA?</h3><p>HPA or Horizontal Pod Autoscaler is the autoscaling feature explained before but for Kubernetes pods. HPA offers the following advantages: economy, automatic sizing can offer longer uptime and more availability in cases where production workloads are variable and unpredictable. Automatic sizing differs from having a fixed amount of pods in that it responds to actual usage patterns and therefore reduces the potential disadvantage of having few or many pods for the traffic load. For example, if traffic is usually less at midnight, a static scale solution can schedule some pods to sleep at night, on the other hand, it can better handle unexpected traffic spikes.</p><h3>Requirements for HPA</h3><h3>1. Metrics Server</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EPf8NQd7aq74X8Mj" /></figure><blockquote><a href="https://github.com/kubernetes-sigs/metrics-server">https://github.com/kubernetes-sigs/metrics-server</a></blockquote><p>Metrics Server is a scalable, efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.</p><p>Metrics Server collects resource metrics from Kubelets and exposes them in Kubernetes API server through <a href="https://github.com/kubernetes/metrics">Metrics API</a> for use by <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/">Horizontal Pod Autoscaler</a> and <a href="https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler">Vertical Pod Autoscaler</a>. Metrics API can also be accessed by kubectl top, making it easier to debug autoscaling pipelines.</p><p>Metrics Server is not meant for non-autoscaling purposes. For example, don’t use it to forward metrics to monitoring solutions, or as a source of monitoring solution metrics.</p><p><strong>Metrics Server Installation:</strong></p><pre>kubectl apply -f <a href="https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.6/components.yaml">https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.6/components.yaml</a></pre><p><strong>Installation for KOPS:</strong></p><p>If you are using the kops to manager your cluster, you need to enable a specific configuration to enable the metrics-sever:</p><blockquote><a href="https://github.com/kubernetes/kops/tree/master/addons/metrics-server">https://github.com/kubernetes/kops/tree/master/addons/metrics-server</a></blockquote><p><strong>Validate Metrics-Server installation:</strong></p><p>After install metrics server the kubectl top command will be available on the cluster to use, this command gets the current metrics of the pods and nodes, if the command not working, review the metrics server installation.</p><blockquote><em>kubectl top node</em></blockquote><blockquote><em>kubectl top pod</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*svV7QpJRwHa9VAVstUPBfw.png" /></figure><h3>2. Cluster Auto-Scaler</h3><p>When the HPA controller increases the number of pod replicas, we need to have several nodes (resources) that support these new replicas, the cluster auto-scaler is responsible to increase the number of nodes to supports this demand or decrease the number of nodes when the pods are subtilized.</p><p>Cluster Autoscaler is a tool that automatically adjusts the size of the Kubernetes cluster when one of the following conditions is true:</p><ul><li>some pods failed to run in the cluster due to insufficient resources,</li><li>there are nodes in the cluster that have been underutilized for an extended period and their pods can be placed on other existing nodes.</li></ul><blockquote><a href="https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler">https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*UFLnLvGXFaSG_wBG" /></figure><h4>Cluster Auto-Scaler Installation:</h4><p>Supported cloud providers:</p><ul><li>GCE <a href="https://kubernetes.io/docs/concepts/cluster-administration/cluster-management/">https://kubernetes.io/docs/concepts/cluster-administration/cluster-management/</a></li><li>GKE <a href="https://cloud.google.com/container-engine/docs/cluster-autoscaler">https://cloud.google.com/container-engine/docs/cluster-autoscaler</a></li><li>AWS <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md</a></li><li>Azure <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/azure/README.md">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/azure/README.md</a></li><li>Alibaba Cloud <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/alicloud/README.md">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/alicloud/README.md</a></li><li>OpenStack Magnum <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/magnum/README.md">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/magnum/README.md</a></li><li>DigitalOcean <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/digitalocean/README.md">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/digitalocean/README.md</a></li></ul><p><strong>Validate Cluster Auto-scaler Installation:</strong></p><p>Create a deployment and increase the number of replicas to more than resources available, if it’s working the cluster auto-scaler will create new nodes, decrease the number of replicas, and after a time the nodes will be removed.</p><h3>3. Configure the Resources Requests/Limits and Liveness/Readiness Probe</h3><blockquote>Is very important to configure the resources requests and limits for your application, because the HPA is based on the CPU percentage usage. <a href="https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/">https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/</a></blockquote><blockquote>Is very important to configure the livenesss and readiness probe, is important because the HPA is based on the running pods to set a new desired if the pods are up but the applications are not running the HPA can do problems. <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/">https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/</a></blockquote><h3>4. Understanding the complete flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/0*d-LMnvOq16QCo4-r" /></figure><ol><li>Metrics server takes the aggregated metrics from the current pods and sends them to the kubernetes API when requested</li><li>The HPA controller checks every 15 seconds by default, and if the values fall within the rule determined in the HPA it increases or decreases the number of pods</li><li>In the case of scale-up, the kubernetes scheduler will allocate the pods in the nodes that have available resources</li><li>If you don’t have any resources available, the cluster auto-scaler will check that you don’t have any resources available and will increase the number of nodes needed to supply the pods that are currently scheduled.</li><li>If the rule is scaledown, the HPA will decrease the number of replicas</li><li>The cluster auto-scaler cluster verifying that it has little use of nodes reallocates the pods that can be relocated to other nodes and remove the nodes (scale-down).</li></ol><h3>Horizontal Pod Auto-Scaler</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H_TuFHUKQjDzsnjk" /></figure><blockquote><a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/">https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/</a></blockquote><p>HPA is used to automatically scale the number of pods on deployments, replicasets, statefulsets or a set of them, based on observed usage of CPU, Memory, or using custom-metrics. Automatic scaling of the horizontal pod does not apply to objects that cannot be scaled, for example, DaemonSets.</p><p>The Horizontal Pod Autoscaler is implemented as a control loop, with a period controlled by the — horizontal-pod-autoscaler-sync-period flag of the controller manager (with a default value of 15 seconds). During each period, the controller manager consults resource usage based on the metrics specified in each HorizontalPodAutoscaler definition. The controller manager obtains metrics from the Resource Metrics API (for resource metrics per pod) or the Custom Metrics API (for all other metrics).</p><p>The HPA does this operation below to calculate the number of desired replicas:</p><blockquote>desiredReplicas = ceil[currentReplicas * ( currentMetricValue / desiredMetricValue )]</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5zYNBt7tkGcRV6_3" /></figure><h4>The HPA Manifest:</h4><pre><strong>apiVersion</strong>: autoscaling/v2beta2<br><strong>kind</strong>: HorizontalPodAutoscaler<br><strong>metadata</strong>:<br>  <strong>name</strong>: php-apache<br><strong>spec</strong>:<br>  <strong>scaleTargetRef</strong>:<br>    <strong>apiVersion</strong>: apps/v1<br>    <strong>kind</strong>: Deployment<br>    <strong>name</strong>: php-apache<br>  <strong>minReplicas</strong>: 1<br>  <strong>maxReplicas</strong>: 10<br>  <strong>metrics</strong>:<br>  - <strong>type</strong>: Resource<br>    <strong>resource</strong>:<br>      <strong>name</strong>: cpu<br>      <strong>target</strong>:<br>        <strong>type</strong>: Utilization<br>        <strong>averageUtilization</strong>: 50</pre><p>In this example, we scale up the number of replicas on the deployment php-apache when the CPU average of the all running pods of this application is equal or higher than 50%, and decrease the number of the replicas when the CPU Average is less than 50%.</p><p><strong>When we use the HPA we need to remove the number of replicas of the deployment, pod, replicaset. Because the number of replicas is set by the HPA Controller.</strong></p><p>For scale using the kubectl:</p><blockquote>kubectl autoscale deployment php-apache — cpu-percent=50 — min=1 — max=10</blockquote><p>For verifying the HPA:</p><blockquote>kubectl get hpa php-apache</blockquote><p>For describing the HPA:</p><blockquote>kubectl describe hpa php-apache</blockquote><h3>TroubleShooting:</h3><blockquote>If the kubectl get hpa command show a status <strong>unknow</strong>, we need to verify the metrics-server, because the HPA controller cannot getting the metrics</blockquote><blockquote>If the pods don’t scale-up, if the kubectl describe pods show the status <strong>FailedScheduling nodes not available</strong>, we need to verify the Cluster-Autoscaler.</blockquote><h3>References:</h3><ul><li><a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/">HorizontalPodAutoscaler Walkthrough</a></li><li><a href="https://github.com/kubernetes-sigs/metrics-server">GitHub - kubernetes-sigs/metrics-server: Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.</a></li><li><a href="https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler">autoscaler/cluster-autoscaler at master · kubernetes/autoscaler</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8f3f90938f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-for-zombies/understanding-k8s-autoscale-f8f3f90938f4">Understanding k8s AutoScale</a> was originally published in <a href="https://medium.com/devops-for-zombies">DevOps for Zombies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS VPC Peering for dummies]]></title>
            <link>https://medium.com/devops-for-zombies/aws-vpc-peering-for-dummies-ab93c3eb2cb2?source=rss----91fddc6c6369---4</link>
            <guid isPermaLink="false">https://medium.com/p/ab93c3eb2cb2</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[vpc]]></category>
            <category><![CDATA[vpc-peering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Yros Aguiar]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 13:49:23 GMT</pubDate>
            <atom:updated>2020-07-12T14:35:21.302Z</atom:updated>
            <content:encoded><![CDATA[<p>understanding a little bit about VPC Peering</p><h3>What’s the problem to solve?</h3><p>Developers need to delivery the applications, few times think deep about operations, network and security layer on infrastructure, I worked in some companies that Developers cared of the cloud environment and a common mistake was created servers and databases and publish these servers using the Internet, when you create a backend server(Database, Mongo, ElasticSearch) published trough the Public IP address, open a security risk and if the application that consumes these services connect to it using the public IP will have high latency because the communication is through the limited internet bandwidth. A Common case of this problem is when the servers are distributed in multiples regions or the same region using different VPCs.</p><p>In the image below, we can see the wrong way to connect to another service, because the package out to the Internet and going again to the Internal network.</p><p><strong>Wrong-way</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*G3WhM1xc1CZQvsZW7qgAGg.png" /></figure><h3>Why do we need to create VPC peerings?</h3><p>The AWS VPC peering as other services like VPC Endpoint and Transit Gateway solve this problem, in this post I will talk about VPC Peering, as soon will create articles about VPC Endpoints and Transit Gateway. The VPC peering create a connection between two VPCs, this connection is private, so all traffic is through the internal AWS network, using VPC peering we can pair different VPCs in the same or another region. The requirement to create this connection is, these VPCs can’t use the same network address because is not possible to route the packages between to different network that use the same IP range.</p><p><strong>VPC Peering way:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*R2w1FZbv16lGiEeyoxIw7w.png" /></figure><p>Using the VPC peering we can create an internal and more secure communication between two VPCs on the same or different regions and same or different AWS Account, we can close a connection between your VPC and the Partner or Customer VPC for example.</p><h3>Use Cases:</h3><ul><li>Connect two different VPCs in the same regions</li><li>Connect two VPCs on different regions (Inter-Region)</li><li>Connect two VPCs on different accounts (Cross Accounts)</li></ul><h3>The costs:</h3><p>There is no charge for setting up or running a <strong>VPC peering</strong> connection. Data transferred across <strong>peering</strong> connections is charged at $0.01/GB for send and receive, regardless of the Availability Zones involved</p><h3>How we can create a VPC Peering?</h3><ul><li>We need a requester VPC</li><li>We need an accepter VPC</li><li>We need to configure the Route Table for the Accepter VPC</li><li>We need to configure the Route Table for the Requester VPC</li><li>We need to configure the Security Group for the service that will allow the communications from another VPC</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*j8JKQTn_0vSWrCqLCPCfVw.jpeg" /></figure><p><strong>To request a VPC peering connection with a VPC in another account in the same region</strong></p><ol><li>Open the Amazon VPC console at <a href="https://console.aws.amazon.com/vpc/">https://console.aws.amazon.com/vpc/</a>.</li><li>In the navigation pane, choose <strong>Peering Connections</strong>, <strong>Create Peering Connection</strong>.</li><li>Configure the information as follows, and choose to <strong>Create Peering Connection</strong> when you are done:</li></ol><ul><li><strong>Peering connection name tag</strong>: You can optionally name your VPC peering connection. Doing so creates a tag with a key and a value that you specify. This tag is only visible to you; the owner of the peer VPC can create their own tags for the VPC peering connection.</li><li><strong>VPC (Requester)</strong>: Select the VPC in your account with which to create the VPC peering connection.</li><li><strong>Account</strong>: Choose <strong>Another account</strong>.</li><li><strong>Account ID</strong>: Enter the AWS account ID of the owner of the accepter VPC.</li><li><strong>VPC (Accepter)</strong>: Enter the ID of the VPC with which to create the VP peering connection.</li></ul><p>4. In the confirmation dialog box, choose <strong>OK</strong>.</p><p><strong>To request a VPC peering connection with a VPC in another account in a different region</strong></p><ol><li>Open the Amazon VPC console at <a href="https://console.aws.amazon.com/vpc/">https://console.aws.amazon.com/vpc/</a>.</li><li>In the navigation pane, choose <strong>Peering Connections</strong>, <strong>Create Peering Connection</strong>.</li><li>Configure the information as follows, and choose <strong>Create Peering Connection</strong> when you are done:</li></ol><ul><li><strong>Peering connection name tag</strong>: You can optionally name your VPC peering connection. Doing so creates a tag with a key of Name and a value that you specify. This tag is only visible to you; the owner of the peer VPC can create their own tags for the VPC peering connection.</li><li><strong>VPC (Requester)</strong>: Select the VPC in your account with which to create the VPC peering connection.</li><li><strong>Account</strong>: Choose <strong>Another account</strong>.</li><li><strong>Account ID</strong>: Enter the AWS account ID of the owner of the accepter VPC.</li><li><strong>Region</strong>: Choose <strong>Another region</strong>, select the region in which the accepter VPC resides.</li><li><strong>VPC (Accepter)</strong>: Enter the ID of the VPC with which to create the VPC peering connection</li></ul><h3>Accepting a VPC peering connection</h3><p>A VPC peering connection that’s in the pending-acceptance state must be accepted by the owner of the accepter VPC to be activated. You cannot accept a VPC peering connection request that you&#39;ve sent to another AWS account. If you are creating a VPC peering connection in the same AWS account, you must both create and accept the request yourself.</p><p>If the VPCs are in different regions, the request must be accepted in the region of the accepter VPC.</p><p><strong>Important</strong></p><p>Do not accept VPC peering connections from unknown AWS accounts. A malicious user may have sent you a VPC peering connection request to gain unauthorized network access to your VPC. This is known as peer phishing. You can safely reject unwanted VPC peering connection requests without any risk of the requester gaining access to any information about your AWS account or your VPC. For more information, see <a href="https://docs.aws.amazon.com/vpc/latest/peering/reject-vpc-peering-connection.html">Rejecting a VPC peering connection</a>. You can also ignore the request and let it expire; by default, requests expire after 7 days.</p><p><strong>To accept a VPC peering connection</strong></p><ol><li>Open the Amazon VPC console at <a href="https://console.aws.amazon.com/vpc/">https://console.aws.amazon.com/vpc/</a>.</li><li>Use the region selector to choose the region of the accepter VPC.</li><li>In the navigation pane, choose <strong>Peering Connections</strong>.</li><li>Select the pending VPC peering connection (the status is pending-acceptance), and choose <strong>Actions</strong>, <strong>Accept Request</strong>.</li><li><strong>Note: </strong>If you cannot see the pending VPC peering connection, check the region. An inter-region peering request must be accepted in the region of the accepter VPC.</li><li>In the confirmation dialog box, choose <strong>Yes, Accept</strong>. A second confirmation dialog displays; choose to <strong>Modify my route tables now</strong> to go directly to the route tables page.</li></ol><p>Now that your VPC peering connection is active, you must add an entry to your VPC route table to enable traffic to be directed to the peer VPC. For more information.</p><h3>Configuring routes for a VPC peering connection</h3><ol><li>Open the Amazon VPC console at <a href="https://console.aws.amazon.com/vpc/">https://console.aws.amazon.com/vpc/</a>.</li><li>In the navigation pane, choose <strong>Route Tables</strong>.</li><li>Select the route table that’s associated with the subnet in which your instance resides.</li><li><strong>Note: </strong>If you do not have a route table associated with that subnet, select the main route table for the VPC, as the subnet then uses this route table by default.</li><li>Choose <strong>Routes</strong>, <strong>Edit</strong>, <strong>Add Route</strong>.</li><li>For <strong>Destination</strong>, enter the IPv4 address range to which the network traffic in the VPC peering connection must be directed. You can specify the entire IPv4 CIDR block of the peer VPC, a specific range, or an individual IPv4 address, such as the IP address of the instance with which to communicate. For example, if the CIDR block of the peer VPC is 10.0.0.0/16, you can specify a portion10.0.0.0/28, or a specific IP address 10.0.0.7/32.</li><li>Select the VPC peering (pcx) connection from <strong>Target</strong>, and then choose <strong>Save</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/1*97gbCRatvVresUnvF7-xiQ.png" /></figure><h3>Allow access from the source communication VPC on the Security Group of the Service</h3><p>We need to add the entry for the new network address on the security group of the services that you permit access from another VPC.</p><ol><li>Open the Amazon EC2 console at <a href="https://console.aws.amazon.com/ec2/">https://console.aws.amazon.com/ec2/</a>.</li><li>In the navigation pane, choose <strong>Security Groups</strong>.</li><li>In the list, select the security group and choose <strong>Actions</strong>, <strong>Edit inbound rules</strong>.</li><li>Choose <strong>Add rule</strong> and do the following.</li><li>For <strong>Type</strong>, choose the type of protocol to allow.</li></ol><ul><li>If you choose a custom TCP or UDP protocol, you must manually enter the port range to allow.</li><li>If you choose a custom ICMP protocol, you must choose the ICMP type name from <strong>Protocol</strong>, and, if applicable, the code name from <strong>Port range</strong>.</li><li>If you choose any other type, the protocol and port range are configured automatically.</li></ul><p>6. For <strong>Source</strong>, do one of the following.</p><ul><li>Choose <strong>Custom</strong> and then enter an IP address in CIDR notation, a CIDR block, another security group, or a prefix list from which to allow inbound traffic.</li><li>Choose <strong>Anywhere</strong> to allow all inbound traffic of the specified protocol to reach your instance. This option automatically adds the 0.0.0.0/0 IPv4 CIDR block as an allowed source. This is acceptable for a short time in a test environment, but it&#39;s unsafe for production environments. In production, authorize only a specific IP address or range of addresses to access your instance.</li><li>If your security group is in a VPC that’s enabled for IPv6, this option automatically adds a second rule for IPv6 traffic (::/0).</li><li>Choose custom address, add VPC network address to allow inbound traffic from the other VPC.</li></ul><p>7. For <strong>Description</strong>, optionally specify a brief description for the rule.</p><p>8. Choose <strong>Preview changes</strong>, <strong>Save rules</strong>.</p><p>Okay, now you can already create peering connections, I hope I helped, in the next articles I will talk about VPC Endpoints and VPC transit gateways that are methods of connections between different VPCs and VPC services.</p><h3>Terraform:</h3><h3>Example Usage</h3><pre>resource &quot;aws_vpc_peering_connection&quot; &quot;foo&quot; {<br>  peer_owner_id <strong>=</strong> &quot;${var.peer_owner_id}&quot;<br>  peer_vpc_id   <strong>=</strong> &quot;${aws_vpc.bar.id}&quot;<br>  vpc_id        <strong>=</strong> &quot;${aws_vpc.foo.id}&quot;<br>}</pre><p>Basic usage with connection options:</p><pre>resource &quot;aws_vpc_peering_connection&quot; &quot;foo&quot; {<br>  peer_owner_id <strong>=</strong> &quot;${var.peer_owner_id}&quot;<br>  peer_vpc_id   <strong>=</strong> &quot;${aws_vpc.bar.id}&quot;<br>  vpc_id        <strong>=</strong> &quot;${aws_vpc.foo.id}&quot;</pre><pre>accepter {<br>    allow_remote_vpc_dns_resolution <strong>=</strong> <strong>true</strong><br>  }</pre><pre>requester {<br>    allow_remote_vpc_dns_resolution <strong>=</strong> <strong>true</strong><br>  }<br>}</pre><p>Basic usage with tags:</p><pre>resource &quot;aws_vpc_peering_connection&quot; &quot;foo&quot; {<br>  peer_owner_id <strong>=</strong> &quot;${var.peer_owner_id}&quot;<br>  peer_vpc_id   <strong>=</strong> &quot;${aws_vpc.bar.id}&quot;<br>  vpc_id        <strong>=</strong> &quot;${aws_vpc.foo.id}&quot;<br>  auto_accept   <strong>=</strong> <strong>true</strong></pre><pre>tags <strong>=</strong> {<br>    Name <strong>=</strong> &quot;VPC Peering between foo and bar&quot;<br>  }<br>}</pre><pre>resource &quot;aws_vpc&quot; &quot;foo&quot; {<br>  cidr_block <strong>=</strong> &quot;10.1.0.0/16&quot;<br>}</pre><pre>resource &quot;aws_vpc&quot; &quot;bar&quot; {<br>  cidr_block <strong>=</strong> &quot;10.2.0.0/16&quot;<br>}</pre><p>Basic usage with region:</p><pre>resource &quot;aws_vpc_peering_connection&quot; &quot;foo&quot; {<br>  peer_owner_id <strong>=</strong> &quot;${var.peer_owner_id}&quot;<br>  peer_vpc_id   <strong>=</strong> &quot;${aws_vpc.bar.id}&quot;<br>  vpc_id        <strong>=</strong> &quot;${aws_vpc.foo.id}&quot;<br>  peer_region   <strong>=</strong> &quot;us-east-1&quot;<br>}</pre><pre>resource &quot;aws_vpc&quot; &quot;foo&quot; {<br>  provider   <strong>=</strong> &quot;aws.us-west-2&quot;<br>  cidr_block <strong>=</strong> &quot;10.1.0.0/16&quot;<br>}</pre><pre>resource &quot;aws_vpc&quot; &quot;bar&quot; {<br>  provider   <strong>=</strong> &quot;aws.us-east-1&quot;<br>  cidr_block <strong>=</strong> &quot;10.2.0.0/16&quot;<br>}</pre><p><strong>References:</strong></p><ul><li><a href="https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html">What is VPC peering?</a></li><li><a href="https://www.terraform.io/docs/providers/aws/r/vpc_peering_connection.html">AWS: aws_vpc_peering_connection - Terraform by HashiCorp</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab93c3eb2cb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-for-zombies/aws-vpc-peering-for-dummies-ab93c3eb2cb2">AWS VPC Peering for dummies</a> was originally published in <a href="https://medium.com/devops-for-zombies">DevOps for Zombies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 steps for achieving the CKA certification]]></title>
            <link>https://medium.com/devops-for-zombies/10-steps-to-achieve-the-cka-certification-6f2ad57887ab?source=rss----91fddc6c6369---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f2ad57887ab</guid>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[certification-exam]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cka]]></category>
            <dc:creator><![CDATA[Yros Aguiar]]></dc:creator>
            <pubDate>Fri, 10 Jul 2020 15:40:41 GMT</pubDate>
            <atom:updated>2020-07-17T00:35:09.199Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SihrrXQLKN9BklSNPiufew.png" /></figure><p>There are always new technologies that are well-spoken or that are on Hype, some are here to stay and others are short-lived, Kubernetes, as well as Docker, are examples of technologies that are in love with hipsters and technology enthusiasts. That is why it is very important to stay tuned in technologies that are in high demand in the market and try to update your skills to keep up with the technology changes in the area and not be out of date in the market. As I said earlier, Kubernetes has a big movement in the technology area, so thinking about updating I decide to study and take the Kubernetes certification exam because this tool is very required in the actual technology’ s scenario, I’ll try to describe in this post tips and the way to achieve the CKA certification.</p><p>The Kubernetes certification is maintained by CNCF (Cloud Native Computing Foundation).</p><p>The Exam is scheduled on CNCF site, at this date the appointment costs $300 and you have a retake if you don’t pass, the exam is online.</p><p>You need to understand the concepts, because you do not need to memorize all the documentation or even commands, a differential that makes taking the exam easier is the access to the Kubernetes documentation which is allowed at the time of the exam, so you need to at least have a conceptual understanding of what it is for each component of Kubernetes and which path to follow to configure it, knowing the way you can search about in the documentation and check what are the configuration commands necessary to achieve what the question requires.</p><p><strong>Requirements to be comfortable on your study journey is:</strong></p><ul><li>We need to know about how containers works</li><li>We need to understand concepts and basics about Network, Servers, Services, DNS, SSH, Bash, Linux, Cloud Concepts</li><li>Knowledge of the YAML language</li></ul><p><strong>Links about certification</strong></p><ul><li>Certified Kubernetes Administrator: <a href="https://www.cncf.io/certification/cka/">https://www.cncf.io/certification/cka/</a></li><li>Exam Curriculum (Topics): <a href="https://github.com/cncf/curriculum">https://github.com/cncf/curriculum</a></li><li>Candidate Handbook: <a href="https://www.cncf.io/certification/candidate-handbook">https://www.cncf.io/certification/candidate-handbook</a></li><li>Exam Tips: <a href="http://training.linuxfoundation.org/go//Important-Tips-CKA-CKAD">http://training.linuxfoundation.org/go//Important-Tips-CKA-CKAD</a></li><li>Kubernetes documentation: <a href="https://kubernetes.io/docs/home/">https://kubernetes.io/docs/home/</a></li></ul><h3>1. Create a study plan</h3><ul><li>You need to create an agenda and determinate how much hours per week you can study to achieve your goal</li><li>Organize the study agenda, 6 hours per week is a good time to study and not interfere on your other tasks, depends on your agenda, the more weekly study time you have, the faster the route to the exam will be</li><li>if you want to pass, take the study schedule very seriously because by studying the topics listed on the next topic, you will be able to take the exam without much headache</li><li>Increase the study time a few days before the exam, this strategy is better for you to review topics and accumulate experience without the risk of forgetting the topics along the time</li><li>Try to study at times that you will not be disturbed, times that avoid external interference and loss of focus. I prefer to study in the morning because it is a time that I can absorb more and I did not go through the stress of the day</li><li>I have listed some study plan tips but not all people study and learn the same way, build your study plan according to your needs and your goal of taking the exam, remember that an effort is necessary and having the commitment</li><li>If you want to buy a course, I recommend the course <a href="https://www.udemy.com/course/certified-kubernetes-administrator-with-practice-tests/">Certified Kubernetes Administrator (CKA) with Practice Tests</a> on Udemy platform, this course covers all topics</li></ul><h3>2. Study the exam topics</h3><p>I described below the exam topics, weights, and a brief description, links, and tricks for the principal concepts that you need to study to achieving CKA:</p><ol><li><strong>Core Concepts 19%</strong></li></ol><ul><li>Cluster Architecture</li><li>ETCD Basic concepts</li><li>Kube API Server</li><li>Kube Controller Manager</li><li>Kube Scheduler</li><li>Kubelet</li><li>Kube Proxy</li><li>Pods</li><li>ReplicaSets</li><li>Deployments</li><li>Namespaces</li><li>Services</li><li>Kubectl command</li></ul><p>2. <strong>Installation, Configuration &amp; Validation 12%</strong></p><ul><li>Install Kubernetes using kubeadm</li><li>Install Kubernetes using the Hardway mode (optional but recommended to learn)</li><li>Tests the cluster, analyze</li></ul><p><strong>3. Application Lifecycle Management 8%</strong></p><ul><li>Rolling Updates and Rollbacks</li><li>Commands and arguments</li><li>Configmaps</li><li>Secrets</li><li>Scale</li><li>Multi Container</li><li>Init containers</li></ul><p><strong>4. Networking 11%</strong></p><ul><li>Understand Switching and Routing concepts</li><li>DNS Concepts</li><li>CoreDNS</li><li>Network Namespaces</li><li>Docker Networking</li><li>CNI</li><li>Ingress</li></ul><p><strong>5. Scheduling 5%</strong></p><ul><li>Manual Scheduling</li><li>Labels and Selectors</li><li>Taints and Tolerations</li><li>Node Selectors</li><li>Node Affinity</li><li>Resource Limits</li><li>DaemonSets</li><li>Static Pods</li></ul><p><strong>6. Security 12%</strong></p><ul><li>TLS Basics and Certificates</li><li>Authentication</li><li>kubeconfig</li><li>API Groups</li><li>RBAC</li><li>Cluster Roles and Role Bindings</li><li>Security Contexts</li><li>Network Policy</li></ul><p><strong>7. Logging / Monitoring 5%</strong></p><ul><li>Monitor cluster components</li><li>Application Logs</li><li>kubectl top command</li></ul><p><strong>8. Storage 7%</strong></p><ul><li>Understand storage in docker</li><li>Volumes</li><li>PV (Persistent Volumes)</li><li>PVC (Persistent Volume Claims)</li><li>Configure PVC on applications</li></ul><p><strong>9. Cluster Maintenance 11%</strong></p><ul><li>OS Upgrades</li><li>Cluster Upgrade Process</li><li>Backup and Restore</li><li>ETCDCTL command</li></ul><p><strong>10. Troubleshooting 10%</strong></p><ul><li>Application failure</li><li>Control Plane Failure</li><li>Worker Node failure</li><li>Network issues</li></ul><p><strong>11. Other</strong></p><ul><li>JSON Path</li><li>Kubectl advanced</li></ul><h3>3. Install Kubernetes and create an environment for study</h3><ul><li>We need to create a minimum a cluster with 3 nodes (1 master and 2 worker nodes) to tests and run commands and examples</li><li>You can use a Cloud Provider (AWS. GCP, Azure) to create a remote environment or any virtualized software (VirtualBox, VMWare workstation) to create a local environment on your machine</li><li>This step is very important to simulate the documentation examples and understand about Kubernetes</li><li>You need to install kubernetes using the kubeadm</li><li>You can install using the hard way mode to understand better all components and how these works</li><li>This environment will be used when you’ve read the docs and simulate and run the examples</li></ul><h3>4. Run the examples and simulate troubleshooting scenarios on this environment created before</h3><ul><li>Run the documentation examples about all topics listed on step 2 of this post.</li><li>Simulate errors and problems on this environment to understand how you can solve problems on the applications or in the cluster</li></ul><h3>5. Do exam mocks</h3><ul><li><a href="https://github.com/alijahnas/CKA-practice-exercises">https://github.com/alijahnas/CKA-practice-exercises</a></li><li><a href="https://github.com/stretchcloud/cka-lab-practice">https://github.com/stretchcloud/cka-lab-practice</a></li><li><a href="https://medium.com/bb-tutorials-and-thoughts/practice-enough-with-these-questions-for-the-ckad-exam-2f42d1228552">https://medium.com/bb-tutorials-and-thoughts/practice-enough-with-these-questions-for-the-ckad-exam-2f42d1228552</a></li><li>On the internet has a lot of mock exams paid, you can buy one of these exams to training your knowledge. But if you don’t want to spend your money, you can found examples of the exam questions available on Github and blogs for free</li></ul><h3>6. Schedule the exam</h3><ul><li>The cost is $300 and includes one free retake.</li><li>Look for discount coupons or if the CNCF has any promotions/exam vouchers before you schedule. You can save your money.</li><li>I scheduled the exam for a monday morning, so I had a weekend to review the topics and focus on the subjects that had the most difficulty.</li><li>I scheduled the exam before starting the study, that way I was forced to study and fulfill the goal, it worked for me, but you should make this decision</li></ul><h3>7. Understand the Exam</h3><ul><li>The exam has 24 questions and you have 3 hours to finalize</li><li>The questions are hands-on, you have a shell to execute the commands and you need to save commands outputs some times</li><li>Pay attention to the time for complete, because if you have difficulty on any question, mark the question for review and skip to return posteriorly</li><li>You need to install a chrome extension recommended by the exam provider</li><li>Close all windows, leave only the navigator window on the exam page and another tab on the documentation page</li><li>You cannot use headphones or any devices, just the computer that you access the exam site and Kubernetes documentation, your desk needs to be clean, at the time of the exam a chat is opened and a person checks these points together with you, your screen is shared at the time of the exam, that person from the exam center will pass all instructions by chat</li><li>Pay attention to the k8s contexts, because the exam has a lot of contexts, for each question the context will be specified, take a look at this point.</li></ul><h3>8. Review the topics that you have more difficulty</h3><ul><li>Review the topics that you have more difficulty and have the highest weight</li><li>Execute commands and create objects in the kubernetes to memorize</li></ul><h3>9. Keep Calm</h3><ul><li>Stay calm, plan a way to quickly search the documentation, memorize keywords and topics in the documentation to make it easier to search on the day of the exam</li><li>The exam is not so complicated but it takes time, stays calm, by having the documentation you can do anything related to Kubernetes, it is important to know the paths and have knowledge of the operation to be more accurate in the research</li></ul><h3>10. Do the Exam</h3><ul><li>Since the exam requires concentrated effort for 3 hours and is straining both physically and mentally, I’d the advice to <strong><em>schedule the exam during morning hours.</em></strong></li><li>Create multiples alias on the exam bash: e.q: # alias kl=kubectl logs or #alias kg=kubectl get, using alias you can save your time, is better to type less.</li><li>Pay attention to the exam time, if you are wasting a lot of time on an issue check for review and skip to the next question</li><li>You can have a bottle of water on your desk, as long as it has no labels and is transparent</li><li>The exam result is sent within 72 hours of completion.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2ad57887ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-for-zombies/10-steps-to-achieve-the-cka-certification-6f2ad57887ab">10 steps for achieving the CKA certification</a> was originally published in <a href="https://medium.com/devops-for-zombies">DevOps for Zombies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>