Instructions in README are outdated and use deprecated functions

[carreter]

I'm working through setting up some e2e tests and noticed that the README.md of this repo is outdated. Things I've noticed so far:

• cluster creation with envfuncs.CreateKindCluster is deprecated

I'll keep adding to this as I go along.

[przemolb]

Where is it written that envfuncs.CreateKindCluster is deprecated ?

[carreter]

e2e-framework/pkg/envfuncs/kind_funcs.go

Lines 35 to 39 in a4bef02

	// Deprecated: This handler has been deprecated in favor of CreateCluster which can now accept
	// support.ClusterProvider type as input in order to setup the cluster using right providers
	func CreateKindCluster(clusterName string) env.Func {
	return CreateCluster(kind.NewProvider(), clusterName)
	}

[mbtamuli]

Yes, the new function to replace that is CreateCluster

[vladimirvivien]

@carreter thanks for pointing this out. It's possible there is outdated info in the project.
It's been evolving and some documentation will fall through the cracks.
Thanks again for using the project.

[carreter]

I'll put up a PR to clean up what I found!

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten