Commit Graph

129475 Commits

Author SHA1 Message Date
Kubernetes Release Robot
8adc0f041b Release commit for Kubernetes v1.33.1 2025-05-15 08:19:07 +00:00
Jan Chaloupka
f240b3abf5 SchedulerPreemption [Serial] validates various priority Pods preempt expectedly with the async preemption: replace finalizers with preStop hook and TerminationGracePeriodSeconds
Finalizers do not work as expected when an informer with a field
selector is used. Any time a pod changing its state gets excluded by the
field selector a synthetic delete event is issues even though the pod
with a finalizer set is still present. Thus, making the scheduler
schedule the high and medium priority pods before any of the low
priority pod finalizers is removed. Instead, rely on preStop hook and
TerminationGracePeriodSeconds to keep all low priority pods long enough
included by the field selector so all high priority pods can set their
.status.nominatedNodeName field.

Also, update the check for how many medium priority pods are expected to
be scheduled. Each node can accept 10 pods of the given extended
resources. Given there's 5 high priority created per node, there's
always 5 times number of nodes spots left for the medium priority pods.
2025-05-14 16:23:46 +02:00
Taha Farahani
cce99a8c73
Automated cherry pick of #130503: Unhandled panic crash on rollout_history printer.PrintObj (#131496)
* Change: Handling nil runtime.Object

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Return only if there is error in rollout_history

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Return the unknown revision error directly in rollout_history.go

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Remove unintended newline

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Using go idiomatic way for checking if historyInfo[o.Revision] exists

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Remove 'error:' from returned error message in rollout_history.go

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Check for printer.PrintObj returned err

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Add TestRolloutHistoryErrors test

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Simple typo fix on Complete() function description

Signed-off-by: Taha Farahani <tahacodes@proton.me>

* Change: Checking for error on o.Complete in TestRolloutHistoryErrors

Signed-off-by: Taha Farahani <tahacodes@proton.me>

---------

Signed-off-by: Taha Farahani <tahacodes@proton.me>
2025-05-14 00:26:54 -07:00
Kubernetes Prow Robot
00ebe85a29
Merge pull request #131636 from gnufied/automated-cherry-pick-of-#131568-upstream-release-1.33
Automated cherry pick of #131568: Disable size checking performed during resize
2025-05-13 23:13:02 -07:00
Kubernetes Prow Robot
5dc469cd4f
Merge pull request #131523 from carlory/automated-cherry-pick-of-#131495-release-1.33
Automated cherry pick of #131495: Handle unsupported node expansion for RWX volumes
2025-05-13 23:12:55 -07:00
Kubernetes Prow Robot
973b3812d6
Merge pull request #131437 from gnufied/automated-cherry-pick-of-#131418-upstream-release-1.33
Automated cherry pick of #131418: Check for newer fields when deciding expansion recovery feature status
2025-05-13 23:12:48 -07:00
Kubernetes Prow Robot
b5a1738ccc
Merge pull request #131708 from tigrato/automated-cherry-pick-of-#131702-upstream-release-1.33
Automated cherry pick of #131702: Panic in `NewYAMLToJSONDecoder`
2025-05-13 05:05:15 -07:00
Kubernetes Prow Robot
3a09aeb4fa
Merge pull request #131679 from mortent/automated-cherry-pick-of-#131662-upstream-release-1.33
Automated cherry pick of #131662: DRA: Fix failure to allocate large number of devices
2025-05-13 03:51:16 -07:00
Tiago Silva
a257be8299
fix: fixes a possible panic in NewYAMLToJSONDecoder
This PR fixes a possible panic caused by decoding a JSON document
followed by a YAML document that is shorter than the first json
document.

