Released version of setup-envtest

[fabienmifsud]

Hi,

Is there any released version of setup-envtest, we can't only rely on "latest" version for our CI pipeline.

Thanks !

[varshaprasad96]

This needs to be fixed. A similar issue has been raised in #1670. We will bring this up in the community meeting and try fixing it soon.

[camilamacedo86]

@varshaprasad96 , @vincepri
Could we add this one as a priority?

[FillZpp]

As I said in #1670, controller-runtime does have the setup-envtest in releases. But You have to import it in your project with build tool and then you can install it with the required version.

You can follow this: #1670 (comment)

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[camilamacedo86]

@FillZpp.

After discussuion we might not able to move forward with the approach recommended in : #1670 (comment) and we might not want suggest that.

See: kubernetes-sigs/kubebuilder#2480 (comment)

c/c @joelanford

[camilamacedo86]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[camilamacedo86]

/remove-lifecycle stale