Skip to content

Add label field to lkenodepool #786

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

sphan-akamai
Copy link

@sphan-akamai sphan-akamai commented Jul 21, 2025

📝 Description

What does this PR do and why is this change necessary?
This PR adds the Label field to lkenodepool. LKE recently added support for lkenodepool naming via the Label field. (ex., when a customer provides a Label during the creation/update of a lkenodepool, nodes in that nodepool will following this naming convention <lkenodepool namespace>-<lkenodepool label>-<5 char hash>).

✔️ How to Test

What are the steps to reproduce the issue or verify the changes?

How do I run the relevant unit/integration tests?

Unit Tests

Run make test-unit TEST_ARGS='-run TestLKENodePool_Create'
Run make test-unit TEST_ARGS='-run TestLKENodePool_Update'

📷 Preview

If applicable, include a screenshot or code snippet of this change. Otherwise, please remove this section.

@sphan-akamai sphan-akamai requested a review from a team as a code owner July 21, 2025 16:05
@sphan-akamai sphan-akamai requested review from PawelSnoch and yec-akamai and removed request for a team July 21, 2025 16:05
@@ -92,6 +93,7 @@ type LKENodePoolCreateOptions struct {
Tags []string `json:"tags"`
Labels LKENodePoolLabels `json:"labels"`
Taints []LKENodePoolTaint `json:"taints"`
Label string `json:"label,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

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

Can we make it as a pointer to distinguish "" and field omitted in actual API call?

@lgarber-akamai lgarber-akamai removed the request for review from PawelSnoch July 24, 2025 18:10
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.

2 participants