# io.k8s.api.lifecycle.v1alpha1.TargetResponder

From **Kubernetes**.

TargetResponder allows you to specify the responder reacting to the Eviction. Responders should observe and communicate through the Eviction API (see .state) to help with the graceful eviction of a target (e.g. termination of a pod).

- Type: `object`

## Properties

### `name`

- Required: true
- Type: `string`

name allows you to identify the responder reacting to the Eviction.

It must be a valid domain-prefixed key (such as "acme.io/foo"). This field must be unique for each responder. This field is required.

### `priority`

- Required: true
- Type: `integer`
- Format: `int32`

priority for this responder. Higher priorities are selected first by the evictionrequest-controller. If there are responders with the same priority, the responder whose domain name comes first in the alphabetical higher domain order, will be picked. This means that the top domain labels are compared alphabetically first, followed by the lower domain labels. The key is compared last.

The responder that is the managing controller of the pod should set the value of this field to 10000 to allow both for preemption or fallback registration by other responders.

The minimum value is 0 and the maximum value is 100000. The interval 0-999 is reserved for responders with *.k8s.io suffix. This field is required and immutable.

### `state`

- Required: true
- Type: `string`

state specifies a state that is assigned by the evictionrequest-controller. Responders should observe this state in order to navigate their lifecycle. - Inactive means that the responder should not yet process this eviction request. - Active means that the responder is either running or expected to start soon.
  Also, startTime has been set in the ResponderStatus by the evictionrequest-controller.

  An active responder should currently interact with the eviction process by updating
  .status.responders, where .name is the active responder name. ResponderStatus fields
  should be periodically updated to indicate the progress or completion of the eviction process.
  If .status.responders[].heartbeatTime field is not updated within the heartbeat deadline defined
  by the Eviction API (currently 20 minutes), the eviction is passed over to the next responder
	 with a lower priority. Only one responder can be active at a time.
- Interrupted means that the responder has failed to start or failed to update
  heartbeatTime in ResponderStatus in a timely manner.
- Canceled means that the responder has been canceled. In other words, there	is no
  EvictionRequest with the same target and Eviction intent in .spec.intent.
- Completed means that the responder has successfully completed and set completionTime
  in ResponderStatus.

Please refer to the ResponderStatus in .status.responders for more details on each responder.

## JSON Schema

```json
{"description":"TargetResponder allows you to specify the responder reacting to the Eviction. Responders should observe and communicate through the Eviction API (see .state) to help with the graceful eviction of a target (e.g. termination of a pod).","properties":{"name":{"default":"","description":"name allows you to identify the responder reacting to the Eviction.\n\nIt must be a valid domain-prefixed key (such as \"acme.io/foo\"). This field must be unique for each responder. This field is required.","type":"string"},"priority":{"description":"priority for this responder. Higher priorities are selected first by the evictionrequest-controller. If there are responders with the same priority, the responder whose domain name comes first in the alphabetical higher domain order, will be picked. This means that the top domain labels are compared alphabetically first, followed by the lower domain labels. The key is compared last.\n\nThe responder that is the managing controller of the pod should set the value of this field to 10000 to allow both for preemption or fallback registration by other responders.\n\nThe minimum value is 0 and the maximum value is 100000. The interval 0-999 is reserved for responders with *.k8s.io suffix. This field is required and immutable.","format":"int32","type":"integer"},"state":{"default":"","description":"state specifies a state that is assigned by the evictionrequest-controller. Responders should observe this state in order to navigate their lifecycle. - Inactive means that the responder should not yet process this eviction request. - Active means that the responder is either running or expected to start soon.\n  Also, startTime has been set in the ResponderStatus by the evictionrequest-controller.\n\n  An active responder should currently interact with the eviction process by updating\n  .status.responders, where .name is the active responder name. ResponderStatus fields\n  should be periodically updated to indicate the progress or completion of the eviction process.\n  If .status.responders[].heartbeatTime field is not updated within the heartbeat deadline defined\n  by the Eviction API (currently 20 minutes), the eviction is passed over to the next responder\n\t with a lower priority. Only one responder can be active at a time.\n- Interrupted means that the responder has failed to start or failed to update\n  heartbeatTime in ResponderStatus in a timely manner.\n- Canceled means that the responder has been canceled. In other words, there\tis no\n  EvictionRequest with the same target and Eviction intent in .spec.intent.\n- Completed means that the responder has successfully completed and set completionTime\n  in ResponderStatus.\n\nPlease refer to the ResponderStatus in .status.responders for more details on each responder.","type":"string"}},"required":["name","priority","state"],"type":"object","x-kubernetes-map-type":"atomic"}
```