Weekly Status: Week 5, 2022

[cwayne18]

Weekly Report

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

Weekly Stats

	Opened this week	Closed this week
Issues	22	27
PR's	14	13

New stars	43
New forks	10

PR's Closed

• #5068: Update README.md
• #5064: Check for --kubeconfig flag with embedded kubectl
• #5057: Sign CSRs for legacy-unknown with the server CA
• #5055: [Engine-1.21] Add --server flag to k3s secrets-encrypt
• #5054: [Release-1.21] Add --server flag to k3s secrets-encrypt
• #5053: [Release-1.22] Add --server flag to k3s secrets-encrypt
• #5050: Bump K3s stable to v1.22.6
• #5035: Update versions of K3S root, flannel and cni_plugins
• #4968: Use double quotes for variables in IF
• #4897: Fixes to Drone CI Stability
• #4534: netpol: Use kube-router as a library
• #4248: install.sh: on uninstall remove /var/lib/rancher if empty
• #4203: Update install.sh

PR's Opened

• #5079: netpol: Use kube-router as a library
• #5075: [Release-1.22] Check for --kubeconfig flag with embedded kubectl (Check for --kubeconfig flag with embedded kubectl #5064)
• #5074: [Release-1.21] Check for --kubeconfig flag with embedded kubectl (Check for --kubeconfig flag with embedded kubectl #5064)
• #5069: Update traefik helm chart and enable http3 support
• #5068: Update README.md
• #5064: Check for --kubeconfig flag with embedded kubectl
• #5063: [Release 1.21] Remove the iptables rules from ipmasq flannel
• #5062: [Release 1.22] Update flannel version and remove the iptables rules from ipmasq flannel
• #5059: Remove the iptables rules from ipmasq flannel
• #5057: Sign CSRs for legacy-unknown with the server CA
• #5055: [Engine-1.21] Add --server flag to k3s secrets-encrypt
• #5054: [Release-1.21] Add --server flag to k3s secrets-encrypt
• #5053: [Release-1.22] Add --server flag to k3s secrets-encrypt
• #5050: Bump K3s stable to v1.22.6

Issues Opened

• #5082: k3s-server take too mush cpu on SONiC system
• #5081: Auto-Deploying Manifests Ordering
• #5080: unable to start k3s agent - cgroup support not found - synology ds220plus
• #5078: Use kube-router upstream libraries to consume the netpol controller
• #5077: Metrics Server unhealthy, zero replicas available - connection refused - on fresh installation
• #5076: Failed to execute iptables-restore" err="exit status 1 (ip6tables-restore: line 21 failed\n)
• #5073: [Release-1.22] - Warning when using correct --kubeconfig flag in k3s kubectl
• #5072: [Release-1.21] - Warning when using correct --kubeconfig flag in k3s kubectl
• #5071: Warning when using correct --kubeconfig flag in k3s kubectl
• #5070: --cluster-reset renders entire cluster hosed
• #5067: Fix etcd-snapshot-schedule-cron Usage Note
• #5066: Bump containerd and stargz-snapshotter
• #5061: [Release 1.21] Remove flannel ipmasq iptable rules when destroying k3s
• #5060: [Release 1.22] Remove flannel ipmasq iptable rules when destroying k3s
• #5058: CIS Benchmark error - results: no such file or directory
• #5056: Upgrading k3s leaves orphaned replicasets?
• #5052: [Release-1.21] - k3s secrets-encrypt status is not able to connect to API not bound to 127.0.0.1
• #5051: [Release-1.22] - k3s secrets-encrypt status is not able to connect to API not bound to 127.0.0.1
• #5049: Allow customizing etcd wal-dir
• #5048: Using k3s when WiFi goes down/unavailable for sometime
• #5047: [k3s-upgrade] not working for K3OS installe K3S
• #5046: K3s cannot be installed on SLES15 SP3

Issues Closed

• #5070: --cluster-reset renders entire cluster hosed
• #5048: Using k3s when WiFi goes down/unavailable for sometime
• #5045: Strange DNS behavior in some containers including cert-manager
• #5030: [BUG] K3s CoreDNS terminates around every minute
• #5026: Cut v1.23.3+k3s1
• #4882: Drone failures on sonobuoy testing.
• #3997: [k3s-upgrade] Upgrade to 1.22 from 1.21.4
• #3705: Can /etc/rancher/k3s/config.yaml be used to init k3s-agents?
• #3703: k3s issue with helm3 and pvc pending
• #3702: Update SECURITY.md
• #3699: k3s service failed to restart after etcd error
• #3689: failed to get CA certs (with public IP)
• #2813: Update rancher docs clarifying removal of node-passwd file
• #2704: Panic with 1.19.5+k3s1 on rpi-4 server
• #2466: Restarting a highly available k3s cluster
• #1988: Customize servicelb daemonset tolerations (traefik)
• #1541: K3s' kubectl prefers /etc/rancher/k3s/k3s.yaml over ~/.kube/config
• #1527: DNS resolution with k3s cluster is broken
• #1303: Pod Ready and Running Status not correct / not consistent when using StatefulSet
• #1268: Can't start agent: Failed to connect to proxy too many colons in address
• #1106: [v1.0.0] kubectl get cs return age
• #1009: When installing rancher on k3s cluster, secret tls-rancher-ingress is not created.
• #925: [HA] k3s master nodes should check if the bootstrap data isnt available
• #876: K3s Master Token
• #838: Not killing pods by default, system OOM takes over
• #800: traefik appears to be generating invalid IPtables rules
• #185: Docs on builtin service load balancer; NodeAffinity for host ports feature request

Community PRs Closed

• #5068: Update README.md
• #5057: Sign CSRs for legacy-unknown with the server CA
• #4968: Use double quotes for variables in IF
• #4248: install.sh: on uninstall remove /var/lib/rancher if empty
• #4203: Update install.sh

Community PRs Opened

• #5069: Update traefik helm chart and enable http3 support
• #5068: Update README.md
• #5057: Sign CSRs for legacy-unknown with the server CA