Last updated：2021-05-11 10:41:40
KCE supports the following workload access methods: Public Access(LoadBalancer), Via VPC(LoadBalancer), Intra-Cluster(ClusterIP), and NodePort(NodePort). KCE also allows you to leave the access method unspecified by clearing Enabled for Associated Service. You can select an appropriate access method based on your business requirements.
This option allows Services to be exposed to the Internet through SLB so that they can be accessed over the Internet.
You can access the Services through the IP address of a public SLB instance and a Service port.
The system automatically creates a public SLB instance and an EIP to expose the Services to the Internet and enables dynamic listening and mounting of listeners.
The public access bandwidth for an EIP is 1 Mbit/s by default, which can be adjusted based on your business requirements.
This option allows Services to be exposed to the VPC where the Kubernetes cluster resides through SLB so that they can be accessed by other resources or Kubernetes clusters in the VPC.
You can access the Services through the IP address of a private SLB instance and a Service port.
If Enabled is cleared for Associated Service, no entry to the container is provided for frontend Service access requests. This way, you can implement custom Service discovery or simply start multiple pods.
Do not change the name of the SLB instance that is automatically created by the cluster. Otherwise, the cluster may not recognize an existing SLB instance and create a new one.
Do not change the project of the EIP and SLB instance that are automatically created by the cluster.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.