From 0c3e853865204c16eb91bb27c59a5c0c4e06e5da Mon Sep 17 00:00:00 2001 From: Amrita Date: Wed, 23 Feb 2022 22:22:32 +0530 Subject: [PATCH] NE-726 CP issues --- modules/nw-dns-forward.adoc | 45 +++---- .../dns-operator-openshift-io-v1.adoc | 116 +++++++++--------- 2 files changed, 83 insertions(+), 78 deletions(-) diff --git a/modules/nw-dns-forward.adoc b/modules/nw-dns-forward.adoc index 2d56f74401..74dfcc7bbf 100644 --- a/modules/nw-dns-forward.adoc +++ b/modules/nw-dns-forward.adoc @@ -39,36 +39,39 @@ spec: servers: - name: foo-server <1> zones: <2> - - foo.com + - foo.com forwardPlugin: - upstreams: <3> - - 1.1.1.1 - - 2.2.2.2:5353 + policy: Random <3> + upstreams: <4> + - 1.1.1.1 + - 2.2.2.2:5353 - name: bar-server zones: - - bar.com - - example.com + - bar.com + - example.com forwardPlugin: + policy: Random upstreams: - - 3.3.3.3 - - 4.4.4.4:5454 - upstreamResolvers: <4> - policy: Random <5> - upstreams: <6> - - type: SystemResolvConf <7> + - 3.3.3.3 + - 4.4.4.4:5454 + upstreamResolvers: <5> + policy: Random <6> + upstreams: <7> + - type: SystemResolvConf <8> - type: Network - address: 1.2.3.4 <8> - port: 53 <9> + address: 1.2.3.4 <9> + port: 53 <10> ---- <1> Must comply with the `rfc6335` service name syntax. <2> Must conform to the definition of a `subdomain` in `rfc1123`. The cluster domain, `cluster.local`, is an invalid `subdomain` for `zones`. -<3> A maximum of 15 `upstreams` is allowed per `forwardPlugin`. -<4> Optional. You can use it to override the default policy and forward DNS resolution to the specified DNS resolvers (upstream resolvers) for the default domain. If you do not provide any upstream resolvers, the DNS name queries go to the servers in `/etc/resolv.conf`. -<5> Determines the order in which upstream servers are selected for querying. You can specify one of these values: `Random`, `RoundRobin`, and `Sequential`. The default value is `Sequential`. -<6> Optional. You can use it to provide upstream resolvers. -<7> You can specify two types of `upstreams` - `SystemResolvConf` and `Network`. `SystemResolvConf` is for configuring the upstream to use `/etc/resolv.conf` and `Network` is for defining a `Networkresolver`. You can specify one or both. -<8> If the specified type is `Network`, you must provide an IP address. `address` must be a valid IPv4 or IPv6 address. -<9> If the specified type is `Network`, you can optionally provide a port. `port` must be between 1 and 65535. +<3> Defines the policy to select upstream resolvers. Default value is `Random`. You can also use `RoundRobin`, and `Sequential`. +<4> A maximum of 15 `upstreams` is allowed per `forwardPlugin`. +<5> Optional. You can use it to override the default policy and forward DNS resolution to the specified DNS resolvers (upstream resolvers) for the default domain. If you do not provide any upstream resolvers, the DNS name queries go to the servers in `/etc/resolv.conf`. +<6> Determines the order in which upstream servers are selected for querying. You can specify one of these values: `Random`, `RoundRobin`, or `Sequential`. The default value is `Sequential`. +<7> Optional. You can use it to provide upstream resolvers. +<8> You can specify two types of `upstreams` - `SystemResolvConf` and `Network`. `SystemResolvConf` configures the upstream to use ``/etc/resolv.conf` and `Network` defines a `Networkresolver`. You can specify one or both. +<9> If the specified type is `Network`, you must provide an IP address. `address` must be a valid IPv4 or IPv6 address. +<10> If the specified type is `Network`, you can optionally provide a port. `port` must be between 1 and 65535. + [NOTE] ==== diff --git a/rest_api/operator_apis/dns-operator-openshift-io-v1.adoc b/rest_api/operator_apis/dns-operator-openshift-io-v1.adoc index 195a4be73a..1673ffc483 100644 --- a/rest_api/operator_apis/dns-operator-openshift-io-v1.adoc +++ b/rest_api/operator_apis/dns-operator-openshift-io-v1.adoc @@ -12,9 +12,9 @@ toc::[] Description:: + -- -DNS manages the CoreDNS component to provide a name resolution service for pods and services in the cluster. - This supports the DNS-based service discovery specification: https://github.com/kubernetes/dns/blob/master/docs/specification.md - More details: https://kubernetes.io/docs/tasks/administer-cluster/coredns +DNS manages the CoreDNS component to provide a name resolution service for pods and services in the cluster. +This supports the DNS-based service discovery specification: https://github.com/kubernetes/dns/blob/master/docs/specification.md +More details: https://kubernetes.io/docs/tasks/administer-cluster/coredns -- Type:: @@ -72,14 +72,14 @@ Type:: | `nodePlacement` | `object` -| nodePlacement provides explicit control over the scheduling of DNS pods. - Generally, it is useful to run a DNS pod on every node so that DNS queries are always handled by a local DNS pod instead of going over the network to a DNS pod on another node. However, security policies may require restricting the placement of DNS pods to specific nodes. For example, if a security policy prohibits pods on arbitrary nodes from communicating with the API, a node selector can be specified to restrict DNS pods to nodes that are permitted to communicate with the API. Conversely, if running DNS pods on nodes with a particular taint is desired, a toleration can be specified for that taint. +| nodePlacement provides explicit control over the scheduling of DNS pods. + Generally, it is useful to run a DNS pod on every node so that DNS queries are always handled by a local DNS pod instead of going over the network to a DNS pod on another node. However, security policies may require restricting the placement of DNS pods to specific nodes. For example, if a security policy prohibits pods on arbitrary nodes from communicating with the API, a node selector can be specified to restrict DNS pods to nodes that are permitted to communicate with the API. Conversely, if running DNS pods on nodes with a particular taint is desired, a toleration can be specified for that taint. If unset, defaults are used. See nodePlacement for more details. | `servers` | `array` -| servers is a list of DNS resolvers that provide name query delegation for one or more subdomains outside the scope of the cluster domain. If servers consists of more than one Server, longest suffix match will be used to determine the Server. - For example, if there are two Servers, one for "foo.com" and another for "a.foo.com", and the name query is for "www.a.foo.com", it will be routed to the Server with Zone "a.foo.com". +| servers is a list of DNS resolvers that provide name query delegation for one or more subdomains outside the scope of the cluster domain. If servers consists of more than one Server, longest suffix match is used to determine the server. + For example, if there are two servers, one for "foo.com" and another for "a.foo.com", and the name query is for "www.a.foo.com", it is routed to the server with Zone "a.foo.com". If this field is nil, no servers are created. | `servers[]` @@ -91,8 +91,8 @@ Type:: Description:: + -- -nodePlacement provides explicit control over the scheduling of DNS pods. - Generally, it is useful to run a DNS pod on every node so that DNS queries are always handled by a local DNS pod instead of going over the network to a DNS pod on another node. However, security policies may require restricting the placement of DNS pods to specific nodes. For example, if a security policy prohibits pods on arbitrary nodes from communicating with the API, a node selector can be specified to restrict DNS pods to nodes that are permitted to communicate with the API. Conversely, if running DNS pods on nodes with a particular taint is desired, a toleration can be specified for that taint. +nodePlacement provides explicit control over the scheduling of DNS pods. + Generally, it is useful to run a DNS pod on every node so that DNS queries are always handled by a local DNS pod instead of going over the network to a DNS pod on another node. However, security policies may require restricting the placement of DNS pods to specific nodes. For example, if a security policy prohibits pods on arbitrary nodes from communicating with the API, a node selector can be specified to restrict DNS pods to nodes that are permitted to communicate with the API. Conversely, if running DNS pods on nodes with a particular taint is desired, a toleration can be specified for that taint. If unset, defaults are used. See nodePlacement for more details. -- @@ -108,16 +108,16 @@ Type:: | `nodeSelector` | `object (string)` -| nodeSelector is the node selector applied to DNS pods. - If empty, the default is used, which is currently the following: - kubernetes.io/os: linux - This default is subject to change. +| nodeSelector is the node selector applied to DNS pods. + If empty, the default is used, which is currently the following: + kubernetes.io/os: linux + This default is subject to change. If set, the specified selector is used and replaces the default. | `tolerations` | `array` -| tolerations is a list of tolerations applied to DNS pods. - If empty, the DNS operator sets a toleration for the "node-role.kubernetes.io/master" taint. This default is subject to change. Specifying tolerations without including a toleration for the "node-role.kubernetes.io/master" taint may be risky as it could lead to an outage if all worker nodes become unavailable. +| tolerations is a list of tolerations applied to DNS pods. + If empty, the DNS operator sets a toleration for the "node-role.kubernetes.io/master" taint. This default is subject to change. Specifying tolerations without including a toleration for the "node-role.kubernetes.io/master" taint may be risky as it could lead to an outage if all worker nodes become unavailable. Note that the daemon controller adds some tolerations as well. See https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ | `tolerations[]` @@ -129,8 +129,8 @@ Type:: Description:: + -- -tolerations is a list of tolerations applied to DNS pods. - If empty, the DNS operator sets a toleration for the "node-role.kubernetes.io/master" taint. This default is subject to change. Specifying tolerations without including a toleration for the "node-role.kubernetes.io/master" taint may be risky as it could lead to an outage if all worker nodes become unavailable. +tolerations is a list of tolerations applied to DNS pods. + If empty, the DNS operator sets a toleration for the "node-role.kubernetes.io/master" taint. This default is subject to change. Specifying tolerations without including a toleration for the "node-role.kubernetes.io/master" taint may be risky as it could lead to an outage if all worker nodes become unavailable. Note that the daemon controller adds some tolerations as well. See https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ -- @@ -171,7 +171,7 @@ Type:: | `tolerationSeconds` | `integer` -| TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system. +| TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values are treated as 0 (evict immediately) by the system. | `value` | `string` @@ -182,8 +182,8 @@ Type:: Description:: + -- -servers is a list of DNS resolvers that provide name query delegation for one or more subdomains outside the scope of the cluster domain. If servers consists of more than one Server, longest suffix match will be used to determine the Server. - For example, if there are two Servers, one for "foo.com" and another for "a.foo.com", and the name query is for "www.a.foo.com", it will be routed to the Server with Zone "a.foo.com". +servers is a list of DNS resolvers that provide name query delegation for one or more subdomains outside the scope of the cluster domain. If servers consists of more than one Server, longest suffix match is used to determine the server. + For example, if there are two servers, one for "foo.com" and another for "a.foo.com", and the name query is for "www.a.foo.com", it is routed to the server with Zone "a.foo.com". If this field is nil, no servers are created. -- @@ -220,7 +220,7 @@ Type:: | `zones` | `array (string)` -| zones is required and specifies the subdomains that Server is authoritative for. Zones must conform to the rfc1123 definition of a subdomain. Specifying the cluster domain (i.e., "cluster.local") is invalid. +| zones is required and specifies the subdomains that server is authoritative for. Zones must conform to the rfc1123 definition of a subdomain. Specifying the cluster domain (i.e., "cluster.local") is invalid. |=== === .spec.servers[].forwardPlugin @@ -240,10 +240,14 @@ Type:: |=== | Property | Type | Description +| `policy` +| `array (string)` +| Policy defines the policy to select upstream resolvers. There are 3 values: `Random` is the default, and is a policy that implements random upstream selections,`RoundRobin` is a policy that select hosts based on round robin order, and `Sequential` is a policy that select hosts based on sequential order. + | `upstreams` | `array (string)` -| upstreams is a list of resolvers to forward name queries for subdomains of Zones. Upstreams are randomized when more than 1 upstream is specified. Each instance of CoreDNS performs health checking of Upstreams. When a healthy upstream returns an error during the exchange, another resolver is tried from Upstreams. Each upstream is represented by an IP address or IP:port if the upstream listens on a port other than 53. - A maximum of 15 upstreams is allowed per ForwardPlugin. +| `upstreams` is a list of resolvers to forward name queries for subdomains of Zones. `upstreams` are randomized when more than 1 upstream is specified. Each instance of CoreDNS performs health checking of `upstreams`. When a healthy upstream returns an error during the exchange, another resolver is tried from `upstreams`. Each upstream is represented by an IP address or IP:port if the upstream listens on a port other than 53. + A maximum of 15 `upstreams` is allowed per ForwardPlugin. |=== === .status @@ -268,20 +272,20 @@ Required:: | `clusterDomain` | `string` -| clusterDomain is the local cluster DNS domain suffix for DNS services. This will be a subdomain as defined in RFC 1034, section 3.5: https://tools.ietf.org/html/rfc1034#section-3.5 Example: "cluster.local" +| clusterDomain is the local cluster DNS domain suffix for DNS services. This is a subdomain as defined in RFC 1034, section 3.5: https://tools.ietf.org/html/rfc1034#section-3.5 Example: "cluster.local" More info: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service | `clusterIP` | `string` -| clusterIP is the service IP through which this DNS is made available. - In the case of the default DNS, this will be a well known IP that is used as the default nameserver for pods that are using the default ClusterFirst DNS policy. - In general, this IP can be specified in a pod's spec.dnsConfig.nameservers list or used explicitly when performing name resolution from within the cluster. Example: dig foo.com @ +| clusterIP is the service IP through which this DNS is made available. + In the case of the default DNS, this is a well-known IP that is used as the default nameserver for pods that are using the default ClusterFirst DNS policy. + In general, this IP can be specified in a pod's spec.dnsConfig.nameservers list or used explicitly when performing name resolution from within the cluster. Example: dig foo.com @ More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies | `conditions` | `array` -| conditions provide information about the state of the DNS on the cluster. - These are the supported DNS conditions: +| conditions provide information about the state of the DNS on the cluster. + These are the supported DNS conditions: * Available - True if the following conditions are met: * DNS controller daemonset is available. - False if any of those conditions are unsatisfied. | `conditions[]` @@ -293,8 +297,8 @@ Required:: Description:: + -- -conditions provide information about the state of the DNS on the cluster. - These are the supported DNS conditions: +conditions provide information about the state of the DNS on the cluster. + These are the supported DNS conditions: * Available - True if the following conditions are met: * DNS controller daemonset is available. - False if any of those conditions are unsatisfied. -- @@ -323,23 +327,23 @@ Type:: | `lastTransitionTime` | `string` -| +| | `message` | `string` -| +| | `reason` | `string` -| +| | `status` | `string` -| +| | `type` | `string` -| +| |=== @@ -390,7 +394,7 @@ Description:: | allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | `continue` | `string` -| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". +| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request is included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | `fieldSelector` @@ -403,7 +407,7 @@ This field is not supported when watch is true. Clients may start a watch from t | `integer` | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. -The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. +The server guarantees that the objects returned when using continue are identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued is included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | `resourceVersion` | `string` | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. @@ -449,7 +453,7 @@ Description:: | allowWatchBookmarks requests watch events with type "BOOKMARK". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. | `continue` | `string` -| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the "next key". +| The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request is included in the response, as long as their keys are after the "next key". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications. | `fieldSelector` @@ -462,7 +466,7 @@ This field is not supported when watch is true. Clients may start a watch from t | `integer` | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. -The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. +The server guarantees that the objects returned when using continue is identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued is included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | `resourceVersion` | `string` | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. @@ -505,7 +509,7 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `fieldManager` | `string` | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. @@ -517,7 +521,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../operator_apis/dns-operator-openshift-io-v1.adoc#dns-operator-openshift-io-v1[`DNS`] schema -| +| |=== .HTTP responses @@ -568,16 +572,16 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `gracePeriodSeconds` | `integer` -| The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. +| The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type is used. Defaults to a per object value if not specified. zero means delete immediately. | `orphanDependents` | `boolean` -| Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both. +| Deprecated: please use the PropagationPolicy, this field is deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer is added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both. | `propagationPolicy` | `string` -| Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. +| Whether and how garbage collection is performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. |=== .Body parameters @@ -586,7 +590,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../objects/index.adoc#io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions_v2[`DeleteOptions_v2`] schema -| +| |=== .HTTP responses @@ -643,7 +647,7 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `fieldManager` | `string` | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. @@ -655,7 +659,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../objects/index.adoc#io.k8s.apimachinery.pkg.apis.meta.v1.Patch[`Patch`] schema -| +| |=== .HTTP responses @@ -681,7 +685,7 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `fieldManager` | `string` | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. @@ -693,7 +697,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../operator_apis/dns-operator-openshift-io-v1.adoc#dns-operator-openshift-io-v1[`DNS`] schema -| +| |=== .HTTP responses @@ -771,7 +775,7 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `fieldManager` | `string` | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. @@ -783,7 +787,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../objects/index.adoc#io.k8s.apimachinery.pkg.apis.meta.v1.Patch[`Patch`] schema -| +| |=== .HTTP responses @@ -809,7 +813,7 @@ Description:: | Parameter | Type | Description | `dryRun` | `string` -| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages are processed | `fieldManager` | `string` | fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. @@ -821,7 +825,7 @@ Description:: | Parameter | Type | Description | `body` | xref:../operator_apis/dns-operator-openshift-io-v1.adoc#dns-operator-openshift-io-v1[`DNS`] schema -| +| |=== .HTTP responses @@ -835,5 +839,3 @@ Description:: | 401 - Unauthorized | Empty |=== - -