Technology Encyclopedia Home >Why does TKE Serverless not create a CLB instance for Ingress or Service?

Why does TKE Serverless not create a CLB instance for Ingress or Service?

TKE Serverless does not create a CLB instance for Ingress or Service primarily due to its design philosophy and operational model. TKE Serverless, as part of Tencent Cloud's Kubernetes Engine, focuses on providing a serverless environment where users can deploy and run containerized applications without the need to manage underlying infrastructure.

In traditional Kubernetes setups, Ingress and Service resources are often used to expose services externally and manage traffic routing. However, in a serverless architecture, the underlying infrastructure is managed by the cloud provider, and the need for manual configuration of load balancers is reduced or eliminated.

For example, when you deploy an application in TKE Serverless, the platform automatically handles the scaling and load balancing of your application. You don't need to create a CLB instance manually because TKE Serverless uses its own internal mechanisms to distribute traffic among the available instances.

Moreover, TKE Serverless integrates with other Tencent Cloud services, such as Tencent Cloud Load Balancer (CLB), to provide seamless traffic management. However, the creation and management of CLB instances are abstracted away from the user to simplify the deployment and operation process.

If you need more advanced traffic management features or want to customize the load balancing behavior, you can still use the CLB service provided by Tencent Cloud in conjunction with TKE Serverless. This allows you to leverage the benefits of both serverless computing and advanced load balancing capabilities.

In summary, TKE Serverless streamlines the deployment and operation of containerized applications by abstracting away the need for manual CLB instance creation, enabling users to focus on their application code rather than infrastructure management.