Skip to content

gha: shorten conformance-externalworkloads cluster name#33939

Merged
joamaki merged 1 commit intocilium:mainfrom
giorio94:pr/giorio94/main/gha-external-workloads-name
Jul 23, 2024
Merged

gha: shorten conformance-externalworkloads cluster name#33939
joamaki merged 1 commit intocilium:mainfrom
giorio94:pr/giorio94/main/gha-external-workloads-name

Conversation

@giorio94
Copy link
Copy Markdown
Member

The cluster name is used both for the GKE cluster and in the Cilium's context. However, since [1] Cilium imposes a maximum cluster name length of 32 characters. Given the recent increase in the length of the run_id, the generated cluster name is dangerously close to the limit, and can easily exceed it in case of forks if the repository owner name is slightly longer. Hence, let's trim the final suffix to get back a few more characters.

[1]: 3ba429d0f2f6 ("options: formalize and validate cluster name format")

The cluster name is used both for the GKE cluster and in the Cilium's
context. However, since [1] Cilium imposes a maximum cluster name
length of 32 characters. Given the recent increase in the length of
the run_id, the generated cluster name is dangerously close to the
limit, and can easily exceed it in case of forks if the repository
owner name is slightly longer. Hence, let's trim the final suffix
to get back a few more characters.

[1]: 3ba429d0f2f6 ("options: formalize and validate cluster name format")

Signed-off-by: Marco Iorio <[email protected]>
@giorio94 giorio94 added area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Jul 22, 2024
@giorio94 giorio94 requested review from a team as code owners July 22, 2024 12:24
@giorio94
Copy link
Copy Markdown
Member Author

/test

@Artyop
Copy link
Copy Markdown
Contributor

Artyop commented Jul 22, 2024

Hey, not here to hijack Viktor's reviewer role, but do we really need the ${{ github.repository_owner }}- part prefixing the cluster name?
Removing it would allow us to have more lenience toward the increase of the run_id length and avoid crossing this issue in the future

@giorio94
Copy link
Copy Markdown
Member Author

Hey, not here to hijack Viktor's reviewer role, but do we really need the ${{ github.repository_owner }}- part prefixing the cluster name? Removing it would allow us to have more lenience toward the increase of the run_id length and avoid crossing this issue in the future

Not totally sure on the background there, honestly, but all the other workflows also follow a similar pattern for the name. Another possibility could be just explicitly configuring a shorter cluster name for Cilium, but it didn't seem necessary at the moment (also to keep the workflow consistent with the others).

@giorio94 giorio94 removed the request for review from thorn3r July 23, 2024 09:31
@giorio94 giorio94 added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jul 23, 2024
@joamaki joamaki added this pull request to the merge queue Jul 23, 2024
Merged via the queue into cilium:main with commit eeb4973 Jul 23, 2024
@joestringer joestringer mentioned this pull request Jul 24, 2024
10 tasks
@github-actions github-actions bot added backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. and removed backport-pending/1.16 labels Jul 24, 2024
michi-covalent added a commit to cilium/cilium-cli that referenced this pull request Jul 30, 2024
Shorten cluster names to avoid getting this error:

    Error: Unable to install Cilium: execution error at (cilium/templates/validate.yaml:100:5):
    The cluster name is invalid: must not be more than 32 characters.
    Configure 'upgradeCompatibility' to 1.15 or earlier to temporarily
    skip this check at your own risk

Ref: cilium/cilium#33939

Signed-off-by: Michi Mutsuzaki <[email protected]>
michi-covalent added a commit to cilium/cilium-cli that referenced this pull request Jul 31, 2024
Shorten cluster names to avoid getting this error:

    Error: Unable to install Cilium: execution error at (cilium/templates/validate.yaml:100:5):
    The cluster name is invalid: must not be more than 32 characters.
    Configure 'upgradeCompatibility' to 1.15 or earlier to temporarily
    skip this check at your own risk

Ref: cilium/cilium#33939

Signed-off-by: Michi Mutsuzaki <[email protected]>
michi-covalent added a commit that referenced this pull request Aug 5, 2024
[ cherry-picked from cilium/cilium-cli repository ]

Shorten cluster names to avoid getting this error:

    Error: Unable to install Cilium: execution error at (cilium/templates/validate.yaml:100:5):
    The cluster name is invalid: must not be more than 32 characters.
    Configure 'upgradeCompatibility' to 1.15 or earlier to temporarily
    skip this check at your own risk

Ref: #33939

Signed-off-by: Michi Mutsuzaki <[email protected]>
github-merge-queue bot pushed a commit that referenced this pull request Aug 16, 2024
[ cherry-picked from cilium/cilium-cli repository ]

Shorten cluster names to avoid getting this error:

    Error: Unable to install Cilium: execution error at (cilium/templates/validate.yaml:100:5):
    The cluster name is invalid: must not be more than 32 characters.
    Configure 'upgradeCompatibility' to 1.15 or earlier to temporarily
    skip this check at your own risk

Ref: #33939

Signed-off-by: Michi Mutsuzaki <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/CI Continuous Integration testing issue or flake backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. 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.

6 participants