Suggest adding a link in case the reader is not familiar with what "anonymous requests" means. This paragraph also includes a reference to "anonymous user," so I think the link is warranted. Thanks.
* Revise CertificateSigningRequest approval & rejection details
API clients can deny CSRs. Document this and tidy the page.
"There is currently not a mechanism for a signer implementation to report
its inability to sign a request." seemed misleading; clients can set
status.
* Tidy page
Co-Authored-By: Jordan Liggitt <jordan@liggitt.net>
Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
* Update to match website style guide
* Use glossary shortcodes
* Overall tidying
* Drop mention of old (unsupported) releases
* Reword RBAC notes & warnings
* Write “role bindings” as two words
* Tweak RBAC guide wording
* Tweak RBAC out-of-the-box roles table
* Mention other authorizers
There are other authorizers than RBAC and ABAC; hint that these exist
and that the API server might run with these configured.
* Fix formatting of API discovery roles
Also add table caption
* Drop incorrect reference to cluster-status
* Drop vestigial RBAC warning
* Clarify content-type and tracking of all objects
* Update content/en/docs/reference/using-api/api-concepts.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* SSA: Improve a couple of sentences
Co-authored-by: Kevin Wiesmueller <kwiesmueller@seibert-media.net>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* adding cheatsheet.md
adding kubectl command to get containerIDs of all
initContainers for every Pod in the cluster
helps to identify stopped container which should not be removed,
when running manual cleanup of stopped containers on K8s cluster nodes
* adding more context for finding initContainer IDs
* removing reference to github issue
Signed-off-by: Anastas Dancha <anapsix@random.io>
Personally the explanation was quite difficult to understand without looking into the code.
I hope I managed to simplify it a bit and added an example how to add annotations to a
namespace so they can be consumed by the PodTolerationRestriction admission
controller.
Signed-off-by: Manuel Rüger <manuel@rueg.eu>
It is not clear that the 'caBundle' field in the Mutating/Validating webhook object is used for client-side validation from the admission controller itself.
The comment which appears at the source code is much more clear --> https://github.com/kubernetes/api/blob/master/admissionregistration/v1beta1/types.go#L534-L537
My suggestion is to change the description to match the documentation which is IMO much more clear
* [WIP] Update Topology Manager for 1.18
Move from Alpha to Beta.
Remove Known Limitation - fixed in 1.18.
* Nit: Update content/en/docs/tasks/administer-cluster/topology-manager.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Add section on feature gate with version guidance.
* Add Known Limitation on Memory/Hugepages
* Update content/en/docs/tasks/administer-cluster/topology-manager.md
Clean up wording of known limitations
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Edits to feature gate description based on review
* Up date feature gates table.
Co-authored-by: Tim Bannister <tim@scalefactory.com>
You can't specify more then one resources at one for explain. See error below:
$ kubectl explain pods,svc
the server doesn't have a resource type "pods,svc"
error: We accept only this format: explain RESOURCE
* Update dry-run docs.
* Promote server-side dry-run feature state to stable in 1.18
* Replace --dry-run with --dry-run=server|client|none accordingly
* Update server-side dry-run blog post
* Update content/en/docs/reference/using-api/api-concepts.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Address comments
* Add note at end of server-side dry-run blogpost
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Adds an entry to the Concepts section that gives an overview of the feature
and builds upon the generated API documentation.
Also adds a Glossary entry for shuffle sharding.
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
Co-Authored-By: Mike Spreitzer <mspreitz@us.ibm.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Mike Spreitzer <mspreitz@us.ibm.com>
* Update hugepages documentation
- described support for multiple huge page sizes
- described container isolation of the huge pages
* Add HugePageStorageMediumSize description
* update description for container isolation of hugepages
Signed-off-by: Byonggon Chun <bg.chun@samsung.com>
Co-authored-by: Byonggon Chun <bg.chun@samsung.com>
vineeth