cryostatio / cryostatio/cryostat-operator
[Request] Agent auto-config for multiple containers in one Pod
- Dominant language
- Go
- Stars
- 37
- Forks
- 22
- Avg merge
- 21h 37m
- Merged PRs (30d)
- 22
Description
If I have an application where multiple Java containers are deployed together within a single Pod, and I want to use the Operator autoconfig feature to dynamically attach the Cryostat Agent, then there is currently no way for me to get the Agent attached to all of my containers. By default it will choose the first container in the Pod, or I can use a label to specify which container to use by name. It would be good to have some way to use the label to specify multiple names, ex. by comma-separated name values.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Operator autoconfig path that selects the first container or reads the container-name label. Determine how multiple container names should be represented and validated. Done means the label can target multiple Java containers in one Pod and the Cryostat Agent attaches to each, with coverage for the selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100