Added marking add-ons as deprecated

[kyleprice]

No description provided.

[github-actions]

🚀 Deployed on https://6435c778a1218040cf251754--kurlsh-staging.netlify.app

[AmberAlston]

Lots of comments. Let me know if you want to discuss any of them in more depth outside of async comments.

Visuals/Content:

• The Deprecated label is really hard to read unless you’re on a high-res monitor. Maybe it’s the length of the word or the color. We could try using the existing beta red.
• Why are we stating the start date for deprecation (March 23) on some of the add-ons but not others?
• Why is Antrea June 1, and AWS is May 1. Latter is beta, but both don’t appear to have any usage
• How did we reach the date of Sept 1 for the others? That’s approx 5mo. Is that enough time for an add-on like Weave, which is highly used today?
• For Weave specifically we should say something in the deprecation notice about the upstream maintainers no longer maintaining the project, and as such we can no longer maintain it as a viable CNI add-on for KURL.
• For Docker specifically we should highlight that “Kubernetes no longer supports Docker as of 1.24, and therefore any in-support versions of Kubernetes must leverage ContainerD”. That way is reinforces that this isn’t our decision. We say something similar later, but it should be in the deprecation notice.
• We need to change this language in the messages, “Support for existing installs will continue to be best effort.”, it sounds like we’re abandoning our support responsibilities. I’d suggest something like, “Existing installs that use this add-on will continue to be best-effort supported until the deprecation date.” Are we continuing to patch these add-ons during this window? That answer may drive some additional copy tweaks

Other related changes needed:

• If we are making Longhorn as deprecated we should clean up these example specs that say to use Longhorn: https://kurl.sh/docs/install-with-kurl/#latest & https://kurl.sh/docs/create-installer/
• The IPv6 alpha https://kurl.sh/docs/install-with-kurl/ipv6 only works with Antrea. How are we reconciling that as we mark Antrea deprecated?

Non-code complimentary work to address before this is merged:

• What are we doing to proactively communicate this deprecation to vendors using Longhorn, Docker, and Weave. I don’t want them to stumble across the deprecation notices on the website and ask us about it. These needs to be paired with a formalized announcement to vendors impacted by these changes to let them know: (1) about the deprecation, (2) how they can move forward
• We also need to let the field facings teams (Sales, SE, CRE) know ahead of pushing this change live, so they are prepared for possible questions.

[camilamacedo86]

What fully vs partial deprecated does means?
It seems that you want say it is deprecated now and at September 31st goes in EOL.

[emosbaugh]

Can we use the term remove rather than deprecate?

[AmberAlston]

Updated comments below

• Re-reading this again today, I’d suggest we tweak the main deprecation copy as follows. This would help address Camila’s feedback as well.
  • As of March 27, 2023, kURL no longer intends to continue to offer this add-on as part of the ongoing kURL project. This add-on is now considered deprecated, and may no longer be offered by the project after (DATE). Existing installs that use this add-on will be best effort supported during this deprecation window. (MIGRATION GUIDANCE & ANY OTHER INFO)
• I didn’t get an answer on my question about patching updates during this deprecation window or not. That answer may drive some additional copy tweaks.
• Docker - I’d still like to see a reference to the K8s incompatibility within the deprecation notice itself. That way it’s clearer this isn’t our decision, it’s deprecated by virtue of K8s moving on from it.
• It looks like the reference to longhorn was corrected in the "latest" link, but not https://kurl.sh/docs/install-with-kurl/#latest
• IPv6- I feel like we should just remove the page. It’s in alpha, and we’re not aware of any one using it. By marking it as deprecated we risk implying that we’ve decided we don’t intend to support IPv6 at all. In actuality, we want signals that people want this so we can consider it with Flannel. Marking as deprecated may discourage that signal. If we remove we should include in the SE notification portion of my “Non-code complimentary work to address before this is merged” part of my prior comment.

[emosbaugh]

Suggested change

	kURL will not be moving forward with support of this add-on in kURL starting March 23, 2023 and will be fully deprecated after June 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the deprecation date. Please consider using the [Flannel](https://kurl.sh/docs/add-ons/flannel) for your CNI needs moving forward.
	kURL will not be moving forward with support of this add-on starting March 23, 2023 and will be fully removed after June 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the removal date. Please consider using the [Flannel](https://kurl.sh/docs/add-ons/flannel) add-on for your CNI needs moving forward.

[emosbaugh]

Suggested change

	kURL will not be moving forward with support of this add-on in kURL starting March 23, 2023 and will be fully deprecated after April 31st 2023.
	kURL will not be moving forward with support of this add-on starting March 23, 2023 and will be fully removed after April 31st 2023.

[emosbaugh]

Suggested change

	kURL will not be moving forward with support of this add-on in kURL starting March 23, 2023 and will be fully deprecated after September 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the deprecation date. To migrate to [Containerd](https://kurl.sh/docs/add-ons/containerd) please change your kURL spec to containerd to migrate existing installs.
	kURL will not be moving forward with support of this add-on starting March 23, 2023 and will be fully removed after September 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the removal date. Please remove Docker from your spec and replace it with [Containerd](https://kurl.sh/docs/add-ons/containerd) to migrate existing installs.

[kyleprice]

Took the 2nd part and added it to the add-on page. I used Amber's wording for the first part around removal/support.

[emosbaugh]

Suggested change

	Kubenetes 1.24.0+ does not support Dockershim. As a result of this, therefore you must use an alternative CRI, such as [containerd](/docs/add-ons/containerd), instead.
	Kubenetes 1.24.0+ no loner supports Dockershim, therefore you must use an alternative CRI such as [containerd](/docs/add-ons/containerd).

[kyleprice]

Move this to the deprecation section

[emosbaugh]

Suggested change

kURL will not be moving forward with support of this add-on in kURL starting March 23, 2023 and will be fully deprecated after September 31st, 2023. Existing installs that use this add-on will continue to be best-effort supported until the deprecation date. Please consider using the [OpenEBS](https://kurl.sh/docs/add-ons/openebs) or [Rook](https://kurl.sh/docs/add-ons/rook) add-on for your CSI needs moving forward. We offer a migration path for existing customer installs as described [here](https://kurl.sh/docs/install-with-kurl/migrating-csi).

kURL will not be moving forward with support of this add-on starting March 23, 2023 and will be fully removed after September 31st, 2023. Existing installs that use this add-on will continue to be best-effort supported until the removal date. Please consider using the [OpenEBS](https://kurl.sh/docs/add-ons/openebs) or [Rook](https://kurl.sh/docs/add-ons/rook) add-on for your CSI needs moving forward. We offer a migration path for existing customer installs as described [here](https://kurl.sh/docs/install-with-kurl/migrating-csi).

[emosbaugh]

Can we use the term remove rather than deprecate?

[emosbaugh]

Suggested change

kURL will not be moving forward with support of this add-on in kURL starting March 23, 2023 and will be fully deprecated after September 31st 2023. This add-on is no longer supported by the upstream maintainers. Existing installs that use this add-on will continue to be best-effort supported until the deprecation date. Please consider using the [Flannel](https://kurl.sh/docs/add-ons/flannel) for your CNI needs moving forward. We offer a migration path for existing customer installs as described [here](https://kurl.sh/docs/add-ons/flannel#migration-from-weave).

kURL will not be moving forward with support of this add-on starting March 23, 2023 and will be fully removed after September 31st 2023. This add-on is no longer supported by the upstream maintainers. Existing installs that use this add-on will continue to be best-effort supported until the removal date. Please consider using the [Flannel](https://kurl.sh/docs/add-ons/flannel) add-on for your CNI needs moving forward. We offer a migration path for existing customer installs as described [here](https://kurl.sh/docs/add-ons/flannel#migration-from-weave).

[emosbaugh]

Suggested change

	kURL will not be moving forward with support of ipv6 in kURL starting March 23, 2023 and will be fully deprecated after June 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the deprecation date. This is due to the deprecation of the Antrea add-on.
	kURL will not be moving forward with support of ipv6 starting March 23, 2023 and will be fully removed after June 31st 2023. Existing installs that use this add-on will continue to be best-effort supported until the removal date. This is due to the deprecation of the Antrea add-on.

[kyleprice]

Removed this page.

[AmberAlston]

@replicatedhq/replicated-docs - I wanted to make sure you were aware of this pr since I don't see you in the review process yet. The team is planning to push it live in the next couple of days. I have been involved in the review so far on wording, etc.

[paigecalvert]

Thanks @AmberAlston ! @kyleprice , let us know when/if it would be helpful to have a docs review on the language.

[paigecalvert]

@kyleprice before I review any other notices (which I think are all very similar/the same), could you let me know what you think of these edits? I wanted to cut down on the number of words, and also try to clarify phrases like "may no longer be offered by the project".

A couple questions for you:

• "may no longer be offered by the project" --> does this mean that you all are removing it? Would it make sense to say "scheduled to be removed", or maybe "tentatively scheduled to be removed"?
• "after June 31st, 2023" --> does this mean you all are planning to remove it on July 1? Or just anytime after June 31st is fair play?
• "will be best effort supported" --> is it okay to just say that it's supported? or is there a way to clarify what "best effort" includes/excludes?

[kyleprice]

Pretty much we would like to have the option to remove it after x date. We aren't sure if we will remove it or not at the moment but we want to make sure people know its a possibility.

Anytime after June 31st would be fair. We will initially just remove it from the website though after that date.

We can just say it is supported until that date.

[paigecalvert]

done with docs edits @kyleprice !