Deprecate the Krew plugin

[dvaldivia]

We are deprecating the krew plugin in favor of focusing on the kustomize and helm approach of installing the operator.

[shtripat]

There is an enterprise test using this for expand tenant feature test. We may need to change that.

[cniackz]

LGTM

[cniackz]

Tested and deployed the tenant with this compiled version. It shouldn't break functionality, although I agree with @shtripat that tests should catch up with the changes, as should the documentation. @ravindk89, please be aware.

[cniackz]

Oh I see, tests are updated and regarding common.sh these changes looks good to me:

[allanrogerr]

@dvaldivia @cniackz
This is a breaking change to our users' workflows. Therefore how will this be announced, giving users sufficient time to change their workflows?

[ravindk89]

@dvaldivia @cniackz if I may suggest:

• Hold this PR for now
• Open a fresh PR that marks all kubectl minio commands as deprecated and returns a non-blocking warning on each run (this may break user workflows who parse output in some way)
• Docs will warn that we are deprecating kubectl minio route of installation and focus on kubectl apply -k github.com/minio/operator and the equivalent for Tenants
• Merge this PR for the subsequent Operator release

With this, we would

• Publish 5.0.15 with a deprecation warning
• Publish 5.0.16 with the deprecation

Users do not always track latest stable that closely, and can stay on 5.0.15 until they have readied their systems to move to Kustomize.

Thoughts?

[harshavardhana]

This is a breaking change to our users' workflows. Therefore how will this be announced, giving users sufficient time to change their workflows?

There is no such workflow

[harshavardhana]

@dvaldivia @cniackz if I may suggest:

• Hold this PR for now
• Open a fresh PR that marks all kubectl minio commands as deprecated and returns a non-blocking warning on each run (this may break user workflows who parse output in some way)
• Docs will warn that we are deprecating kubectl minio route of installation and focus on kubectl apply -k github.com/minio/operator and the equivalent for Tenants
• Merge this PR for the subsequent Operator release

With this, we would

• Publish 5.0.15 with a deprecation warning
• Publish 5.0.16 with the deprecation

Users do not always track latest stable that closely, and can stay on 5.0.15 until they have readied their systems to move to Kustomize.

Thoughts?

No we move to v6.0.0 - we break this and bump the major version.

[feorlen]

What is the timeline for this? It's a major change to how docs describes the k8s install process. We do have some preliminary docs for kustomize in GitHub, but multiple pages in the web docs need rework to feature that instead of krew.

[allanrogerr]

Consider the changes to goreleaser made here: #2062

[cniackz]

I will solve the conflict:

The change that was taken into consideration is now gone!

[cniackz]

The conflict has been resolved, and now I'm awaiting the completion of tests. Once they pass, I'll request the team to review again, and then proceed with the merge.