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

Create and Add HasStatus interface on Objects which Actually have Status #93

Open
snowdrop-bot opened this issue Nov 16, 2021 · 0 comments

Comments

@snowdrop-bot
Copy link

Some of the standard Kuberentes objects like ConfigMaps don't use status sub-resource, others like (Deployments, Pods, ...) do.

It would be very useful to have a HasStatus interface similar to HasMetadata to differentiate between those resource. So all the k8s objects would implement HasStatus (with a getter and setter), that use status sub-resource. Other don't.

This would help to implement this issue in Java Operator SDK: operator-framework/java-operator-sdk#667

It might be an ide to also support this in the CustomResource abstraction, currently all custom resource POJO has status, although in k8s this is not necessarily true. CRD can define a custom resource without status subresource.


fabric8io#3586


$upstream:3586$

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants