Google Kubernetes Engine (GKE) Quick Start on CLI

Google Cloud provides a nice quickstart guide for GKE:

https://cloud.google.com/kubernetes-engine/docs/quickstart


This post follows the steps on CLI.

You need to install gcloud & kubectl as a pre-requisite.


# enable GKE
% gcloud services enable container.googleapis.com
% gcloud services list | grep -i 'kube'
container.googleapis.com          Kubernetes Engine API
# config gcloud
% gcloud config set project YOUR_PROJECT_ID
% gcloud config set compute/zone us-west1-a
% gcloud config set compute/region us-west1
# create cluster (few minutes)
% gcloud container clusters create hello-cluster --num-nodes=1
% gcloud container clusters list
NAME           LOCATION    MASTER_VERSION   MASTER_IP     MACHINE_TYPE  NODE_VERSION     NUM_NODES  STATUS
hello-cluster  us-west1-a  1.18.17-gke.100  35.230.17.63  e2-medium     1.18.17-gke.100  1          RUNNING
# get credentials
% gcloud container clusters get-credentials hello-cluster
# deploy
% kubectl create deployment hello-server --image=gcr.io/google-samples/hello-app:1.0
% kubectl get deploy
NAME           READY   UP-TO-DATE   AVAILABLE   AGE
hello-server   1/1     1            1           7s
# create LB (few minutes)
% kubectl expose deployment hello-server --type LoadBalancer --port 80 --target-port 8080
% kubectl get service hello-server
NAME           TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)        AGE
hello-server   LoadBalancer   10.115.254.75   34.105.110.107   80:30448/TCP   56s
# access
% curl http://34.105.110.107/
Hello, world!
Version: 1.0.0
Hostname: hello-server-57684579f-pdbk9
# delete LB (needed to avoid incurring charges)
% kubectl delete service hello-server
service "hello-server" deleted
# delete cluster (few minutes)
% gcloud container clusters delete hello-cluster


Comments

Post a Comment

Popular posts from this blog

Selenide: Quick Start

Selenide is a Selenium wrapper in Java for testing.   This post describes how you can start using Selenide (using Gradle). 1. Setup Java Application # keep pressing enters to choose default values gradle init --type java-application # confirm that test succeeds gradle test 2. Add Selenide Dependency open build.gradle and edit as: dependencies {   ...   testImplementation 'com.codeborne:selenide:5.13.0' } 3. Write Test (replace the existing test with selenide code) src/test/java/selenide/AppTest.java package selenide; import static com.codeborne.selenide.Condition.text; import static com.codeborne.selenide.Selenide.$; import static com.codeborne.selenide.Selenide.open; import org.junit.Test;   public class AppTest { @Test public void test() { open("https://www.google.ca/"); $("input[type=text]").val("test").pressEnter(); $("body").shouldHave(text("test")); } } 4. Run Selenide gradle test This will open a browser t...
Read more

Minikube Installation for M1 Mac

Image
In this post, I am going to try Minikube on Mac with M1 Chip. what is minikube Minikube is k8s tool running on a local machine. See also kind  for multi cluster implementation for local k8s. install % curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-darwin-arm64 % install minikube-darwin-arm64 /usr/local/bin/minikube % minikube version  minikube version: v1.20.0  Note: Installing with brew fails due to a different binary as of 2021-05-24. % brew install minikube % minikube version ❌  Exiting due to MK_WRONG_BINARY_M1: You are trying to run amd64 binary on M1 system. Please use darwin/arm64 binary instead (Download at https://github.com/kubernetes/minikube/releases/download/v1.20.0/minikube-darwin-amd64.) % brew uninstall minikube start The default driver 'virtualbox' is not supported on M1, but you can use 'docker' driver:  https://minikube.sigs.k8s.io/docs/drivers/docker/  . Make sure docker is running, and then specify the driver ...
Read more

Server Testing Tools: Serverspec, InSpec, Testinfra, Goss

In this post, I am going to describe differences among server-testing frameworks that I have briefly tried so far: Comparison Serverspec InSpec Testinfra Goss my blog post link link link link language Ruby / RSpec Ruby / RSpec Python / pytest Go / yaml package gem gem pip none remote exec yes yes yes no license MIT Chef Apache 2.0 Apache 2.0 github repo link link link link - created_at 2013 2015 2015 2015 - stars 2.4k 2.3k 1.9k 4.3k Thought Personally, I liked Goss the most as you can write it in yaml. The biggest drawback is that you have to run it on the server itself, and this makes it harder to introduce the tool on the existing production environment. Next, InSpec was easy to start with. I was going to use it at work until I noticed the license issue. Thus, I have basically two options. Serverspec seems great, but since my team members tends to prefer Python to other languages, we might start using Testinfra first.
Read more