Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for disrupted (0.07 sec)

  1. common-protos/k8s.io/api/policy/v1beta1/generated.proto

      // but not yet healthy can be evicted only if the guarded application is not
      // disrupted (status.currentHealthy is at least equal to status.desiredHealthy).
      // Healthy pods will be subject to the PDB for eviction.
      //
      // AlwaysAllow policy means that all running pods (status.phase="Running"),
      // but not yet healthy are considered disrupted and can be evicted regardless
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Mar 11 18:43:24 UTC 2024
    - 19.6K bytes
    - Viewed (0)
  2. istioctl/pkg/tag/tag.go

    		Use:   "remove <revision-tag>",
    		Short: "Remove Istio control plane revision tag",
    		Long: `Remove Istio control plane revision tag.
    
    Removing a revision tag should be done with care. Removing a revision tag will disrupt sidecar injection in namespaces
    that reference the tag in an "istio.io/rev" label. Verify that there are no remaining namespaces referencing a
    revision tag before removing using the "istioctl tag list" command.
    `,
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Mon Jul 22 15:40:30 UTC 2024
    - 16.5K bytes
    - Viewed (0)
  3. CHANGELOG/CHANGELOG-1.2.md

    DaemonSet objects you created in 1.1 won’t work with in the 1.2 release.
         * Before upgrading to 1.2, <strong>delete all DaemonSet alpha-version resources</strong>. If you do not want to disrupt the pods, use kubectl delete daemonset <name>
    --cascade=false. Then create DaemonSet Beta resources after upgrading to 1.2.
         * Client (kubectl) and server versions must match (both 1.1 or both 1.2) for any
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Fri Dec 04 06:36:19 UTC 2020
    - 41.4K bytes
    - Viewed (0)
Back to top