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.

Sign up for GitHub

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

Jump to bottom

Deprecate FlightRecorder/Recording APIs #349

Closed
ebaron opened this issue Mar 2, 2022 · 1 comment · Fixed by #356
Closed

Deprecate FlightRecorder/Recording APIs #349

ebaron opened this issue Mar 2, 2022 · 1 comment · Fixed by #356
Milestone
2.1.0

Comments

@ebaron
Copy link
Member

ebaron commented Mar 2, 2022

These APIs are falling behind in capabilities compared to the Cryostat HTTP API and web client. While it is interesting to have recording management functionality available through CRDs, it's currently too great of a maintenance burden. The operator will focus on deploying and customizing Cryostat.
@ebaron ebaron added this to the 2.1.0 milestone Mar 2, 2022
@ebaron
Copy link
Member Author

ebaron commented Mar 17, 2022

Deprecating should be fine, but before these can be removed, these CRDs must be replaced in the Cryostat permissions API:
https://github.com/cryostatio/cryostat/blob/42d92207a318b11083332adb671c03b98f958aaa/src/main/java/io/cryostat/net/OpenShiftAuthManager.java#L579-L580

This was referenced Mar 25, 2022
Merged
Closed
This was referenced Apr 13, 2022
Closed
Closed
Closed
Closed
@ebaron ebaron mentioned this issue May 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.1.0
Development

Successfully merging a pull request may close this issue.

fix(api): deprecate FlightRecorder and Recording CRDs ebaron/cryostat-operator
1 participant
@ebaron