Weekly Status: Week 8, 2022

[cwayne18]

Weekly Report

Weekly status report for k3s-io/k3s Week #8 2022

Weekly Stats

	Opened this week	Closed this week
Issues	14	22
PR's	12	5

New stars	54
New forks	7

PR's Closed

• #5155: Integration tests: move to a global test lock
• #5150: [Engine-1.21] Update to v1.21.10
• #5140: Create encryption-hash.json file if it doesn't exist
• #5137: Upgrade to V1.21.10+k3s1
• #5135: Update to V1.23.4 k3s1

PR's Opened

• #5171: [Release-1.22] Integration tests: move to a global test lock
• #5170: [Engine-1.21] Create encryption hash file if it doesn't exist
• #5169: [Release-1.22] Create encryption hash file if it doesn't exist
• #5168: [Release-1.21] Create encryption hash file if it doesn't exist
• #5164: Move temporary etcd startup code into etcd module
• #5161: Cleanup excess runtime reference
• #5158: Add function to clear local alarms on etcd startup
• #5157: E2E Add external DB options to ValidateCluster test
• #5155: Integration tests: move to a global test lock
• #5154: Add contributors documentation
• #5150: [Engine-1.21] Update to v1.21.10
• #5149: Add http/2 support to API server

Issues Opened

• #5167: [Release-1.21] - Secrets encryption rotation does not work when upgrading from older K3s versions.
• #5166: [Release-1.22] - Secrets encryption rotation does not work when upgrading from older K3s versions.
• #5165: Volume subPath not working for NFS volumes
• #5163: x509: certificate has expired or is not yet valid
• #5162: [k3s-upgrade] Wrong image tag in latest release channel: v1.23.4-k3s1, it should be v1.23.4+k3s1
• #5160: After I add the "--tls-san rancher.k3s.cn" instruction, this should be the server nodes, but it turned out to be the agent node
• #5159: Can someone tell me what to fill here in 'k3s.yml' [server: [LOAD-BALANCER-DNS]:6443 # Edit this line]
• #5156: Pods crash loop on selinux enabled cluster due to SELinux preventing /usr/bin/bash read access on the file network
• #5153: Cut v1.23.4+k3s1
• #5152: Cut v1.22.7+k3s1
• #5151: Cut v1.21.10+k3s1
• #5148: Missing http/2 support in kube-apiserver
• #5147: Test to modify the server time rolling update ca certificate, ca certificate can not be updated
• #5146: k3s server can't start after reboot machine

Issues Closed

• #5165: Volume subPath not working for NFS volumes
• #5162: [k3s-upgrade] Wrong image tag in latest release channel: v1.23.4-k3s1, it should be v1.23.4+k3s1
• #5159: Can someone tell me what to fill here in 'k3s.yml' [server: [LOAD-BALANCER-DNS]:6443 # Edit this line]
• #5156: Pods crash loop on selinux enabled cluster due to SELinux preventing /usr/bin/bash read access on the file network
• #5146: k3s server can't start after reboot machine
• #5088: [Release 1.21] Use kube-router upstream libraries to consume the netpol controller
• #5086: [Release 1.22] Use kube-router upstream libraries to consume the netpol controller
• #5078: Use kube-router upstream libraries to consume the netpol controller
• #5066: Bump containerd and stargz-snapshotter
• #5052: [Release-1.21] - k3s secrets-encrypt status is not able to connect to API not bound to 127.0.0.1
• #5034: Update flannel, cni-plugins and root version
• #5019: dual stack k3s kills default ::0 route after start
• #5006: k3s secrets-encrypt status is not able to connect to API not bound to 127.0.0.1
• #5001: Some iptable rules remain after destroy cluster
• #4564: [release 1.21] selinux: most items under /var/lib/rancher/k3s/data/current/bin should not be container_runtime_exec_t
• #3806: Cluster Reset Issue
• #3803: k3s state inconsistent after filesystem rollback of all nodes in cluster
• #3799: etcd-snapshot-dir setting in config file is not honored for k3s etcd snapshot command
• #2932: K3s requires /bin/sh
• #2427: where are my certs - connection reset
• #1644: k3s CCM must allow for custom patching during node join
• #1255: Interactions with kubectl very slow compared to k3s kubectl

Community PRs Closed

None

Community PRs Opened

• #5149: Add http/2 support to API server