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
Rationalize KubernetesList/BaseKubernetesList/DefaultKubernetesResourceList #3906
Comments
Ideal state is:
Since the generation logic seems more involved that I want to mess with, that means we need to keep KubernetesResourceList as the resource lists will not have a common base with the other lists. From there no matter what I try if I have a generic BaseKubernetesList something fails with the buildable logic with KubernetesList - if BaseKubernetesList is not buildable, the KubernetesListFluent isn't aware of the necessary fields. If BaseKubernetesList is buildable, I get:
So I think that means the I'm stuck. If we want to retain a KubernetesList builder, then we cannot improve on the current set of classes other than to deprecate CustomResourceList |
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! |
Shall we go ahead with the CustomResourceList deprecation? |
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! |
Is your task related to a problem? Please describe
These classes after #3628 there are further cleanups that can be made to several list classes.
Describe the solution you'd like
KubernetesList should implement KubernetesResourceList.- it already doesDescribe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: