Skip to content
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.

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

[release-1.26] Backports for 2023-11 release #8879

Merged
merged 10 commits into from
Nov 16, 2023

Conversation

brandond
Copy link
Member

@brandond brandond commented Nov 16, 2023

Proposed Changes

Backports for:

Types of Changes

Verification

Testing

See linked issues

Linked Issues

User-Facing Change

new timezone info in Docker image allows the use of `spec.timeZone` in CronJobs
Bumped kine to v0.11.0 to resolve issues with postgres and NATS, fix performance of watch channels under heavy load, and improve compatibility with the reference implementation.
Containerd may now be configured to use rdt or blockio configuration by defining `rdt_config.yaml` or `blockio_config.yaml` files.
Add agent flag disable-apiserver-lb, agent will not start load balance proxy.
Improved ingress IP ordering from ServiceLB
Disable helm CRD installation for disable-helm-controller
Omit snapshot list configmap entries for snapshots without extra metadata
Add jitter to client config retry to avoid hammering servers when they are starting up

Further Comments

iwilltry42 and others added 10 commits November 16, 2023 00:16
Signed-off-by: Thorsten Klein <tk@thklein.io>
(cherry picked from commit a264416)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Ref: https://github.com/k3s-io/kine/releases/tag/v0.11.0
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 32a1efa)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Problem:
Configuring qos-class features in containerd requres a custom containerd configuration template.

Solution:
Look for configuration files in default locations and configure containerd to use them if they exist.

Signed-off-by: Oliver Larsson <larsson.e.oliver@gmail.com>
(cherry picked from commit 30c8ad9)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* add node flag disable-agent-lb
* add agent flag disable-apiserver-lb

Co-authored-by: Brad Davidson <brad@oatmail.org>
Signed-off-by: chenk008 <kongchen28@gmail.com>
(cherry picked from commit b47cbbf)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Omit snapshot list configmap entries for snapshots without extra metadata; reduce log level of warnings about missing s3 metadata files.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 2088218)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 7ecd587)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Tweaked order of ingress IPs in ServiceLB
    Previously, ingress IPs were only string-sorted when returned
    Sorted by IP family and string-sorted in each family as part of
    filterByIPFamily method
* Update pkg/cloudprovider/servicelb.go
* Formatting

Signed-off-by: Jason Costello <jason@hazy.com>
Co-authored-by: Brad Davidson <brad@oatmail.org>
(cherry picked from commit 07ee854)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller
    The NewContext package requires config as input which would
    require all third-party callers to update when the new go module
    is published.

    This change only affects the behaviour of installation of helm
    CRDs. Existing helm crds installed in a cluster would not be removed
    when disable-helm-controller flag is set on the server.

    Addresses k3s-io#8701
* address review comments
* remove redundant check

Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com>
(cherry picked from commit abc2efd)
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Also:
* Replaces labeled for/continue RETRY loops with wait helpers for improved readability
* Pulls secrets and nodes from cache for node password verification
* Migrate nodepassword tests to wrangler mocks for better code reuse

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond brandond requested a review from a team as a code owner November 16, 2023 00:25
Copy link

codecov bot commented Nov 16, 2023

Codecov Report

Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (cb5cb55) 17.47% compared to head (0731e80) 17.48%.

Files Patch % Lines
pkg/etcd/s3.go 0.00% 8 Missing ⚠️
pkg/etcd/snapshot_controller.go 0.00% 5 Missing ⚠️
...enerated/controllers/k3s.cattle.io/v1/interface.go 0.00% 2 Missing ⚠️
pkg/cli/cmds/agent.go 0.00% 1 Missing ⚠️
pkg/cluster/bootstrap.go 0.00% 1 Missing ⚠️
...d/controllers/k3s.cattle.io/v1/etcdsnapshotfile.go 0.00% 1 Missing ⚠️
pkg/nodepassword/nodepassword.go 66.66% 1 Missing ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##           release-1.26    #8879      +/-   ##
================================================
+ Coverage         17.47%   17.48%   +0.01%     
================================================
  Files                94       93       -1     
  Lines              6319     6314       -5     
================================================
  Hits               1104     1104              
+ Misses             4982     4977       -5     
  Partials            233      233              
Flag Coverage Δ
unittests 17.48% <17.39%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@brandond brandond merged commit b723eea into k3s-io:release-1.26 Nov 16, 2023
15 checks passed
@brandond brandond deleted the 2023-11-backports_release-1.26 branch June 6, 2024 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants