Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 20 for opacify (0.16 sec)

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

      // are specific to the node & CRI configuration.  It is assumed that all
      // handlers are available on every node, and handlers of the same name are
      // equivalent on every node.
      // For example, a handler called "runc" might specify that the runc OCI
      // runtime (using native Linux containers) will be used to run the containers
      // in a pod.
      // The handler must be lowercase, conform to the DNS Label (RFC 1123) requirements,
      // and is immutable.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 4.4K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/authorization/v1beta1/generated.proto

      // NonResourceAttributes describes information for a non-resource access request
      // +optional
      optional NonResourceAttributes nonResourceAttributes = 2;
    
      // User is the user you're testing for.
      // If you specify "User" but not "Group", then is it interpreted as "What if User were not a member of any groups
      // +optional
      optional string user = 3;
    
      // Groups is the groups you're testing for.
      // +optional
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 11.9K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/networking/v1/generated.proto

      // (whether or not they contain an ingress section) are assumed to affect ingress.
      // If you want to write an egress-only policy, you must explicitly specify policyTypes [ "Egress" ].
      // Likewise, if you want to write a policy that specifies that no egress is allowed,
      // you must specify a policyTypes value that include "Egress" (since such a policy would not include
      // an egress section and would otherwise default to just [ "Ingress" ]).
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 25.2K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/flowcontrol/v1beta2/generated.proto

    // at least one member of verbs matches the request, (b) at least one
    // member of apiGroups matches the request, (c) at least one member of
    // resources matches the request, and (d) either (d1) the request does
    // not specify a namespace (i.e., `Namespace==""`) and clusterScope is
    // true or (d2) the request specifies a namespace and least one member
    // of namespaces matches the request's namespace.
    message ResourcePolicyRule {
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 19.4K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/flowcontrol/v1alpha1/generated.proto

    // at least one member of verbs matches the request, (b) at least one
    // member of apiGroups matches the request, (c) at least one member of
    // resources matches the request, and (d) either (d1) the request does
    // not specify a namespace (i.e., `Namespace==""`) and clusterScope is
    // true or (d2) the request specifies a namespace and least one member
    // of namespaces matches the request's namespace.
    message ResourcePolicyRule {
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 19.4K bytes
    - Viewed (0)
  6. common-protos/k8s.io/api/admissionregistration/v1/generated.proto

      // SideEffects states whether this webhook has side effects.
      // Acceptable values are: None, NoneOnDryRun (webhooks created via v1beta1 may also specify Some or Unknown).
      // Webhooks with side effects MUST implement a reconciliation system, since a request may be
      // rejected by a future step in the admission chain and the side effects therefore need to be undone.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24.4K bytes
    - Viewed (0)
  7. operator/README.md

    --set flag. For example, to select the minimal profile:
    
    ```yaml
    # minimal.yaml
    
    apiVersion: install.istio.io/v1alpha1
    kind: IstioOperator
    spec:
      profile: minimal
    ```
    
    If you don't specify a configuration profile, Istio is installed using the `default` configuration profile. All
    profiles listed in istio.io are available by default, or `profile:` can point to a local file path to reference a custom
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sun Sep 17 08:27:52 GMT 2023
    - 17.5K bytes
    - Viewed (0)
  8. common-protos/k8s.io/api/batch/v1/generated.proto

      // resumed again.
      // +optional
      optional int64 activeDeadlineSeconds = 3;
    
      // Specifies the policy of handling failed pods. In particular, it allows to
      // specify the set of actions and conditions which need to be
      // satisfied to take the associated action.
      // If empty, the default behaviour applies - the counter of failed pods,
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.1K bytes
    - Viewed (0)
  9. common-protos/k8s.io/api/networking/v1beta1/generated.proto

      // is optional to allow the loadbalancer controller or defaulting logic to
      // specify a global default.
      // +optional
      optional IngressBackend backend = 1;
    
      // tls represents the TLS configuration. Currently the Ingress only supports a
      // single TLS port, 443. If multiple members of this list specify different hosts,
      // they will be multiplexed on the same port according to the hostname specified
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 14.9K bytes
    - Viewed (0)
  10. common-protos/k8s.io/api/node/v1/generated.proto

      // are specific to the node & CRI configuration.  It is assumed that all
      // handlers are available on every node, and handlers of the same name are
      // equivalent on every node.
      // For example, a handler called "runc" might specify that the runc OCI
      // runtime (using native Linux containers) will be used to run the containers
      // in a pod.
      // The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements,
      // and is immutable.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 4.4K bytes
    - Viewed (0)
Back to top