Skip to content

chore: bump k8s libs to v1.33 #3116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamjensenbot merged 1 commit into from
Nov 21, 2025
Merged

chore: bump k8s libs to v1.33 #3116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion cmd/virtual-kubelet/root/http.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,6 @@ func newCertificateRetriever(kubeClient kubernetes.Interface, signer, nodeName s
certificates.UsageServerAuth,
},
CertificateStore: certificateStore,
Logf: klog.V(2).Infof,
})
if err != nil {
return nil, fmt.Errorf("failed to initialize server certificate manager: %w", err)
Expand Down
13 changes: 6 additions & 7 deletions deployments/liqo/charts/liqo-crds/crds/ipam.liqo.io_ips.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -451,13 +451,12 @@ spec:
type: object
trafficDistribution:
description: |-
TrafficDistribution offers a way to express preferences for how traffic is
distributed to Service endpoints. Implementations can use this field as a
hint, but are not required to guarantee strict adherence. If the field is
not set, the implementation will apply its default routing strategy. If set
to "PreferClose", implementations should prioritize endpoints that are
topologically close (e.g., same zone).
This is a beta field and requires enabling ServiceTrafficDistribution feature.
TrafficDistribution offers a way to express preferences for how traffic
is distributed to Service endpoints. Implementations can use this field
as a hint, but are not required to guarantee strict adherence. If the
field is not set, the implementation will apply its default routing
strategy. If set to "PreferClose", implementations should prioritize
endpoints that are in the same zone.
type: string
type:
description: |-
Expand Down
63 changes: 35 additions & 28 deletions deployments/liqo/charts/liqo-crds/crds/networking.liqo.io_wggatewayclients.yaml
View file
Open in desktop

Large diffs are not rendered by default.

76 changes: 41 additions & 35 deletions deployments/liqo/charts/liqo-crds/crds/networking.liqo.io_wggatewayservers.yaml
View file
Open in desktop

Large diffs are not rendered by default.

62 changes: 40 additions & 22 deletions deployments/liqo/charts/liqo-crds/crds/offloading.liqo.io_shadowendpointslices.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,12 +61,12 @@ spec:
properties:
addresses:
description: |-
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.
items:
type: string
type: array
Expand All @@ -77,26 +77,25 @@ spec:
properties:
ready:
description: |-
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.
type: boolean
serving:
description: |-
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".
type: boolean
terminating:
description: |-
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".
type: boolean
type: object
deprecatedTopology:
Expand All @@ -115,10 +114,28 @@ spec:
hints contains information associated with how an endpoint should be
consumed.
properties:
forNodes:
description: |-
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.
items:
description: ForNode provides information about which
nodes should consume this endpoint.
properties:
name:
description: name represents the name of the node.
type: string
required:
- name
type: object
type: array
x-kubernetes-list-type: atomic
forZones:
description: |-
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.
items:
description: ForZone provides information about which
zones should consume this endpoint.
Expand Down Expand Up @@ -233,8 +250,9 @@ spec:
port:
description: |-
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.
format: int32
type: integer
protocol:
Expand Down
Loading