Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Demonstration how to use the newly introduced https redirect support in native GKE ingress resources.

License

Notifications You must be signed in to change notification settings

doitintl/gke-https-redirect

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 

Repository files navigation

gke-https-redirect

Demonstration how to use the newly introduced https redirect support in native GKE ingress resources (GCLB).

These files accompany my medium article At last: Redirect http to https in GKE ingress.

Requirements

GKE version

As mentioned in the article, your GKE cluster needs to be running at least a recent version 1.17-gke for this to work.

Named IP address

You will need a static reserved ip address going by the name of gke-https-redirect. Create it like this:

gcloud compute addresses create gke-https-redirect --global

DNS Names

You will want to override the domain names listed in managedcertificate.yaml. Also make sure they exist and point to the IP adress you created above.

Installation

kubectl apply -f k8s/

About

Demonstration how to use the newly introduced https redirect support in native GKE ingress resources.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published