kudobuilder / kudobuilder/kuttl
Background Process Readiness Probe
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 824
- Forks
- 103
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 6
Description
When the BG process is started KUTTL moves forward with other commands (and tests).. however the commands could need the BG process to be ready to success. We do want to the process in the background however we need to know when it is live.
An example use case:
commands:
- command: ./bin/kubectl-kudo init --crd-only - command: ./bin/kubectl-kudo init --crd-only
- command: ./bin/manager
background: true
- command: ./bin/kubectl-kudo install --skip-instance ./repository/cassandra/3.11/operator/
The kudo install command will fail if manager isn't ready. We need manager to be "ready" before the install command.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating how KUTTL launches background commands and represents command configuration, then determine how a readiness condition could be specified and observed. Done means later commands wait until the background process is ready instead of failing because it has not started.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100