feat(status): CR status for database and storage secrets #825
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to Cryostat! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
git commit -S -m "YOUR_COMMIT_MESSAGE"
Related to #710
Description of the change:
v1beta2
since they are only applicable in Cryostat3.0
.kubectl get cryostat
(default output).NAME APPLICATION URL TARGET NAMESPACES STORAGE SECRET DATABASE SECRET cryostat-sample https://cryostat-sample-myns.apps-crc.testing ["myns"] cryostat-sample-storage-secret-key cryostat-sample-db
xDescriptors={"urn:alm:descriptor:io.kubernetes:Secret"}
for Secrets. On OpenShift, this should render the status fields as clickable links to view the corresponding secrets.Motivation for the change:
Status fields for database and storage secrets are missing in the Cryostat CR. These fields would also be useful for tackling #475.
How to manually test: