Release 2.0.5
Changes in this release:
- Added a new options for the
appIngressMethod
parameter callednodeport-internal
. This uses NodePort services for ingress from the workload drivers to the applications, but uses the Internal IP addresses of the nodes. This differs from thenodeport
option which uses the External IP addresses of the nodes. Note that in your drivers and applications are running in different clusters, then this option will only work if the nodes' internal addresses are routable from the driver cluster. - Increased the timeouts on the readiness probes for most services to avoid occasional non-ready status when the nodes are actually OK.
- Changed the Service type for RabbitMQ from NodePort to ClusterIP. The use of NodePort was a bug that might cause an error on some clusters.
- Remove port 80 from the Nginx Service. This port was not used, and it inclusion could use up load-balancer resources in some clusters.