Skip to content

clustermesh up/downgrade: test maxConnectedCluster#30446

Merged
aanm merged 1 commit intomainfrom
pr/thorn3r/clustermesh511UpDownTest
Feb 14, 2024
Merged

clustermesh up/downgrade: test maxConnectedCluster#30446
aanm merged 1 commit intomainfrom
pr/thorn3r/clustermesh511UpDownTest

Conversation

@thorn3r
Copy link
Copy Markdown
Contributor

@thorn3r thorn3r commented Jan 25, 2024

Configure the max-connected-clusters option for feature coverage in the ClusterMesh upgrade/downgrade tests.

Previously, all clusters in the matrix were using the default value of
255. Now, 2 of the clusters will be configured to support up to 511 clusters. While we are not utilizing the full range of cluster IDs in the test, this feature changes the way identities are allocated and parsed. Enabling this will provide additional test coverage for this aspect.

@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jan 25, 2024
@thorn3r
Copy link
Copy Markdown
Contributor Author

thorn3r commented Jan 25, 2024

/test

@thorn3r thorn3r added the kind/enhancement This would improve or streamline existing functionality. label Jan 25, 2024
@thorn3r thorn3r marked this pull request as ready for review January 25, 2024 19:09
@thorn3r thorn3r requested review from a team as code owners January 25, 2024 19:09
@thorn3r thorn3r requested review from aanm, marseel and tklauser January 25, 2024 19:09
@aanm aanm enabled auto-merge January 26, 2024 10:46
Copy link
Copy Markdown
Member

@marseel marseel left a comment

Choose a reason for hiding this comment

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

LGTM, but pending unresolved Marco's comment

Configure the max-connected-clusters option for feature coverage in the
ClusterMesh upgrade/downgrade tests.

Previously, all clusters in the matrix were using the default value of
255. Now, 2 of the clusters will be configured to support up to 511
clusters. While we are not utilizing the full range of cluster IDs in
the test, this feature changes the way identities are allocated and
parsed. Enabling this will provide additional test coverage for this aspect.

Signed-off-by: Tim Horner <timothy.horner@isovalent.com>
@thorn3r thorn3r force-pushed the pr/thorn3r/clustermesh511UpDownTest branch from 613352b to 319bf88 Compare January 26, 2024 13:48
@thorn3r
Copy link
Copy Markdown
Contributor Author

thorn3r commented Jan 26, 2024

/test

@tklauser tklauser added the release-note/ci This PR makes changes to the CI. label Jan 30, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jan 30, 2024
@thorn3r
Copy link
Copy Markdown
Contributor Author

thorn3r commented Feb 14, 2024

/ci-gateway-api

@aanm aanm added this pull request to the merge queue Feb 14, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Feb 14, 2024
Merged via the queue into main with commit 03dd16f Feb 14, 2024
@aanm aanm deleted the pr/thorn3r/clustermesh511UpDownTest branch February 14, 2024 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/enhancement This would improve or streamline existing functionality. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants