优先级增删查改、Deployment增删改查

#K8sAPI

API	操作方式	描述
SchedulingV1Api	使用 SchedulingV1Api apiInstance = new SchedulingV1Api();	优先级增删改查
AppsV1Api	使用 AppsV1Api apiInstance = new AppsV1Api();	Deployment增删改查

SchedulingV1Api

回到K8sAPI根目录

All URIs are relative to http://localhost

Method	HTTP request	Description
createPriorityClass	POST /apis/scheduling.k8s.io/v1/priorityclasses	创建优先级
deleteCollectionPriorityClass	DELETE /apis/scheduling.k8s.io/v1/priorityclasses	删除多个优先级
deletePriorityClass	DELETE /apis/scheduling.k8s.io/v1/priorityclasses/{name}	删除优先级
getAPIResources	GET /apis/scheduling.k8s.io/v1/	获取可用资源
listPriorityClass	GET /apis/scheduling.k8s.io/v1/priorityclasses	优先级列表
patchPriorityClass	PATCH /apis/scheduling.k8s.io/v1/priorityclasses/{name}	修改优先级
readPriorityClass	GET /apis/scheduling.k8s.io/v1/priorityclasses/{name}	查询指定优先级
replacePriorityClass	PUT /apis/scheduling.k8s.io/v1/priorityclasses/{name}	替换优先级

createPriorityClass

回到SchedulingV1Api目录

V1PriorityClass createPriorityClass(body, pretty, dryRun, fieldManager)

create a PriorityClass

Example

// Import classes:
import io.kubernetes.client.openapi.ApiClient;
import io.kubernetes.client.openapi.ApiException;
import io.kubernetes.client.openapi.Configuration;
import io.kubernetes.client.openapi.auth.*;
import io.kubernetes.client.openapi.models.*;
import io.kubernetes.client.openapi.apis.SchedulingV1Api;

public class Example {
   
  public static void main(String[] args) {
   
    ApiClient defaultClient = Configuration.getDefaultApiClient();
    defaultClient.setBasePath("http://localhost");
    
    // Configure API key authorization: BearerToken
    ApiKeyAuth BearerToken = (ApiKeyAuth) defaultClient.getAuthentication("BearerToken");
    BearerToken.setApiKey("YOUR API KEY");
    // Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
    //BearerToken.setApiKeyPrefix("Token");

    SchedulingV1Api apiInstance = new SchedulingV1Api(defaultClient);
    V1PriorityClass body = new V1PriorityClass(); // V1PriorityClass | 
    String pretty = "pretty_example"; // String | 如果为“true”，则输出相当打印。If 'true', then the output is pretty printed.
    String dryRun = "dryRun_example"; // String | 如果存在，则表示不应保留修改。无效或无法识别的dryRun指令将导致错误响应，并且不会进一步处理请求。有效值为：-全部：将处理所有干运行阶段。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
    String fieldManager = "fieldManager_example"; // String |  fieldManager是与进行这些更改的参与者或实体关联的名称。该值的长度必须小于或128个字符，并且仅包含可打印字符，如https://golang.org/pkg/unicode/#IsPrint.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.
    try {
   
      V1PriorityClass result = apiInstance.createPriorityClass(body, pretty, dryRun, fieldManager);
      System.out.println(result);
    } catch (ApiException e) {
   
      System.err.println("Exception when calling SchedulingV1Api#createPriorityClass");
      System.err.println("Status code: " + e.getCode());
      System.err.println("Reason: " + e.getResponseBody());
      System.err.println("Response headers: " + e.getResponseHeaders());
      e.printStackTrace();
    }
  }
}

Parameters

Name	Type	Description	Notes
body	V1PriorityClass
pretty	String	如果为“true”，则输出相当打印。If 'true', then the output is pretty printed.	[optional]
dryRun	String	如果存在，则表示不应保留修改。无效或无法识别的dryRun指令将导致错误响应，并且不会进一步处理请求。有效值为：-全部：将处理所有干运行阶段。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	[optional]
fieldManager	String	fieldManager是与进行这些更改的参与者或实体关联的名称。该值的长度必须小于或128个字符，并且仅包含可打印字符，如https://golang.org/pkg/unicode/#IsPrint.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.	[optional]