This can cause a panic because the stream already consumed the JSON
data. When we fallback to YAML reader, the YAML starts with a zero
offset while the stream consumed data is non-zero. This could lead into
consuming negative bytes because `d.yaml.InputOffset() -
d.stream.Consumed()` is negative which will cause a panic.

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
2025-05-09 23:37:42 +01:00
Morten Torkildsen
b59deb4914 DRA: Fix failure to allocate large number of devices 2025-05-08 20:03:36 +00:00
Prince Pereira
750d2c02f0 Update hnslib version in Windows KubeProxy. 2025-05-07 09:26:11 -07:00
Kubernetes Prow Robot
d3c7573e54
Merge pull request #131427 from princepereira/automated-cherry-pick-of-#131138-upstream-release-1.33
Automated cherry pick of #131138: Fix for HNS local endpoint was being deleted instead of the remote endpoint.
2025-05-06 17:59:13 -07:00
Hemant Kumar
c916dba607 Disable size check for xfs/ext3/ext4 filesystems before expansion 2025-05-06 16:54:51 -04:00
Hemant Kumar
c8f2295d68 Disable disk size checking when calling NeedsResize function 2025-05-06 16:54:51 -04:00
Nick Baker
ba345a494b fix(kubelet): acquire imageRecordsLock when removing image 2025-05-01 21:54:52 -07:00
carlory
3caaf056f1 Handle unsupported node expansion for RWX volumes
Co-authored-by: Hemant Kumar <gnufied@users.noreply.github.com>
Signed-off-by: carlory <baofa.fan@daocloud.io>
2025-04-29 10:43:44 +08:00
Hemant Kumar
c7eb93190c Mark NodeExpansion finsihed without featuregate check 2025-04-24 07:51:31 -04:00
Hemant Kumar
74035d7b77 Also change final status by removing featuregate check 2025-04-24 07:51:30 -04:00
Hemant Kumar
1a9d4fc468 Check for newer fields when deciding expansion recovery feature status 2025-04-24 07:51:30 -04:00
Prince Pereira
950bb3baf5 Fix for HNS local endpoint was being deleted instead of the remote endpoint. 2025-04-23 23:07:16 -07:00
Kubernetes Release Robot
5dc8b8dd26 Update CHANGELOG/CHANGELOG-1.33.md for v1.33.0 2025-04-23 13:24:20 +00:00
Kubernetes Release Robot
60a317eadf Release commit for Kubernetes v1.33.0 2025-04-23 13:00:13 +00:00
Kubernetes Release Robot
4190f9fd5d Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-23 07:38:22 +00:00
Kubernetes Release Robot
9ba7dcecc3 CHANGELOG: Update directory for v1.30.12 release 2025-04-23 02:22:45 +00:00
Kubernetes Release Robot
191c34eaba CHANGELOG: Update directory for v1.31.8 release 2025-04-23 02:22:38 +00:00
Kubernetes Release Robot
7bf818fb88 CHANGELOG: Update directory for v1.32.4 release 2025-04-22 16:21:58 +00:00
Kubernetes Release Robot
c0d2e6d81f Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-22 13:35:27 +00:00
Kubernetes Prow Robot
680ea07dbb
Merge pull request #131369 from ameukam/update-1242-master
[Go] Bump dependencies, images and versions used to Go 1.24.2 and distroless iptables
2025-04-21 09:19:06 -07:00
Kubernetes Release Robot
0019f96205 Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-20 01:32:51 +00:00
Kubernetes Prow Robot
0d9dccfc6b
Merge pull request #131382 from liggitt/watch-list-e2e
Correctly feature-gate WatchList e2e
2025-04-19 16:20:59 -07:00
Jordan Liggitt
95b926c93a
Feature-gate watchlist e2e 2025-04-19 17:18:31 -04:00
Kubernetes Release Robot
8d3db5cd56 Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-18 19:35:40 +00:00
Kubernetes Prow Robot
66931f07d9
Merge pull request #131359 from deads2k/disable
Stop exposing list-via-watch from the server
2025-04-18 07:55:08 -07:00
Arnaud Meukam
e467c9530b
[Go] Bump dependencies, images and versions used to Go 1.24.2 and distroless-iptables
Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
2025-04-18 15:49:48 +02:00
David Eads
660df229bf Stop exposing list-via-watch from the server
With StreamingCollectionEncodingToJSON and
StreamingCollectionEncodingToProtobuf, the WatchList must re-justify its
necessity.  To prevent an ecosystem from building around a feature that
may not be promoted, we will stop serving list-via-watch until
performance numbers can justify its inclusion.

