<?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 Anoop L on Medium]]></title>
        <description><![CDATA[Stories by Anoop L on Medium]]></description>
        <link>https://medium.com/@anoopl?source=rss-e1eaec447b72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ogNMCNvGXjhRwBi6</url>
            <title>Stories by Anoop L on Medium</title>
            <link>https://medium.com/@anoopl?source=rss-e1eaec447b72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:57:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anoopl/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[How to Setup Strimzi Kafka Operator with Mutual TLS and Simple Authorization]]></title>
            <link>https://medium.com/@anoopl/how-to-setup-strimzi-kafka-operator-with-mutual-tls-and-simple-authorization-b397a9ef7295?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/b397a9ef7295</guid>
            <category><![CDATA[strimzi]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kafka]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Thu, 26 Dec 2019 09:30:11 GMT</pubDate>
            <atom:updated>2020-02-06T12:06:27.629Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PV_zhwtBquA9Bh-k" /><figcaption>Photo by <a href="https://unsplash.com/@fczls?utm_source=medium&amp;utm_medium=referral">Fabien Martin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This assumes that you have setup a Strimzi Kafka Operator. You can follow the links to install it on Openshift/Kubernetes:</p><p><a href="https://strimzi.io/quickstarts/">https://strimzi.io/quickstarts/</a></p><p>Detailed setup: <a href="https://strimzi.io/docs/master/full.html#getting-started-str">https://strimzi.io/docs/master/full.html#getting-started-str</a></p><ol><li>Once you have the Kafka Operator up and running. Create a Kafka Cluster using following yaml:</li></ol><p><a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-persistent.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-persistent.yaml</a></p><pre>kubectl apply -f <a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-persistent.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-persistent.yaml</a></pre><p>Wait for a few minutes so that Kafka and Zookeeper pods are in ready state</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AaBHRgl65b1SEBcxkgD1nA.png" /><figcaption>Kafka and Zookeeper pods Running</figcaption></figure><p>This creates a Kafka Cluster named my-cluster with TLS authentication and Simple Authorization enabled. This creates and Kubernetes Service with LoadBalancer which can be used to access the Kafka cluster outside Kubernetes cluster.</p><p>You can get the Load Balancer IP by listing the Services in the namespace:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LwrsC4QyMJAkesQEKpDrnw.png" /></figure><p>Use the “my-cluster-kafka-external-bootstrap” Service’s External IP to access your Kafka Cluster from outside.</p><p>2. Create a Kafka Topic using the operator with following yaml:</p><p><a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-topic.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-topic.yaml</a></p><pre>kubectl apply -f <a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-topic.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-topic.yaml</a></pre><p>3. Create a Kafka User with Authentication TLS &amp; Simple Authorization</p><p><a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-user.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-user.yaml</a></p><pre>kubectl apply -f <a href="https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-user.yaml">https://raw.githubusercontent.com/anoopl/strimzi-kafka-operator-authn-authz/master/kafka-user.yaml</a></pre><p>4. Download the Cluster CA Cert and PKCS12 ( .p12) keys of User to use with Kafka Client:</p><pre>kubectl get secret my-cluster-cluster-ca-cert -o jsonpath=’{.data.ca\.crt}’ | base64 -d &gt; ca.crt</pre><pre>kubectl get secret my-user -o jsonpath=’{.data.user\.password}’ | base64 -d &gt; user.password</pre><pre>kubectl get secret my-user -o jsonpath=’{.data.user\.p12}’ | base64 -d &gt; user.p12</pre><p>5. Convert the ca.cert to truststore jks and user.p12 to Keystore.jks</p><p>Please note that use the password for keystore same as the password you got from the above step:</p><pre>keytool -keystore user-truststore.jks -alias CARoot -import -file ca.crt</pre><pre>keytool -importkeystore -srckeystore user.p12 -srcstoretype pkcs12 -destkeystore user-keystore.jks -deststoretype jks</pre><p>6. Use Kafkatool ( <a href="http://www.kafkatool.com/">http://www.kafkatool.com/</a>) to connect to the Kafka cluster. Use the LoadBalance IP you got from describing service: my-cluster-kafka-external-bootstrap to connect to cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_ZByl0KnS9kYKBwMplNAg.png" /></figure><p>Use the JKS key path and password to connect:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkMv2-Eb-FNWDgsfuKbGMg.png" /></figure><p>7. Now you can see your topics here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRadcIToQm4bEgUADtcLOA.png" /></figure><p>Yay!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b397a9ef7295" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create an User in Kubernetes and Permit to use a Specific Namespace]]></title>
            <link>https://medium.com/@anoopl/create-an-user-in-kubernetes-and-permit-to-use-a-specific-namespace-e37100dbb8a4?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/e37100dbb8a4</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Wed, 23 Oct 2019 09:57:01 GMT</pubDate>
            <atom:updated>2019-11-17T16:50:26.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E6q-7JISz5u9cGWc" /><figcaption>Photo by <a href="https://unsplash.com/@guibolduc?utm_source=medium&amp;utm_medium=referral">Guillaume Bolduc</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Create an User in Kubernetes and Permit to use a Specific Namespace</strong></p><p>In this post we try to learn how to configure an user for Kubernetes and allow only to use a certain name space. This is about to set RBAC policies for a user.</p><p>We are assuming that your Kubernetes uses SSL certificate based authentication. Make sure that RBAC is enabled. You can check that whether Kubernetes API</p><p>Please follow the steps below to create an user named user1 and assign developer role on namespace app1:</p><ol><li>Create an SSL key for the user using the Openssl command:</li></ol><h4><em>openssl genrsa -out user1.key 2048</em></h4><p>2. Create a Certificate Signing Request using the key:</p><h4><em>openssl req -new -key user1.key -out user1.csr -subj “/CN=user1/O=Test Organization”\n</em></h4><p>Please remove the CN=user1 with user name that you need. O=Test Organization to your company name</p><p>3. Sign the CSR with the Kubernetes Cluster Certificate Authority and generate the Certificate for user1. For this you need ca.key and ca.crt from one of the cluster master. Usually the location is /etc/kubernetes/pki/ca.key and /etc/kubernetes/pki/ca.crt on Kind. Minikube it’s under ~/.minikube/certs/ca.key and ~/.minikube/certs/ca.crt. You can find this by looking at what keys API server service or Pod is using. Once you have the certs copied use:</p><h4><em>openssl x509 -req -in user1.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out user1.crt -days 500</em></h4><p>4. Create the Kubeconfig for the user1 with the key and cert:</p><h4>kubectl config set-credentials user1 — client-certificate=~/user1.crt — client-key=~/user1.key</h4><p>Use the full path to key and cert</p><h4>kubectl config set-context user1-context — cluster=kind — namespace=app1 — user=user1</h4><p>5. Create the RBAC Role for the user with following manifest:</p><p><em>kind: Role<br>apiVersion: rbac.authorization.k8s.io/v1beta1<br>metadata:<br> namespace: app1<br> name: developer<br>rules:<br>- apiGroups: [“”, “extensions”, “apps”]<br> resources: [“deployments”, “replicasets”, “pods”]<br> verbs: [“get”, “list”, “watch”, “create”, “update”, “patch”, “delete”]</em></p><p>Copy this to a yaml file and apply.</p><h4>kubectl apply -f dev-role.yaml</h4><p>6. Create a Rolebinding that to bind the role to user user1 to role developer:</p><p><em>kind: RoleBinding<br>apiVersion: rbac.authorization.k8s.io/v1beta1<br>metadata:<br> name: dev-binding<br> namespace: app1<br>subjects:<br>- kind: User<br> name: user1<br> apiGroup: “”<br>roleRef:<br> kind: Role<br> name: developer<br> apiGroup: “”</em></p><p>copy this to a yaml file and apply:</p><h4>kubectl apply -f dev-role-binding.yaml</h4><p>7. Test the RBAC rule:</p><h4>kubectl — context=employee-context get pods — namespace=defaultIt</h4><p>Will not work and you would get the following error:</p><p><em>Error from server (Forbidden): pods is forbidden: User “user1” cannot list resource “pods” in API group “” in the namespace “default”</em></p><p>Now run pod on the app1 namespace:</p><h4>kubectl — context=user1-context run — image nginx nginx</h4><h4>kubectl — context=user1-context get pods — namespace=app1</h4><p>Now you have created user1 with only access to namespace app1</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e37100dbb8a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Install Istio using Helm Template Generation]]></title>
            <link>https://medium.com/@anoopl/install-istio-using-helm-template-generation-92be2ae198af?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/92be2ae198af</guid>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[service-mesh]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Fri, 08 Mar 2019 11:41:33 GMT</pubDate>
            <atom:updated>2019-03-08T11:41:33.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*plNObHAWMQM85ifH" /><figcaption>Photo by <a href="https://unsplash.com/@hansonlujx?utm_source=medium&amp;utm_medium=referral">Hanson Lu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Install Istio using Helm Template Generation</strong></p><p>We can install Istio with 3 methods. We have already discussed the first method on previous post.</p><p>Complete installation steps for Istio on Kubernetes can be found a</p><p><a href="https://istio.io/docs/setup/kubernetes/">Kubernetes</a></p><p><a href="https://istio.io/docs/setup/kubernetes/quick-start/">https://istio.io/docs/setup/kubernetes/quick-start/</a></p><p>Now lets discuss the second method using Helm template generate. This method makes it easier to customise the installation ( even post install).</p><ol><li>Download Istio latest using:</li></ol><p>curl -L <a href="https://git.io/getLatestIstio">https://git.io/getLatestIstio</a> | sh -</p><p>cd istio-1.0.6</p><p>Current latest is 1.0.6</p><p>2. Generate the manifest file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f748d7bf9375be525576654a74cbfaee/href">https://medium.com/media/f748d7bf9375be525576654a74cbfaee/href</a></iframe><p>10.0.0.0/16 is Network CIDR for your cluster. We had to use this to make outbound/internet traffic work on the app pods.</p><p>3. Create a Istio Namespace and apply the manifest:</p><p>kubectl create ns istio-system</p><p>kubectl apply -f istio.yaml</p><p>You can keep versioning on the yaml file name for easy recognition like istio-v1.yaml so on.</p><p>If you want to make changes after applying the manifest you can generate the new yaml with different — set options then apply it using kubectl.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92be2ae198af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Install Istio on Kubernetes on 3 steps]]></title>
            <link>https://medium.com/@anoopl/install-istio-on-kubernetes-on-3-steps-e77d8d88f0f3?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/e77d8d88f0f3</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[istio]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 10:32:48 GMT</pubDate>
            <atom:updated>2019-02-26T12:29:25.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tdLD9Y8PGtfO7SRd" /><figcaption>Photo by <a href="https://unsplash.com/@cmventi20?utm_source=medium&amp;utm_medium=referral">Cameron Venti</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Install Istio on Kubernetes in 3 steps</strong></p><p>This describes how to Install Istio on Kubernetes in 3 easy steps.</p><p>Same Steps can be used on any Kubernetes Cluster on AKS/EKS/Minikube.</p><p>For more detailed information please refer: <a href="https://istio.io/docs/setup/kubernetes/">https://istio.io/docs/setup/kubernetes/</a></p><p>Here we follow installing Kubernetes using yaml. There are other options available like installing with Helm etc..</p><ol><li>Download Istio latest using:</li></ol><p><strong>curl -L </strong><a href="https://git.io/getLatestIstio"><strong>https://git.io/getLatestIstio</strong></a><strong> | sh -</strong></p><h4>Current latest version 1.0.6 it seems that 1.1.0 will be released very soon</h4><p><strong>cd istio-1.0.6</strong></p><p><strong>export PATH=$&lt;ISTIO_HOME&gt;/bin:$PATH</strong></p><p><a href="https://istio.io/docs/concepts/security/#mutual-tls-authentication">https://istio.io/docs/concepts/security/#mutual-tls-authentication</a>Please replace &lt;ISTIO_PATH&gt; with where you have downloaded Istio</p><p>This export sets istioctl command available on your system</p><p>2. Install Istio’s Custom Resource Definitions using:</p><p><strong>kubectl apply -f install/kubernetes/helm/istio/templates/crds.yaml</strong></p><p>3. Install Istio with default Mutual TLS authentication:</p><p><strong>kubectl apply -f install/kubernetes/helm/istio/templates/crds.yaml</strong></p><p>If you need with no mutual TLS use:</p><p><strong>kubectl apply -f install/kubernetes/istio-demo.yaml</strong></p><p>To understand more about Mutual TLS on Istio, please refer: <a href="https://istio.io/docs/concepts/security/#mutual-tls-authentication">https://istio.io/docs/concepts/security/#mutual-tls-authentication</a></p><p>With this 3 steps Istio is installed. Make sure all services are fine and Pods are running by:</p><p><strong>kubectl -n istio-system get svc</strong></p><p><strong>kubectl -n istio-system get po</strong></p><p>Output would be something like:</p><blockquote>NAME READY STATUS RESTARTS AGE<br>grafana-59b8896965-qbj97 1/1 Running 2 4d<br>istio-citadel-6f444d9999-xghlz 1/1 Running 0 3d7h<br>istio-egressgateway-68994d7c69-lv4v5 1/1 Running 2 3d9h<br>istio-egressgateway-68994d7c69-mzxzm 1/1 Running 1 4d<br>istio-egressgateway-68994d7c69-pbdnd 1/1 Running 0 3d4h<br>istio-egressgateway-68994d7c69-ph986 1/1 Running 0 3d4h<br>istio-egressgateway-68994d7c69-v2vj2 1/1 Running 0 3d4h<br>istio-galley-685bb48846-zmwzt 1/1 Running 2 4d<br>istio-ingressgateway-544c458fd6-hpsxb 1/1 Running 0 2d23h<br>istio-ingressgateway-544c458fd6-pqmgh 1/1 Running 0 2d16h<br>istio-ingressgateway-544c458fd6-qbxwf 1/1 Running 0 3d4h<br>istio-pilot-6cb5c55fb8-hpdvn 2/2 Running 4 4d<br>istio-policy-66ccc8df5f-7lwxv 2/2 Running 2 4d<br>istio-security-post-install-55rqd 0/1 Completed 0 4d<br>istio-sidecar-injector-5d8dd9448d-7dw5t 1/1 Running 0 3d7h<br>istio-telemetry-586ccd6d57-cjdtb 2/2 Running 5 4d<br>istio-telemetry-586ccd6d57-n9g62 2/2 Running 1 3d7h<br>istio-tracing-6b994895fd-wf2g4 1/1 Running 0 3d7h<br>prometheus-76b7745b64-pq576 1/1 Running 0 3d7h<br>servicegraph-cb9b94c-bg8xm 1/1 Running 0 2d23h</blockquote><p>On another post I could explain how to install a test app/nginx test deployment using Istio</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e77d8d88f0f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cluster Autoscaler on AKS]]></title>
            <link>https://medium.com/@anoopl/cluster-autoscaler-on-aks-d3028a89313a?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3028a89313a</guid>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Wed, 06 Feb 2019 11:35:04 GMT</pubDate>
            <atom:updated>2019-02-26T17:38:47.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UxV9RjNA7GClDPzk" /><figcaption>Photo by <a href="https://unsplash.com/@rebeccageorgia?utm_source=medium&amp;utm_medium=referral">Rebecca Georgia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Cluster Autoscaler is used to scale up or down cluster nodes according to load ( pending pods) or free nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tR9qeCMDoTAMyUeNiaefTQ.png" /></figure><p>Earlier we had to manually configure Cluster Autoscaling on AKS cluster. Recently Azure AKS released this as a feature. So in this tutorial I would be explaining both the steps.</p><p>Manual:</p><ol><li>Generate the secret with the cluster details by running the following script:</li></ol><p><a href="https://gist.github.com/anoopl/d0bfb7c78a7a0027934689a7f675796d">https://gist.github.com/anoopl/d0bfb7c78a7a0027934689a7f675796d</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6785b5080592c749b09546714690c85/href">https://medium.com/media/d6785b5080592c749b09546714690c85/href</a></iframe><p>2. Run the script and copy the output to a yaml file cluster-autoscaler.yaml:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/708896d44e7cd1e80b504823e5f74ad1/href">https://medium.com/media/708896d44e7cd1e80b504823e5f74ad1/href</a></iframe><p>3. Create the secret :</p><blockquote>kubectl apply -f cluster-autoscaler-secret.yaml</blockquote><p>4. Use the following yaml to create other resources for the CA:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8620ba61d038a81baeb4026c1a63f649/href">https://medium.com/media/8620ba61d038a81baeb4026c1a63f649/href</a></iframe><blockquote>You can set the minimum and maximum number of nodes in the yaml: — — nodes=1:10:nodepool1</blockquote><blockquote>Create the resources with : kubectl apply -f cluster-autoscaler-all.yaml</blockquote><p>You can check the logs to see everything working as expected by checking CA Pod’s logs.</p><blockquote>kubectl -n kube-system logs -f &lt;cluster-autoscaler-pod&gt;</blockquote><p>Enable Cluster Autoscale feature on AKS</p><ol><li>Update the Az Cli to the latest version:</li></ol><blockquote>sudo apt-get update &amp;&amp; sudo apt-get install --only-upgrade -y azure-cli</blockquote><p>2. Enable aks preview mode</p><blockquote>az extension add --name aks-preview</blockquote><p>3. Create new cluster with Autoscaling enabled:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/440ec6f542d87861eaa2a87ad4a9bda8/href">https://medium.com/media/440ec6f542d87861eaa2a87ad4a9bda8/href</a></iframe><p>You can test the autoscaling by running a deployment of nginx with many replicaset:</p><p>Example:</p><p><a href="https://gist.github.com/anoopl/891965dd6c9110cdc7950f2d1529041a">https://gist.github.com/anoopl/891965dd6c9110cdc7950f2d1529041a</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3028a89313a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create AKS Cluster using Azure CLI]]></title>
            <link>https://medium.com/@anoopl/create-aks-cluster-using-azure-cli-9a05ce0382e2?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a05ce0382e2</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 13:13:49 GMT</pubDate>
            <atom:updated>2019-02-26T17:32:26.930Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Create AKS Cluster using Azure CLI</strong></p><p><strong>Deployment Steps:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*ZdC0gVFzrcgQ2ymZJ8bhvg.png" /></figure><p><strong>prerequisites:</strong></p><ol><li>Azure account with a subcription</li><li>Azure Cli installed and logged in. You can install Azure CLI by following <a href="https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest">https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest</a></li><li>Kubectl — Kuberntes Command Line Interface installed</li><li>Create a resource group</li></ol><p>az group create -n &lt;resource-group-name&gt; -l &lt;location&gt;</p><p>2. Create Virtualnet</p><p>az network vnet create -g &lt;resource-group-name&gt; -n &lt;vnet-name&gt; --address-prefix &lt;CIDR&gt;</p><p>Example: az network vnet create -g xxxgggg -n k8s-vnet --address-prefix xx.xx.xx.xx/x</p><p>3. Create Subnet</p><p>This Subnet is used for the Pods network and Nodes</p><p>az network vnet subnet create -n &lt;subnet-name&gt; -g &lt;resource-group&gt; --vnet-name &lt;vnet-name&gt; --address-prefix &lt;CIDR-<strong>for</strong>-<strong>this</strong>-subnet&gt;</p><p>Example: az network vnet subnet create -n k8s-nodes-subnet -g pocCCPwu2rg --vnet-name k8s-vnet --address-prefix xx.xx.xx/x</p><p>4. Create Service principal</p><p>This Service Principal will be used for creating other resources like Load Balancer, Storage Disk etc</p><p>az ad sp create-<strong>for</strong>-rbac -n &lt;service-principal-name&gt; --skip-assignment</p><p>Example: az ad sp create-<strong>for</strong>-rbac -n aks-poc-sp --skip-assignment</p><p>Output would be something like below. Use the AppID and Password in the command for creating cluster</p><p>{</p><p>&quot;appId&quot;: &quot;xxxxxxxx&quot;,</p><p>&quot;displayName&quot;: &quot;aks-poc-sp&quot;,</p><p>&quot;name&quot;: &quot;<a href="http://aks-poc-sp"/">http://aks-poc-sp&quot;</a>,</p><p>&quot;password&quot;: &quot;xxxxxxxx-xxxxxxx&quot;,</p><p>&quot;tenant&quot;: &quot;xxxxxxxxx&quot;</p><p>}</p><p>4. Show Available Kubernetes versions:</p><p>5 . Create AKS cluster</p><p>az aks create --resource-group xxxgggggg --name aks-poc --kubernetes-version 1.11.5 --node-count 1 --node-vm-size Standard_DS1_v2 --vnet-subnet-id &quot;/subscriptions/xxx-xxx-xxxx-xxxx-xxxx/resourceGroups/xxx-rg/providers/Microsoft.Network/virtualNetworks/k8s-vnet/subnets/k8s-nodes-subnet&quot; --network-plugin azure --service-principal &lt;app_id_from_service_principal&gt; --client-secret &lt;service_principal_password&gt; --service-cidr xx.xx.xx.xx/x--dns-service-ip xx.xx.xx.xx</p><p>Note:</p><p>Use — generate-ssh-keys to generate a new ssh key for SSH access to nodes. If this option is not used key ~/.ssh/id_rsa is used if it’s present</p><p>VM sizes list <a href="https://docs.microsoft.com/en-us/azure/virtual-machines/linux/sizes">https://docs.microsoft.com/en-us/azure/virtual-machines/linux/sizes</a> — node</p><p>Even though documentation says Network Policy with Calico is supported, it’s not yet available.</p><p>Please read previous story for help on Network design &amp; CIDR.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a05ce0382e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure AKS advanced Networking Design]]></title>
            <link>https://medium.com/@anoopl/azure-aks-advanced-networking-design-cf1d39de8db4?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf1d39de8db4</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 12:47:44 GMT</pubDate>
            <atom:updated>2019-01-31T12:47:44.930Z</atom:updated>
            <content:encoded><![CDATA[<p>Kubernetes cluster is created under Virtual Network k8s-vnet 10.0.0.0/8 (but it is limited to 65,536 configured IP addresses)</p><p>Under this Vnet we need to create a new Subnet named k8s-nodes-subnet with CIDR 10.10.0.0/16. This subnet is used by K8s nodes and Pods, so plan the sizing accordingly</p><p>Service Subnet 10.20.0.0/16. This IP ranges are used by the services in Kubernetes. This subnet should not conflict with the Nodes Subnet or Docker Bridge CIDR (Default 172.17.0.0/16)</p><p><strong>Network Architecture</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fenAEwsyhZUy150KfnbdQ.png" /><figcaption>Azure AKS Network Design</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf1d39de8db4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AKS — Azure Kubernetes Service Overview]]></title>
            <link>https://medium.com/@anoopl/aks-azure-kubernetes-service-overview-73506b040f4e?source=rss-e1eaec447b72------2</link>
            <guid isPermaLink="false">https://medium.com/p/73506b040f4e</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[ak]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Anoop L]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 12:40:37 GMT</pubDate>
            <atom:updated>2019-02-26T17:31:01.499Z</atom:updated>
            <content:encoded><![CDATA[<p>AKS — Azure Kubernetes Service Overview</p><p>AKS is a managed Kubernetes service by Azure.</p><p>Kubernetes master/control plane is maintained and managed by Azure. We can SSH in to Nodes and manage nodes to a certain extent.</p><p>We can access the cluster through Kuberenetes API. Azure provides monitoring integration with Azure monitor.</p><p>Docker UCP is the container runtime in Nodes. We do not have much options to customise API server configuration parameters or change Container Run time.</p><p>Different versions of Kubernetes are available in AKS. Latest version available as of today is 1.12.4</p><p>It’s easy to upgrade kubernetes versions on AKS, which is possible with a single command.</p><p>In an AKS cluster creating or managing other Azure resources like Load Balancer, Azure file, Azure disk are done through Service Principal</p><p>Architecture overview:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Prgpffw8skXPCCX3myIjhw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73506b040f4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>