googlecloudplatform / gke-networking-demos Goto Github PK

This project presents a number of best practices for establishing network links between Kubernetes Engine clusters, and exposing cluster services across Google Cloud projects. You will use a set of Deployment Manager templates to create networks, subnets, vpn connections, and Kubernetes Engine clusters.

License: Apache License 2.0

Makefile 2.05% Python 18.73% Shell 48.63% Dockerfile 0.68% HCL 29.91%

kubernetes kubernetes-engine networking google-cloud-platform vpn routing gke-helmsman gke

gke-networking-demos's Introduction

Kubernetes Engine Networking

Introduction

Google cloud networking with Kubernetes Engine clusters can be complex. Assigning optimal CIDR ranges for the relevant VPC subnets and the Kubernetes Engine clusters' reserved IP ranges from the start is very important since VPC subnets are not always easy to resize and the cluster's reserved IP ranges are immutable. Using the correct method to expose the applications in the cluster is important as every method was designed for a different set of use cases.

The demos in the project demonstrate the following best practices:

Connecting two GCP networks using VPC peering and Cloud VPN containing two Kubernetes Engine clusters each.
Deploying the nginx pods.
Exposing the pods using Kubernetes Engine services
Validating pod-to-service communication across the Kubernetes Engine clusters within the same region and the different regions.

Prerequisites

Tools

Install Cloud SDK

The Google Cloud SDK is used to interact with your GCP resources. Installation instructions for multiple platforms are available online.

Install kubectl CLI

The kubectl CLI is used to interteract with both Kubernetes Engine and kubernetes in general. Installation instructions for multiple platforms are available online.

Directory Structure

The gke-to-gke-peering and gke-to-gke-vpn folders each contain a project.
README files exist for the above examples; gke-to-gke-peering/README.md and gke-to-gke-vpn/README.md.
The network folder contains the manifest files and deployment manager templates to setup networks.
The clusters folder contains the manifest files and deployment manager templates to create Kubernetes Engine clusters.
The manifests folder contains the manifest files to create Kubernetes Engine services.

This is not an officially supported Google product

gke-networking-demos's People

Contributors

Stargazers

Watchers

gke-networking-demos's Issues

K8s can't access repo "pso-examples"

I've come across an error while trying to complete the lab "Kubernetes Engine Communication Through VPC Peering" from qwiklabs (https://www.qwiklabs.com/focuses/5540).

This is equivalent to another issue that I filed for "gke-security-scenarios-demo": GoogleCloudPlatform/gke-security-scenarios-demo#27

Error: "Cannot pull image 'gcr.io/pso-examples/nginx-curl:1.0.0' from the registry."

Dynamic Subdomains

Hi,
I am having an issue in Google DNS
I am trying to give subdomain as feature my client , So the subdomains has to be dynamic and I am supposed to listen all dynamic subdomains.
What should I do on GCP DNS to make it work?
Where I am only able add subdomain in manually

Error 400: Master version "1.14.7-gke.10" is unsupported

Initial install using qwiklabs fails with following error:

google_container_node_pool.cluster4_nodes: Refreshing state... [id=us-central1-c/cluster-deployment-cluster4/cluster4-nodes]
google_container_node_pool.cluster1_nodes: Refreshing state... [id=us-east1-d/cluster-deployment-cluster1/cluster1-nodes]
google_container_node_pool.cluster2_nodes: Refreshing state... [id=us-central1-b/cluster-deployment-cluster2/cluster2-nodes]
google_container_cluster.cluster-deployment-cluster3: Creating...
   
Error: googleapi: Error 400: Master version "1.14.7-gke.10" is unsupported., badRequest

  on main.tf line 106, in resource "google_container_cluster" "cluster-deployment-cluster3":
 106: resource "google_container_cluster" "cluster-deployment-cluster3" {

version: a2f1413

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

cloudbuild

container/cloudbuild.yaml

dockerfile

container/Dockerfile

terraform

gke-to-gke-vpn/terraform/provider.tf

google 2.11.0

gke-to-gke-vpn/terraform/versions.tf

hashicorp/terraform >= 0.12

Check this box to trigger a request for Renovate to run again on this repository

Verify-functions backend checks

The way the backends_exists function is called in verify-functions.sh, it will pick up other backends that have the name k8s-ig-- and wait until they are gone until all 50 iterations have completed. If other backends are in place with those names, they can hold up the cleanup.sh process and cause a build teardown failure.