This contains the Nginx configuration for k8s.io and the associated subdomain redirectors.
NOTE: please see k8s.io/k8s.io/configmap-nginx.yaml for server
definitions
- https://go.k8s.io/api-review
- https://go.k8s.io/bot-commands
- https://go.k8s.io/calendar
- https://go.k8s.io/github-labels
- https://go.k8s.io/good-first-issue
- https://go.k8s.io/help-wanted
- https://go.k8s.io/needs-ok-to-test
- https://go.k8s.io/oncall
- https://go.k8s.io/oncall-hotlist
- https://go.k8s.io/owners
- https://go.k8s.io/owners/${GITHUB_USER}
- https://go.k8s.io/partner-request
- https://go.k8s.io/pr-dashboard
- https://go.k8s.io/redirects
- https://go.k8s.io/start
- https://go.k8s.io/stuck-prs
- https://go.k8s.io/test-health
- https://go.k8s.io/test-history
- https://go.k8s.io/triage
- https://go.k8s.io/logo
NOTE: please see configmap-nginx.yaml for rewrite rules.
-
Log into Google Cloud Shell. Our clusters do not allow access from the internet.
-
Get the credentials for the cluster, if you don't already have them. Run
gcloud container clusters get-credentials aaa --region us-central1 --project kubernetes-public
. When this is done, you should be able to list namespaces withkubectl --context gke_kubernetes-public_us-central1_aaa get ns
. -
Run
./deploy.sh
. This will effectively run./deploy.sh canary
to push and test configs in the canary namespace, followed by./deploy.sh prod
to do the same in prod if tests pass against canary.