{
			Action: batch.PodFailurePolicyActionIgnore,
			OnExitCodes: &batch.PodFailurePolicyOnExitCodesRequirement{
				Operator: batch.PodFailurePolicyOnExitCodesOpIn,
				Values:   []int32{1, 2, 3},
			},
		},
		{
			Action: batch.PodFailurePolicyActionFailJob,
			OnExitCodes: &batch.PodFailurePolicyOnExitCodesRequirement{
				Operator: batch.PodFailurePolicyOnExitCodesOpIn,

	Action PodFailurePolicyAction `json:"action" protobuf:"bytes,1,req,name=action"`

	// Represents the requirement on the container exit codes.
	// +optional
	OnExitCodes *PodFailurePolicyOnExitCodesRequirement `json:"onExitCodes" protobuf:"bytes,2,opt,name=onExitCodes"`

	// Represents the requirement on the pod conditions. The requirement is represented
	// as a list of pod condition patterns. The requirement is satisfied if at

  completions: 2
  managedBy: managedByValue
  manualSelector: true
  maxFailedIndexes: 13
  parallelism: 1
  podFailurePolicy:
    rules:
    - action: actionValue
      onExitCodes:
        containerName: containerNameValue
        operator: operatorValue
        values:
        - 3
      onPodConditions:
      - status: statusValue
        type: typeValue

        "parallelism": 1,
        "completions": 2,
        "activeDeadlineSeconds": 3,
        "podFailurePolicy": {
          "rules": [
            {
              "action": "actionValue",
              "onExitCodes": {
                "containerName": "containerNameValue",
                "operator": "operatorValue",
                "values": [
                  3
                ]
              },

	return map_PodFailurePolicyOnPodConditionsPattern
}

var map_PodFailurePolicyRule = map[string]string{
	"":                "PodFailurePolicyRule describes how a pod failure is handled when the requirements are met. One of onExitCodes and onPodConditions, but not both, can be used in each rule.",

  // Defaults to True.
  optional string status = 2;
}

// PodFailurePolicyRule describes how a pod failure is handled when the requirements are met.
// One of onExitCodes and onPodConditions, but not both, can be used in each rule.
message PodFailurePolicyRule {
  // Specifies the action taken on a pod failure when the requirements are satisfied.
  // Possible values are:
  //

      completions: 2
      managedBy: managedByValue
      manualSelector: true
      maxFailedIndexes: 13
      parallelism: 1
      podFailurePolicy:
        rules:
        - action: actionValue
          onExitCodes:
            containerName: containerNameValue
            operator: operatorValue
            values:
            - 3
          onPodConditions:
          - status: statusValue
            type: typeValue

    ]
  },
  "spec": {
    "parallelism": 1,
    "completions": 2,
    "activeDeadlineSeconds": 3,
    "podFailurePolicy": {
      "rules": [
        {
          "action": "actionValue",
          "onExitCodes": {
            "containerName": "containerNameValue",
            "operator": "operatorValue",
            "values": [
              3
            ]
          },
          "onPodConditions": [
            {

      completions: 2
      managedBy: managedByValue
      manualSelector: true
      maxFailedIndexes: 13
      parallelism: 1
      podFailurePolicy:
        rules:
        - action: actionValue
          onExitCodes:
            containerName: containerNameValue
            operator: operatorValue
            values:
            - 3
          onPodConditions:
          - status: statusValue
            type: typeValue

        "parallelism": 1,
        "completions": 2,
        "activeDeadlineSeconds": 3,
        "podFailurePolicy": {
          "rules": [
            {
              "action": "actionValue",
              "onExitCodes": {
                "containerName": "containerNameValue",
                "operator": "operatorValue",
                "values": [
                  3
                ]
              },