Modifications are as following(`APPENDIX` -> `**easyrsa**`):
1, fix Jenkins GCE e2e failure, mainly for markdown errors;
2, change `"${MASTER_IP}"` to `"IP:${MASTER_IP}"` to keep align with `make-ca-cert.sh`
3, change `/pki/` to `pki/` for the generated certs/key
4, other tiny improvements
Please check, thanks.
This commit merges the NamespaceExists admission controller
into the NamespaceLifecycle admission controller.
New tests were added to the NamespaceLifecycle addmission controller
tests, and the test case was fixed so that it runs without panicing.
Additionally, the NamespaceExists admission controller was marked as
deprecated in the docs.
Closes#12053
Two modifications:
1, The example used in this document is outdated so update it
2, Delete the old `kubectl namespace myspace` since it produces an error `error: namespace has been superceded by the context.namespace field of .kubeconfig files`
Amend two markdown errors in authentication.md.
1, amend order list display error by enter a newline after the first sentence
2, add two backticks to make ``"@`date +%s`"`` display correctly
gunk when installing the google-fluentd agent.
Also let it log things by not redirecting to a file within the container
and only using -q (warning logs only) rather than -qq (error logs only).
Change `chmod +X` to `chmod +x`, since `+X` does not take affect when there is no execute permission bit already set (either user, group or other).
```console
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
# chmod +X /usr/bin/kubectl
# ls -l /usr/bin/kubectl
-rw-r--r-- 1 root root 14190181 Aug 10 16:16 /usr/bin/kubectl
```
Please refer to [chmod](https://en.wikipedia.org/wiki/Chmod "chmod") for more details.
>which is not a permission in itself but rather can be used instead of x. It applies execute permissions to directories regardless of their current permissions and **applies execute permissions to a file which already has at least one execute permission bit already set (either user, group or other)**. It is only really useful when used with '+' and usually in combination with the -R option for giving group or other access to a big directory tree without setting execute permission on normal files (such as text files), which would normally happen if you just used "chmod -R a+rx .", whereas with 'X' you can do "chmod -R a+rX ." instead
