Skip to content
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

[Feature] Strategy to handle very long CR name #3076

Open
1 of 2 tasks
kevin85421 opened this issue Feb 19, 2025 · 2 comments
Open
1 of 2 tasks

[Feature] Strategy to handle very long CR name #3076

kevin85421 opened this issue Feb 19, 2025 · 2 comments
Assignees
Labels
1.4.0 enhancement New feature or request

Comments

@kevin85421
Copy link
Member

kevin85421 commented Feb 19, 2025

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

Two possible solutions:

  1. Chunk the K8s resource name if it is very long.
  2. Validate the CR name and create an issue if it is invalid

Maybe we need both strategies. If the resource name needs to be deterministic, we must use (2). Otherwise, (1) is OK.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@kevin85421 kevin85421 added enhancement New feature or request triage 1.4.0 and removed triage labels Feb 19, 2025
@kevin85421
Copy link
Member Author

/assign @rueian

@rueian
Copy link
Contributor

rueian commented Feb 19, 2025

👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.4.0 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants