* Add support to ipFamilyPolicy and ipFamilies fields in Helm chart
As stated in the prerequisites' session of https://kubernetes.io/docs/concepts/services-networking/dual-stack/, in order to use Kubernetes IPv4/IPv6 dual stack, v1.20 is needed. This commit aims in supporting these dual-stack-ness in ingress-nginx's chart.
Signed-off-by: jaehnri <joao.henri.cr@gmail.com>
* Standardize documentation with two '#'s
Signed-off-by: jaehnri <joao.henri.cr@gmail.com>
* Bump Helm chart version to 4.1.0
Signed-off-by: jaehnri <joao.henri.cr@gmail.com>
* Update Helm Chart changelog with 4.1.0 description
Signed-off-by: jaehnri <joao.henri.cr@gmail.com>
* Revert Helm Chart bump and remove CHANGELOG
As there will be more things in the release, in the review of this PR, it was asked to revert the bumps:
https://github.com/kubernetes/ingress-nginx/pull/7651#pullrequestreview-757311449
Signed-off-by: jaehnri <joao.henri.cr@gmail.com>
Minor update to the helm chart to set the [appProtocol][1] field on all
http / https ports defined in the various services created by the helm
chart:
- http and https for controller-service
- http and https for controller-service-internal
- https for controler-service-webhook
- http for default-backend-service
These are only added in kubernetes >= 1.20, which is when this feature
became stable.
[1]: https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol
