(WIP) Implement KLT -> Keptn name change

[StackScribe]

Goal

<what do we want to achieve?>

Problem

The product developed under the "Keptn Lifecycle Toolkit", KLT, etc has an official release name of "Keptn".

• All references to “Keptn LTS” or “Keptn V1” in the current Keptn documentation should be consolidated as “Keptn V1”.
• These changes should be done only in the documentation of the current Keptn version and not for V1.
• We will need to add banners in V1 documentation and the “keptn/keptn” repos to inform them of the EoL

Technical Details

The documentation using the new product name needs to be published on 7 September 2023 in coordination with the blog post and announcements.

NO changes will be made to the docs other than those necessary to support the name change during this process. Inevitably, we will uncover some pieces that need work; we will file issues for anything requiring significant work to ensure that we can complete this process quickly.

DoD

Tasks

Beta Give feedback

1. ArtifactHub, Project readme and pinned repo updates community#307
   +0
2. link to the ticket2

[agardnerIT]

I am in favour of moving on from "v1" and making the distinction clearer. There is precedence here too. Flux did it with flux2 (see discussion later) and I'm sure other projects have too.

I don't believe this will work (as currently proposed) for several reasons:

1. It seems like we have a problem but no goal. This requirement is not fully formed yet. This should probably be an KEP which indicates there is a period for community comment - not an issue which kind of implies it's a done deal and ready for implementation.
2. We need to call it "Keptn next gen", "keptn kubernetes native", "KeptnV2" or "Keptn2" or something. Not just Keptn.
3. We need a LOT longer to communicate this to the world than a few weeks.
4. We risk adding further confusion and "brand reputation damage" if we rush this.

Flux Moves to v2: Timeline

If we look at the timeline for flux's move from v1 to v2. As far as I can interpret:

• October 2020: "v1" enters maintenance mode
• February 2021: "v2" reaches feature parity
• June 2021: Project begins encouraging the migration from v1 to v2
• November 2022: v1 obsolete

That's just over 2 years end-to-end and 18 months after feature parity between v1 and v2 was achieved.

CCing some others who may have a viewpoint / opinion on this: @staceypotter @thschue @bradmccoydev

[thisthat]

1. It seems like we have a problem but no goal. This requirement is not fully formed yet. This should probably be an KEP which indicates there is a period for community comment - not an issue which kind of implies it's a done deal and ready for implementation.

There was a KEP to discuss this: keptn/enhancement-proposals#100
I believe the ticket is still a work in progress item from @StackScribe given the question marks and the missing details. I mark it as WIP now.

2. We need to call it "Keptn next gen", "keptn kubernetes native", "KeptnV2" or "Keptn2" or something. Not just Keptn.

Thanks for your input. I suggest discussing this with @DavidPHirsch and @staceypotter

3. We need a LOT longer to communicate this to the world than a few weeks.

The EOL promise is not few weeks, but we have at least to announce EOL 3 months in advance

4. We risk adding further confusion and "brand reputation damage" if we rush this.

I agree with this 👍

[thisthat]

Official announcement: https://keptn.slack.com/archives/CFH4VK9GT/p1691758857265069