-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add hasSpec
Abstraction Over Kubernetes Resource
#3816
Labels
Milestone
Comments
Relates to #3586 |
Updated the description. We will need also |
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Would like to re-open this as this should still be addressed, imo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your enhancement related to a problem? Please describe
In Java Operator SDK we would like to automate some of the aspects of dependent resource management. In a default use-case when a reconciliation happens, the spec of the target resource is compared to the spec of the actual resource. Currently we use
hasMetadata
as the base class, would be great to have access to the specs through some abstraction.Describe the solution you'd like
Having
hasSpec
of a standalone interface or as an interface that extendshasMetadata
.Could look like this:
Describe alternatives you've considered
Alternative is read this via reflection. What is not the most elegant solution.
Additional context
No response
The text was updated successfully, but these errors were encountered: