Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for purge (0.13 sec)

  1. operator/cmd/mesh/operator-remove.go

    	if err != nil {
    		l.LogAndFatal(err)
    	}
    
    	// If the user is performing purge but also specified a revision, we should warn
    	// that the purge will still remove all resources
    	if orArgs.purge && orArgs.revision != "" {
    		orArgs.revision = ""
    		l.LogAndPrint("Purge remove will remove all Istio operator controller, ignoring the specified revision\n")
    	}
    
    	var installed bool
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Mar 15 01:18:49 GMT 2024
    - 5.4K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/apps/v1beta2/generated.proto

      // reason (Ready transitions to false, is evicted, or is drained) an updated
      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 36.4K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/apps/v1/generated.proto

      // reason (Ready transitions to false, is evicted, or is drained) an updated
      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 34.5K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/extensions/v1beta1/generated.proto

      // reason (Ready transitions to false, is evicted, or is drained) an updated
      // pod is immediatedly created on that node without considering surge limits.
      // Allowing surge implies the possibility that the resources consumed by the
      // daemonset on any given node can double if the readiness check fails, and
      // so resource intensive daemonsets should take into account that they may
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 45.6K bytes
    - Viewed (0)
Back to top