Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Create and Add `HasStatus` interface on Objects which Actually have Status
See original GitHub issueSome 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: https://github.com/java-operator-sdk/java-operator-sdk/issues/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.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
From Java Operator SDK perspective this issues can be closed. For now only the automated observed generation aware functionality would require this. However, it does not makes that much sense for well known Kubernetes resources since the status is already handled by the original controller.
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!