mirror of
https://github.com/ceph/ceph-csi.git
synced 2025-06-14 02:43:36 +00:00
rebase: update replaced k8s.io modules to v0.33.0
Signed-off-by: Niels de Vos <ndevos@ibm.com>
This commit is contained in:
committed by
mergify[bot]
parent
dd77e72800
commit
107407b44b
78
e2e/vendor/k8s.io/api/discovery/v1/generated.proto
generated
vendored
78
e2e/vendor/k8s.io/api/discovery/v1/generated.proto
generated
vendored
@ -31,12 +31,12 @@ option go_package = "k8s.io/api/discovery/v1";
|
||||
|
||||
// Endpoint represents a single logical "backend" implementing a service.
|
||||
message Endpoint {
|
||||
// addresses of this endpoint. The contents of this field are interpreted
|
||||
// according to the corresponding EndpointSlice addressType field. Consumers
|
||||
// must handle different types of addresses in the context of their own
|
||||
// capabilities. This must contain at least one address but no more than
|
||||
// 100. These are all assumed to be fungible and clients may choose to only
|
||||
// use the first element. Refer to: https://issue.k8s.io/106267
|
||||
// addresses of this endpoint. For EndpointSlices of addressType "IPv4" or "IPv6",
|
||||
// the values are IP addresses in canonical form. The syntax and semantics of
|
||||
// other addressType values are not defined. This must contain at least one
|
||||
// address but no more than 100. EndpointSlices generated by the EndpointSlice
|
||||
// controller will always have exactly 1 address. No semantics are defined for
|
||||
// additional addresses beyond the first, and kube-proxy does not look at them.
|
||||
// +listType=set
|
||||
repeated string addresses = 1;
|
||||
|
||||
@ -82,36 +82,42 @@ message Endpoint {
|
||||
|
||||
// EndpointConditions represents the current condition of an endpoint.
|
||||
message EndpointConditions {
|
||||
// ready indicates that this endpoint is prepared to receive traffic,
|
||||
// ready indicates that this endpoint is ready to receive traffic,
|
||||
// according to whatever system is managing the endpoint. A nil value
|
||||
// indicates an unknown state. In most cases consumers should interpret this
|
||||
// unknown state as ready. For compatibility reasons, ready should never be
|
||||
// "true" for terminating endpoints, except when the normal readiness
|
||||
// behavior is being explicitly overridden, for example when the associated
|
||||
// Service has set the publishNotReadyAddresses flag.
|
||||
// should be interpreted as "true". In general, an endpoint should be
|
||||
// marked ready if it is serving and not terminating, though this can
|
||||
// be overridden in some cases, such as when the associated Service has
|
||||
// set the publishNotReadyAddresses flag.
|
||||
// +optional
|
||||
optional bool ready = 1;
|
||||
|
||||
// serving is identical to ready except that it is set regardless of the
|
||||
// terminating state of endpoints. This condition should be set to true for
|
||||
// a ready endpoint that is terminating. If nil, consumers should defer to
|
||||
// the ready condition.
|
||||
// serving indicates that this endpoint is able to receive traffic,
|
||||
// according to whatever system is managing the endpoint. For endpoints
|
||||
// backed by pods, the EndpointSlice controller will mark the endpoint
|
||||
// as serving if the pod's Ready condition is True. A nil value should be
|
||||
// interpreted as "true".
|
||||
// +optional
|
||||
optional bool serving = 2;
|
||||
|
||||
// terminating indicates that this endpoint is terminating. A nil value
|
||||
// indicates an unknown state. Consumers should interpret this unknown state
|
||||
// to mean that the endpoint is not terminating.
|
||||
// should be interpreted as "false".
|
||||
// +optional
|
||||
optional bool terminating = 3;
|
||||
}
|
||||
|
||||
// EndpointHints provides hints describing how an endpoint should be consumed.
|
||||
message EndpointHints {
|
||||
// forZones indicates the zone(s) this endpoint should be consumed by to
|
||||
// enable topology aware routing.
|
||||
// forZones indicates the zone(s) this endpoint should be consumed by when
|
||||
// using topology aware routing. May contain a maximum of 8 entries.
|
||||
// +listType=atomic
|
||||
repeated ForZone forZones = 1;
|
||||
|
||||
// forNodes indicates the node(s) this endpoint should be consumed by when
|
||||
// using topology aware routing. May contain a maximum of 8 entries.
|
||||
// This is an Alpha feature and is only used when the PreferSameTrafficDistribution
|
||||
// feature gate is enabled.
|
||||
// +listType=atomic
|
||||
repeated ForNode forNodes = 2;
|
||||
}
|
||||
|
||||
// EndpointPort represents a Port used by an EndpointSlice
|
||||
@ -132,8 +138,9 @@ message EndpointPort {
|
||||
optional string protocol = 2;
|
||||
|
||||
// port represents the port number of the endpoint.
|
||||
// If this is not specified, ports are not restricted and must be
|
||||
// interpreted in the context of the specific consumer.
|
||||
// If the EndpointSlice is derived from a Kubernetes service, this must be set
|
||||
// to the service's target port. EndpointSlices used for other purposes may have
|
||||
// a nil port.
|
||||
optional int32 port = 3;
|
||||
|
||||
// The application protocol for this port.
|
||||
@ -155,9 +162,12 @@ message EndpointPort {
|
||||
optional string appProtocol = 4;
|
||||
}
|
||||
|
||||
// EndpointSlice represents a subset of the endpoints that implement a service.
|
||||
// For a given service there may be multiple EndpointSlice objects, selected by
|
||||
// labels, which must be joined to produce the full set of endpoints.
|
||||
// EndpointSlice represents a set of service endpoints. Most EndpointSlices are created by
|
||||
// the EndpointSlice controller to represent the Pods selected by Service objects. For a
|
||||
// given service there may be multiple EndpointSlice objects which must be joined to
|
||||
// produce the full set of endpoints; you can find all of the slices for a given service
|
||||
// by listing EndpointSlices in the service's namespace whose `kubernetes.io/service-name`
|
||||
// label contains the service's name.
|
||||
message EndpointSlice {
|
||||
// Standard object's metadata.
|
||||
// +optional
|
||||
@ -169,7 +179,10 @@ message EndpointSlice {
|
||||
// supported:
|
||||
// * IPv4: Represents an IPv4 Address.
|
||||
// * IPv6: Represents an IPv6 Address.
|
||||
// * FQDN: Represents a Fully Qualified Domain Name.
|
||||
// * FQDN: Represents a Fully Qualified Domain Name. (Deprecated)
|
||||
// The EndpointSlice controller only generates, and kube-proxy only processes,
|
||||
// slices of addressType "IPv4" and "IPv6". No semantics are defined for
|
||||
// the "FQDN" type.
|
||||
optional string addressType = 4;
|
||||
|
||||
// endpoints is a list of unique endpoints in this slice. Each slice may
|
||||
@ -178,10 +191,11 @@ message EndpointSlice {
|
||||
repeated Endpoint endpoints = 2;
|
||||
|
||||
// ports specifies the list of network ports exposed by each endpoint in
|
||||
// this slice. Each port must have a unique name. When ports is empty, it
|
||||
// indicates that there are no defined ports. When a port is defined with a
|
||||
// nil port value, it indicates "all ports". Each slice may include a
|
||||
// this slice. Each port must have a unique name. Each slice may include a
|
||||
// maximum of 100 ports.
|
||||
// Services always have at least 1 port, so EndpointSlices generated by the
|
||||
// EndpointSlice controller will likewise always have at least 1 port.
|
||||
// EndpointSlices used for other purposes may have an empty ports list.
|
||||
// +optional
|
||||
// +listType=atomic
|
||||
repeated EndpointPort ports = 3;
|
||||
@ -197,6 +211,12 @@ message EndpointSliceList {
|
||||
repeated EndpointSlice items = 2;
|
||||
}
|
||||
|
||||
// ForNode provides information about which nodes should consume this endpoint.
|
||||
message ForNode {
|
||||
// name represents the name of the node.
|
||||
optional string name = 1;
|
||||
}
|
||||
|
||||
// ForZone provides information about which zones should consume this endpoint.
|
||||
message ForZone {
|
||||
// name represents the name of the zone.
|
||||
|
Reference in New Issue
Block a user