apiserver

Commit Graph

Author	SHA1	Message	Date
SataQiu	d9a11fffae	remove DeprecatedInsecureServingOptionsWithLoopback Kubernetes-commit: d545de2b96de094107c3b687d8d48663af8f9fae	2022-09-11 21:22:18 +08:00
Antonio Ojea	bd10b9f5fb	bind-address flag usage Kubernetes-commit: 2e4aed2d4a8dc32acbd12ee7464fa00e650e0204	2020-12-11 18:42:51 +01:00
Mateusz Gozdek	e843f3790e	kube-apiserver: use SO_REUSEPORT when creating listener on Unix systems So multiple instances of kube-apiserver can bind on the same address and port, to provide seamless upgrades. Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io> Kubernetes-commit: dfe1f968ac31ba9b81a353d4de86d28e73d22d4e	2020-03-06 09:59:20 +01:00
Andy Goldstein	637cea444b	Fix max port value to 65535 Signed-off-by: Andy Goldstein <goldsteina@vmware.com> Kubernetes-commit: 9bba2c93ec6042fc4140afecc672f025ba491928	2019-06-24 15:13:27 -04:00
Justin SB	3883f41494	Add code comments to guard inadvertent removal of insecure-bind-address Though the flags are deprecated, the deprecation process revealed that the flag is important for health checks in more secure environments. Add a link to #43784 to help developers understand why the flags have not yet been removed. Issue #43784 Issue #74172 Issue #59018 Kubernetes-commit: 7dbbab0476b35b74f600f62b6751212ed3afe574	2019-02-18 12:58:59 -05:00
qingsenLi	1e20513561	fix typo and instead of amd Kubernetes-commit: 3e83f0f08abab4c10dfab7053529709883c9b834	2018-10-30 01:27:50 +08:00
Jordan Liggitt	a3f2a871b3	Surface help for insecure ports to explain how to disable Kubernetes-commit: 819b502768034b8104904cd7031db8c4838f900a	2018-11-30 10:52:37 -05:00
tanshanshan	631dda550e	kube-scheduler: enable secure ports 10259 Kubernetes-commit: cb95edafe8bf4f294beb53d0a7bc04d62584577c	2018-09-05 16:42:16 +08:00
Dr. Stefan Schimanski	3698d7a898	apiserver: move controller-manager's insecure config into apiserver Kubernetes-commit: 1d9a896066b3e10e8c1a0d506e00bc354b7772f0	2018-08-16 20:47:15 +02:00

9 Commits