This also stops the kube-controller-manager from using the
list-via-watch by default.  The fallback is a regular list, so during
the skew during an upgrade the "right" thing will happen and the new
StreamingCollectionEncoding will be used.
2025-04-18 09:21:23 -04:00
Kubernetes Release Robot
1064a98ad9 Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-16 19:33:06 +00:00
Kubernetes Prow Robot
b53b9fb557
Merge pull request #131015 from aojea/final_servicecidr
Add the missing Conformance Test for ServiceCIDR and IPAddress APIS
2025-04-16 11:05:08 -07:00
Kubernetes Release Robot
84d2d56308 Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-16 01:34:27 +00:00
Antonio Ojea
a8f6d77c8d ServiceCIDR and IPAddess Conformance
Change-Id: I6ee188cc8c163c312f8a8da9f1277d83e1ea634c
2025-04-15 21:47:43 +00:00
Kubernetes Release Robot
44c230bf5c CHANGELOG: Update directory for v1.33.0-rc.1 release 2025-04-15 17:20:14 +00:00
Kubernetes Release Robot
4939c17914 Update CHANGELOG/CHANGELOG-1.33.md for v1.33.0-rc.1 2025-04-15 17:20:14 +00:00
Kubernetes Release Robot
92e86d1b4b Release commit for Kubernetes v1.33.0-rc.1 2025-04-15 16:51:25 +00:00
Kubernetes Release Robot
2f7a115a69 Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-14 19:31:24 +00:00
Kubernetes Prow Robot
30469e1803
Merge pull request #131263 from aojea/dualstack_upgrade
Allow to convert clusters Service CIDRs from single to dual stack
2025-04-14 11:17:06 -07:00
Antonio Ojea
0266d3bcb3 Allow single-to-dual-stack reconfiguration for ServiceCIDR
This change modifies the validation logic for ServiceCIDR updates
(`ValidateServiceCIDRUpdate`) to specifically permit upgrading a
single-stack ServiceCIDR (either IPv4 or IPv6) to a dual-stack
configuration.

This reconfiguration path is considered safe because it only involves adding
a new CIDR range without altering the existing primary CIDR. This
ensures that existing Service IP allocations are not disrupted.

Other modifications, such as:
- Downgrading from dual-stack to single-stack
- Reordering CIDRs in a dual-stack configuration
- Changing the primary CIDR during a single-to-dual-stack
  reconfiguration

remain disallowed by the validation. These operations carry a higher
risk of breaking existing Services or cluster networking
configurations. Preventing these updates automatically encourages
administrators to perform such changes manually after carefully
assessing the potential impact on their specific cluster environment.
The validation errors and controller logs provide guidance when such
disallowed changes are attempted.

Change-Id: I41dc09dfddb05f277925da2262f8114d6accbd1d
2025-04-14 17:05:44 +00:00
Kubernetes Prow Robot
cfed8c7d41
Merge pull request #131234 from carlory/fix-131229
Fix flaky test: Metrics should grab all metrics from kubelet /metrics/resource endpoint
2025-04-14 08:19:13 -07:00
Kubernetes Prow Robot
d6e3f34f70
Merge pull request #131211 from BenTheElder/max-pods
fix flaky garbage collector tests
2025-04-14 08:19:06 -07:00
Kubernetes Release Robot
bbdcee749c Merge remote-tracking branch 'origin/master' into release-1.33 2025-04-11 13:32:52 +00:00
Kubernetes Prow Robot
b15dfce6cb
Merge pull request #131240 from jsafrane/selinux-tests-tag
Tag SELinux tests that require SELinux warning controller
2025-04-11 04:46:42 -07:00
carlory
7d7fc2d989 Fix flaky test: Metrics should grab all metrics from kubelet /metrics/resource endpoint
Signed-off-by: carlory <baofa.fan@daocloud.io>
2025-04-11 11:30:28 +08:00