Batch fix links (5)
This commit is contained in:
@@ -9,7 +9,7 @@ weight: 95
|
|||||||
|
|
||||||
<!-- overview -->
|
<!-- overview -->
|
||||||
The tables below enumerate the configuration parameters on
|
The tables below enumerate the configuration parameters on
|
||||||
[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) objects, whether the field mutates
|
[PodSecurityPolicy](/docs/concepts/security/pod-security-policy/) objects, whether the field mutates
|
||||||
and/or validates pods, and how the configuration values map to the
|
and/or validates pods, and how the configuration values map to the
|
||||||
[Pod Security Standards](/docs/concepts/security/pod-security-standards/).
|
[Pod Security Standards](/docs/concepts/security/pod-security-standards/).
|
||||||
|
|
||||||
@@ -31,9 +31,9 @@ The fields enumerated in this table are part of the `PodSecurityPolicySpec`, whi
|
|||||||
under the `.spec` field path.
|
under the `.spec` field path.
|
||||||
|
|
||||||
<table class="no-word-break">
|
<table class="no-word-break">
|
||||||
<caption style="display:none">Mapping PodSecurityPolicySpec fields to Pod Security Standards</caption>
|
<caption style="display:none">Mapping PodSecurityPolicySpec fields to Pod Security Standards</caption>
|
||||||
<tbody>
|
<tbody>
|
||||||
<tr>
|
<tr>
|
||||||
<th><code>PodSecurityPolicySpec</code></th>
|
<th><code>PodSecurityPolicySpec</code></th>
|
||||||
<th>Type</th>
|
<th>Type</th>
|
||||||
<th>Pod Security Standards Equivalent</th>
|
<th>Pod Security Standards Equivalent</th>
|
||||||
@@ -54,19 +54,19 @@ under the `.spec` field path.
|
|||||||
<td>
|
<td>
|
||||||
<p><b>Baseline</b>: subset of</p>
|
<p><b>Baseline</b>: subset of</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li><code>AUDIT_WRITE</code></li>
|
<li><code>AUDIT_WRITE</code></li>
|
||||||
<li><code>CHOWN</code></li>
|
<li><code>CHOWN</code></li>
|
||||||
<li><code>DAC_OVERRIDE</code></li>
|
<li><code>DAC_OVERRIDE</code></li>
|
||||||
<li><code>FOWNER</code></li>
|
<li><code>FOWNER</code></li>
|
||||||
<li><code>FSETID</code></li>
|
<li><code>FSETID</code></li>
|
||||||
<li><code>KILL</code></li>
|
<li><code>KILL</code></li>
|
||||||
<li><code>MKNOD</code></li>
|
<li><code>MKNOD</code></li>
|
||||||
<li><code>NET_BIND_SERVICE</code></li>
|
<li><code>NET_BIND_SERVICE</code></li>
|
||||||
<li><code>SETFCAP</code></li>
|
<li><code>SETFCAP</code></li>
|
||||||
<li><code>SETGID</code></li>
|
<li><code>SETGID</code></li>
|
||||||
<li><code>SETPCAP</code></li>
|
<li><code>SETPCAP</code></li>
|
||||||
<li><code>SETUID</code></li>
|
<li><code>SETUID</code></li>
|
||||||
<li><code>SYS_CHROOT</code></li>
|
<li><code>SYS_CHROOT</code></li>
|
||||||
</ul>
|
</ul>
|
||||||
<p><b>Restricted</b>: empty / undefined / nil OR a list containing <i>only</i> <code>NET_BIND_SERVICE</code>
|
<p><b>Restricted</b>: empty / undefined / nil OR a list containing <i>only</i> <code>NET_BIND_SERVICE</code>
|
||||||
</td>
|
</td>
|
||||||
@@ -236,9 +236,9 @@ The [annotations](/docs/concepts/overview/working-with-objects/annotations/) enu
|
|||||||
table can be specified under `.metadata.annotations` on the PodSecurityPolicy object.
|
table can be specified under `.metadata.annotations` on the PodSecurityPolicy object.
|
||||||
|
|
||||||
<table class="no-word-break">
|
<table class="no-word-break">
|
||||||
<caption style="display:none">Mapping PodSecurityPolicy annotations to Pod Security Standards</caption>
|
<caption style="display:none">Mapping PodSecurityPolicy annotations to Pod Security Standards</caption>
|
||||||
<tbody>
|
<tbody>
|
||||||
<tr>
|
<tr>
|
||||||
<th><code>PSP Annotation</code></th>
|
<th><code>PSP Annotation</code></th>
|
||||||
<th>Type</th>
|
<th>Type</th>
|
||||||
<th>Pod Security Standards Equivalent</th>
|
<th>Pod Security Standards Equivalent</th>
|
||||||
|
|||||||
@@ -2,9 +2,10 @@
|
|||||||
title: Extensions
|
title: Extensions
|
||||||
id: Extensions
|
id: Extensions
|
||||||
date: 2019-02-01
|
date: 2019-02-01
|
||||||
full_link: /docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
full_link: /docs/concepts/extend-kubernetes/#extensions
|
||||||
short_description: >
|
short_description: >
|
||||||
Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
|
Extensions are software components that extend and deeply integrate with Kubernetes to support
|
||||||
|
new types of hardware.
|
||||||
|
|
||||||
aka:
|
aka:
|
||||||
tags:
|
tags:
|
||||||
@@ -15,4 +16,6 @@ tags:
|
|||||||
|
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
Many cluster administrators use a hosted or distribution instance of Kubernetes. These clusters come with extensions pre-installed. As a result, most Kubernetes users will not need to install [extensions](/docs/concepts/extend-kubernetes/extend-cluster/#extensions) and even fewer users will need to author new ones.
|
Many cluster administrators use a hosted or distribution instance of Kubernetes. These clusters
|
||||||
|
come with extensions pre-installed. As a result, most Kubernetes users will not need to install
|
||||||
|
[extensions](/docs/concepts/extend-kubernetes/) and even fewer users will need to author new ones.
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
title: Garbage Collection
|
title: Garbage Collection
|
||||||
id: garbage-collection
|
id: garbage-collection
|
||||||
date: 2021-07-07
|
date: 2021-07-07
|
||||||
full_link: /docs/concepts/workloads/controllers/garbage-collection/
|
full_link: /docs/concepts/architecture/garbage-collection/
|
||||||
short_description: >
|
short_description: >
|
||||||
A collective term for the various mechanisms Kubernetes uses to clean up cluster
|
A collective term for the various mechanisms Kubernetes uses to clean up cluster
|
||||||
resources.
|
resources.
|
||||||
@@ -12,13 +12,16 @@ tags:
|
|||||||
- fundamental
|
- fundamental
|
||||||
- operation
|
- operation
|
||||||
---
|
---
|
||||||
Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up
|
|
||||||
cluster resources.
|
Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up
|
||||||
|
cluster resources.
|
||||||
|
|
||||||
<!--more-->
|
<!--more-->
|
||||||
|
|
||||||
Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images),
|
Kubernetes uses garbage collection to clean up resources like
|
||||||
|
[unused containers and images](/docs/concepts/architecture/garbage-collection/#containers-images),
|
||||||
[failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection),
|
[failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection),
|
||||||
[objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/),
|
[objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/),
|
||||||
[completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources
|
[completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources
|
||||||
that have expired or failed.
|
that have expired or failed.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user