v1.0.11
Changes by Kind
Feature
Following configuration will be applied to the all ports of service.
“service.beta.kubernetes.io/azure-load-balancer-health-probe-protocol” “service.beta.kubernetes.io/azure-load-balancer-health-probe-interval” “service.beta.kubernetes.io/azure-load-balancer-health-probe-num-of-probe” “service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path”
If health probe is needed, user should specify AppProtocol in port object of Service spec. And following protocols are supported: http, tcp, https
Additional annotations are added. where port is the port number of port object
service.beta.kubernetes.io/port_{port}health-probe_interval service.beta.kubernetes.io/port{port}health-probe_num-of-probe service.beta.kubernetes.io/port{port}_health-probe_request-path
Please refer to docs. (#1130, @MartinForReal)
Bug or Regression
- This code change fixes the bug that UDP services would trigger unnecessary LoadBalancer updates. The root cause is that a field not working for non-TCP protocols is considered. ref: #1090 (#1107, @lzhecheng)
Uncategorized
- Fix: remove outdated ipv4 route when the corresponding node is deleted (#1186, @k8s-infra-cherrypick-robot)
- If spec.LoadBalancerSourceRanges is specified and lb is in internal mode, LB is open for public access.(close by default for security reasons) (#1123, @k8s-infra-cherrypick-robot)
Dependencies
Added
Nothing has changed.
Changed
- github.com/Azure/azure-sdk-for-go: v61.4.0+incompatible → v61.6.0+incompatible
- k8s.io/api: v0.21.9 → v0.21.10
- k8s.io/apimachinery: v0.21.9 → v0.21.10
- k8s.io/apiserver: v0.21.9 → v0.21.10
- k8s.io/client-go: v0.21.9 → v0.21.10
- k8s.io/cloud-provider: v0.21.9 → v0.21.10
- k8s.io/component-base: v0.21.9 → v0.21.10
- k8s.io/controller-manager: v0.21.9 → v0.21.10
Removed
Nothing has changed.