<?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 Pushkar Kothavade on Medium]]></title>
        <description><![CDATA[Stories by Pushkar Kothavade on Medium]]></description>
        <link>https://medium.com/@pushkarbk?source=rss-c79cc28e2999------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*h6EZvI2mYWvDy1L7b-8JYA.png</url>
            <title>Stories by Pushkar Kothavade on Medium</title>
            <link>https://medium.com/@pushkarbk?source=rss-c79cc28e2999------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:06:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pushkarbk/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[Google Cloud Anthos Series: Migrate for Anthos and GKE]]></title>
            <link>https://medium.com/google-cloud/google-cloud-anthos-series-part8-2af3bdce0c9b?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/2af3bdce0c9b</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[anthos]]></category>
            <category><![CDATA[containers]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Fri, 01 Apr 2022 04:22:53 GMT</pubDate>
            <atom:updated>2022-04-10T04:00:43.254Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud Anthos Series: Part 8</h4><p>Welcome to Part-8 of the ‘Google Cloud Anthos series’. You can find the complete series <a href="https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179">Here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvxWcDZ2FFNWPYsib8w-2Q.png" /><figcaption>Note: The company names (Samajik and Purogami) and personas (Ram and Guhan) mentioned in the storyline are fictional</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kwq4UQt3vGc6mUHDTqiWWw.png" /></figure><p><strong>Migrate for Anthos and GKE</strong></p><p>This tool makes it fast and easy to modernize traditional applications away from virtual machines and into native containers. Find this tool in Anthos dashboard with the name ‘Migrate to containers’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMB0_Fq5gRdZJLxklGXRbg.png" /><figcaption><strong>Anthos Dashboard: Migrate for containers</strong></figcaption></figure><p>Use Migrate for Anthos and GKE to convert VM-based workloads into containers that run on Google Kubernetes Engine (GKE) or Anthos clusters. Workloads from VMs that run on VMware, AWS, Azure, or Compute Engine can be migrated to GCP in container format with ease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNXBw5-rBw4imqJrDN1pRw.png" /><figcaption><strong>Migrate VMs running on VMware, AWS, Azure, or Compute Engine to containers</strong></figcaption></figure><p>This unique automated approach extracts the critical application elements from the VM so that those elements can be easily inserted into containers in GKE or Anthos clusters without the VM layers (like Guest OS) that become unnecessary with containers.</p><p>This significantly reduces the cost and labor that would be required for a manual application modernisation project. Post migration customer’s DevOps team gets modern controls offered by the GKE/Anthos to manage these applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jN8asfpV9k63oeZB1CnZeA.png" /><figcaption><a href="https://cloud.google.com/migrate/anthos/docs/compatible-os-versions"><strong>Compatible operating systems and Kubernetes versions</strong></a><strong>.</strong></figcaption></figure><p><strong>Migrate for Anthos and GKE : Quickstart Guide</strong></p><p>In this Quickstart hands-on guide, Create a simple Compute Engine virtual machine (VM) on GCP first then use ‘Migrate for Anthos and GKE’ to migrate the VM to a Google Kubernetes Engine (GKE) processing cluster in the Cloud.</p><p><strong>PART-1: GCE VM Setup</strong></p><p>Create a GCE VM on Google cloud platform and install simple Apache web server application on it.</p><blockquote>1.1. Setup Env Variables</blockquote><pre>PROJECT_ID=&quot;&lt;your-project-id&gt;&quot;<br>REGION=&quot;&lt;gcp-region&gt;&quot;<br>ZONE=&quot;&lt;zone&gt;&quot;</pre><blockquote>1.2. Create a VM with a web server</blockquote><pre>gcloud compute instances create quickstart-instance \<br> --project=${PROJECT_ID} --zone=${ZONE} --machine-type=e2-standard-2 \<br> --subnet=default --scopes=&quot;cloud-platform&quot; \<br> --tags=http-server,https-server --image=ubuntu-minimal-1604-xenial-v20210119a \<br> --image-project=ubuntu-os-cloud --boot-disk-size=10GB --boot-disk-type=pd-standard \<br> --boot-disk-device-name=quickstart-instance</pre><blockquote>1.3. Create a Firewall Rule</blockquote><pre>gcloud compute --project=${PROJECT_ID} firewall-rules create default-allow-http \<br> --direction=INGRESS --priority=1000 --network=default --action=ALLOW \<br> --rules=tcp:80 --source-ranges=0.0.0.0/0 --target-tags=http-server</pre><blockquote>1.4. SSH to the VM &amp; Install the apache2 Package</blockquote><pre>sudo apt-get update &amp;&amp; sudo apt-get install apache2 -y</pre><pre>echo &#39;&lt;!doctype html&gt;&lt;html&gt;&lt;body&gt;&lt;h1&gt;Hello World!&lt;/h1&gt;&lt;/body&gt;&lt;/html&gt;&#39; | sudo tee /var/www/html/index.html</pre><blockquote>1.5. Verify the Installation</blockquote><blockquote>Open the browser and type http://&lt;quickstart-instance-Public-IP&gt;</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*qcl8dUNOiKL5cfddmbaidA.png" /></figure><blockquote>1.6. Stop the VM</blockquote><p><strong>PART-2: GKE Processing Cluster Setup</strong></p><blockquote>2.1. Creating a processing cluster</blockquote><p>Create a GKE cluster in the Cloud that you use as a processing cluster. This is where you install Migrate for Anthos and GKE and execute the migration.</p><pre>gcloud container clusters create migration-processing \<br>--project=${PROJECT_ID} --zone=${ZONE} --machine-type e2-standard-4 \<br>--image-type ubuntu --num-nodes 1 \<br>--subnetwork &quot;projects/${PROJECT_ID}/regions/${REGION}/subnetworks/default&quot;</pre><p><strong>PART-3: Install ‘Migrate for Anthos and GKE’</strong></p><blockquote>3.1. Create the m4a-install service account</blockquote><pre>gcloud iam service-accounts create m4a-install \<br>  --project=${PROJECT_ID}</pre><blockquote>3.2. Grant the storage.admin role to the service account</blockquote><pre>gcloud projects add-iam-policy-binding ${PROJECT_ID}  \<br>  --member=&quot;serviceAccount:m4a-install@${PROJECT_ID}.iam.gserviceaccount.com&quot; \<br>  --role=&quot;roles/storage.admin&quot;</pre><blockquote>3.3. Download the key file for the service account</blockquote><pre>gcloud iam service-accounts keys create m4a-install.json \<br>  --iam-account=m4a-install@${PROJECT_ID}.iam.gserviceaccount.com \<br>  --project=${PROJECT_ID}</pre><blockquote>3.4. Connect to the cluster</blockquote><pre>gcloud container clusters get-credentials migration-processing \<br>  --zone ${ZONE} --project ${PROJECT_ID}</pre><blockquote>3.5. Set up Migrate for Anthos and GKE components on the processing cluster</blockquote><pre>migctl setup install --json-key=m4a-install.json</pre><blockquote>3.6 Validate the Migrate for Anthos and GKE installation</blockquote><pre>migctl doctor</pre><p><strong>PART-4: Migrating the VM: Create Service Account</strong></p><blockquote>4.1. Create the m4a-ce-src service account</blockquote><pre>gcloud iam service-accounts create m4a-ce-src \<br>  --project=${PROJECT_ID}</pre><blockquote>4.2. Grant the compute.viewer role to the service account</blockquote><pre>gcloud projects add-iam-policy-binding ${PROJECT_ID}  \<br>  --member=&quot;serviceAccount:m4a-ce-src@${PROJECT_ID}.iam.gserviceaccount.com&quot; \<br>  --role=&quot;roles/compute.viewer&quot;</pre><blockquote>4.3. Grant the compute.storageAdmin role to the service account</blockquote><pre>gcloud projects add-iam-policy-binding ${PROJECT_ID}  \<br>  --member=&quot;serviceAccount:m4a-ce-src@${PROJECT_ID}.iam.gserviceaccount.com&quot; \<br>  --role=&quot;roles/compute.storageAdmin&quot;</pre><blockquote>4.4. Download the key file for the service account</blockquote><pre>gcloud iam service-accounts keys create m4a-ce-src.json \<br>  --iam-account=m4a-ce-src@${PROJECT_ID}.iam.gserviceaccount.com \<br>  --project=${PROJECT_ID}</pre><blockquote>4.5. Create the migration source</blockquote><pre>migctl source create ce quickstart-source --project ${PROJECT_ID} --json-key=m4a-ce-src.json</pre><p><strong>PART-5: Migrating the VM: Create a migration</strong></p><blockquote>5.1. Create a migration Plan</blockquote><pre>migctl migration create my-migration --source quickstart-source \<br>  --vm-id quickstart-instance --intent Image</pre><blockquote>5.2. Check the migration status</blockquote><pre>migctl migration status my-migration</pre><blockquote>5.3. Download the migration plan</blockquote><pre>migctl migration get my-migration</pre><blockquote>5.4. Migrate the VM using the migration plan</blockquote><pre>migctl migration generate-artifacts my-migration</pre><blockquote>5.5. After the migration begins, check its status until it finishes</blockquote><pre>migctl migration status my-migration</pre><p><strong>PART-6: Deploying the migrated workload</strong></p><blockquote>6.1. Once the migration is complete, download the generated YAML artefacts</blockquote><pre>migctl migration get-artifacts my-migration</pre><blockquote>6.2. Add following service to the ‘deployment_spec.yaml’ file</blockquote><pre>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: hello-service<br>spec:<br>  selector:<br>    app: quickstart-instance<br>  ports:<br>    - protocol: TCP<br>      port: 80<br>      targetPort: 80<br>  type: LoadBalancer</pre><blockquote>6.3.Apply the deployment spec YAML to deploy the workload</blockquote><pre>kubectl apply -f deployment_spec.yaml</pre><blockquote>6.4. Check for an external IP address</blockquote><pre>kubectl get service hello-service</pre><blockquote>6.5. Test the migration by opening a browser and visiting the web page at the external IP address</blockquote><pre>http://&lt;EXTERNAL-IP&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*b3koSd3sZaAY9iI105DLRg.png" /></figure><p>Check ‘Migrate to containers’ Dashboard under ‘Kubernetes Engine’ section on GCP console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2RGT0kfZbs-qWaMguO3KJw.png" /></figure><p><strong>Reference</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BiqQarGeW2zACmKscw8FQ.png" /><figcaption><a href="https://www.youtube.com/playlist?list=PLIivdWyY5sqLbI6lgiwBLI6OJ94X7AjNW"><strong>https://www.youtube.com/playlist?list=PLIivdWyY5sqLbI6lgiwBLI6OJ94X7AjNW</strong></a></figcaption></figure><p><strong>Coming up..</strong></p><p>In this blog we discussed ‘Migrate for Anthos &amp; GKE’ tool to migrate VMs to containers. In upcoming blogs we will continue the Samajik’s journey of Anthos adoption.</p><p>Contributors: <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2af3bdce0c9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-anthos-series-part8-2af3bdce0c9b">Google Cloud Anthos Series: Migrate for Anthos and GKE</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Anthos Series - Anthos Marketplace Applications]]></title>
            <link>https://medium.com/google-cloud/google-cloud-anthos-series-part7-6b85c5f7016f?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b85c5f7016f</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[gcp-marketplace]]></category>
            <category><![CDATA[anthos]]></category>
            <category><![CDATA[gke]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Wed, 16 Mar 2022 12:55:09 GMT</pubDate>
            <atom:updated>2022-04-10T04:02:25.619Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google Cloud Anthos Series: Anthos Marketplace Applications</h3><h4>Google Cloud Anthos Series: Part 7</h4><p>Welcome to Part 7 of the ‘Google Cloud Anthos series’. You can find the complete series <a href="https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179">Here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vTdVizK-xmR3qs6ooh7G9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1a3_aNiyWqowzDUUARSKiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BTxLb6ch3pL5Zo3s1JWPA.png" /></figure><h3>Google Cloud <strong>Marketplace</strong></h3><p><strong>Improve your solution procurement experience</strong></p><p>Google Cloud Marketplace lets you quickly deploy functional software packages that run on Google Cloud. Even if you are unfamiliar with GCP services, you can start up a familiar software package without having to manually configure the software, virtual machine (VM) instances, storage, or network settings. You can deploy a software package now, and scale that deployment later when your apps require additional capacity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDK22dFxGlA9uWilIt5RmQ.png" /></figure><p><strong>Deploy Kubernetes apps with ease</strong></p><p>A Kubernetes app is a containerised app that you can run on your Kubernetes cluster. The Kubernetes apps in Cloud Marketplace include container images and configuration files, such as a ‘kubectl’ configuration or a Helm chart. When you deploy an app from Cloud Marketplace, the Kubernetes resources are created in your cluster, and you can manage the resources as a group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDmDYd7HqL9iRbTcnzl1_w.png" /></figure><p><strong>Search your desired Kubernetes apps</strong></p><p>Type ‘gitlab’ in the search bar to locate the Kubernetes app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ol8XvAoLtAwf4Cf63ZbJkg.png" /></figure><p><strong>Configure your Kubernetes app - GitLab</strong></p><p>Click on the ‘CONFIGURE’ option and select appropriate parameter like ‘Existing Kubernetes Cluster’, ‘Namespace’ and ‘App instance name’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zDdImE9MH428jjUTeLkO9w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-oMbHaVl5W5E3hcyBh5GMw.png" /></figure><p><strong>GitLab deployment</strong> <strong>status</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aOvBhvFCiXIvMCp0aBk-zA.png" /></figure><p><strong>GitLab deployment details</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*KqA4ASfuOVNEJjclvuDYrw.png" /></figure><p><strong>Access GitLab Instance</strong></p><p>Use given credentials in the ‘Details’ page to access the GitLab instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4cE5VXXfKSR6akZv1EBYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19GDrNMwrMqeSkRxbOwo2g.png" /></figure><p><strong>Coming up..</strong></p><p>In this blog we discussed Anthos Kubernetes Apps. In upcoming blogs we will continue the Samajik’s journey of Anthos adoption.</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b85c5f7016f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-anthos-series-part7-6b85c5f7016f">Google Cloud Anthos Series - Anthos Marketplace Applications</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Anthos Series: Getting started with Anthos Platform]]></title>
            <link>https://medium.com/google-cloud/google-cloud-anthos-series-part3-e8af35e47bc?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8af35e47bc</guid>
            <category><![CDATA[multi-cloud-management]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[anthos]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Tue, 08 Feb 2022 23:04:22 GMT</pubDate>
            <atom:updated>2022-04-10T03:58:58.448Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud Anthos Series: Part 3</h4><p>Welcome to Part-3 of the ‘Google Cloud Anthos series’. You can find the complete series <a href="https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179">Here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N61teiCdNVIKFmdw8dZFyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_yGbkhP3b8_ToUyMyqppg.png" /></figure><h4><strong>Anthos: Pricing Overview</strong></h4><p>There are two pricing models. <strong>‘Pricing Model-1: Anthos Pricing (All in One)’</strong> makes more sense if organisation wants to use all Anthos native features whereas <strong>‘Pricing Model-2: Individual pricing for Anthos components’</strong> is suitable if organisation want to use one or two features while completely running on Google Cloud Platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ESBUIZ_Wq53AmafJEDBAkA.png" /></figure><blockquote><strong><em>Pricing Model-1: Anthos Pricing (All in One)</em></strong></blockquote><blockquote>In this approach the user just needs to enable ‘Anthos API’ from the Google Cloud Console. Users can select either ‘Pay-as-you-go’ pricing plan or ‘Subscription’ pricing plan.</blockquote><p><strong>Enable Anthos API</strong></p><p>Anthos charges apply to all Anthos managed clusters and are based on the number of Anthos cluster vCPUs, charged on an hourly basis. A vCPU is considered ‘under management’ when it is seen as schedulable compute capacity by the Anthos control plane.</p><p><strong><em>Reference</em></strong>: <a href="https://cloud.google.com/anthos/pricing"><em>Anthos Pricing</em></a></p><blockquote><strong><em>Pricing Model-2: Individual pricing for Anthos components. </em></strong>(Applicable only while running on Google Cloud Platform)</blockquote><blockquote>In this approach Anthos API should be disabled. Users need to enable individual Anthos components.</blockquote><p><strong>Disable Anthos API</strong></p><p>Make sure that Anthos API is disabled if you want to go for an ‘Individual Anthos components pricing’ model.</p><p><strong>Anthos Service mesh</strong></p><p>Anthos Service Mesh is available as part of Anthos or as a standalone offering on Google Cloud. Google APIs enabled on the project determine how you are billed. To use Anthos Service Mesh as a standalone service, don’t enable the Anthos API on your project. If you want to use Anthos Service Mesh on-premises or on other clouds, you must subscribe to Anthos.</p><p><strong><em>Reference</em></strong><em>: </em><a href="https://cloud.google.com/service-mesh/pricing"><em>Service Mesh Pricing</em></a></p><p><strong>Anthos Config Management</strong></p><p>Config Controller uses a GKE cluster as the underlying infrastructure, and you are billed for the Anthos Config Management fee and GKE clusters until the clusters are deleted.</p><p>Note: Anthos customers (Pricing Model-1) are not billed the Anthos Config Management fee as Anthos Config Management is already included in the <a href="https://cloud.google.com/anthos/pricing">Anthos pricing</a>.</p><p><strong><em>Reference</em></strong><em>: </em><a href="https://cloud.google.com/anthos-config-management/docs/pricing"><em>Config Management Pricing</em></a></p><p><strong>Anthos Multi-Cluster Ingress</strong></p><p>If you have GKE clusters that are not licensed for Anthos, you are billed at the standalone pricing rate when you use Multi Cluster Ingress. The functionality of Multi Cluster Ingress is the same whether you use it with Anthos licensing or standalone pricing.</p><p>Note: Multi Cluster Ingress is included as part of Anthos. If you enable the Anthos API and your clusters are registered to a fleet, then there is no additional charge to use Multi Cluster Ingress.</p><p><strong><em>Reference</em></strong><em>: </em><a href="https://cloud.google.com/kubernetes-engine/pricing#multi-cluster-ingress"><em>Anthos Multi-Cluster Ingress</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5m-Mor6YFKOtq2ouoMfTg.png" /></figure><h4>Anthos: Initial Setup Guide</h4><p>This blog series is going to follow ‘<strong>Pricing Model-1: Anthos Pricing (All in One)’</strong> by enabling Anthos API.</p><p>Diagram below indicates the Samajik’s end state architecture. Please follow the step by step guide to setup the Anthos platform and register GKE clusters spread across Asia, Europe and US.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tk_vjraek91b8uPE_yFuVg.png" /><figcaption>Samajik’s End State Architecture on Anthos Platform.</figcaption></figure><p><strong>Google Cloud Project &amp; Billing Account</strong></p><p>In the Google Cloud Console, on the project selector page, select or create a Google Cloud project. Also make sure that billing is enabled for your Cloud project.</p><p><strong>Google Cloud Console: Anthos API</strong></p><p>Enable the Anthos API for your project. Enabling this API entitles you to use Anthos features with the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hcsLbE-nrqhY1Dp03DXRZQ.png" /><figcaption>Anthos API: Google Cloud Dashboard</figcaption></figure><p><strong>Anthos Dashboard: Clusters Option</strong></p><p>In the Google Cloud Console, select the ‘Clusters’ option present in the Anthos section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*Axt0TbqxS1Gtz_hG0YIZcQ.png" /></figure><p><strong>Anthos Dashboard: Create GKE Clusters</strong></p><p>From Anthos dashboard, create new GKE clusters across Asia, Europe and US regions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*oXAwYqYuP3SnEE_RJa0wVw.png" /><figcaption>Anthos Dashboard: Create Cluster Option</figcaption></figure><p><strong>Anthos Dashboard: Register GKE Clusters</strong></p><p>Register newly created GKE clusters to the Anthos control plane</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rKCSoCcL_nL7PHb8cqHgMA.png" /></figure><p><strong>Coming up..</strong></p><p>In this blog we discussed Anthos pricing and Anthos initial setup process. In upcoming blogs we will continue the Samajik’s journey of Anthos adoption.</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8af35e47bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-anthos-series-part3-e8af35e47bc">Google Cloud Anthos Series: Getting started with Anthos Platform</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Anthos Series: Anthos Platform Technical Details]]></title>
            <link>https://medium.com/google-cloud/google-cloud-anthos-series-f12e91c8c928?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/f12e91c8c928</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[multi-cloud-management]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[anthos]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 13:03:44 GMT</pubDate>
            <atom:updated>2022-04-10T03:56:53.675Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud Anthos Series: Part 2</h4><p>Welcome to Part-2 of the ‘Google Cloud Anthos series’. You can find the complete series <a href="https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179">Here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwiIUjvZ8S_l26QaWlYdkg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnvOTAhUJh7EAoVrVGVuOQ.png" /></figure><h3><strong>Anthos Platform: Bringing the cloud to you</strong></h3><p>Anthos unifies the management of applications running on Kubernetes clusters across multiple regions of Google Cloud, On-premises and in multiple public clouds with a Google Cloud backed control plane for consistent operation at scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPlv59G0f5ruQQ_zLd6vsA.png" /></figure><p><strong>Anthos Unified User Interface</strong></p><p>The Anthos dashboard in the Google Cloud Console provides users a secure, unified user interface to view and manage applications spread across multiple Kubernetes clusters. It also provides a simplified view for all Anthos resources. Find sample Anthos dashboard below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9WhNRnh_DG9FDPZL4EQCsQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUPXanqSDPQ63MT9Wf01hA.png" /></figure><p><strong>Anthos Service Mesh</strong></p><p>A service mesh is an architecture that enables managed, observable and secure communication across microservices, letting users create robust enterprise applications made up of many microservices. Service meshes factor out all the common concerns of running a service such as monitoring, networking and security with consistent and powerful tools. Service mesh empowers Developers and DevOps team to focus on creating and managing great applications for their users without making changes to application code.</p><p>Anthos Service Mesh is powered by <a href="https://istio.io/">Istio</a>, a highly configurable and powerful open source service mesh platform. The service mesh monitors all traffic through a proxy. On Kubernetes platform the proxy is deployed by a sidecar pattern to the microservices in the mesh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2OnjaU6y5bhzK33TGEMNzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jynq7DlL5rglef1aSVyzZQ.png" /></figure><p><strong>Anthos Config Management</strong></p><p>Anthos Config Management is a service for configuration and policy management that combines Policy Controller, Config Sync and Config Controller. Application spanning across multiple Kubernetes environments adds complexity in terms of Governance, resource management and consistency. Anthos Config Management provides solution to address this challenge.</p><p>‘GitOps’ or ‘Configuration as code’ is one common approach to managing this complexity, allowing users to store the desired state of the hybrid / multi-cloud environment under Git version control and apply it directly with repeatable results. This approach leverages core Kubernetes concepts, such as Namespaces, labels and annotations to determine how and where to apply the config changes to all of your Kubernetes clusters, no matter where they reside. The Git repo provides a versioned, secured, and controlled single source of truth for all of your Kubernetes configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EUQIuL_yz0KWidQ2k9vhw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X8TzkmMX_M_AoaV1hJyG-A.png" /></figure><p><strong>Anthos Multi-Cluster Ingress</strong></p><p>Multi Cluster Ingress is a cloud-hosted multi-cluster Ingress controller for GKE clusters. It’s a Google-hosted service that supports deploying shared load balancing resources across clusters and across regions. Multi Cluster Ingress is designed to meet the load balancing needs of multi-cluster, multi-regional environments. It’s a controller for the external HTTP(S) load balancer to provide ingress for traffic coming from the internet across one or more clusters.</p><p>Many factors drive multi-cluster topologies, including close user proximity for apps, cluster and regional high availability, security and organisational separation, cluster migration and data locality. As the reasons for multiple clusters grow, the need for a formal and productised multi-cluster platform becomes more urgent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aybLm2h1IjglhB-t-8xwUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HoHuiUj1Kp3Bui7VzadFg.png" /></figure><p><strong>Anthos Logging, Monitoring &amp; Trace</strong></p><p>Google Cloud’s Operations suite offers Integrated monitoring, logging and trace managed services for applications and systems running on Google Cloud and beyond.</p><p><a href="https://cloud.google.com/logging">Cloud Logging</a> is a fully managed service that performs at scale and can ingest application and platform log data, as well as custom log data from GKE environments, VMs, and other services inside and outside of Google Cloud.</p><p><a href="https://cloud.google.com/monitoring">Cloud Monitoring</a> provides visibility into the performance, uptime, and overall health of cloud-powered applications. Collect metrics, events, and metadata from Google Cloud services, hosted uptime probes, application instrumentation, and a variety of common application components.</p><p>Application Performance Management (APM) combines the monitoring and troubleshooting capabilities of Cloud Logging and Cloud Monitoring with <a href="https://cloud.google.com/trace">Cloud Trace</a>, <a href="https://cloud.google.com/debugger">Cloud Debugger</a>, and <a href="https://cloud.google.com/profiler">Cloud Profiler</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_SUTS3g_o-mGR-Dcihp4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Shp3FWXIXQBfXl4PcI_5A.png" /></figure><p><strong>Anthos Marketplace Applications</strong></p><p>A Kubernetes app is a ‘Containerized’ app that can be run on the Kubernetes cluster. The Kubernetes apps in Cloud Marketplace include container images and configuration files, such as a ‘Kubectl’ configuration or a ‘Helm chart’. When user deploys an app from Cloud Marketplace, the Kubernetes resources gets created in the cluster, and it can be managed as a group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xQA7HNhhT2EvA7514ElFXA.png" /></figure><p><strong>Anthos Cloud Run</strong></p><p>Cloud Run for Anthos is Google’s managed and fully supported <a href="https://knative.dev/">Knative</a> offering. Cloud Run for Anthos abstracts away the complexity of Kubernetes, making it easy to build and deploy serverless workloads across hybrid and multi-cloud environments. Cloud Run is also available as a fully managed serverless platform on Google Cloud, without the Kubernetes platform requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*comnC_F2fHz2_TFSoMISpg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tmYqG1ih9v3sb9Mps0Z_A.png" /></figure><p><strong>No Vendor Lock-In</strong></p><p>Anthos platform has been designed keeping Open Source technologies in mind which gives freedom to users to modernise without vendor lock-in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s7gDFnwZUG89rS6KvzgTng.png" /></figure><p><strong>Coming up..</strong></p><p>In this blog we discussed Anthos technical details and capabilities. In upcoming blogs we will continue the Samajik’s journey of Anthos adoption.</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f12e91c8c928" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-anthos-series-f12e91c8c928">Google Cloud Anthos Series: Anthos Platform Technical Details</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Anthos Series: Anthos Platform Introduction]]></title>
            <link>https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b9a35e9179</guid>
            <category><![CDATA[gke]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[anthos]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Tue, 18 Jan 2022 12:53:44 GMT</pubDate>
            <atom:updated>2022-04-10T03:53:36.780Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud Anthos Series: Part 1</h4><p>Welcome to the multi part series on ‘Google Cloud Anthos platform’. In this blog series, we will explore how fictional organisation called ‘Samajik’ can scale their Kubernetes based application across multiple Google Cloud regions using Google Cloud’s Anthos platform.</p><p>We will cover the Samajik’s Anthos adoption journey in this blog series.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsW2JzjoMMXYM_GA-MwGvA.png" /><figcaption>*The company name and personas mentioned in the storyline are fictional</figcaption></figure><p><strong>Part-1</strong>: Anthos Platform Introduction (This blog)</p><p><strong>Part-2</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-f12e91c8c928">Anthos Platform Technical Details</a></p><p><strong>Part-3: </strong><a href="https://medium.com/google-cloud/google-cloud-anthos-series-part3-e8af35e47bc">Getting started with Anthos Platform</a></p><p><strong>Part-4</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-part4-e23172b61ec9">Anthos Service Mesh</a></p><p><strong>Part-5</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-part5-a17ce89ddc7a">Anthos Config Management</a></p><p><strong>Part-6</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-part6-bbb70e2f9979">Anthos Multi-cluster Ingress</a></p><p><strong>Part-7</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-part7-6b85c5f7016f">Anthos Marketplace Applications</a></p><p><strong>Part-8</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-part8-2af3bdce0c9b">Migrate for Anthos and GKE</a></p><p><strong>Part9</strong>: <a href="https://medium.com/google-cloud/google-cloud-anthos-series-anthos-multi-cloud-hybrid-story-fc70ce352c40">Anthos Multi-cloud &amp; Hybrid story</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQdzDmDZigoRrz8T6CM1Uw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFFGremvPbWQLMnXtKnxuw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ioh1ncMpeXTaNtnSxecuLQ.png" /></figure><p>This is Samajik’s application architecture diagram. Internally the application is called ‘Unicorn’ which is currently running in the Google Cloud’s Mumbai region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oV2bgux6BjMeiaZTJ64YVw.png" /><figcaption>Samajik’s ‘Unicorn’ Application architecture on Google Cloud</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9W20orX9J9_R4DH7GvPI9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_0T8veWCLYe_GmXzmxNww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*akHLYW6uuHANfg-MITC_2Q.png" /></figure><p><strong>Introducing Google Cloud’s Anthos Platform</strong></p><p>Anthos is a modern application management platform that provides a unified model for computing, networking, and even service management across multiple clouds (GCP, AWS, Azure) and private On-premise data centres. The technology stack is built on a consistent set of APIs based on open-source technologies which empowers developers and operators with a single set of tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*C9nTGfQWt38Y__1yiD_yUA.png" /></figure><p>Anthos is a Kubernetes-based platform that runs everywhere you do, with a cloud-backed control plane for centralised management. Anthos provides</p><ol><li>Application Management</li><li>Infrastructure Automation</li><li>End-to-End Observability</li><li>Compliance &amp; Governance</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6eXfGsY6uoVapHp6g1zrxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-hvGI2v6jF6DE5ZBBrruw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tk_vjraek91b8uPE_yFuVg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUhZSGLFhyopVGo02ABnhw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4FeFPabSV7q57hWVDPJCKw.png" /><figcaption>Reference: <a href="https://services.google.com/fh/files/misc/the_total_economic_impact_of_anthos.pdf">https://services.google.com/fh/files/misc/the_total_economic_impact_of_anthos.pdf</a></figcaption></figure><p><strong>Coming up..</strong></p><p>In this blog we discussed Anthos value proposition. In upcoming blogs we will continue the Samajik’s journey of Anthos adoption.</p><p><strong>Reference</strong></p><p>You can refer to the <a href="https://medium.com/google-cloud/google-cloud-devops-part-1-introduction-to-google-native-devops-process-bfb55be9e3f3">Google Cloud DevOps Series </a>to understand ‘How Samajik transformed their DevOps landscape using Google Cloud native tools &amp; principles’.</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b9a35e9179" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-anthos-series-23b9a35e9179">Google Cloud Anthos Series: Anthos Platform Introduction</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud DevOps Series: Observability with SRE principles]]></title>
            <link>https://medium.com/google-cloud/part-5-google-devops-observability-with-sre-principles-33446da05c16?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/33446da05c16</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Wed, 01 Dec 2021 05:31:53 GMT</pubDate>
            <atom:updated>2022-03-28T04:31:17.225Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud DevOps Series: Part-5</h4><p><strong>Welcome to Part 5 of the Google Cloud DevOps series.. You can find the complete series </strong><a href="https://medium.com/google-cloud/google-cloud-devops-part-1-introduction-to-google-native-devops-process-bfb55be9e3f3"><strong>Here</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQmlQnoJkEU0JH3u6B6v0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*WIp8vnvlgVeYrCSJu3-lnA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*hdDbEHvJSDCBvUcZsRtC9A.png" /></figure><p>As Samajik becomes more agile and moves towards increasing development velocity, Samajik DevOps team would want to make sure that they respond to urgent issues that are impacting customers and not reacting to minor issues and being woken up in the middle of the night. To accomplish this objective, many organisations are adopting the SRE model defined by Google.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GQqdxEhvq4enpv4zhZvVTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1n-4tta7zTislUpsdoaAuA.png" /><figcaption>Reference: <a href="https://sre.google/books/">https://sre.google/books/</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*P9F_LHUFW5v6jBNYsktQJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oaxxADlSkSd89UiAZxOK3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iD8p2dDQaiK2UoH0Jiz4Kg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gC-NDuWI4iuRCAYtv-Jocg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4n9xWLDVuDZu0ZdrpBgzJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hzamRlYog0-tSa3TLua7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3dNbD9BsCQ_upaiUxE2q5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*SNWS-XTM78XLbGEW9d9UEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CeZGJjo7oCgEVanlKGk0fQ.png" /></figure><h4><strong><em>GKE Platform Observability-Logging and Monitoring (Demo)</em></strong></h4><p>In the earlier parts of this series we have created multiple GKE clusters. Let’s understand Observability techniques using the Production cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*JtoFmHTCqI57q63D_EA7KQ.png" /></figure><p>One of the key benefits of ‘Google Cloud Operations’ is the ability to collect Out-of-the-box collection of system metrics, logs, and rich context without any agent deployment.</p><p><strong>Salient Features:</strong></p><ol><li>Key metrics for GKE clusters, nodes, namespaces without installing agents.</li><li>Default collection of application logs</li><li>Metadata and relationships amongst GKE entities objects</li></ol><blockquote>Navigate to the <strong><em>Operations-Monitoring</em></strong> and click on the <strong><em>Dashboards. </em></strong><em>It will show Dashboards for all Google Cloud services.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CB-PDdXMgBQrsnkJsjXqtQ.png" /><figcaption><strong>Google Cloud Monitoring Dashboards-All Services</strong></figcaption></figure><blockquote>Navigate to the <strong><em>Dashboards </em></strong>section<strong><em> </em></strong>and click on the <strong><em>GKE</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pLQs7phZqKRFGSib-KALhw.png" /></figure><blockquote>Navigate to the <strong><em>Services section. </em></strong>On this ‘services overview’ page, there is a list of services and a summary of services for which alerts are firing on SLOs as well as services that are out of error budgets. Observe that currently there are no SLOs defined for the services.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8dWX3h_og3c_Qa_ykHUMg.png" /><figcaption><strong>Google Cloud Monitoring Services Dashboard</strong></figcaption></figure><blockquote>Let’s define the Service first. Go to the <strong><em>DEFINE SERVICE</em></strong> option and select the service for example <strong><em>‘frontend’ </em></strong>service</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3_xlC6Y_ByPQ8I33eFsuOA.png" /></figure><blockquote>Before we can set an SLO, the first thing we need to do is to identify a Service Level Indicator on which we create an SLO. Click on the ‘<strong><em>frontend’</em></strong> service and select the ‘<strong><em>Create SLO</em></strong>’ option. Follow the steps given below.</blockquote><blockquote>Step-1: Set your Service Level Indicator by selecting either Request-based or Window-based option and then click on Continue.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dtj30RTvmgaHfFOV_vnZMg.png" /></figure><blockquote>Step-2: Define Service Level Indicator details by selecting the appropriate Performance metric eg. ‘kubernetes.io/container/restart_count’</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ri0mUkxd7RxyCxaVTChrQ.png" /></figure><blockquote>Step-3: Define your Service Level Objective by selecting ‘Compliance period’ and ‘Performance goal’</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aS5y51pDeg8MiSsdkmDCqA.png" /></figure><blockquote>Step-4: Review the settings and Create the SLO.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8E9QKXIP6tlVrAOyCSGSQ.png" /></figure><blockquote>Navigate to the <strong>Operations-Logging</strong> <em>section</em>.<em> Logs of the desired microservice can be explored using the Query in search section.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUQKFPjbrCskBO5QIbg8HQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*fQMAoEIBJQBuglLZzdue_w.png" /></figure><p>You can refer to the <a href="https://www.youtube.com/playlist?list=PLIivdWyY5sqJrKl7D2u-gmis8h9K66qoj">SRE implements DevOps Series</a> on YouTube to understand more about SRE principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDEwM-rndIO5GxYgDUQV_Q.png" /><figcaption>Reference: <a href="https://www.youtube.com/watch?v=uTEL8Ff1Zvk&amp;list=PLIivdWyY5sqJrKl7D2u-gmis8h9K66qoj">https://www.youtube.com/watch?v=uTEL8Ff1Zvk&amp;list=PLIivdWyY5sqJrKl7D2u-gmis8h9K66qoj</a></figcaption></figure><h4>Coming up…</h4><p>In this blog, we learned SRE principles and how to implement them using Cloud Operations tools. Guhan was impressed with the DevOps philosophy and Google SRE practice. Guhan and his team at Samajik implemented not just the CI/CD and developer workflow but Observability as well. Let’s stay tuned for the discussion which will cover Agility with Cost-optimisation…</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/ee905ea343d">Tushar Gupta</a></p><p>Update: You can read Part-6 <a href="https://medium.com/@tusharguptag/google-devops-agility-with-cost-optimization-930ad77ccc63">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33446da05c16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/part-5-google-devops-observability-with-sre-principles-33446da05c16">Google Cloud DevOps Series: Observability with SRE principles</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud DevOps Series: Continuous Development Workflow]]></title>
            <link>https://medium.com/google-cloud/part-3-google-devops-continuous-development-workflow-3ef446edfeb7?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ef446edfeb7</guid>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Wed, 03 Nov 2021 05:38:08 GMT</pubDate>
            <atom:updated>2022-03-28T04:20:12.424Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud DevOps Series: Part-3</h4><p><strong>Welcome to Part 3 of the Google Cloud DevOps series.. You can find the complete series </strong><a href="https://medium.com/google-cloud/google-cloud-devops-part-1-introduction-to-google-native-devops-process-bfb55be9e3f3"><strong>Here</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xw-1UABifozj4fRoqd3L7w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73j6xIqQdXhfWojHn1BMig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WEq94sxgmizJ8gLqUea3Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ks5YWIpTrUwNCUqsaBKfog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oy20B1Y4MV3MdWu4XSv7zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KzhoZTNtutN_7lxsC75aXA.png" /></figure><p><strong>Continuous Development Workflow: Hands-on Demo</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gdeK7EQuTpDX-f5T" /></figure><p>‘gcloud’ is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell. In the cloud shell environment type the following command to set the project.</p><pre>gcloud config set project &lt;Your-Project-Name&gt;</pre><p>Set ‘PROJECT_NAME’ variable</p><pre>PROJECT_NAME=&lt;Your-Project-Name&gt;</pre><p>Create the GKE cluster for development purpose</p><pre>gcloud beta container --project &quot;$PROJECT_NAME&quot; clusters create &quot;dev-cluster&quot; --zone &quot;us-central1-a&quot; --no-enable-basic-auth --cluster-version &quot;1.20.10-gke.301&quot; --release-channel &quot;regular&quot; --machine-type &quot;e2-medium&quot; --image-type &quot;COS_CONTAINERD&quot; --disk-type &quot;pd-standard&quot; --disk-size &quot;10&quot; --metadata disable-legacy-endpoints=true --scopes &quot;https://www.googleapis.com/auth/cloud-platform&quot; --max-pods-per-node &quot;110&quot; --num-nodes &quot;6&quot; --logging=SYSTEM,WORKLOAD --monitoring=SYSTEM --enable-ip-alias --network &quot;projects/placeholder-322809/global/networks/default&quot; --subnetwork &quot;projects/placeholder-322809/regions/us-central1/subnetworks/default&quot; --no-enable-intra-node-visibility --default-max-pods-per-node &quot;110&quot; --no-enable-master-authorized-networks --addons HorizontalPodAutoscaling,HttpLoadBalancing,GcePersistentDiskCsiDriver --enable-autoupgrade --enable-autorepair --max-surge-upgrade 1 --max-unavailable-upgrade 0 --enable-shielded-nodes --node-locations &quot;us-central1-a&quot;</pre><p>Verify newly created GKE cluster on Google Cloud console</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*47YUbahPVrzrSiPw" /></figure><p>Go to the cloud Shell and connect to the cluster</p><pre>gcloud container clusters get-credentials dev-cluster — zone us-central1-a — project $PROJECT_NAME</pre><p>Open <strong>ide.cloud.google.com</strong> and navigate to the microservices-demo folder which you have already cloned. (Note — Refer to the <a href="https://medium.com/google-cloud/google-cloud-devops-series-4013adab603b"><strong>Blog-2</strong></a><strong> </strong>for steps)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/0*2aNnZ09f8cWlfJGQ" /></figure><p>Locate the skaffold.yaml file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d67ZFrwqZrxEhwtT" /></figure><p>Select the ‘Cloud Code’ option</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EQDi1C9Vi-u3CLc6" /></figure><p>Select the ‘Run on Kubernetes’ option</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m5aIuJYzXsPEAWql" /></figure><p>Select the appropriate GKE cluster</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Oa1SWHrt3xLSVPgL" /></figure><p>It will start building the Microservices. Check the progress in the output section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_853KbD45cPKNgdl" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CQ4CzOr6H_HKpEfP" /></figure><p>Access the application:</p><p>Note the Public IP address of the frontend-external service. Click on the Public IP address and it will open the application in your default browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0B8qupBSm_0V_xCR" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x59k2nL7VklFPma5" /></figure><p>Make the code changes and observe automatic deployment</p><p>Go to the file ‘microservices-demo/src/frontend/templates/header.html’ in the source codebase and locate the following text</p><pre>Free shipping with $75 purchase!</pre><p>Change ‘$75’ to ‘$150’</p><pre>Free shipping with $150 purchase!</pre><p>Skaffold detects the change automatically, starts the build and deploy process for the corresponding Microservice. Skaffold does not build and deploy other microservices which are not associated with the code change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tHNGRVPk0qxkDR0O" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHQBiizDufVOgiIoImyZNA.png" /></figure><h4>Coming up…</h4><p>In this blog, we learned continuous development workflow with GKE in Google Cloud. Now Guhan became even more curious to learn how he can implement end to end CI/CD workflow on Google cloud for Samajik’s containerised workloads. Stay tuned to Ram and Guhan’s conversation to know more about this..</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/ad9524f7f7fa">Jeevana Hegde</a>, <a href="https://medium.com/u/ee905ea343d">Tushar Gupta</a></p><p>Update: You can read Part-4 <a href="https://medium.com/google-cloud/part-4-google-devops-continuous-development-workflow-3feb1ea2227e">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ef446edfeb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/part-3-google-devops-continuous-development-workflow-3ef446edfeb7">Google Cloud DevOps Series: Continuous Development Workflow</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud DevOps Series: Introduction to DevOps in Google Cloud]]></title>
            <link>https://medium.com/google-cloud/google-cloud-devops-part-1-introduction-to-google-native-devops-process-bfb55be9e3f3?source=rss-c79cc28e2999------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfb55be9e3f3</guid>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Pushkar Kothavade]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 11:57:18 GMT</pubDate>
            <atom:updated>2022-03-28T04:25:36.677Z</atom:updated>
            <content:encoded><![CDATA[<h4>Google Cloud DevOps Series: Part-1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UU-1gGelK6aqWdF30ZJ7SQ.png" /><figcaption>*The company name and personas mentioned in the storyline are fictional</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zAOU70_GN8mr_HV17OWu-A.png" /></figure><p><strong>What is DevOps in a Google way?</strong></p><p>As every organization is becoming a software company, agile software development practices and DevOps practices are becoming mainstream today. As a part of the digital transformation journey, organizations are adopting DevOps practices with the primary objective of increasing collaboration between the development team and operations team, to enable frequent, faster and reliable software releases. Improved return on investment (RoI) is a natural by-product of this process.</p><p>As each organization has different culture, processes, technical capabilities, technology adoption, and tech debt, Google Cloud offers a comprehensive solution through a Google Cloud Application Modernization Program (<a href="https://cloud.google.com/camp"><em>CAMP</em></a>) to meet the customers where they are and make their application development and deployment process better. CAMP program leverages Google’s multiple decades of software development experience and research findings from the DevOps Research and Assessment (DORA) Project. Built on the foundation of CAMP and DORA, Google Cloud has come up with the opinionated solution for the end-to-end application development for the containerized workloads.</p><p>We will take a detailed look at all the DevOps stages below:</p><p><strong>Part-1</strong>: Introduction to DevOps in Google Cloud (This blog)</p><p><strong>Part-2</strong>: <a href="https://medium.com/google-cloud/google-cloud-devops-series-4013adab603b">Google Cloud compute options for Kubernetes</a></p><p><strong>Part-3</strong>: <a href="https://medium.com/@pushkarbk/part-3-google-devops-continuous-development-workflow-3ef446edfeb7">Google DevOps-Continuous Development Workflow</a></p><p><strong>Part-4</strong>: <a href="https://medium.com/@anchitn_19522/part-4-google-devops-continuous-development-workflow-3feb1ea2227e">Google DevOps-Continuous Integration / Continuous Deployment Workflow</a></p><p><strong>Part-5</strong>: <a href="https://medium.com/google-cloud/part-5-google-devops-observability-with-sre-principles-33446da05c16">Google DevOps-Observability with SRE principles</a></p><p><strong>Part-6</strong>: <a href="https://medium.com/@tusharguptag/google-devops-agility-with-cost-optimization-930ad77ccc63">Google DevOps-Agility with Cost Optimisation</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7U2Zm9T5k9YTKL9A_GIVNg.png" /></figure><p><strong>Kubernetes is the de-facto platform for the containers</strong></p><p>Google is the birthplace of Kubernetes. It builds on 15+ years’ experience of running Google’s containerized production workloads and also the valuable contributions from the large open-source community. Kubernetes is a spinoff from Google’s internal cluster management system, Borg. Google decided to open-source the Kubernetes project in the year 2014 and currently the project is hosted under CNCF foundation.</p><p>Kubernetes is the leading open-source platform today for container orchestration and management. It provides automated deployment, operations, scaling, and management of the containerized applications. With the widespread adoption of containers among digital natives and enterprise businesses, Kubernetes has become the de-facto standard to deploy and operate containerized applications. Agility is the key to success in today’s fast paced cloud-scale world. Kubernetes provides an automated container orchestration that reduces the time-to-market (TTM) for mission-critical business applications, enabling you to deliver value to customers in faster iterations. It enhances reliability of the system and reduces the operational overhead which helps organizations obtain better RoI.</p><p>Google Kubernetes Engine (GKE) provides managed Kubernetes clusters on the Google Cloud Platform. GKE can be deployed in minutes with just a few clicks.</p><p>GKE provides a highly available, scalable, secured, and completely managed platform to run production grade workloads. (We will be exploring GKE in detail in part two of this blog series)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3E8jC8YhyG5KGnqvi2lqw.png" /></figure><p><strong>How can you build a CI/CD system for Kubernetes ?</strong></p><p>Post release of Kubernetes in 2014, the entire CI/CD ecosystem around the containers also started evolving. As with any new technology, this evolution of DevOps processes for Kubernetes was also not free of challenges. On one hand, organizations started leveraging existing tools and deployment methodologies which were not optimized for containerized workloads; on the other hand, people also started experimenting and integrating various open-source tools like Argo CD for CI/CD, Harbour for container registry, Helm for package management etc. Kubernetes native CI/CD system mainly consists of the following building blocks:</p><ul><li>Version control system (eg. Git)</li><li>CI tool (eg. Jenkins)</li><li>Container registry (eg. Docker registry)</li><li>CD tool (eg. Spinnaker)</li><li>Compute platform for containers (eg. self-managed or managed Kubernetes platform)</li></ul><p>Though these solutions serve the purpose of CI/CD, the amount of effort it takes from the DevOps / Platform team to build and maintain the integrations is substantial. At Google Cloud, we solve this challenge by providing the complete end-to-end CI/CD platform, keeping containers at the center stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CF_I3KzKu76_cLBS39V5RQ.png" /></figure><p><strong>End-to-end Application Modernization platform using Google DevOps</strong></p><p>Google Cloud provides end-to-end opinionated solutions for the entire DevOps process. The Google Site Reliability Engineering (SRE) team manages Google DevOps Platform services and it is also completely serverless in nature. It comes as no surprise that Google Cloud is positioned as a leader in the ‘Multi-Cloud Container Development Platform’ category as per the Forrester Wave, 2020 report (<a href="https://www.forrester.com/report/The-Forrester-Wave-Multicloud-Container-Development-Platforms-Q3-2020/RES157266">Reference</a>).</p><p><strong>Google DevOps Platform — Building blocks</strong></p><p>Google DevOps platform consists of the following building blocks that describe key activities/tools at each stage- Code, Source Repo, Build &amp; Package, Deploy, Run, Operate/SRE. A high-level overview of how they integrate with each other is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNu2qYW8kuRGgOooBQz6Dg.png" /></figure><p>Let’s explore each of these building blocks in detail-</p><p><strong>Code</strong></p><p>Cloud Code is a set of Integrated Development Environment (IDE) plugins which can be used in conjunction with existing IDEs, in order to simplify the cloud-native development process, developers can write, deploy, and debug containerized applications directly from IDEs, such as <a href="https://cloud.google.com/code">VS Code</a> and <a href="https://cloud.google.com/code">IntelliJ</a>, onto fully-managed compute offerings like GKE and Cloud Run(serverless).</p><p><strong>Source Repo</strong></p><p>Google Source Repository is a single place for the entire team to store, manage, and track codebase. Some notable feature of the service are:</p><ul><li>Google Source Repository is Git compliant</li><li>It can be configured to automatically sync with the hosted repository on GitHub or Bitbucket</li><li>Provides an inbuilt view to focus on a specific branch, tag, or commit</li></ul><p><strong>Build</strong></p><p>Cloud Build provides a fully-managed serverless platform to build software quickly across all programming languages, including Golang, Java, Python, Node.js, and other programming languages.</p><p><strong>Package</strong></p><p>Artifact Registry is an universal package manager which enables customers to centrally store artifacts and build dependencies. Seamless integration with other cloud services, like Cloud Build and GKE, provides integrated Google Cloud experience.</p><p><strong>Run</strong></p><p>Google Cloud provides multiple options to run your containerized application workloads including:</p><ul><li>GKE : Google Cloud provides GKE service which is a managed service for running Kubernetes</li><li>Cloud Run: It provides a fully-managed serverless platform to run containerized stateless application workloads</li></ul><p><strong>Operate/SRE</strong></p><p>Google Cloud’s operations suite extends Google’s best SRE tools and practices to the customers. Cloud Monitoring, Cloud Logging, and Advanced Observability tools (Trace, Debugger, and Profiler) are part of Google Cloud’s operations suite and has the following capabilities available out of the box</p><ul><li>Capture signals like metrics, logs, and trace from applications and cloud services</li><li>Provides dashboard and troubleshooting tools for visualization and analysis</li><li>Manage incidents through Alerts, Errors, and Service-Level Objectives (SLOs)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bUQXgrqTxGPTDDrma0Im-w.png" /></figure><p><strong>Coming up..</strong></p><p>In this blog we listened to Ram’s suggestions to Guhan on the main constructs of Google Cloud DevOps and how Google Cloud can help him get started in his modernization journey through DevOps and containerized workloads. Let us stay tuned for further details shared by Ram to Guhan on the tools and managed services that can help him build his own DevOps processes for modern workloads.</p><p>Contributors: <a href="https://medium.com/u/41b475b881ff">Shijimol A K</a>, <a href="https://medium.com/u/71d9487165c6">Dhandus</a>, <a href="https://medium.com/u/2d47f7f3f8e2">Anchit Nishant</a>, <a href="https://medium.com/u/ad9524f7f7fa">Jeevana Hegde</a></p><p>Update: You can read Part-2 <a href="https://medium.com/google-cloud/google-cloud-devops-series-4013adab603b">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfb55be9e3f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-devops-part-1-introduction-to-google-native-devops-process-bfb55be9e3f3">Google Cloud DevOps Series: Introduction to DevOps in Google Cloud</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>