Skip to content

Commit 00210b8

Browse files
fra98fra98
committed
chore: bump k8s libs to v1.33
1 parent de96cea commit 00210b8

File tree

9 files changed

+298
-248
lines changed

9 files changed

+298
-248
lines changed

‎cmd/virtual-kubelet/root/http.go‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,6 @@ func newCertificateRetriever(kubeClient kubernetes.Interface, signer, nodeName s
189189
certificates.UsageServerAuth,
190190
},
191191
CertificateStore: certificateStore,
192-
Logf: klog.V(2).Infof,
193192
})
194193
if err != nil {
195194
return nil, fmt.Errorf("failed to initialize server certificate manager: %w", err)

‎deployments/liqo/charts/liqo-crds/crds/ipam.liqo.io_ips.yaml‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -451,13 +451,12 @@ spec:
451451
type: object
452452
trafficDistribution:
453453
description: |-
454-
TrafficDistribution offers a way to express preferences for how traffic is
455-
distributed to Service endpoints. Implementations can use this field as a
456-
hint, but are not required to guarantee strict adherence. If the field is
457-
not set, the implementation will apply its default routing strategy. If set
458-
to "PreferClose", implementations should prioritize endpoints that are
459-
topologically close (e.g., same zone).
460-
This is a beta field and requires enabling ServiceTrafficDistribution feature.
454+
TrafficDistribution offers a way to express preferences for how traffic
455+
is distributed to Service endpoints. Implementations can use this field
456+
as a hint, but are not required to guarantee strict adherence. If the
457+
field is not set, the implementation will apply its default routing
458+
strategy. If set to "PreferClose", implementations should prioritize
459+
endpoints that are in the same zone.
461460
type: string
462461
type:
463462
description: |-

‎deployments/liqo/charts/liqo-crds/crds/networking.liqo.io_wggatewayclients.yaml‎

Lines changed: 35 additions & 28 deletions
Large diffs are not rendered by default.

‎deployments/liqo/charts/liqo-crds/crds/networking.liqo.io_wggatewayservers.yaml‎

Lines changed: 41 additions & 35 deletions
Large diffs are not rendered by default.

‎deployments/liqo/charts/liqo-crds/crds/offloading.liqo.io_shadowendpointslices.yaml‎

Lines changed: 40 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -61,12 +61,12 @@ spec:
6161
properties:
6262
addresses:
6363
description: |-
64-
addresses of this endpoint. The contents of this field are interpreted
65-
according to the corresponding EndpointSlice addressType field. Consumers
66-
must handle different types of addresses in the context of their own
67-
capabilities. This must contain at least one address but no more than
68-
100. These are all assumed to be fungible and clients may choose to only
69-
use the first element. Refer to: https://issue.k8s.io/106267
64+
addresses of this endpoint. For EndpointSlices of addressType "IPv4" or "IPv6",
65+
the values are IP addresses in canonical form. The syntax and semantics of
66+
other addressType values are not defined. This must contain at least one
67+
address but no more than 100. EndpointSlices generated by the EndpointSlice
68+
controller will always have exactly 1 address. No semantics are defined for
69+
additional addresses beyond the first, and kube-proxy does not look at them.
7070
items:
7171
type: string
7272
type: array
@@ -77,26 +77,25 @@ spec:
7777
properties:
7878
ready:
7979
description: |-
80-
ready indicates that this endpoint is prepared to receive traffic,
80+
ready indicates that this endpoint is ready to receive traffic,
8181
according to whatever system is managing the endpoint. A nil value
82-
indicates an unknown state. In most cases consumers should interpret this
83-
unknown state as ready. For compatibility reasons, ready should never be
84-
"true" for terminating endpoints, except when the normal readiness
85-
behavior is being explicitly overridden, for example when the associated
86-
Service has set the publishNotReadyAddresses flag.
82+
should be interpreted as "true". In general, an endpoint should be
83+
marked ready if it is serving and not terminating, though this can
84+
be overridden in some cases, such as when the associated Service has
85+
set the publishNotReadyAddresses flag.
8786
type: boolean
8887
serving:
8988
description: |-
90-
serving is identical to ready except that it is set regardless of the
91-
terminating state of endpoints. This condition should be set to true for
92-
a ready endpoint that is terminating. If nil, consumers should defer to
93-
the ready condition.
89+
serving indicates that this endpoint is able to receive traffic,
90+
according to whatever system is managing the endpoint. For endpoints
91+
backed by pods, the EndpointSlice controller will mark the endpoint
92+
as serving if the pod's Ready condition is True. A nil value should be
93+
interpreted as "true".
9494
type: boolean
9595
terminating:
9696
description: |-
9797
terminating indicates that this endpoint is terminating. A nil value
98-
indicates an unknown state. Consumers should interpret this unknown state
99-
to mean that the endpoint is not terminating.
98+
should be interpreted as "false".
10099
type: boolean
101100
type: object
102101
deprecatedTopology:
@@ -115,10 +114,28 @@ spec:
115114
hints contains information associated with how an endpoint should be
116115
consumed.
117116
properties:
117+
forNodes:
118+
description: |-
119+
forNodes indicates the node(s) this endpoint should be consumed by when
120+
using topology aware routing. May contain a maximum of 8 entries.
121+
This is an Alpha feature and is only used when the PreferSameTrafficDistribution
122+
feature gate is enabled.
123+
items:
124+
description: ForNode provides information about which
125+
nodes should consume this endpoint.
126+
properties:
127+
name:
128+
description: name represents the name of the node.
129+
type: string
130+
required:
131+
- name
132+
type: object
133+
type: array
134+
x-kubernetes-list-type: atomic
118135
forZones:
119136
description: |-
120-
forZones indicates the zone(s) this endpoint should be consumed by to
121-
enable topology aware routing.
137+
forZones indicates the zone(s) this endpoint should be consumed by when
138+
using topology aware routing. May contain a maximum of 8 entries.
122139
items:
123140
description: ForZone provides information about which
124141
zones should consume this endpoint.
@@ -233,8 +250,9 @@ spec:
233250
port:
234251
description: |-
235252
port represents the port number of the endpoint.
236-
If this is not specified, ports are not restricted and must be
237-
interpreted in the context of the specific consumer.
253+
If the EndpointSlice is derived from a Kubernetes service, this must be set
254+
to the service's target port. EndpointSlices used for other purposes may have
255+
a nil port.
238256
format: int32
239257
type: integer
240258
protocol:

0 commit comments

Comments
 (0)