Weekly Status: Week #43, 2022

[cwayne18]

Weekly Report

Weekly status report for k3s-io/k3s Week #43 2023

Weekly Stats

	Opened this week	Closed this week
Issues	14	34
PR's	7	7

New stars	412
New forks	25

PR's Closed

• #8692: [release-1.25] Backport etcd fixes
• #8691: [release-1.26] Backport etcd fixes
• #8682: [v1.28] Update to v1.28.3 and Go to v1.20.10
• #8681: [v1.27] Update to v1.27.7 and Go to v1.20.10
• #8680: [v1.26] Update to v1.26.10 and Go to v1.20.10
• #8679: [v1.25] Update to v1.25.15 and Go to v1.20.10
• #8224: Draft: Add ability to specify local storage class name

PR's Opened

• #8717: add agent flag disable-apiserver-lb
• #8711: Tweaked order of ingress IPs in ServiceLB
• #8710: Bump Sonobuoy version
• #8709: Use JSONPatch to update node labels and annotations
• #8703: Silence SELinux warning on INSTALL_K3S_SKIP_SELINUX_RPM
• #8702: Disable helm CRD installation for disable-helm-controller
• #8699: Bump github.com/nats-io/nats-server/v2 from 2.9.18 to 2.9.23

Issues Opened

• #8720: QoS-class resource containerd config files
• #8718: Managing an embedded etcd cluster
• #8716: K3s crashing instantly building kine: commands out of sync
• #8714: Replace confusing log
• #8712: My k3s cluster powering down with data anomalies
• #8708: API complains on resources exist during helm install and which actually not
• #8706: NodePort only working on nodes with pod
• #8705: Unexpected SELinux warning when INSTALL_K3S_SKIP_DOWNLOAD=true
• #8704: ServiceLB return ingress address list in alphabetical order, instead of sorted by address family
• #8701: Helm CRDS are installed despite turning off helm-controller
• #8700: Make alternative container runtimes easier to use
• #8697: Reorganize networking content in the docs
• #8696: Kubectl in rancher/k3s Docker image doesn't work
• #8695: K3s invalid capacity 0 on image filesystem. cri_stats_provider.go:455] "Failed to get the info of the filesystem with mountpoint

Issues Closed

• #8718: Managing an embedded etcd cluster
• #8712: My k3s cluster powering down with data anomalies
• #8706: NodePort only working on nodes with pod
• #8696: Kubectl in rancher/k3s Docker image doesn't work
• #8695: K3s invalid capacity 0 on image filesystem. cri_stats_provider.go:455] "Failed to get the info of the filesystem with mountpoint
• #8693: Hybrid cluster with some VM in same network
• #8689: [Release-1.25] - no nodes have reconciled ETCDSnapshotFile resources, requeuing error on clusters with no etcd snapshots
• #8688: [Release-1.26] - no nodes have reconciled ETCDSnapshotFile resources, requeuing error on clusters with no etcd snapshots
• #8687: [Release-1.27] - no nodes have reconciled ETCDSnapshotFile resources, requeuing error on clusters with no etcd snapshots
• #8686: [Release-1.25] - Split server setup fails on etcd-only, cp-only config
• #8685: [Release-1.26] - Split server setup fails on etcd-only, cp-only config
• #8684: [Release-1.27] - Split server setup fails on etcd-only, cp-only config
• #8672: Split server setup fails on etcd-only, cp-only config
• #8668: [release-1.27] CloudDualStackNodeIPs feature-gate not consistently enabled
• #8666: CloudDualStackNodeIPs feature-gate not consistently enabled
• #8665: no nodes have reconciled ETCDSnapshotFile resources, requeuing error on clusters with no etcd snapshots
• #8645: [Release-1.25] Windows port of K3s agent role
• #8614: [Release-1.25] - k3s-etcd-snapshots configmap grows too large when snapshot retention is high
• #8613: [Release-1.26] - k3s-etcd-snapshots configmap grows too large when snapshot retention is high
• #8612: [Release-1.27] - k3s-etcd-snapshots configmap grows too large when snapshot retention is high
• #8611: k3s-etcd-snapshots configmap grows too large when snapshot retention is high
• #8610: [Release-1.25] - rancher/mirrored-library-busybox:1.34.1 has critical vulnerability
• #8609: [Release-1.26] - rancher/mirrored-library-busybox:1.34.1 has critical vulnerability
• #8608: [Release-1.27] - rancher/mirrored-library-busybox:1.34.1 has critical vulnerability
• #8503: [Release-1.25] - Dual-stack not supporting
• #8502: [Release-1.26] - Dual-stack not supporting
• #8501: [Release-1.27] - Dual-stack not supporting
• #8483: [Release-1.25] - Add a flag --image-service-endpoint and also default image service endpoint to container runtime endpoint if set.
• #8482: [Release-1.26] - Add a flag --image-service-endpoint and also default image service endpoint to container runtime endpoint if set.
• #8481: [Release-1.27] - Add a flag --image-service-endpoint and also default image service endpoint to container runtime endpoint if set.
• #8467: Dual-stack not supporting
• #8432: [Release-1.25] - Etcd removal annotation not removed on cluster reset / restore
• #8373: rancher/mirrored-library-busybox:1.34.1 has critical vulnerability
• #8234: database is locked during Rancher (moderate) stress test

Community PRs Closed

• #8682: [v1.28] Update to v1.28.3 and Go to v1.20.10
• #8681: [v1.27] Update to v1.27.7 and Go to v1.20.10
• #8680: [v1.26] Update to v1.26.10 and Go to v1.20.10
• #8679: [v1.25] Update to v1.25.15 and Go to v1.20.10
• #8224: Draft: Add ability to specify local storage class name

Community PRs Opened

• #8717: add agent flag disable-apiserver-lb
• #8711: Tweaked order of ingress IPs in ServiceLB
• #8710: Bump Sonobuoy version
• #8703: Silence SELinux warning on INSTALL_K3S_SKIP_SELINUX_RPM
• #8702: Disable helm CRD installation for disable-helm-controller
• #8699: Bump github.com/nats-io/nats-server/v2 from 2.9.18 to 2.9.23