# Create and Manage Cloud Resources

## Task 1: Create a project jumphost instance

You will use this instance to perform maintenance for the project.

#### **Requirements:**

* Name the instance **nucleus-jumphost**.
* Use an *f1-micro* machine type.
* Use the default image type (Debian Linux).

```
gcloud compute instances create nucleus-jumphost \
    --machine-type f1-micro \
    --zone us-east1-b
```

## Task 2: Create a Kubernetes service cluster

The team is building an application that will use a service running on Kubernetes.

#### You need to:

* Create a cluster (in the us-east1-b zone) to host the service.

```
gcloud container clusters create service-cluster \
    --zone us-east1-b
```

```
gcloud container clusters get-credentials service-cluster \
    --zone us-east1-b
```

* Use the Docker container hello-app (`gcr.io/google-samples/hello-app:2.0`) as a placeholder; the team will replace the container with their own work later.

```
kubectl create deployment hello-server --image=gcr.io/google-samples/hello-app:2.0
```

* Expose the app on port 8080.

```
kubectl expose deployment hello-server --type=LoadBalancer --port 8080
```

## Task 3: Set up an HTTP load balancer

You will serve the site via nginx web servers, but you want to ensure that the environment is fault-tolerant. Create an HTTP load balancer with a managed instance group of **2 nginx web servers**. Use the following code to configure the web servers; the team will replace this with their own configuration later.

```
cat << EOF > startup.sh
#! /bin/bash
apt-get update
apt-get install -y nginx
service nginx start
sed -i -- 's/nginx/Google Cloud Platform - '"\$HOSTNAME"'/' /var/www/html/index.nginx-debian.html
EOF
```

#### You need to:

* Create an instance template.

```
gcloud compute instance-templates create nginx-template \
--metadata-from-file startup-script=startup.sh
```

* Create a target pool.

```
gcloud compute target-pools create nginx-pool
```

* Create a managed instance group.

```
gcloud compute instance-groups managed create nginx-group \
--base-instance-name nginx \
--size 2 \
--template nginx-template \
--target-pool nginx-pool 
```

`gcloud compute instances list`

* Create a firewall rule to allow traffic (80/tcp).

```
gcloud compute firewall-rules create www-firewall \
--allow tcp:80 
```

```
gcloud compute forwarding-rules create nginx-lb \
--region us-east1 \
--ports=80 \
--target-pool nginx-pool
```

`gcloud compute forwarding-rules list`

* Create a health check.

```
gcloud compute http-health-checks create http-basic-check
```

```
gcloud compute instance-groups managed \
set-named-ports nginx-group \
--named-ports http:80
```

* Create a backend service, and attach the managed instance group.

```
gcloud compute backend-services create nginx-backend \
--protocol HTTP --http-health-checks http-basic-check --global
```

```
gcloud compute backend-services add-backend nginx-backend \
--instance-group nginx-group \
--instance-group-zone us-east1-b \
--global
```

* Create a URL map, and target the HTTP proxy to route requests to your URL map.

```
gcloud compute url-maps create web-map \
--default-service nginx-backend 
```

```
gcloud compute target-http-proxies create http-lb-proxy \
--url-map web-map
```

* Create a forwarding rule.

```
gcloud compute forwarding-rules create http-content-rule\
--global \
--target-http-proxy http-lb-proxy \
--ports 80 
```

`gcloud compute forwarding-rules list`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dailyjournal.gitbook.io/cloud-computing/qwiklabs-challenge-labs/create-and-manage-cloud-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.