The latest articles on DEV Community by Mezbaur Rahman (@myjanala). https://dev.to/myjanala https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F347424%2F905e3fc3-1654-4964-bcbf-d3486cc35b83.png https://dev.to/myjanala en Mezbaur Rahman Sat, 19 Feb 2022 11:01:42 +0000 https://dev.to/myjanala/code-organisation-strategy-for-gitops-3jh1 https://dev.to/myjanala/code-organisation-strategy-for-gitops-3jh1 <p>One of the most often question is: Is GitOps just another way of doing CI/CD? The answer to this question is simply NO. GitOps only takes care of the CD part, the delivery part. To achieve this, one would think about organising the repo structure. So, you would maintain 3 different repos to main:</p> <ul> <li>GitOps Fleet </li> <li>Project Deployment </li> <li>Project/App Source</li> </ul> <p><strong>GitOps Fleet Repository</strong> to manage organisation wide deployments to Kubernetes with FluxCD. This repository would contain</p> <ul> <li>Cluster Configuration </li> <li>Cluster Wide Infrastructure Components e.g. Ingress Controllers, Repository Secrets etc.</li> <li>Project onboarding configurations aka. tenants spec.</li> </ul> <p><strong>Project Deployment Repository</strong> (tenant). This repository would contain k8s manifests for </p> <ul> <li>infra </li> <li>app and </li> <li>pipelines/tekton </li> </ul> <p>The code could be either </p> <ul> <li>Helm charts source code</li> <li>YAML Manifests as either <ul> <li>Plain YAML</li> <li>Kustomize Overlays</li> </ul> </li> </ul> <p><strong>Project/App Source Repository</strong></p> <ul> <li>Application Source Code</li> <li>Contains Source Code + Dockerfile etc. </li> </ul> <p>Now, the following diagram shows the code organisation strategy described above, above with a clear separation of the CI and CD stages.</p> <p><a href="https://res.cloudinary.com/practicaldev/image/fetch/s--v6F0V8iK--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fhdy13fzjte0c093t732.jpeg" class="article-body-image-wrapper"><img src="https://res.cloudinary.com/practicaldev/image/fetch/s--v6F0V8iK--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fhdy13fzjte0c093t732.jpeg" alt="Image description" width="880" height="549"></a></p> <p>note: I have taken encouragement from this <a href="https://github.com/devopsfoo/flux-fleet/tree/02-onboard-instavote">example</a>. </p> gitops Mezbaur Rahman Sun, 16 Jan 2022 12:07:13 +0000 https://dev.to/myjanala/get-to-know-a-devops-engineer-me-32a https://dev.to/myjanala/get-to-know-a-devops-engineer-me-32a <p>Hello, </p> <p><a href="https://www.youtube.com/watch?v=hpHVE1CH1IU&amp;t=1191s">Get to know a DevOps Engineer - Mezbaur Rahman</a> is my first ever and I must admit, not very good attempt to give a talk about being a DevOps engineer on youtube on a session arranged by <a href="https://codebar.io/">Codebar</a>. A huge thanks to <a href="https://twitter.com/kimberleycook91?lang=en">Kimberley</a> for giving me the opportunity, </p> <p>I would appreciate comments, suggestions or even any criticism. </p> devops