Document basic workflow for the kind deployer

[rexagod]

Hello! 👋🏼

I'm trying to run the node tester with the kind deployer, but I'm having no luck so far. The command below fails with a 1 exit code without any logs whatsoever.

kubetest2 kind --test=node --build --up --down -- --focus-regex='Kubelet Config' --repo-root="." -v 2

Also, I want to point out that a simple kubetest2 --help will print out a help message, within which, there's this line:

kubetest2 should be called with a deployer like: 'kubetest2 kind --help'

However, doing kubetest2 kind --help prints nothing either.

Am I missing something here?

[elieser1101]

To get the deployer help you should install the deployer itself, in your case will be go install sigs.k8s.io/kubetest2/kubetest2-kind@latest

[rexagod]

I followed the README, and it suggests doing go install sigs.k8s.io/kubetest2/...@latest which I reckon includes that?

[rexagod]

Yep, same results unfortunately.

┌[rexagod@nebuchadnezzar] [/dev/ttys004] [kubelet-allow-disabling-metrics] [130]
└[~/repositories/oss/kubernetes]> go install sigs.k8s.io/kubetest2/kubetest2-kind@latest
go: downloading sigs.k8s.io/kubetest2 v0.0.0-20241105154129-acda51a5e9e3
┌[rexagod@nebuchadnezzar] [/dev/ttys004] [kubelet-allow-disabling-metrics]
└[~/repositories/oss/kubernetes]> kubetest2 kind --help
┌[rexagod@nebuchadnezzar] [/dev/ttys004] [kubelet-allow-disabling-metrics] [1]
└[~/repositories/oss/kubernetes]>

[elieser1101]

did u ensure the downloaded kubetest2-kind binary is available on your PATH?

[rexagod]

Yep, in the $PATH.

┌[rexagod@nebuchadnezzar] [/dev/ttys004] [kubelet-allow-disabling-metrics] [1]
└[~/repositories/oss/kubernetes]> which kubetest2-kind
/Users/rexagod/go/bin/kubetest2-kind

[elieser1101]

Hi @rexagod I think there might be two separate things here.

1. For some reason kubetests2 is not able to find kubetest2-kind to execute it
   1.1 You could try running /Users/rexagod/go/bin/kubetest2-kind --help itself, maybe its not executable for some reason
2. I think what you are trying to do is not supported at the moment, the tester node is defaulting to test with gce nodes.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale