[QUESTION/HELP] go: k8s.io/kubelet@v0.0.0: invalid version: unknown revision v0.0.0

[boskiv]

trying to use pkg client but got an error when go mod tidy

package main

import (
	k3dCluster "github.com/k3d-io/k3d/v5/pkg/client"

	l "github.com/k3d-io/k3d/v5/pkg/logger"
)

func main() {
	if err := k3dCluster.ClusterRun(cmd.Context(), runtimes.SelectedRuntime, clusterConfig); err != nil {
		// rollback if creation failed
		l.Log().Errorln("Failed to create cluster >>> Rolling Back")
		if err := k3dCluster.ClusterDelete(cmd.Context(), runtimes.SelectedRuntime, &clusterConfig.Cluster, k3d.ClusterDeleteOpts{SkipRegistryCheck: true}); err != nil {
			l.Log().Errorln(err)
			l.Log().Fatalln("Cluster creation FAILED, also FAILED to rollback changes!")
		}
		l.Log().Fatalln("Cluster creation FAILED, all changes have been rolled back!")
	}
}

GOROOT=/opt/homebrew/opt/go/libexec #gosetup
GOPATH=/Users/iskiridomov/go #gosetup
/opt/homebrew/opt/go/libexec/bin/go list -modfile=/Users/iskiridomov/GolandProjects/testk3d/go.mod -m -json -mod=mod all #gosetup
go: k8s.io/kubelet@v0.0.0: invalid version: unknown revision v0.0.0

[colearendt]

Hitting the same issue. I believe this is where it is coming from: https://github.com/rancher/wharfie/blob/cf9a8880fbd75445c3ce0fcab2c5b21548bc197c/go.mod#L88

[iwilltry42]

Hey 👋
That's weird. Is there anything special about your development setups?
Seems to be working fine for me when building either of them (k3d and wharfie) 🤔
The wharfie go.mod file has a replace statement for the kubelet import.
@brandond do you have any idea on this?
I guess following the online guides about switching the versions in go.mod isn't the best idea here.

[brandond]

you need to add require or replace statements to your go.mod to pull in specific versions of Kubernetes. For example:

https://github.com/rancher/system-upgrade-controller/blob/master/go.mod#L14-L20

You'll see this same pattern across all projects that import Kubernetes libs. Repeat those entries for any other Kubernetes libraries your project is importing, either explicitly or implicitly. Note that replace entries from go.mod don't don't affect projects that import that module; each project needs to add them on their own.

[iwilltry42]

@brandond thank you, so it is indeed what's written everywhere.
I guess it's a misunderstanding on my side.
I'm wondering though why it affects this, since in k3d's go.mod we have require statements and no replace statements.