cryostatio / cryostatio/cryostat-operator
Deployment broken in `default` namespace
Open
bug
- Dominant language
- Go
- Stars
- 37
- Forks
- 22
- Avg merge
- 21h 37m
- Merged PRs (30d)
- 22
Description
See previous discussion: https://github.com/rh-jmc-team/container-jfr-operator/pull/176
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the previous discussion in PR 176, the only reference in this issue, and trace the deployment failure in the operator’s Kubernetes deployment path. Done means deployment succeeds in the default namespace; the issue names no file or test, so confirm the affected entry point and validation steps from that discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100