Return type

V1PriorityClass

Authorization

BearerToken

HTTP request headers

• Content-Type: Not defined
• Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

HTTP response details

Status code	Description	Response headers
200	OK	-
201	Created	-
202	Accepted	-
401	Unauthorized	-

deleteCollectionPriorityClass

回到SchedulingV1Api目录

V1Status deleteCollectionPriorityClass(pretty, _continue, dryRun, fieldSelector, gracePeriodSeconds, labelSelector, limit, orphanDependents, propagationPolicy, resourceVersion, timeoutSeconds, body)

delete collection of PriorityClass

Example

// Import classes:
import io.kubernetes.client.openapi.ApiClient;
import io.kubernetes.client.openapi.ApiException;
import io.kubernetes.client.openapi.Configuration;
import io.kubernetes.client.openapi.auth.*;
import io.kubernetes.client.openapi.models.*;
import io.kubernetes.client.openapi.apis.SchedulingV1Api;

public class Example {
   
  public static void main(String[] args) {
   
    ApiClient defaultClient = Configuration.getDefaultApiClient();
    defaultClient.setBasePath("http://localhost");
    
    // Configure API key authorization: BearerToken
    ApiKeyAuth BearerToken = (ApiKeyAuth) defaultClient.getAuthentication("BearerToken");
    BearerToken.setApiKey("YOUR API KEY");
    // Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
    //BearerToken.setApiKeyPrefix("Token");

    SchedulingV1Api apiInstance = new SchedulingV1Api(defaultClient);
    String pretty = "pretty_example"; // String | 如果为“true”，则输出相当打印。If 'true', then the output is pretty printed.
    String _continue = "_continue_example"; // String | 从服务器检索更多结果时，应设置“继续”选项。由于此值是服务器定义的，因此客户端只能使用具有相同查询参数（continue值除外）的上一个查询结果中的continue值，服务器可能会拒绝它无法识别的continue值。如果指定的continue值因过期（通常为5到15分钟）或服务器上的配置更改而不再有效，服务器将响应410 ResourceExpired错误和continue令牌。如果客户端需要一个一致的列表，它必须在不使用continue字段的情况下重新启动它们的列表。从另一台服务器发送的结果可能与前一台服务器发送的结果不一致，但从下一台服务器发送的结果可能与前一台服务器发送的结果不一致，只要他们的钥匙在“下一个钥匙”之后。watch为true时不支持此字段。客户端可以从服务器返回的最后一个resourceVersion值开始监视，并且不会错过任何修改。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".  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.(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\".  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.
    String dryRun = "dryRun_example"; // String | 如果存在，则表示不应保留修改。无效或无法识别的dryRun指令将导致错误响应，并且不会进一步处理请求。有效值为：-全部：将处理所有干运行阶段。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
    String fieldSelector = "fieldSelector_example"; // String | 一个选择器，用于按字段限制返回对象的列表。默认为一切。A selector to restrict the list of returned objects by their fields. Defaults to everything.
    Integer gracePeriodSeconds = 56; // Integer | 删除对象前的持续时间（秒）。值必须是非负整数。值为零表示立即删除。如果此值为nil，则将使用指定类型的默认宽限期。如果未指定，则默认为每对象值。零表示立即删除。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.
    String labelSelector = "labelSelector_example"; // String | 一个选择器，用于根据返回对象的标签限制其列表。默认为一切。A selector to restrict the list of returned objects by their labels. Defaults to everything.
    Integer limit = 56; // Integer | limit是列表调用返回的最大响应数。如果存在更多项，服务器会将列表元数据上的“continue”字段设置为一个值，该值可用于同一初始查询，以检索下一组结果。如果所有请求的对象都被过滤掉，设置限制可能会返回少于请求数量的项目（最多为零个项目），客户端应该只使用continue字段来确定是否有更多结果可用。服务器可能会选择不支持limit参数，并将返回所有可用的结果。如果指定了limit且continue字段为空，则客户端可能会认为没有更多结果可用。如果watch为true，则不支持此字段。服务器保证在使用continue时返回的对象将与无限制地发出单个列表调用相同——也就是说，在发出第一个请求后创建、修改或删除的对象不会包含在任何后续的continue请求中。这有时被称为一致性快照，可以确保使用limit接收非常大结果的较小数据块的客户端可以确保看到所有可能的对象。如果在分块列表期间更新对象，则返回在计算第一个列表结果时存在的对象版本。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.
    Boolean orphanDependents = true; // Boolean | 已弃用：请使用PropagationPolicy，此字段将在1.7中弃用。从属对象应该是孤立的吗。如果为真/假，“孤立”终结器将被添加到对象的终结器列表中或从中删除。可以设置此字段或PropagationPolicy，但不能同时设置两者。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.
    String propagationPolicy = "propagationPolicy_example"; // 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.
    String resourceVersion = "resourceVersion_example"; // String | 当通过监视调用指定时，显示在资源的特定版本之后发生的更改。默认为历史开始时的更改。为列表指定时：-如果未设置，则根据仲裁读取标志从远程存储返回结果；-如果是0，那么我们只返回当前缓存中的内容，不保证；-如果设置为非零，则结果至少与给定值一样新鲜When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.
    Integer timeoutSeconds = 56; // Integer | 列表/监视呼叫超时。这会限制通话的持续时间，而不管通话是否处于活动状态。列表/监视呼叫超时。这会限制通话的持续时间，而不管通话是否处于活动状态。Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
    V1DeleteOptions body = new V1DeleteOptions(); // V1DeleteOptions | 
    try {
   
      V1Status result = apiInstance.deleteCollectionPriorityClass(pretty, _continue, dryRun, fieldSelector, gracePeriodSeconds, labelSelector, limit, orphanDependents, propagationPolicy, resourceVersion, timeoutSeconds, body);
      System.out.println(result);
    } catch (ApiException e) {
   
      System.err.println("Exception when calling SchedulingV1Api#deleteCollectionPriorityClass");
      System.err.println("Status code: " + e.getCode());
      System.err.println("Reason: " + e.getResponseBody());
      System.err.println("Response headers: " + e.getResponseHeaders());
      e.printStackTrace();
    }
  }
}

