cryostatio / cryostatio/cryostat-operator
[Story] Add operator logs to Scorecard tests
- Dominant language
- Go
- Stars
- 37
- Forks
- 22
- Avg merge
- 21h 37m
- Merged PRs (30d)
- 22
Description
I've observed a strange Scorecard test failure for the `cryostat-cr` test. The Cryostat deployment was never created before the timeout occurred. The logs show repeated messages of:
```
deployment cryostat-cr is not yet found
```
There might be some useful information in the operator pod logs as to why this occurred.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Scorecard test for `cryostat-cr` and trace the timeout path where the deployment is reported as not found. Check how operator pod logs can be collected there. Done means the relevant operator logs are included when this test fails, providing context for deployment-creation timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100