Justin J. Janes

$ k3s -v ``` k3s version v1.27.10-rc2+k3s1 (ce6158f8) go version go1.20.13 ``` $ grype /usr/local/bin/k3s --add-cpes-if-none ``` ✔ Vulnerability DB [no update available] ✔ Indexed file system /usr/local/bin ✔ Cataloged...

$ k3s -v ``` k3s version v1.29.1-rc2+k3s1 (d8907ce6) go version go1.21.6 ``` $ grype /usr/local/bin/k3s --add-cpes-if-none ``` ✔ Vulnerability DB [no update available] ✔ Indexed file system /usr/local/bin ✔ Cataloged...

$ k3s -v ``` k3s version v1.28.6-rc2+k3s1 (39a00015) go version go1.20.13 ``` $ grype /usr/local/bin/k3s --add-cpes-if-none ``` ✔ Vulnerability DB [no update available] ✔ Indexed file system /usr/local/bin ✔ Cataloged...

Modified comments above to reflect requested changes.

##Environment Details Reproduced using VERSION=v1.29.2+k3s1 Validated using VERSION=v1.29.3-rc1+k3s1 *Infrastructure* - [X] Cloud *Node(s) CPU architecture, OS, and version:* Linux 5.11.0-1022-aws x86_64 GNU/Linux PRETTY_NAME="Ubuntu 20.04.3 LTS" *Cluster Configuration:* ``` NAME STATUS...

I haven't tried it on a single host at all we don't usually try to do conformance tests without a 3-1 cluster.

TLDR from above link where I encountered this issue while testing the latest COMMIT_ID for v1.28 branch $ kg pv -A ``` NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM...

##Environment Details Reproduced using VERSION=v1.29.3+k3s1 Validated using COMMIT=49414a8defd931e5ec200d21e814a3bb38a8a79f *Infrastructure* - [X] Cloud *Node(s) CPU architecture, OS, and version:* Linux 5.14.21-150500.53-default x86_64 GNU/Linux PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5" *Cluster Configuration:*...

This validation is stalled pending this bug fix - https://github.com/k3s-io/k3s/issues/10023

Hey @bruth I DM'd you back on your home Slack if you want to work together I'd be more than happy to. :)