Skip to main content

Kubernetes on Google Cloud Platform - Part 1 Set up GCP

Moving into a containerized world can be tricky and confusing at first. The orchestration portion of containers and the ability to scale them can be the trickiest. In this 3 part series, we're going to go over spinning up Kubernetes in Google Cloud Platform. Kubernetes original design was built by Google itself, so what other better place to test and host our Kubernetes cluster?

Please Note: To follow along in this blog post, this will require a credit card. This is so Google can confirm identity. Google will give a free 300 credit for at the time of writing this is 12 months.

The first thing we want to do is head over to https://cloud.google.com/ and confirm you have a Gmail account. Next, let's click the "try free" button.

Next, let's click through the EULA and confirm your information on step 2. (You will see a second screen that is different than mine. I did not show a screenshot due to personal information)




You should see a "Creating project" screen. This is GCC getting your console ready with your account.


Once completed, you will be at the home page of your console.


On the left pane you will see a Kubernetes button. Go ahead and click that, then click "clusters".

Please Note: It will take some time for the Kubernetes cluster to get started.




When that is complete, let's go ahead and create our Kubernetes cluster.

For our purposes, we'll go ahead and create a cluster with the following configurations:
1) Standard cluster
2) Name = Whatever you'd like (lower case characters are allowed)
3) Zone = us-central1-a
4) Kubernetes master version = default(1.10.9-gke5)
5) Nodes = 2
6) CPUs = 2vCPUs
7) RAM = 7.5GB

On the bottom, go ahead and click "create".


Once the cluster is complete, you'll see a green check mark.

Now that our cluster is up, let's go ahead and click the "connect" button. You have two  ways to connect:
1) Google Shell
2) Dashboard

Because we dislike the GUI and love the terminal, let's use the Shell!

There will be a pre-made line for you already in the shell. Go ahead and click enter. You should see something like the following:

Fetching cluster endpoint and auth data. 
kubeconfig entry generated for mikes-k8s-cluster.

And there you have it! Our cluster is created. In our next blog post, we will explore the ins and outs of our cluster and the options we have. Thanks for reading!

Comments

Popular posts from this blog

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

Pre-reqs;
1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.



Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…