Incompatibility between region name and kubernetes namespace rules

Bug #1842991 reported by Tim McNamara on 2019-09-06
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

The bootstrap process into a k8s cloud fails when that k8s cloud has been defined with a region name that includes capital letters. Kubernetes attempts to create a namespace that includes those capitals (via the controller name?) and then aborts with an error relating to DNS.

See original thread

Tags: k8s Edit Tag help
Ian Booth (wallyworld) wrote :

The default controller name is composed from <cloud>-<region>, if not specified.

For VM clouds it's just a label so it doesn't matter.
For k8s clouds, a namespace is created from the controller name to contain the controller artefacts. So the name matters.

A workaround is to explicitly name the controller when bootstrapping.

summary: - Incompatibility between region name roles and kubernetes name rules
+ Incompatibility between region name and kubernetes namespace rules
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers