2
VOTE
Status
Future consideration
Workspace
* IBM Cloud Ideas
Categories
Containers
Created by
Guest
Created on
Sep 3, 2019
RELATED IDEAS
URL management for Multi-AZ K8s cluster
Currently, the URL to access a multi-AZ k8s cluster is dynamically created with little possibility for the customer to influence it. https://cloud.ibm.com/docs/containers?topic=containers-ingress-about&locale=en%5C043science#mzlb
In organizations where changing a CNAME is a manual process, this can get tricky especially in disaster recovery scenarios where an automated recreation of the cluster is needed.
Therefore it would be really good to be able to have an influence on the subdomain at cluster creation time to set it to a static value.
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi Dan,
your suggestions sounds very good for me. This would indeed also help us for our migration from singlezone to multizone, I guess. And it would also allow an "easy" switch from one cluster to another one.
Regards, Ruben
Having a generated domain name that is consistent and predictable was chosen over the convoluted approach that IKS had to ensure uniqueness of domain names which is still required.
I would prefer that we keep the domain generation name the same but move to decouple DNS registration from clusters. This way a single DNS domain can be associated with load balancers that span clusters. This would help in migration scenarios and would allow a customer to "move" the generated subdomain to another cluster avoiding the need to change the CNAME records. I believe the approach that I have laid out is more flexible and solves more problems than simply controlling the subdomain name.