Activate Cloud Shell
Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.
Click Activate Cloud Shell
at the top of the Google Cloud console.
When you are connected, you are already authenticated, and the project is set to your PROJECT_ID. The output contains a line that declares the PROJECT_ID for this session:
Your Cloud Platform project in this session is set to YOUR_PROJECT_ID
gcloud is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.
- (Optional) You can list the active account name with this command:
gcloud auth list
Click Authorize.
Your output should now look like this:
Output:
ACTIVE: *
ACCOUNT: student-01-xxxxxxxxxxxx@qwiklabs.net
To set the active account, run:
$ gcloud config set account `ACCOUNT`
- (Optional) You can list the project ID with this command:
gcloud config list project
Output:
[core]
project = <project_ID>
Example output:
[core]
project = qwiklabs-gcp-44776a13dea667a6
Note: For full documentation of gcloud, in Google Cloud, refer to the gcloud CLI overview guide.
Overview
In this lab, you'll learn how to deploy a static website using Traefik as a reverse proxy and Cloud Run for serving the content. You will containerize a simple static site, push the image to Artifact Registry, configure Traefik to route traffic, and deploy it all to Cloud Run.
Task 1. Set Up Your Environment
Configure your Google Cloud environment for this lab.
- Enable the necessary APIs: Cloud Run, Artifact Registry, and Cloud Build.
gcloud services enable run.googleapis.com artifactregistry.googleapis.com cloudbuild.googleapis.com
Note:
This command enables the required Google Cloud services.
- Set your Project ID.
gcloud config set project qwiklabs-gcp-04-e2c6201b1f19
Note:
Replace PROJECT_ID with your actual project ID.
- Set your default run region.
gcloud config set run/region us-central1
Note:
Replace REGION with your desired region (e.g., us-central1).
Task 2. Create an Artifact Registry Repository
Create a Docker repository in Artifact Registry to store your container images.
- Create a Docker repository named 'traefik-site'.
gcloud artifacts repositories create traefik-repo --repository-format=docker --location=us-central1 --description="Docker repository for static site images"
Note:
This command creates a Docker repository in Artifact Registry.
Task 3. Build and Push the Static Site Image
Create a simple static site, containerize it using Docker, and push the image to Artifact Registry.
- Create a directory for your static site.
mkdir traefik-site && cd traefik-site && mkdir public
- Create an
public/index.html file with some simple content.
cat > public/index.html <<EOF
<html>
<head>
<title>My Static Website</title>
</head>
<body>
<p>Hello from my static website on Cloud Run!</p>
</body>
</html>
EOF
Note:
This is the HTML content for the static site.
- Authenticate Docker to Artifact Registry.
gcloud auth configure-docker us-central1-docker.pkg.dev
Note:
This command configures Docker to use your Google Cloud credentials.
- Create a
traefik.yml with the following content:
entryPoints:
web:
address: ":8080"
providers:
file:
filename: /etc/traefik/dynamic.yml
watch: true
log:
level: INFO
Note:
This command creates the Traefik configuration file.
- Create a
dynamic.yml with the following content:
http:
routers:
static-files:
rule: "PathPrefix(`/`)"
entryPoints:
- web
service: static-service
services:
static-service:
loadBalancer:
servers:
- url: "http://localhost:8000"
Note:
This command creates the dynamic content configuration file.
Task 4. Create the Dockerfile
Define the Docker image for Traefik and your static website.
- Create a
Dockerfile with the following content:
FROM alpine:3.20
RUN apk add --no-cache traefik caddy
COPY traefik.yml /etc/traefik/traefik.yml
COPY dynamic.yml /etc/traefik/dynamic.yml
COPY public/ /public/
EXPOSE 8080
ENTRYPOINT [ "caddy" ]
CMD [ "file-server", "--listen", ":8000", "--root", "/public", "&", "traefik" ]
Note:
This Dockerfile uses the official Alpine image, sets the working directory, and copies your website and Caddyfile. Traefik will be used to handle routing and Caddy used to serve web content.
Task 5. Build and push the Docker image
Build the Docker image and push it to Artifact Registry.
- Build the Docker image. Replace
us-central1 and qwiklabs-gcp-04-e2c6201b1f19 with your region and project ID.
docker build -t us-central1-docker.pkg.dev/qwiklabs-gcp-04-e2c6201b1f19/traefik-repo/traefik-static-site:latest .
Note:
This command builds the Docker image and tags it with the Artifact Registry repository URL.
- Push the Docker image to Artifact Registry.
docker push us-central1-docker.pkg.dev/qwiklabs-gcp-04-e2c6201b1f19/traefik-repo/traefik-static-site:latest
Note:
This command pushes the Docker image to Artifact Registry.
Task 6. Deploy to Cloud Run
Deploy the container image to Cloud Run.
- Deploy the service to Cloud Run. Replace
us-central1 and qwiklabs-gcp-04-e2c6201b1f19 with your region and project ID.
gcloud run deploy traefik-static-site --image us-central1-docker.pkg.dev/qwiklabs-gcp-04-e2c6201b1f19/traefik-repo/traefik-static-site:latest --platform managed --allow-unauthenticated --port 8000
Note:
This command deploys the Docker image to Cloud Run and allows unauthenticated access.
- When prompted, confirm the service name as
traefik-static-site and allow unauthenticated invocations.
Note:
This configures the service name and permissions.
- Note the service URL provided by Cloud Run.
Note:
This is the URL where your static website is accessible.
Task 7. Access your website
Access the deployed website through the Cloud Run service URL.
- Open the Cloud Run service URL in your web browser.
Note:
Verify that your static website is displayed correctly.
Solution of Lab
curl -LO raw.githubusercontent.com/Techcps/Google-Cloud-Skills-Boost/master/Deploy%20a%20Static%20Site%20Using%20Traefik%20and%20Cloud%20Run/techcps.sh
sudo chmod +x techcps.sh
./techcps.sh
