Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-3345

Remove use of implicit public IP address for Azure pod VM

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: High High
    • None
    • None
    • None
    • 3
    • 0
    • 0
    • Customer Facing

      For Azure pod VM, the default egress is provided implicitly by DefaultOutboundAccess which is going to be retired - https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access#how-is-default-outbound-access-provided

      We also realised that the DefaultOutboundAccess option is implicit and not explicit. So if a cluster admin wants to use a private subnet then this implicit behaviour defeats the purpose.

      This story is to track the work to move away from DefaultOutboundAccess and instead use explicit subnet setting for egress.

       

      Magnus from Azure is working on a patch which I had tested. Once the changes are upstreamed and merged in cloud-api-adaptor, we should be able to use downstream.

       

      This story will require doc changes.

       

       

              Unassigned Unassigned
              bpradipt Pradipta Banerjee
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: