The 'metrics.k8s.io' APIs are exposed by the 'metrics-server' component to facilitate
auto-scaling. The other two APIs are for fetching metrics from custom or
external sources respectively.
This PR fixes the IPVS scheduler name list by adding schedulers that
were missing and adding some descriptions (copied for source code
comments) for each.
The upstream source comments are not quite strict at using `*`s,
`<`s or `>`s. These characters, when not enclosed in backtiqs, are
interpreted as Markdown emphasize markers or HTML tags.
Hacking the generator code is not the right solution. We should
attempt to fix them in the source code instead.
Before that, let's keep fixing the generated outputs manually.
* Single column css and documentation.md
* Wrapper class added & SCSS adjusted accordingly
* some label fixes
* Wrapper class is now metric only
* Final fixes for labels and padding in mobile devices
* Change text in Pod Security Admission metrics
* remove changes from the metrics.md file
* Correct in the page about ValidatingAdmissionPolicy uses a mixture of API groups
* Revert "remove changes from the metrics.md file"
This reverts commit da450f4471.
* Refactoring node status to new page
- Created a new page in architecture in node for the status
- Removed the current node status from concepts and moved it there
* Update content/en/docs/reference/node/_index.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/docs/reference/node/node-status.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update content/en/docs/concepts/architecture/nodes.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* Update node-status.md
* Update node-status.md
* Update content/en/docs/reference/node/node-status.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
---------
Co-authored-by: Tim Bannister <tim@scalefactory.com>
The reference generator wasn't able to generate reference for `kubelet`
(for a long time now). This PR updates the reference manually, based on
the output from `kubelet --help`.
This PR makes sure the manifests under `content/en/examples`
are valid in v1.28. The primary fixes are:
- Updated the go.mod/go.sum file for testing against v1.28.0 release.
- Revise test case code to ensure newly added manifests are tested;
- Adapt Pod validation options to upstream validation code change;
- Move a ValidatingWebhookConfiguration YAML back to inline because
the manifest cannot validate against the validator. The CA bundle
referenced is not a valid string (base64 encoded). That means the
YAML cannot be used/tested as is by users.