Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for reply (0.19 sec)

  1. common-protos/k8s.io/api/events/v1/generated.proto

    // Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system.
    // Events have a limited retention time and triggers and messages may evolve
    // with time.  Event consumers should not rely on the timing of an event
    // with a given Reason reflecting a consistent underlying trigger, or the
    // continued existence of events with that Reason.  Events should be
    // treated as informative, best-effort, supplemental data.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 5.5K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/admission/v1beta1/generated.proto

      // +optional
      optional string requestSubResource = 15;
    
      // Name is the name of the object as presented in the request.  On a CREATE operation, the client may omit name and
      // rely on the server to generate the name.  If that is the case, this field will contain an empty string.
      // +optional
      optional string name = 5;
    
      // Namespace is the namespace associated with the request (if any).
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 8.1K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/core/v1/generated.proto

    }
    
    // Event is a report of an event somewhere in the cluster.  Events
    // have a limited retention time and triggers and messages may evolve
    // with time.  Event consumers should not rely on the timing of an event
    // with a given Reason reflecting a consistent underlying trigger, or the
    // continued existence of events with that Reason.  Events should be
    // treated as informative, best-effort, supplemental data.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 255.8K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/admission/v1/generated.proto

      // +optional
      optional string requestSubResource = 15;
    
      // Name is the name of the object as presented in the request.  On a CREATE operation, the client may omit name and
      // rely on the server to generate the name.  If that is the case, this field will contain an empty string.
      // +optional
      optional string name = 5;
    
      // Namespace is the namespace associated with the request (if any).
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 8.1K bytes
    - Viewed (0)
  5. architecture/networking/pilot.md

    The `Proxy` as an input parameter is important, and a major distinction from some other XDS implementations. We are not able to statically translate inputs to XDS without per-client information. For example, we rely on the client's labels to determine the set of policies applied. While this is necessary to implement Istio's APIs, it does limit performance substantially.
    
    #### Caching
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 19.1K bytes
    - Viewed (0)
  6. common-protos/k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto

      // serialization.
      // Servers older than v1.15 do not set this field.
      // The intended use of the remainingItemCount is *estimating* the size of a collection. Clients
      // should not rely on the remainingItemCount to be set or to be exact.
      // +optional
      optional int64 remainingItemCount = 4;
    }
    
    // ListOptions is the query options to a standard REST list call.
    message ListOptions {
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 53.3K bytes
    - Viewed (0)
  7. common-protos/k8s.io/api/events/v1beta1/generated.proto

    // Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system.
    // Events have a limited retention time and triggers and messages may evolve
    // with time.  Event consumers should not rely on the timing of an event
    // with a given Reason reflecting a consistent underlying trigger, or the
    // continued existence of events with that Reason.  Events should be
    // treated as informative, best-effort, supplemental data.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 5.2K bytes
    - Viewed (0)
Back to top