-
Notifications
You must be signed in to change notification settings - Fork 0
Don't stop reconciling if one of the objects is not deserializable #211
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
Comments
Will discuss with upstream kube-rs (and maybe k8s-openapi?) on where to go from here. |
kube-rs/kube#1556 is merged, we should be able to trial-migrate an operator to |
Trial PR: stackabletech/nifi-operator#662 |
The Nifi-Operator PR has now been updated to use the release builds. |
Nifi-Operator PR is merged, ready for wider rollout. |
* Migrate to DeserializeGuard Part of stackabletech/issues#211 * Changelog
* Migrate to DeserializeGuard Part of stackabletech/issues#211 * Changelog
* Migrate to DeserializeGuard Part of stackabletech/issues#211 * Changelog
Some cases have been migrated to PartialObjectMeta instead where only the metadata is used anyway. Part of stackabletech/issues#211. Fixes #237.
* Migrate to DeserializeGuard Some cases have been migrated to PartialObjectMeta instead where only the metadata is used anyway. Part of stackabletech/issues#211. Fixes #237. * Changelog * Avoid requesting CM/secret data entirely Instead of requesting it but throwing it away.
Aaand that should be all of them, nice! |
Great work! Thank you! |
Currently our watchers break entirely if any object fails to deserialize. Ideally this should be confined to only affect the object in question.
The prerequisites have been done by fixing kube-rs and bringing the necessary changes into operator-rs. A sample implementation has also been done for NiFi, we now need to roll this out across the board.
The text was updated successfully, but these errors were encountered: