Notable New Features And Changes
1. Ingress 1.19
- Presented as an API in beta right back in Kubernetes form 1.1, Ingress handles outer admittance to administrations in a cluster, uncovering HTTP and HTTPS courses. It might likewise oversee load adjusting, end SSL/TLS, and give name-based virtual facilitating. All together for the Ingress asset to work, an Ingress regulator must be utilized; the Kubernetes venture as of now underpins and keeps up GCE and nginx regulators.
- In 1.19, Ingress graduates to general accessibility and is added to the systems administration v1 APIs. As a component of this achievement, there are some key contrasts in v1 Ingress objects, including mapping and approval changes. For instance, the ‘pathType’ field no longer has a default esteem and should be indicated.
2. TLS 1.3 Support
Kubernetes 1.19 tends to one of the suggestions that emerged from the Kubernetes security review directed a year ago and includes uphold for new TLS 1.3 codes that can be utilized for Kubernetes.
3. Node Debugging
Accessible in alpha, running the ‘kubectl alpha investigate’ order will make and run another case that runs in the host OS namespaces and can be utilized to investigate hubs. This permits a client to review a running case without restarting it and without entering the compartment itself to, for instance, check the filesystem, execute extra troubleshooting utilities, or starting system demands from the unit arrange namespace. Part of the inspiration for this improvement is to likewise take out most employments of SSH for hub troubleshooting and support.
#devops #kubernetes #release #kubernetes 1.19
