<?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[Stories by Ewere Diagboya on Medium]]></title>
        <description><![CDATA[Stories by Ewere Diagboya on Medium]]></description>
        <link>https://medium.com/@nimboya?source=rss-66218173572e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mAJAsmCMhK8tNlMUuF5xwA.jpeg</url>
            <title>Stories by Ewere Diagboya on Medium</title>
            <link>https://medium.com/@nimboya?source=rss-66218173572e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:48:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nimboya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Farewell to Medium, Hello to EDT (ewere.tech)]]></title>
            <link>https://medium.com/mycloudseries/farewell-to-medium-hello-to-edt-ewere-tech-479de961f736?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/479de961f736</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Wed, 11 Jun 2025 16:36:54 GMT</pubDate>
            <atom:updated>2025-06-11T16:36:54.370Z</atom:updated>
            <content:encoded><![CDATA[<h3>Farewell to Medium, Hello to EDT</h3><ul><li>Medium has been a wonderful run.</li><li>I started writing in 2016</li><li>Thousands of readers globally</li><li>Some good claps on my articles</li><li>I have moved on to something more solid, long-lasting, with more possibilities than Medium</li><li>All articles here will be migrated to my new blog and will be 100% readable</li><li>The new place for my articles is <a href="http://www.ewere.tech/">www.ewere.tech</a></li><li>For all my followers, you can subscribe there at <a href="http://www.ewere.tech/subscribe">www.ewere.tech/subscribe</a></li><li>More DevOps Content and beyond are already available there</li></ul><p>Thank you and see you all there</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=479de961f736" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mycloudseries/farewell-to-medium-hello-to-edt-ewere-tech-479de961f736">Farewell to Medium, Hello to EDT (ewere.tech)</a> was originally published in <a href="https://medium.com/mycloudseries">MyCloudSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Well-Architected EKS (Kubernetes) Cluster]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/aws-well-architected-eks-kubernetes-cluster-92220c084fdf?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/1249/0*eRyZz5XwYUPHw5Oh.png" width="1249"></a></p><p class="medium-feed-snippet">Well Architected Framework for Kubernetes Workload</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/aws-well-architected-eks-kubernetes-cluster-92220c084fdf?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/aws-well-architected-eks-kubernetes-cluster-92220c084fdf?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/92220c084fdf</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Tue, 17 Dec 2024 09:32:41 GMT</pubDate>
            <atom:updated>2025-02-03T17:12:02.625Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to connect to an Amazon EC2 Instance]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/how-to-connect-to-an-amazon-ec2-instance-e05a6bd70331?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/1314/1*bdHhoYLqRjEHPd6-wa1JIw.png" width="1314"></a></p><p class="medium-feed-snippet">EC2 Connection Options</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/how-to-connect-to-an-amazon-ec2-instance-e05a6bd70331?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/how-to-connect-to-an-amazon-ec2-instance-e05a6bd70331?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e05a6bd70331</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Tue, 12 Nov 2024 04:56:43 GMT</pubDate>
            <atom:updated>2024-11-12T14:41:04.930Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Helmfile: An upgraded flow to Helm Deployment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/helmfile-an-upgraded-flow-to-helm-deployment-030030e48b63?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/600/0*88Cnj5gUmL3FFfsL" width="600"></a></p><p class="medium-feed-snippet">How to Deploy Helm with Helmfilel</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/helmfile-an-upgraded-flow-to-helm-deployment-030030e48b63?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/helmfile-an-upgraded-flow-to-helm-deployment-030030e48b63?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/030030e48b63</guid>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[yaml]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 07:01:47 GMT</pubDate>
            <atom:updated>2024-10-24T15:48:06.130Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[GitHub Actions: A Comparison between Composite Actions and Reusable Workflow]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/github-actions-a-comparison-between-composite-actions-and-reusable-workflow-9952801fe757?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/900/1*mMqx7F42NfgnCsLVyrZN8Q.png" width="900"></a></p><p class="medium-feed-snippet">A Comparison between Composite Action and Reusable Workflows</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/github-actions-a-comparison-between-composite-actions-and-reusable-workflow-9952801fe757?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/github-actions-a-comparison-between-composite-actions-and-reusable-workflow-9952801fe757?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9952801fe757</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[github-actions]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Sun, 06 Oct 2024 18:21:16 GMT</pubDate>
            <atom:updated>2024-10-08T12:20:11.352Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Single Helm Chart for All Kubernetes Deployments using ArgoCD (Mono Chart)]]></title>
            <link>https://medium.com/mycloudseries/single-helm-chart-for-all-kubernetes-deployments-using-argocd-mono-chart-e39dee186e4e?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e39dee186e4e</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[yaml]]></category>
            <category><![CDATA[deployment]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Fri, 27 Sep 2024 07:55:55 GMT</pubDate>
            <atom:updated>2026-08-23T17:23:29.962Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to stop using multiple Helm charts for application deployments</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MeQG77upWIdM1ZXKAO9tDg.png" /></figure><p>Kubernetes is doing what Linux did to the world many years ago when it took over the computing space of enterprise computing, giving everyone the power to customize and build operating systems away from Microsoft Windows and Apple’s Mac. Kubernetes is making it easier to manage containers at a large scale and improving the efficiency of applications deployed in this environment, using the right set of configurations which I described in my previous article <a href="https://medium.com/mycloudseries/how-to-deploy-a-highly-available-application-on-kubernetes-092144124aac">here</a>. When the configurations are ready to be deployed in the Kubernetes cluster, what is the most efficient way to perform this deployment and avoid DRY (Don’t Repeat Yourself)? This is a common term used in the IaC (Infrastructure as Code) world, which implies that it is important to avoid repetition when writing code. In Terragrunt, DRY is implementable due to the following features; code reuse, shared configuration, and helper functions. Can this concept be applied in Kubernetes deployments? Let’s talk about DRY in Kubernetes applications.</p><h4>DRY in Kubernetes Deployment</h4><p>In most cases when deployments are to be done to Kubernetes. There is a lot of repetition of YAML files performing very similar deployments. For example, three services need to be deployed; <em>user</em> service, <em>catalog</em> service, and <em>payment</em> services. What usually happens is a DevOps Engineer decides if they will use Helm or Kustomize or good old YAML/kubectl for the deployment. Whatever option the engineer chooses, there will be a replication of these three services. A repository containing a collection of YAML files representing the <em>user</em>, <em>catalog</em>, and <em>payment</em> services, respectively. Either a single repository is used, or multiple repositories are used, but an identical copy of the group of files needed for the deployment is created. These files include; Service, Deployment, Ingress, Secrets/ExternalSecret for a basic deployment. Which is a total of four files; namely; service.yaml deployment.yaml ingress.yaml<em> </em>externalsecrets.yaml. These files will be created in three places making it twelve files in total. The question is what is wrong with this approach? Can it be better? Can we ensure we do not repeat ourselves?</p><h4>The Problem</h4><p>The challenge with this approach, which is typically the default, is that you are essentially repeating yourself. When you examine each of the four files mentioned above, the YAML scripts inside them are almost identical, with only minor differences. This raises the question: why do we need twelve files to deploy three services when four files could be used for all three deployments?</p><p>Configurations across the repositories will require manual maintenance periodically to ensure proper alignment. Any change made to the deployment.yamlfile for one service will require a manual change to other services to maintain consistency. This process can become cumbersome and prone to errors, especially when managing updates for 200 services.</p><p>Another challenge with this approach is adding a new Kubernetes manifest can become cumbersome when services continue to grow. Say you need to add a new feature like a <a href="https://kubernetes.io/docs/tasks/run-application/configure-pdb/">PodDisriptionBudget</a> to the three services mentioned previously. It means you have to create a pdb.yamlfile three times for the three services, in different folders or repositories (depending on your structure).</p><h4>What is a Better Option</h4><p>A better option here will be to use a templating engine. The most popular templating engine for Kubernetes Manifests is <a href="https://helm.sh/">Helm</a>. The home page of Helm&#39;s website describes Helm as “the best way to find, share and use software built for Kubernetes”. Helm is a package manager who helps you package your YAML files into an entity and manages the life cycle of applications&#39; deployments. Helm can deploy to a Kubernetes cluster and roll back deployment to a previous version. It uses a hash in the releases to track release history, thereby having the ability to roll back to earlier releases.</p><p>The template feature in Helm makes it stand out in all the options for deploying to Kubernetes. With templating, you do not need to repeat yourself when creating an identical deployment package. All you need to do is make a boilerplate package and use it to deploy multiple services. In most cases, only a few parts of a Helm package are parameterized. The most common is the image stage in the deployment.yaml file, which is where we need to change the image tag for every new deployment. But Helm can be used for much more than just updating the image tag to the latest Docker image that has been built. Helm has a lot of <a href="https://helm.sh/docs/chart_template_guide/function_list/">functions</a> that can be used for string manipulation, date and time, math operations, logic, flow control, checking Kubernetes API version compatibilities, and many more. Armed with these features of Helm more can be done with Helm than updating just the image tag for a deployment. The next section is a basic example of using some of the functionalities of Helm to script what I will call the “Ultimate Helm Chart” or “Mono Chart”.</p><h4>The Ultimate Helm Chart</h4><p>The following chart is a sample of what a Mono Chart looks like. It contains the following standard features a <a href="https://medium.com/mycloudseries/how-to-deploy-a-highly-available-application-on-kubernetes-092144124aac">production-grade Kubernetes</a> deployment should have at the bare minimum. It has the common parameters that need changes across application services parameterized across different Kubernetes objects used; <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/">Deployment</a>, <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/">Ingress</a>, <a href="https://kubernetes.io/docs/tasks/run-application/configure-pdb/">PodDisruptionBudget</a>, <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/">HorizontalPodAutoscaler</a>, <a href="https://kubernetes.io/docs/concepts/services-networking/service/">Service</a>, <a href="https://external-secrets.io/latest/">ExternalSecret</a>. A few of the objects and the changes made shall be described, the full chart is published here: <a href="https://github.com/MyCloudSeries/mono-chart">https://github.com/MyCloudSeries/mono-chart</a>.</p><p><strong>Deployment</strong></p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: &quot;{{ .Values.service_name }}-{{ .Values.environment }}&quot;<br>spec:<br>  selector:<br>    matchLabels:<br>      app: &quot;{{ .Values.service_name }}-{{ .Values.environment }}&quot;<br>  replicas: {{ .Values.replicas | default 1 }}<br>  strategy:<br>    type: RollingUpdate<br>    rollingUpdate:<br>      maxSurge: 1<br>      maxUnavailable: 0<br>  template:<br>    metadata:<br>      labels:<br>        app: &quot;{{ .Values.service_name }}-{{ .Values.environment }}&quot;<br>    spec:<br>      affinity:<br>        podAntiAffinity:<br>          requiredDuringSchedulingIgnoredDuringExecution:<br>          - labelSelector:<br>              matchLabels:<br>                app: &quot;{{ .Values.service_name }}-{{ .Values.environment }}&quot;<br>            topologyKey: &quot;kubernetes.io/hostname&quot;<br>      terminationGracePeriodSeconds: 70<br>      containers:<br>      - name: &quot;{{ .Values.service_name }}-{{ .Values.environment }}&quot;<br>        image: &quot;{{ .Values.imageuri }}/{{ .Values.service_name }}-{{ .Values.environment }}:{{ .Values.image_tag }}&quot;<br>        securityContext:<br>          allowPrivilegeEscalation: false<br>        resources:<br>          requests:<br>            memory: {{ .Values.memory_limit | default &quot;200Mi&quot; }}<br>            cpu: {{ .Values.cpu_limit | default &quot;50m&quot; }}<br>          limits:<br>            memory: {{ .Values.memory_limit | default &quot;200Mi&quot; }}<br>        ports:<br>        - name: app-port<br>          containerPort: {{ .Values.container_port | default 80 }}<br>        lifecycle: <br>          preStop: <br>            exec: <br>              command: [&quot;/bin/sh&quot;, &quot;-c&quot;, &quot;sleep 50&quot;]<br>        livenessProbe:<br>          httpGet:<br>            port: app-port<br>            path: {{ .Values.health_check_path }}<br>          periodSeconds: 60<br>          initialDelaySeconds: 10<br>        readinessProbe:<br>          httpGet:<br>            port: app-port<br>            path: {{ .Values.health_check_path }}<br>          periodSeconds: 60<br>          initialDelaySeconds: 10<br>        envFrom:<br>        - secretRef:<br>            name: &quot;{{ $.Values.service_name }}-secret-{{ $.Values.environment }}&quot;<br>      {{ if .Values.cron }}<br>      - name: &quot;{{ .Values.service_name }}-{{ .Values.environment }}-cron&quot;<br>        image: &quot;{{ .Values.imageuri }}/{{ .Values.service_name }}-{{ .Values.environment }}:{{ .Values.image_tag }}&quot;<br>        command: [&quot;node&quot;, &quot;app/cron.py&quot;]<br>        securityContext:<br>          allowPrivilegeEscalation: false<br>        resources:<br>          requests:<br>            memory: {{ .Values.cron_memory_limit | default &quot;200Mi&quot; }}<br>            cpu: {{ .Values.cron_cpu_limit | default &quot;50m&quot; }}<br>          limits:<br>            memory: {{ .Values.cron_memory_limit | default &quot;200Mi&quot; }}<br>        lifecycle: <br>          preStop: <br>            exec: <br>              command: [&quot;/bin/sh&quot;, &quot;-c&quot;, &quot;sleep 50&quot;]<br>        envFrom:<br>        - secretRef:<br>            name: &quot;{{ $.Values.service_name }}-secret-{{ $.Values.environment }}&quot;<br>      {{ end }}</pre><p><strong>Ingress<br></strong>Please note that the Ingress used here is <a href="https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.8/">ALB Ingress</a> which needs to be deployed in your cluster before this Ingress configuration can work</p><pre>{{ if .Values.enable_ingress }}<br>apiVersion: networking.k8s.io/v1<br>kind: Ingress<br>metadata:<br>  name: &quot;{{ .Values.service_name }}-ing-{{ .Values.environment }}&quot;<br>  annotations:<br>    alb.ingress.kubernetes.io/group.name: &quot;{{ .Values.environment }}-ing&quot;<br>    alb.ingress.kubernetes.io/scheme: internet-facing<br>    alb.ingress.kubernetes.io/target-type: ip<br>    alb.ingress.kubernetes.io/actions.ssl-redirect: &#39;{&quot;Type&quot;: &quot;redirect&quot;, &quot;RedirectConfig&quot;: { &quot;Protocol&quot;: &quot;HTTPS&quot;, &quot;Port&quot;: &quot;443&quot;, &quot;StatusCode&quot;: &quot;HTTP_301&quot;}}&#39;<br>    alb.ingress.kubernetes.io/listen-ports: &#39;[{&quot;HTTP&quot;: 80}, {&quot;HTTPS&quot;:443}]&#39;<br>    alb.ingress.kubernetes.io/healthcheck-path: /<br>spec:<br>  ingressClassName: alb<br>  rules:   <br>  - host: {{ .Values.app_url }}<br>    http:<br>      paths:<br>      - path: /<br>        pathType: Prefix<br>        backend:<br>          service:<br>            name: &quot;{{ .Values.service_name }}-svc-{{ .Values.environment }}&quot;<br>            port:<br>              number: 80<br>{{ end }}</pre><p><strong>ExternalSecret<br></strong>The External Secrets Object (ESO) must be deployed in your cluster, and the ClusterSecretStore must be configured before the ExternalSecret deployment can function correctly.</p><pre>apiVersion: external-secrets.io/v1beta1<br>kind: ExternalSecret<br>metadata:<br>  name: &quot;{{ .Values.service_name }}-secret-{{ .Values.environment }}&quot;<br>spec:<br>  refreshInterval: 1m<br>  secretStoreRef:<br>    name: cluster-secret-store-engine<br>    kind: ClusterSecretStore<br>  target:<br>    name: &quot;{{ .Values.service_name }}-secret-{{ .Values.environment }}&quot;<br>  dataFrom:<br>  - extract:<br>      key: &quot;{{ $.Values.environment }}/{{ $.Values.service_name }}/creds&quot;</pre><p>In the sample scripts above, most of the static values have been parameterized, making the Helm chart more flexible for handling different scenarios. One thing to also note is the customization added to the Deployment part. It can support the cron/sidecar option to deploy multiple containers in a single pod. The parameter to enable is the cron:true value. This is a simple customization, the Mono Chart can be customized for various scenarios and use cases. The repository for the complete Helm Chart is here: <a href="https://github.com/MyCloudSeries/mono-chart">https://github.com/MyCloudSeries/mono-chart</a>. Next, let us head using the Mono Chart.</p><h4>Using the Mono Chart</h4><p>The Mono Chart is the same as a normal Helm chart, the difference is everything is compacted into a single repo, just line a Mono repo. To use the chart for deployment, the two options that exist in Helm are the values.yaml file option, or the Helm CLI to pass parameters to the file. The following is an example of the Mono Chart values.yaml file.</p><pre>service_name: myapp<br>environment: dev<br>image_tag: latest<br>replicas: 1<br>memory_limit: 400Mi<br>cpu_limit: 20m<br>cron_memory_limit: 400Mi<br>cron_cpu_limit: 20m<br>enable_ingress: true<br>cron: false<br>app_url: demo.example.com<br>health_check_path: /health<br>imageuri: nimboya/myapp<br>container_port: 80</pre><p>The other option is to use the Helm CLI command to pass parameters. The following is a sample script</p><pre>helm install userservice MyCloudSeries/monochart --set service_name=userservice --set environment=dev --set image_tag=latest --set replicas=1 --set memory_limit=400Mi --set cpu_limit=20m --set cron_memory_limit=400Mi --set cron_cpu_limit=20m --set enable_ingress=true --set cron=true app_url=demo.example.com --set health_check_path=health --set imageuri=nimboya/app --set container_port=80</pre><p>The script above does not only reduce the redundancy of scripts for multiple services, but it also ensures multiple scripts are not used for multiple environments (dev, staging, and prod), as the environment you need to deploy to can either be in the values.yaml or via the Helm CLI script.</p><p>One last deployment technique is with ArgoCD. The following is an ArgoCD application deploying the Mono Chart.</p><pre>apiVersion: argoproj.io/v1alpha1<br>kind: Application<br>metadata:<br>  name: userservice<br>  namespace: argocd<br>spec:<br>  project: default<br>  source:<br>    repoURL: https://github.com/MyCloudSeries/mono-chart<br>    targetRevision: HEAD<br>    chart: MyCloudSeries/monochart<br>    helm:<br>      parameters:<br>        - name: service_name<br>          value: userservice<br>        - name: environment<br>          value: dev<br>        - name: image_tag<br>          value: latest<br>        - name: replicas<br>          value: &quot;1&quot;<br>        - name: memory_limit<br>          value: 400Mi<br>        - name: cpu_limit<br>          value: 20m<br>        - name: cron_memory_limit<br>          value: 400Mi<br>        - name: cron_cpu_limit<br>          value: 20m<br>        - name: enable_ingress<br>          value: &quot;true&quot;<br>        - name: cron<br>          value: &quot;true&quot;<br>        - name: app_url<br>          value: demo.example.com<br>        - name: health_check_path<br>          value: health<br>        - name: imageuri<br>          value: nimboya/app<br>        - name: container_port<br>          value: &quot;80&quot;<br>  destination:<br>    server: https://kubernetes.default.svc<br>    namespace: default<br>  syncPolicy:<br>    automated:<br>      prune: true<br>      selfHeal: true</pre><p>Alternatively, the ArgoCD Helm config can be pointed to a values.yaml file.</p><p>Finally, let us outline the advantages of a Mono chart.</p><p><strong>Advantages of Mono Chart</strong></p><ul><li>Manage all deployments from a single source of truth.</li><li>It establishes a golden path for all Kubernetes deployments.</li><li>Accelerates the adoption of platform engineering.</li><li>Centralize and manage Kubernetes application security efficiently.</li><li>Eliminates YAML script of death.</li></ul><p><strong>Disadvantages of Mono Chart</strong></p><ul><li>There is a single point of failure because all deployments use the same Helm chart. Any bug in the Helm chart will be replicated on all deployments.</li><li>It can become complex if clear golden paths are not defined for applications.</li></ul><h4>Conclusion</h4><p>Deployment should minimize repetition to promote code reuse, facilitate easy modifications, and accelerate the application delivery process. This enhances the efficiency of the software development life cycle, boosting the productivity of software engineers and ensuring that high-quality software is delivered promptly and effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e39dee186e4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mycloudseries/single-helm-chart-for-all-kubernetes-deployments-using-argocd-mono-chart-e39dee186e4e">Single Helm Chart for All Kubernetes Deployments using ArgoCD (Mono Chart)</a> was originally published in <a href="https://medium.com/mycloudseries">MyCloudSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seven ways to save cost on your AWS Workload]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/seven-ways-to-save-cost-on-your-aws-workload-83a7d60e9e80?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/2600/1*5E_FbHIi5iehewh-7uPriA.jpeg" width="5592"></a></p><p class="medium-feed-snippet">Strategies to save cost on your AWS workload</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/seven-ways-to-save-cost-on-your-aws-workload-83a7d60e9e80?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/seven-ways-to-save-cost-on-your-aws-workload-83a7d60e9e80?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/83a7d60e9e80</guid>
            <category><![CDATA[cloud-cost-optimization]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Thu, 29 Aug 2024 16:57:11 GMT</pubDate>
            <atom:updated>2024-09-01T02:05:02.504Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[AWS Container Orchestration 2: App Runner vs ECS Fargate]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/aws-container-orchestration-2-app-runner-vs-ecs-fargate-d948f2cbc8fe?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/1400/0*YNb4d263lxj8NqTP.png" width="1400"></a></p><p class="medium-feed-snippet">App Runner vs ECS Fargate</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/aws-container-orchestration-2-app-runner-vs-ecs-fargate-d948f2cbc8fe?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/aws-container-orchestration-2-app-runner-vs-ecs-fargate-d948f2cbc8fe?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d948f2cbc8fe</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containers]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Sun, 28 Jul 2024 12:17:05 GMT</pubDate>
            <atom:updated>2024-08-26T18:15:52.819Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Single-Deployment Observability on Kubernetes: Introducing Robusta for Kubernetes Monitoring]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/single-deployment-observability-on-kubernetes-introducing-robusta-for-kubernetes-monitoring-e9b6a8ab920c?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/1400/0*GpdgJwitnzfrVzDE.png" width="1400"></a></p><p class="medium-feed-snippet">Single Deployment Observability for your Kubernetes cluster</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/single-deployment-observability-on-kubernetes-introducing-robusta-for-kubernetes-monitoring-e9b6a8ab920c?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/single-deployment-observability-on-kubernetes-introducing-robusta-for-kubernetes-monitoring-e9b6a8ab920c?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9b6a8ab920c</guid>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[grafana-prometheus]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Sun, 14 Jul 2024 18:26:21 GMT</pubDate>
            <atom:updated>2024-07-27T07:30:28.116Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Simplified Docker Deployments with AWS App Runner: An Introduction to AWS AppRunner]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mycloudseries/simplified-docker-deployments-with-aws-app-runner-an-introduction-to-aws-apprunner-705450c7906b?source=rss-66218173572e------2"><img src="https://cdn-images-1.medium.com/max/1024/1*PqfIKprApiLH_QtKgp4sug.png" width="1024"></a></p><p class="medium-feed-snippet">The easiest way to Deploy Docker Images on AWS</p><p class="medium-feed-link"><a href="https://medium.com/mycloudseries/simplified-docker-deployments-with-aws-app-runner-an-introduction-to-aws-apprunner-705450c7906b?source=rss-66218173572e------2">Continue reading on MyCloudSeries »</a></p></div>]]></description>
            <link>https://medium.com/mycloudseries/simplified-docker-deployments-with-aws-app-runner-an-introduction-to-aws-apprunner-705450c7906b?source=rss-66218173572e------2</link>
            <guid isPermaLink="false">https://medium.com/p/705450c7906b</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ewere Diagboya]]></dc:creator>
            <pubDate>Mon, 17 Jun 2024 15:56:09 GMT</pubDate>
            <atom:updated>2024-08-26T18:16:18.066Z</atom:updated>
        </item>
    </channel>
</rss>