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.

Sign up for GitHub

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

Jump to bottom

Use apivalidation.ValidateImmutableField instead of field.Forbidden #1175

Closed
Gekko0114 opened this issue Oct 3, 2023 · 1 comment · Fixed by #1179
Closed

Use apivalidation.ValidateImmutableField instead of field.Forbidden #1175

Gekko0114 opened this issue Oct 3, 2023 · 1 comment · Fixed by #1179
Assignees
@Gekko0114
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@Gekko0114
Copy link
Member

What would you like to be cleaned:
When validating CRDs, we should use apivalidation.ValidateImmutableField instead of field.Forbidden for simplicity.
Also discussed here #1081
@Gekko0114 Gekko0114 added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Oct 3, 2023
@Gekko0114
Copy link
Member Author

/assign

@Gekko0114 Gekko0114 mentioned this issue Oct 4, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Gekko0114 Gekko0114

Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use apivalidation.ValidateImmutableField instead of field.Forbidden Gekko0114/kueue
1 participant
@Gekko0114