K-S6 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
The chart's pre-flight check and Kubernetes events need to tell 'can't reach PostgreSQL' from 'bad credentials' from 'bad config'.
Done when
Distinct log line and exit code per case, documented
**K-S6** · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
The chart's pre-flight check and Kubernetes events need to tell 'can't reach PostgreSQL' from 'bad credentials' from 'bad config'.
**Done when**
- Distinct log line and exit code per case, documented
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:40 +00:00
Done in #472: each data store failure at start-up now has its own first words and exit code. The docs are inbuxa/inbuxa.org#174, which ships with rc.32.
Done in #472: each data store failure at start-up now has its own first words and exit code. The docs are inbuxa/inbuxa.org#174, which ships with rc.32.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-S6 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
The chart's pre-flight check and Kubernetes events need to tell 'can't reach PostgreSQL' from 'bad credentials' from 'bad config'.
Done when
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Started: #472.
Done in #472: each data store failure at start-up now has its own first words and exit code. The docs are inbuxa/inbuxa.org#174, which ships with rc.32.