Skip to content

CLOUDP-316083: Add Unified State Machine support libraries #2359

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

josvazg
Copy link
Collaborator

@josvazg josvazg commented May 30, 2025

Summary

Add support for the Unified State Machine.

Proof of Work

This has been tested in #2313

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?
  • Have you signed our CLA?

@josvazg josvazg requested a review from a team as a code owner May 30, 2025 11:15
@josvazg josvazg temporarily deployed to openshift-test May 30, 2025 11:33 — with GitHub Actions Inactive
Comment on lines +134 to +136
if u, ok := clientObj.(*unstructured.Unstructured); ok {
u.SetGroupVersionKind(r.unstructuredGVK)
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q: Why do you need this check?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This came straight from the PoC using unstructured CRDs, I believe we do not need it for our controllers, but...
Qe might still test with unstructured data sometime?

I will let @s-urbaniak chime in to confirm whether or not we might need this going forward, even if not for production code.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is needed if we are reconciling unstructured. For unstructured objects we must set the GVK otherwise the underlying shared index informer won't be able to find it in the cache, it won't know what type it is.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yet the question remains, are we going to use unstructured at all? when?

I suspect we might use it for some experiments on the side. This being expected to be a library I guess it merits the flexibility to support unstructured. Right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think it is fine to leave the support for unstructured, mostly for proof of concepts.

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

Successfully merging this pull request may close these issues.

3 participants