In this blog, we are going to deploy a highly available application on GKE with a step-by-step guide.<\/p>\n
Step 1: Activate GCP Cloud Shell by clicking on the icon\u00a0 It will activate the Cloud Shell as per below:<\/p>\n Note: The Project has already been selected as we open Cloudshell from web browser. Use gcloud config set project [PROJECT_ID]<\/strong> to change project.<\/p><\/blockquote>\n Step 2: Create a ct-demo<\/strong> repository for storing container images in the Docker repository<\/p>\n Step 3: Create a Dockerfile<\/p>\n Step 4: Upload your WAR application in CloudShell<\/p>\n Step 5: Create Docker image from Dockerfile in the same directory where WAR file is uploaded<\/p>\n Output:<\/strong><\/p>\n Note: The PROJECT_ID is environment variable to store Project ID information. Instead of env variable you can also use paste Project ID directly in above command<\/p><\/blockquote>\n Step 6: Push Docker Image in Artifact repository created in Step 2<\/p>\n Step 7: Create GKE Cluster<\/p>\n Step 8: Create deployment.yml from below textbox and run command<\/p>\n Step 9: Create service.yml from below textbox and run command<\/p>\n Step 10: Upload SSL to cloud shell and add SSL into secrets that Ingress controller will use for SSL-termination<\/p>\n Step 11: Create ingress.yml from below textbox and run the command<\/p>\n Step 12: Review all the resources and test your application by requesting an External IP of the ingress controller<\/p>\n Output:<\/strong><\/p>\n To Create HorizontalPodAutoscaler <\/strong>on deployment on the basis of CPU usage<\/p>\n Keep it up! You have deployed a highly available and scalable Tomcat application on GKE<\/p>\n I hope you find this blog helpful for your Kubernetes (GKE) journey<\/p>\n Please do not forget to delete resources to avoid incurring charges to your Google account using the below commands<\/p>\n Kubernetes<\/a> works on the same design principles that run popular Google services and provides the same advantages as automatic management, monitoring, and liveness probes for application containers, automatic scaling, rolling updates, and more. When running your applications on a cluster, you use Google’s 10+ years of technology and experience to run production workloads in containers.<\/p>\n For detailed information on Kubernetes works, here is a blog on Beginner’s Guide with Real-world Illustration<\/strong><\/a><\/p>\n We here at\u00a0CloudThat<\/strong>\u00a0<\/a>are the official Google Cloud Partner, AWS Advanced Consulting Partner, Microsoft gold partner, helping people develop knowledge on cloud and help their businesses aim for higher goals using best in industry cloud computing practices and expertise. We are on a mission to build\u00a0a robust\u00a0cloud computing ecosystem by disseminating\u00a0knowledge on technological intricacies within the cloud space.\u00a0Our blogs, webinars,\u00a0case studies, and white papers\u00a0enable all the stakeholders in the cloud computing sphere.<\/p>\n Feel free to drop a comment or any queries that you have regarding Google Cloud Platform, Google Kubernetes Engine, consulting requirements and we will get back to you quickly. To get started, go through\u00a0our\u00a0Expert Advisory\u00a0<\/strong><\/a>page\u00a0and\u00a0Managed Services Package<\/strong><\/a>\u00a0<\/strong>that is\u00a0CloudThat<\/strong><\/a>\u2019s<\/strong>\u00a0offerings.<\/p>\n","protected":false},"author":219,"featured_media":10731,"parent":0,"comment_status":"open","ping_status":"open","template":"","blog_category":[3607,3718],"user_email":"prarthitm@cloudthat.com","published_by":"324","primary-authors":"","secondary-authors":"","acf":[],"_links":{"self":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/10542"}],"collection":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog"}],"about":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/types\/blog"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/users\/219"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/comments?post=10542"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/10542\/revisions"}],"predecessor-version":[{"id":45727,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog\/10542\/revisions\/45727"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/media?parent=10542"}],"wp:term":[{"taxonomy":"blog_category","embeddable":true,"href":"https:\/\/www.cloudthat.com\/resources\/wp-json\/wp\/v2\/blog_category?post=10542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"GKE\"](\"https:\/\/content.cloudthat.com\/resources\/wp-content\/uploads\/2022\/11\/GKE1.png\")
<\/a><\/p>\nPerquisites:<\/h3>\n
\n
Kubernetes components to be covered:<\/h3>\n
\n
Step by Step Guide<\/h3>\n
<\/a> from the right top of the console<\/p>\n<\/a><\/p>\n$ gcloud artifacts repositories create ct-demo \\\r\n --repository-format=docker \\\r\n --location=asia-south1 \\\r\n --description=\"Docker repository\"\r\n<\/pre>\n
$ mkdir ct-demo && cd ct-demo\r\n$ cat <<EOF > Dockerfile \r\nFROM tomcat:8.5.73-jdk8-corretto\r\n\r\nADD ROOT.war \/usr\/local\/tomcat\/webapps\/\r\n\r\nEXPOSE 8080\r\nCMD [\"catalina.sh\", \"run\"]\r\n<\/pre>\n
<\/a><\/p>\n<\/a><\/p>\n$ docker build -t asia-south1-docker.pkg.dev\/${PROJECT_ID}\/ct-demo\/demo-app:v1 .\r\n$ docker images \r\n<\/pre>\nREPOSITORY TAG IMAGE ID CREATED SIZE\r\nasia-south1-docker.pkg.dev\/my-project\/ct-demo\/demo-app v1 25cfadb1bf28 10 seconds ago 154 MB<\/pre>\n
$ gcloud auth configure-docker asia-south1-docker.pkg.dev\r\n\r\n$ docker push asia-south1-docker.pkg.dev\/${PROJECT_ID}\/ct-demo\/demo-app:v1\r\n<\/pre>\n$ gcloud config set compute\/zone asia-south1-a\r\n\r\n$ gcloud container clusters create demo-cluster\r\n\r\n#It will take few minutes for cluster to come up.\r\n\r\n#verify cluster by running command below \r\n$ kubectl get nodes<\/pre>\n
apiVersion: apps\/v1\r\nkind: Deployment\r\nmetadata:\r\n name: demoapp\r\nspec:\r\n replicas: 1\r\n template:\r\n metadata:\r\n name: demoapp\r\n labels:\r\n app: demoapp\r\n spec:\r\n containers:\r\n - image: asia-south1-docker.pkg.dev\/my-project \/ct-demo\/demo-app:v1\r\n name: demoapp-pod\r\n readinessProbe:\r\n httpGet:\r\n path: \/rest\/health\r\n port: 8080\r\n ports: #Container port number\r\n - containerPort: 8080 \r\n env: #Set the environment variable for the container, and you can connect mysql with the tomcat\r\n - name: JAVA_OPTS\r\n value: \u201c-dDB\u201d \r\n selector:\r\n matchLabels:\r\n app: demoapp<\/pre>\n
$ kubectl create -f deployment.yml<\/pre>\n
apiVersion: v1\r\nkind: Service\r\nmetadata:\r\n name: nodeport-svc-demo\r\nspec:\r\n type: NodePort\r\n selector:\r\n app: demoapp\r\n ports:\r\n - name: demo-port\r\n protocol: TCP\r\n port: 80\r\n targetPort: 8080<\/pre>\n
$ kubectl create -f service.yml<\/pre>\n
$ kubectl create secret tls demo-ssl-cert \\\r\n --cert=path\/to\/cert\/file \\\r\n --key=path\/to\/key\/file<\/pre>\n
apiVersion: networking.k8s.io\/v1\r\nkind: Ingress\r\nmetadata:\r\n name: demo-ingress-lb\r\nspec:\r\n tls:\r\n - secretName: demo-ssl-cert\r\n rules:\r\n - http:\r\n paths:\r\n - pathType: ImplementationSpecific\r\n backend:\r\n service:\r\n name: nodeport-svc-demoa\r\n port:\r\n name: demo-port<\/pre>\n
$ kubectl create -f ingress.yml<\/pre>\n
$ kubectl get all\r\n\r\n$ kubectl get ingress<\/pre>\n
NAME CLASS HOSTS ADDRESS PORTS AGE\r\ndemo-ingress-lb <none> * 31.4.62.179 80, 443 44s<\/pre>\n
Optional:<\/h3>\n
$ kubectl autoscale deployment demo-app --cpu-percent=80 --min=1 --max=5<\/pre>\n
# Delete Ingress\r\n$ kubectl delete ingress demo-ingress-lb\r\n\r\n# Delete Cluster \r\n$ gcloud container clusters delete demo-cluster --zone asia-south1-a\r\n\r\n# Delete you container image repository\r\n$ gcloud artifacts docker images delete \\\r\n asia-south1-docker.pkg.dev\/${PROJECT_ID}\/ct-demo\/demo-app:v1 \\\r\n --delete-tags --quiet<\/pre>\nConclusion:<\/h3>\n
About CloudThat<\/h3>\n