Skip to content

Conversation

@rytswd
Copy link
Member

@rytswd rytswd commented Oct 11, 2025

This is a common label handling logic that will be used by many resources.

Copy link
Collaborator

@fernando-villalba fernando-villalba left a comment

Choose a reason for hiding this comment

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

As far as I can tell, it looks mostly perfect, just have two small questions about potential oversights.

@rytswd
Copy link
Member Author

rytswd commented Oct 12, 2025

@fernando-villalba With b2632ea, I moved all the tests into a separate package. There are a few more minor commits as well. If you could take another look, that would be appreciated!

Copy link
Collaborator

@fernando-villalba fernando-villalba left a comment

Choose a reason for hiding this comment

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

LGTM!

@rytswd
Copy link
Member Author

rytswd commented Oct 12, 2025

Going ahead with the merge, any impl adjustment can happen iteratively

@rytswd rytswd merged commit 7a70266 into main Oct 12, 2025
8 checks passed
@rytswd rytswd deleted the resource-handler-metadata-label-utility branch October 12, 2025 12:14
// Parameters:
// - resourceName: The name of the custom resource instance (e.g., "my-etcd-cluster")
// - componentName: The component type (e.g., "etcd", "gateway", "orch", "pooler")
// - cellName: Optional cell name. If empty, no cell label is added.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe remove this comment now we are doing a default?

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