IBM Cloud - Structured Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

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.

  • Guest
  • Sep 3 2019
  • Future Backlog
  • Guest commented
    6 Sep, 2019 01:23pm

    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

  • Guest commented
    4 Sep, 2019 05:48pm

    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.

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.