Cloud-native applications are built to allow for continuous updating of code without affecting the user experience. A legacy application, on the other hand, requires a complete reload of the application because its parts are all intertwined, and the application has to be taken offline to be updated. Today, this type of interruption is unacceptable.
Cloud-native applications are written such that each part of the application is created in smaller chunks or containers. Because individual software engineering teams can maintain these containers, updating one container has less impact on the ability of a team to keep an application available. Software engineers can publish updated containers without taking the original container offline or affecting the application as a whole.
Containers add complexity in providing access to the teams who are developing applications and managing application delivery. Kubernetes uses Ingress to control access to the services in a cluster, and the Ingress can provide load balancing, SSL termination, and name-based virtual hosting.
NetScaler is an application delivery and security platform that provides traffic control functions such as load balancing and includes features that add security, monitoring, and controls to inbound requests. Updating your NetScaler application delivery controller (ADC) manually when new changes are made to the Kubernetes cluster would make it difficult to meet the automation and fast deployment needs of modern applications.
That’s where NetScaler Ingress Controller and IP Address Management (IPAM) containers from NetScaler can help. NetScaler Ingress Controller watches for changes on the Kubernetes cluster and automatically configures the NetScaler ADC to provide access to the applications deployed as microservices. IPAM delivers the IP address needed, and NetScaler Ingress Controller updates the NetScaler entities (services), ensuring users can access the application without interruption.
In summary, NetScaler gives you a quick, easy, and automated way to gain access to your microservices-based applications.
If you’re looking for an ingress proxy like NetScaler for your microservices-based application delivery, contact the product team at netscaler-appmodernization@cloud.com for a free consultation.
Resources for learning more about NetScaler Ingress Controller and IPAM containers:
- Product documentation
- Automate the NetScaler Ingress Controller
- Configuring multi-cluster Kubernetes ingress with GSLB
- NetScaler Ingress Controller for OpenShift
- Using NetScaler for the OpenShift Control Plane
- NetScaler Ingress Controller on AWS Marketplace
- NetScaler Ingress Controller on Azure Marketplace
- NetScaler Ingress Controller on Google Cloud Platform
- Getting started with NetScaler cloud-native deployment