Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface DeleteNodePoolRequest

example

Click here to see how to use DeleteNodePoolRequest.

Hierarchy

Properties

Optional ifMatch

ifMatch: undefined | string

For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code if-match} parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.

Optional isForceDeletionAfterOverrideGraceDuration

isForceDeletionAfterOverrideGraceDuration: undefined | false | true

If the underlying compute instance should be deleted if you cannot evict all the pods in grace period

nodePoolId

nodePoolId: string

The OCID of the node pool.

Optional opcRequestId

opcRequestId: undefined | string

Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.

Optional overrideEvictionGraceDuration

overrideEvictionGraceDuration: undefined | string

Duration after which OKE will give up eviction of the pods on the node. PT0M will indicate you want to delete the node without cordon and drain. Default PT60M, Min PT0M, Max: PT60M. Format ISO 8601 e.g PT30M

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made