Skip to content

Conversation

@rainest
Copy link
Contributor

@rainest rainest commented Jul 6, 2023

Use the metallb implementation from 0.31, as the old implementation no longer works.

To handle backports in KIC 2.5, we need to continue using KTF 0.15. KTF includes dependencies on client-go, GWAPI, etc., and upgrading those by pulling in the new KTF breaks API compatibility for 2.5. However, the 0.15 metallb addon no longer works.

This change pulls in the latest addon in its entirety and creating a release branch in prep to release a 0.15.2. This technically breaks semver because it's new functionality (although it does not break API compatibility), but I'm not sure what we can really do otherwise since we can't exactly bump the minor version (0.16 already exists). We may want to consider cutting new KTF major releases when we want to do a KIC LTS, although this tightly couples KTF version bumps to something it's not directly.

Use the metallb implementation from 0.31, as the old implementation no
longer works.
@rainest rainest requested a review from a team as a code owner July 6, 2023 21:59
pmalek
pmalek previously approved these changes Jul 7, 2023
Copy link
Member

@pmalek pmalek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This technically breaks semver because it's new functionality

We're pre v1 (do what you want/need) so that doesn't break semver.

@pmalek
Copy link
Member

pmalek commented Jul 7, 2023

The CI is not functional though 😢

@rainest rainest had a problem deploying to integration-tests July 7, 2023 16:29 — with GitHub Actions Failure
@rainest rainest had a problem deploying to integration-tests July 8, 2023 00:13 — with GitHub Actions Failure
@rainest rainest force-pushed the metallb-backport branch from 021a93d to 9c04418 Compare July 8, 2023 00:16
@rainest rainest had a problem deploying to integration-tests July 8, 2023 00:16 — with GitHub Actions Failure
@rainest rainest force-pushed the metallb-backport branch from 9c04418 to b0a6297 Compare July 8, 2023 00:36
@rainest rainest had a problem deploying to integration-tests July 8, 2023 00:36 — with GitHub Actions Failure
@rainest rainest force-pushed the metallb-backport branch 2 times, most recently from 97dead0 to 76c5200 Compare July 8, 2023 00:50
@rainest rainest force-pushed the metallb-backport branch from 76c5200 to 5d9c883 Compare July 8, 2023 00:52
@rainest rainest requested a review from pmalek July 10, 2023 17:17
@rainest rainest merged commit 0cbfca3 into release/0.15.x Jul 10, 2023
@rainest rainest deleted the metallb-backport branch July 10, 2023 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants