Skip to main content

Kubernetes on Google Cloud Platform - Part 2 Into the cluster in GCP! Create our first pod

Now that our cluster is up and running (please see part 1 to see up your K8s cluster), let's take a look inside!

Once we click on the cluster, we see some well-written information right away about our cluster, the size, nodes, networking, and version. 


Scrolling down we can see information about our node pools. Size, version, name, and redundancy information.

Moving over to workloads, lets go ahead and spin up a containerized application.


Here we have a very simple Nginx application that will spin up as "mikes-nginx" and pull the latest version of Nginx from the Docker repo.


We can even take a look at the YAML by clicking "view YAML" to see the code for ourselves.


Now let's go ahead and click the blue "deploy" button. You should see something similar to what I see below.


As you can see above, we can see a ton of great information about our pod. The application its running, logs, labels, active pods, and managing our pods.

Let's scroll back up in the same "Workloads" page and click that Expose button. Exposing an application turns it into a Kubernetes Service and allows the application to be hit publicly. We'll go ahead and leave it on port 80 as an unsecured connection for the purposes of this post.


Now that our service is up, let's go ahead and take a look at it. We see some great info here, but we want to focus on that "External endpoints" IP and port. That's what we're going to use to hit our application. (we also see monitoring and graphs. I will be going into monitoring in part 3 of this blog series).

Let's go ahead and click on that external endpoint.


There you have it! Our application is up, public facing, our pods are active, and we have successfully spun up our pod in Kubernetes on GCP!

On our 3rd and final part of the GCP Kubernetes series, we will go into monitoring our cluster, pods, and applications within GCP.

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…