WLS on AKS: Support T3 tunneling

[galiacheng]

Hello @rjeberhard @mriccell @jacobt123 @edburns I am working on creating a custom T3 channel for the WLS cluster on AKS. I have 2 problems regarding to exposing the T3 channel for public traffic. It would be great to have your suggestions.

Firstly, I would like to list what current offer supports.
The offer only set up default channel for WLS cluster. Also expose public access point to the default channels.

Default channels

• Admin server
  • Default port: 7001
  • Level 4 traffic routing(TCP, T3): set up Azure load balance service routing to admin server default channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to admin server default channel, with path /console*
• Cluster
  • Default port: 8001
  • Level 4 traffic routing(TCP, T3): set up Azure load balance service routing to cluster default channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to cluster default channel, with path /

Networking is configurable, customer can set up Azure Load Balancer Service (for L4 traffic) or Azure Application Gateway Ingress (for L7 traffic), or both of them based on their requirements.

My 1st question is how customer use T3 channel? Could you share more customer usage?

Per my understanding, customer uses default/t3 for the following purposes. Please correct me if I am wrong :)
Customer may use the T3 channel for:

• WLST access
• External JMS, EJB connection

Customer may use the default channel for:

• Admin console access
• Cluster application access

My 2th question is if we set up T3 channel with HTTP enabled, do we expose both channels for public traffic (default + T3Channel)?

My proposal is that, if the customer do not set up T3 channel, then expose the default channel for public access. If T3 channel is enabled, then expose the T3 channel for public access.

Structure looks like

T3 Channel is not set up

• Admin server
  • Default port: 7001
  • Level 4 traffic routing(TCP, T3): set up Azure load balance service routing to admin server default channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to admin server default channel, with path /console*
• Cluster
  • Default port: 8001
  • Level 4 traffic routing(TCP, T3): set up Azure load balance service routing to cluster default channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to cluster default channel, with path /

T3 channel is setup

• Admin server
  • Default port: 7001
  • T3 port: 7005
  • Level 4 traffic routing(TCP, T3), allow customer to select the following options, they can choose both.
    • set up Azure load balance service routing to admin server with default channel.
    • set up Azure load balance service routing to admin server with t3 channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to admin server default channel (port 7001), with path /console*, will not create ingress for t3 channel.
• Cluster
  • Default port: 8001
  • T3 port: 8011
  • Level 4 traffic routing(TCP, T3): allow customer to select the following options, they can choose both.
    • set up Azure load balance service routing to admin server with default channel.
    • set up Azure load balance service routing to admin server with t3 channel.
  • Level 7 traffic routing(HTTP, HTTPS): set up Azure Application Ingress routing to cluster default channel (port 8001), with path /, will not create ingress service for t3 channel.

We might enhance the offer to allow customizing the ports in the future.