If using `localhost` instead of <API_SERVER_IP_ADRESS>, you get a certificate error:
```
kubectl get pods
I0520 16:29:08.178277 41261 versioner.go:58] Get https://localhost:6443/version?timeout=5s: dial tcp 127.0.0.1:6443: connect: connection refused
Unable to connect to the server: x509: certificate is valid for ccqserv225, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, not localhost
```
Please also note that I have a warning message if I unset the `https_proxy` env variable:
```
⚙ kubectl get pods
I0520 16:35:27.955076 43865 versioner.go:56] Remote kubernetes server unreachable
NAME READY STATUS RESTARTS AGE
hub-54c6457f66-vlq2l 1/1 Running 0 4h27m
proxy-7b5b8dfb9d-dxrkz 1/1 Running 0 4h27m
# Whereas with the https_proxy variable:
⚙ export https_proxy=socks5://localhost:1080
⚙ kubectl get pods
NAME READY STATUS RESTARTS AGE
hub-54c6457f66-vlq2l 1/1 Running 0 4h28m
proxy-7b5b8dfb9d-dxrkz 1/1 Running 0 4h28m
```
Any idea is welcome here.
* The link in access-cluster.md is stale
* service name segment of apiserver proxy must have trailing colon when
schema is specified
* Replace apiserver address with a reserved documentation IP address
Signed-off-by: Quan Tian <qtian@vmware.com>
I fixed an imagepulling error in the service.md example on the website. nginx:11.14.2 is no longer on Nginx docker hub: https://hub.docker.com/_/nginx?tab=tags&page=1&name=11.14.2 so I changed the image tag to the latest. please let me know if the latest tag is not the right image to use or if I'm wrong.
This PR fixes several things in the admission-controllers page:
- The `PodSecurity` plugin is enabled by default, but it was not listed so;
- The `apiserver.config.k8s.io/v1alpha1` has been deprecated since v1.17, we are still documenting it side by side with the `apiserver.config.k8s.io/v1` API group;
- The `eventratelimit.admission.k8s.io/v1alpha1` API could use a better reference rather than the design doc; **The imagepolicy.v1alpha1 API is not documented anywhere, I'll add it later on.**
- There are statements about future, which should be removed;
- We are supposed refer to the `LimitRage` API reference rather than pointing users to the design docs;
- We are supposed refer to the `ResourceQuota` API reference rather than pointing users to the design docs;
- There are long lines in the page source which could have been wrapped properly.
Tom Kivlin