Why managed Kubernetes matters in GCP - See It in Action

Why Managed Kubernetes Matters

📖 Scenario: You are working in a small company that wants to deploy applications on the cloud. You have heard about Kubernetes but find it complex to manage. Your team is considering using a managed Kubernetes service on Google Cloud Platform (GCP) to simplify deployment and maintenance.

🎯 Goal: Learn why using a managed Kubernetes service like Google Kubernetes Engine (GKE) is helpful. You will create a simple data structure to represent Kubernetes clusters, add configuration for managed services, filter clusters that are managed, and display the benefits.

📋 What You'll Learn

Create a dictionary with Kubernetes clusters and their types

Add a variable to identify managed clusters

Use a loop to find all managed clusters

Print the list of managed clusters

💡 Why This Matters

🌍 Real World

Companies use managed Kubernetes services like GKE to avoid the complexity of setting up and maintaining Kubernetes themselves. This saves time and reduces errors.

💼 Career

Understanding why managed Kubernetes matters helps you communicate with cloud teams and supports decisions about infrastructure management in DevOps roles.

1

Create Kubernetes clusters dictionary

Create a dictionary called clusters with these exact entries: 'cluster1': 'self-managed', 'cluster2': 'managed', 'cluster3': 'self-managed', 'cluster4': 'managed'.

GCP

# Create the clusters dictionary with exact entries
# Your code here

Hint

Use curly braces to create a dictionary with keys as cluster names and values as their types.

2

Add managed cluster type variable

Create a variable called managed_type and set it to the string 'managed'.

GCP

clusters = {
    'cluster1': 'self-managed',
    'cluster2': 'managed',
    'cluster3': 'self-managed',
    'cluster4': 'managed'
}
# Create the managed_type variable
# Your code here

Hint

Assign the string 'managed' to the variable managed_type.

3

Find all managed clusters

Create a list called managed_clusters that contains the names of clusters from clusters where the cluster type equals managed_type. Use a for loop with variables cluster and ctype to iterate over clusters.items().

GCP

clusters = {
    'cluster1': 'self-managed',
    'cluster2': 'managed',
    'cluster3': 'self-managed',
    'cluster4': 'managed'
}
managed_type = 'managed'
# Create managed_clusters list using a for loop
# Your code here

Hint

Use a loop to check each cluster's type and add the cluster name to the list if it is managed.

4

Display managed clusters

Write a print statement to display the text 'Managed Kubernetes clusters:' followed by the managed_clusters list.

GCP

clusters = {
    'cluster1': 'self-managed',
    'cluster2': 'managed',
    'cluster3': 'self-managed',
    'cluster4': 'managed'
}
managed_type = 'managed'
managed_clusters = []
for cluster, ctype in clusters.items():
    if ctype == managed_type:
        managed_clusters.append(cluster)
# Print the managed clusters
# Your code here

Hint

Use print('Managed Kubernetes clusters:', managed_clusters) to show the result.

Practice

1. What is the main benefit of using managed Kubernetes services like Google Kubernetes Engine (GKE)?

easy

A. It only works with Google Cloud Storage.

B. It requires you to manually update and secure the cluster nodes.

C. It handles infrastructure management so you can focus on your applications.

D. It eliminates the need to write application code.

Solution

1. Step 1: Understand managed Kubernetes purpose

   Managed Kubernetes services automate infrastructure tasks like updates and scaling.

2. Step 2: Focus on application development

   This automation lets developers focus on building and deploying apps instead of managing servers.

3. Final Answer:

   It handles infrastructure management so you can focus on your applications. -> Option C

4. Quick Check:

   Managed Kubernetes = Focus on apps [OK]

Hint: Managed Kubernetes means less server work, more app focus [OK]

Common Mistakes:

• Thinking you must manage updates manually
• Believing it only works with specific storage
• Assuming it removes the need to code

2. Which command correctly creates a new Kubernetes cluster using Google Kubernetes Engine (GKE)?

easy

A. gcloud container clusters create my-cluster --zone us-central1-a

B. kubectl create cluster my-cluster --region us-central1

C. gcloud compute clusters new my-cluster --zone us-central1-a

D. kubectl cluster create my-cluster --zone us-central1-a

Solution

1. Step 1: Identify correct GKE cluster creation command

   The correct command uses 'gcloud container clusters create' with cluster name and zone.

2. Step 2: Check syntax and tool usage

   'kubectl' manages resources inside clusters, not cluster creation; 'gcloud compute' is for VM instances.

3. Final Answer:

   gcloud container clusters create my-cluster --zone us-central1-a -> Option A

4. Quick Check:

   Cluster creation uses gcloud container clusters create [OK]

Hint: Use 'gcloud container clusters create' to make GKE clusters [OK]

Common Mistakes:

• Using kubectl to create clusters
• Confusing compute commands with container commands
• Missing required flags like --zone

3. What will be the output of the following command when run on a managed Kubernetes cluster?

kubectl get nodes

medium

A. Lists all nodes in the cluster with their status and roles.

B. Creates a new node in the cluster.

C. Deletes all nodes in the cluster.

D. Shows the logs of the nodes.

Solution

1. Step 1: Understand 'kubectl get nodes' command

   This command lists all nodes in the Kubernetes cluster, showing their status and roles.

2. Step 2: Differentiate from other commands

   It does not create, delete, or show logs; those require different commands.

3. Final Answer:

   Lists all nodes in the cluster with their status and roles. -> Option A

4. Quick Check:

   'kubectl get nodes' = list nodes [OK]

Hint: 'kubectl get nodes' shows cluster nodes status [OK]

Common Mistakes:

• Thinking it creates or deletes nodes
• Confusing it with log commands
• Expecting detailed pod info instead

4. You tried to create a GKE cluster with this command:

gcloud container clusters create my-cluster --zone us-central1-a --num-nodes -3

What is the problem and how to fix it?

medium

A. The zone flag is incorrect; use --region instead.

B. The number of nodes cannot be negative; use a positive integer instead.

C. The cluster name is invalid; it must start with a capital letter.

D. The command is missing the --machine-type flag.

Solution

1. Step 1: Identify invalid flag value

   The --num-nodes flag cannot be negative; '-3' is invalid.

2. Step 2: Correct the flag value

   Replace '-3' with a positive integer like '3' to specify node count.

3. Final Answer:

   The number of nodes cannot be negative; use a positive integer instead. -> Option B

4. Quick Check:

   Node count must be positive [OK]

Hint: Node count must be positive number, not negative [OK]

Common Mistakes:

• Using negative numbers for node count
• Confusing zone and region flags
• Thinking cluster names must be capitalized

5. You want to ensure your managed Kubernetes cluster automatically updates and scales without downtime. Which feature of managed Kubernetes helps achieve this?

hard

A. Disabling auto-updates to control changes.

B. Manual patching and fixed node counts.

C. Using only pre-built container images.

D. Automatic node upgrades and cluster autoscaling.

Solution

1. Step 1: Identify features for zero downtime

   Managed Kubernetes offers automatic node upgrades and autoscaling to keep clusters updated and responsive.

2. Step 2: Understand why other options fail

   Manual patching risks downtime; disabling updates stops improvements; pre-built images don't handle scaling or upgrades.

3. Final Answer:

   Automatic node upgrades and cluster autoscaling. -> Option D

4. Quick Check:

   Auto upgrades + autoscaling = smooth updates and scaling [OK]

Hint: Auto upgrades and autoscaling keep clusters healthy [OK]

Common Mistakes:

• Thinking manual patching avoids downtime
• Disabling auto-updates for control
• Believing container images handle scaling