Parameters

Name	Type	Description	Notes
pretty	String	如果为“true”，则输出相当打印。If 'true', then the output is pretty printed.	[optional]
_continue	String	从服务器检索更多结果时，应设置“继续”选项。由于此值是服务器定义的，因此客户端只能使用具有相同查询参数（continue值除外）的上一个查询结果中的continue值，服务器可能会拒绝它无法识别的continue值。如果指定的continue值因过期（通常为5到15分钟）或服务器上的配置更改而不再有效，服务器将响应410 ResourceExpired错误和continue令牌。如果客户端需要一个一致的列表，它必须在不使用continue字段的情况下重新启动它们的列表。从另一台服务器发送的结果可能与前一台服务器发送的结果不一致，但从下一台服务器发送的结果可能与前一台服务器发送的结果不一致，只要他们的钥匙在“下一个钥匙”之后。watch为true时不支持此字段。客户端可以从服务器返回的最后一个resourceVersion值开始监视，并且不会错过任何修改。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”. 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.(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". 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.	[optional]
dryRun	String	如果存在，则表示不应保留修改。无效或无法识别的dryRun指令将导致错误响应，并且不会进一步处理请求。有效值为：-全部：将处理所有干运行阶段。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	[optional]
fieldSelector	String	一个选择器，用于按字段限制返回对象的列表。默认为一切。A selector to restrict the list of returned objects by their fields. Defaults to everything.	[optional]
gracePeriodSeconds	Integer	删除对象前的持续时间（秒）。值必须是非负整数。值为零表示立即删除。如果此值为nil，则将使用指定类型的默认宽限期。如果未指定，则默认为每对象值。零表示立即删除。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.	[optional]
labelSelector	String	一个选择器，用于根据返回对象的标签限制其列表。默认为一切。A selector to restrict the list of returned objects by their labels. Defaults to everything.	[optional]
limit	Integer	limit是列表调用返回的最大响应数。如果存在更多项目，服务器将设置&#x60；继续&#x60；字段的值，该值可用于同一初始查询以检索下一组结果。如果所有请求的对象都被过滤掉，设置限制可能会返回少于请求数量的项目（最多为零个项目），客户端应该只使用continue字段来确定是否有更多结果可用。服务器可能会选择不支持limit参数，并将返回所有可用的结果。如果指定了limit且continue字段为空，则客户端可能会认为没有更多结果可用。如果watch为true，则不支持此字段。服务器保证在使用continue时返回的对象将与无限制地发出单个列表调用相同——也就是说，在发出第一个请求后创建、修改或删除的对象不会包含在任何后续的continue请求中。这有时被称为一致性快照，可以确保使用limit接收非常大结果的较小数据块的客户端可以确保看到所有可能的对象。如果在分块列表期间更新对象，则返回在计算第一个列表结果时存在的对象版本。 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.	[optional]
orphanDependents	Boolean	已弃用：请使用PropagationPolicy，此字段将在1.7中弃用。从属对象应该是孤立的吗。如果为真/假，“孤立”终结器将被添加到对象的终结器列表中或从中删除。可以设置此字段或PropagationPolicy，但不能同时设置两者。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.	[optional]
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.	[optional]
resourceVersion	String	当通过监视调用指定时，显示在资源的特定版本之后发生的更改。默认为历史开始时的更改。为列表指定时：-如果未设置，则根据仲裁读取标志从远程存储返回结果；-如果是&#39；s 0，然后我们只返回当前缓存中的内容，不保证；-如果设置为非零，则结果至少与给定值一样新鲜。When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.	[optional]
timeoutSeconds	Integer	列表/监视呼叫超时。这会限制通话的持续时间，而不管通话是否处于活动状态。列表/监视呼叫超时。这会限制通话的持续时间，而不管通话是否处于活动状态。Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.	[optional]
body	V1DeleteOptions		[optional]

Return type

V1Status

Authorization

BearerToken

HTTP request headers

• Content-Type: Not defined
• Accept: application/json, application/yaml, application/vnd.kubernetes.protobuf

HTTP response details

Status code	Description	Response headers
200	OK	-
401	Unauthorized	-

deletePriorityClass

回到SchedulingV1Api目录

V1Status deletePriorityClass(name, pretty, dryRun, gracePeriodSeconds, orphanDependents, propagationPolicy, body)

delete a PriorityClass

Example

// Import classes:
import io.kubernetes.client.openapi.ApiClient;
import io.kubernetes.client.openapi.ApiException;
import io.kubernetes.client.openapi.Configuration;
import io.kubernetes.client.openapi.auth.*;
import io.kubernetes.client.openapi.models.*;
import io.kubernetes.client.openapi.apis.SchedulingV1Api;

public class Example {
   
  public static void main(String[] args) {
   
    ApiClient defaultClient = Configuration.getDefaultApiClient();
    defaultClient.setBasePath("http://localhost");
    
    // Configure API key authorization: BearerToken
    ApiKeyAuth BearerToken = (ApiKeyAuth) defaultClient.getAuthentication("BearerToken");
    BearerToken.setApiKey("YOUR API KEY");
    // Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
    //BearerToken.setApiKeyPrefix("Token");

    SchedulingV1Api apiInstance = new SchedulingV1Api(defaultClient);
    String name = "name_example"; // String | name of the PriorityClass
    String pretty = "pretty_example"; // String | 如果为“true”，则输出相当打印。If 'true', then the output is pretty printed.
    String dryRun = "dryRun_example"; // String | 如果存在，则表示不应保留修改。无效或无法识别的dryRun指令将导致错误响应，并且不会进一步处理请求。有效值为：-全部：将处理所有干运行阶段。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
    Integer gracePeriodSeconds = 56; // Integer | 删除对象前的持续时间（秒）。值必须是非负整数。值为零表示立即删除。如果此值为nil，则将使用指定类型的默认宽限期。如果未指定，则默认为每对象值。零表示立即删除。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.
    Boolean orphanDependents = true; // Boolean | 已弃用：请使用PropagationPolicy，此字段将在1.7中弃用。从属对象应该是孤立的吗。如果为真/假，“孤立”终结器将被添加到对象的终结器列表中或从中删除。可以设置此字段或PropagationPolicy，但不能同时设置两者。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.
    String propagationPolicy = "propagationPolicy_example"; // 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.
    V1DeleteOptions body = new</