<?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 mattia rambelli on Medium]]></title>
        <description><![CDATA[Stories by mattia rambelli on Medium]]></description>
        <link>https://medium.com/@mattia.rambelli?source=rss-ff81c9478f30------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*WLJL6iBIJ1oH38VI</url>
            <title>Stories by mattia rambelli on Medium</title>
            <link>https://medium.com/@mattia.rambelli?source=rss-ff81c9478f30------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:44:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattia.rambelli/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[My journey with Kubernetes and Akamai — deploying Juice Shop]]></title>
            <link>https://towardsdev.com/my-journey-with-kubernetes-and-akamai-deploying-juice-shop-ea8d1205f022?source=rss-ff81c9478f30------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea8d1205f022</guid>
            <category><![CDATA[akamai-computing]]></category>
            <category><![CDATA[linode]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[akamai]]></category>
            <dc:creator><![CDATA[mattia rambelli]]></dc:creator>
            <pubDate>Wed, 30 Nov 2022 09:42:55 GMT</pubDate>
            <atom:updated>2022-12-02T14:52:41.347Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>My journey with Kubernetes and Akamai — deploying Juice Shop</h3><p>Recently Akamai acquired <a href="https://www.linode.com/">Linode</a> and that gave us employees a good opportunity to up-skill on computing.</p><p>Since Linode offers the “Linode Kubernetes Engine (LKE)”, I chose to learn how fully-managed K8s container orchestration engines work online, and document the effort.<br>Deploying an LKE cluster took 2 minutes, then I was ready to test.</p><p>This is what I wanted to achieve:</p><ul><li>develop a Helm Chart to deploy the OWASP Juice Shop</li><li>deploy Ingress, and automatically assign a hostname</li><li>use the hostname to get a Let’s Encrypt certificate</li></ul><p>Few tests and reading online suggested this setup:</p><ul><li><a href="https://github.com/kubernetes-sigs/external-dns">External DNS</a> (supports Akamai Edge DNS)</li><li><a href="https://github.com/kubernetes/ingress-nginx">ingress-nginx</a></li><li><a href="https://github.com/cert-manager/cert-manager">cert-manager</a></li><li><a href="https://owasp.org/www-project-juice-shop/">Juice Shop</a> as app to be deployed</li></ul><p>I wanted to write the Helm chart for Juice Shop on my own, to learn.</p><p>The resulting systems can be seen as following</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2uqhOArjtfeuNrjWHybhLQ.png" /></figure><p>It was important to me that the IP address on ingress-nginx was mapped to Akamai Edge DNS before the cert-manager kicked in, to avoid wasting time.</p><p>For this reason, rather than defining the External DNS mapping on the Juice Shop chart, I preferred to use annotations on the ingress-nginx deployment.</p><p>Code available at <a href="https://github.com/mrambell/LKE-and-juiceshop">https://github.com/mrambell/LKE-and-juiceshop</a></p><p>I went through the following steps, to define and deploy the service</p><p><strong>Configuring External DNS</strong></p><p>First I wanted to have the external DNS service available and running.<br>This was easy using this YAML file (external-dns.yaml)</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: external-dns<br>spec:<br>  strategy:<br>    type: Recreate<br>  selector:<br>    matchLabels:<br>      app: external-dns<br>  template:<br>    metadata:<br>      labels:<br>        app: external-dns<br>    spec:<br>      serviceAccountName: external-dns<br>      containers:<br>      - name: external-dns<br>        image: k8s.gcr.io/external-dns/external-dns:latest<br><br>provider: akamai<br>sources:<br>  - service<br>  - ingress<br>txtOwnerId: YourOwnerName<br>domainFilters: [yourdomain.name]<br>zoneNameFilters: [yourdomain.name]<br>logLevel: debug<br>akamai:<br>  host: &lt;akamai API host&gt;<br>  clientToken: &lt;Akamai client token&gt;<br>  accessToken: &lt;Akamai access token&gt;<br>  clientSecret: &lt;Akamai client secret&gt;</pre><p>command to install (make sure to personalise your namespace)</p><pre>helm install external-dns bitnami/external-dns --version 6.10.1 -f external-dns.yaml --namespace juiceshop-app</pre><p><strong>Deploying ingress and obtaining a DNS record</strong></p><p>Now that the external-dns service is up, we can deploy ingress-nginx with the following annotations</p><pre>controller:<br>  service:<br>    annotations:<br>      external-dns.alpha.kubernetes.io/ingress-hostname-source: annotation-only<br>      external-dns.alpha.kubernetes.io/hostname: your.app.hostname.here<br>      external-dns.alpha.kubernetes.io/ttl: &quot;600&quot;</pre><p>after the deployment we will have a consistent DNS record which cert-manager can use, without waiting for the ingress service definition of the app itself.</p><p><strong>Deploying cert-manager and obtaining a certificate</strong></p><p>the cert-manager deployment is standard, using namespace deployment</p><p><strong>Building and deploying a Juice Shop chart</strong></p><p>For this chart, I first needed to decide how many replicas I wanted, and other applications details.</p><p>Since, later on, all settings should be managed via variables to add new deployments on demand, I opted for this structure</p><pre>app:<br>  juiceshop:<br>    image:<br>      name: bkimminich/juice-shop<br>      tag: latest<br>      pullPolicy: IfNotPresent<br>    replicas: 2<br>    ingress:<br>      url: not.configured.yet<br>      mail: somemail@domain.com</pre><p>“app.juiceshop.image” cnotrols the docker image used, in this case <a href="https://hub.docker.com/r/bkimminich/juice-shop">https://hub.docker.com/r/bkimminich/juice-shop</a></p><p>url and mail are interesting for the ingress service.</p><p>Full files available on <a href="https://github.com/mrambell/LKE-and-juiceshop">https://github.com/mrambell/LKE-and-juiceshop</a></p><p>The most important choice is around the certificate issuer and ingress definition:</p><p>The ingress will use a namespace issuer</p><pre>cert-manager.io/issuer: {{ include &quot;app.name&quot; . }}</pre><p>The cert issuer must be of a consistent kind by specifying</p><pre>kind: Issuer</pre><p><strong>What’s next?</strong></p><p>next I will try to accelerate Juice Shop using Akamai ION, then protect it using App and API protector!</p><p>Also, shoutout to Mike Schiessl, who coached me and taught me a lot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea8d1205f022" width="1" height="1" alt=""><hr><p><a href="https://towardsdev.com/my-journey-with-kubernetes-and-akamai-deploying-juice-shop-ea8d1205f022">My journey with Kubernetes and Akamai — deploying Juice Shop</a> was originally published in <a href="https://towardsdev.com/">Towards Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>