Support provider deprecation

[richardcase]

User Story

As a provider implementer, I would like to be able to deprecate a provider to support changes in the provider types / deployment options for a provider.

Detailed Description

In CAPA prior to version 0.7.0 we had infrastructure, control plane and bootstrap providers. This separation caused some technical and UX issues. So with the 0.7.0 release we have removed the separate control plane and bootstrap providers and combined them into the infrastructure provider.

It would be good if there was the ability to mark a provider as deprecated from a specific version (from 0.7.0 in out case for the aws-eks control plane and bootstrap providers).

We can't just removethe providers as someone may use clusterctl to install a version prior to 0.7.0

/kind feature
/area clusterctl

[richardcase]

/assign

[richardcase]

@fabriziopandini @randomvariable @sedefsavas - fyi

[vincepri]

It might be good to have support for deprecation in the metadata file if possible, and include also a deprecation message

[sbueringer]

Mirroring what I wrote in Slack. Right now we have the following situation:

• clusterctl v0.3.x: is able to install v1alpha3 providers (CAPA < v0.7.0)
• clusterctl v0.4.x: is able to install v1alpha4 providers (CAPA >= v0.7.0) and only to upgrade v1alpha3 providers to v1alpha4

So tl;dr current clusterctl is already unable to install your old providers as they are not using the v1alpha4 contract.

[richardcase]

Thanks @sbueringer - this behaviour solves the short-term problem for CAPA.

Do we see a need to support provider deprecation in the future?

[sbueringer]

+1 as it provides a better UX for end users and then less questions in Slack :)

[vincepri]

/milestone v1.0

[richardcase]

/unassign

[richardcase]

/help

[k8s-ci-robot]

@richardcase:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[richardcase]

/lifecycle frozen

[fabriziopandini]

/triage accepted

[fabriziopandini]

(doing some cleanup on old issues without updates)
/close
unfortunately, no one is picking up the task. the thread will remain available for future reference

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

(doing some cleanup on old issues without updates)
/close
unfortunately, no one is picking up the task. the thread will remain available for future reference

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.