Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 58 of 58 for Statuses (0.31 sec)

  1. CHANGELOG/CHANGELOG-1.27.md

    - Give terminal phase correctly to all pods that will not be restarted. 
    
      In particular, assign Failed phase to pods which are deleted while pending. Also, assign a terminal 
      phase (Succeeded or Failed, depending on the exit statuses of the pod containers) to pods which
      are deleted while running.
      
      This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions 
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Tue Jun 11 23:01:06 UTC 2024
    - 455.3K bytes
    - Viewed (0)
  2. pkg/controller/statefulset/stateful_set_utils.go

    }
    
    // completeRollingUpdate completes a rolling update when all of set's replica Pods have been updated
    // to the updateRevision. status's currentRevision is set to updateRevision and its' updateRevision
    // is set to the empty string. status's currentReplicas is set to updateReplicas and its updateReplicas
    // are set to 0.
    func completeRollingUpdate(set *apps.StatefulSet, status *apps.StatefulSetStatus) {
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 05 19:06:41 UTC 2024
    - 26.7K bytes
    - Viewed (0)
  3. pkg/kubelet/volumemanager/reconciler/reconstruct_common.go

    		outerVolumeSpecName: volume.volumeSpecName,
    		pod:                 pod,
    		deviceMounter:       deviceMounter,
    		volumeGidValue:      "",
    		// devicePath is updated during updateStates() by checking node status's VolumesAttached data.
    		// TODO: get device path directly from the volume mount path.
    		devicePath:          "",
    		mounter:             volumeMounter,
    		blockVolumeMapper:   volumeMapper,
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Tue Apr 09 07:34:33 UTC 2024
    - 14.1K bytes
    - Viewed (0)
  4. tests/integration/pilot/testdata/gateway-api-crd.yaml

                            See the GRPCBackendRef definition for the rules about what makes a single
                            GRPCBackendRef invalid.
    
    
                            When a GRPCBackendRef is invalid, `UNAVAILABLE` statuses MUST be returned for
                            requests that would have otherwise been routed to an invalid backend. If
                            multiple backends are specified, and some are invalid, the proportion of
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Thu May 09 02:01:51 UTC 2024
    - 912.2K bytes
    - Viewed (0)
  5. api/openapi-spec/v3/apis__apps__v1_openapi.json

    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 810.7K bytes
    - Viewed (0)
  6. api/openapi-spec/v3/api__v1_openapi.json

    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 1.8M bytes
    - Viewed (0)
  7. pkg/generated/openapi/zz_generated.openapi.go

    being modified.\n - Infeasible\n  Infeasible indicates that the request has been rejected as invalid by the CSI driver. To\n\t  resolve the error, a valid VolumeAttributesClass needs to be specified.\nNote: New statuses can be added in the future. Consumers should check for unknown statuses and fail appropriately.\n\nPossible enum values:\n - `\"InProgress\"` InProgress indicates that the volume is being modified\n - `\"Infeasible\"` Infeasible indicates that the request has been rejected as invalid...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 05 18:37:07 UTC 2024
    - 3M bytes
    - Viewed (0)
  8. api/openapi-spec/swagger.json

    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 05 18:37:07 UTC 2024
    - 3.1M bytes
    - Viewed (0)
Back to top