Closes#5. Every server pod gets an init container running inbuxa --check (inbuxa/inbuxa-server#473). A pod that can't use the data store, blob store or NATS stays in Init:Error, and kubectl describe pod shows the part and why, for example coordinator: credentials refused: nats.data.svc:4222: authorization violation. The server container also keeps its last log lines as its termination message, so a start that fails for another reason shows in the pod status too.
The check is server.check.enabled (on by default) and has small resources of its own. 65 tests pass, and check.sh passes.
Hold for rc.33, like #19: an older server doesn't know --check, and every pod would stop in its init container.
Closes #5. Every server pod gets an init container running `inbuxa --check` (inbuxa/inbuxa-server#473). A pod that can't use the data store, blob store or NATS stays in `Init:Error`, and `kubectl describe pod` shows the part and why, for example `coordinator: credentials refused: nats.data.svc:4222: authorization violation`. The server container also keeps its last log lines as its termination message, so a start that fails for another reason shows in the pod status too.
The check is `server.check.enabled` (on by default) and has small resources of its own. 65 tests pass, and `check.sh` passes.
**Hold for rc.33**, like #19: an older server doesn't know `--check`, and every pod would stop in its init container.
--check (inbuxa/inbuxa-server#473) merged after rc.32 was cut, so this now holds for rc.33. The chart's default is server.check.enabled: true, so on an rc.32 image every pod would stop in Init:Error. Changelog and values say rc.33 now.
`--check` (inbuxa/inbuxa-server#473) merged after rc.32 was cut, so this now holds for **rc.33**. The chart's default is `server.check.enabled: true`, so on an rc.32 image every pod would stop in `Init:Error`. Changelog and values say rc.33 now.
An init container runs inbuxa --check: a pod that can't use the data
store, the blob store or NATS stays in Init:Error, and its status names the
part and why. The server container keeps its last log lines as its
termination message too. server.check, on by default; needs server
27.1-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.
Closes #5. Every server pod gets an init container running
inbuxa --check(inbuxa/inbuxa-server#473). A pod that can't use the data store, blob store or NATS stays inInit:Error, andkubectl describe podshows the part and why, for examplecoordinator: credentials refused: nats.data.svc:4222: authorization violation. The server container also keeps its last log lines as its termination message, so a start that fails for another reason shows in the pod status too.The check is
server.check.enabled(on by default) and has small resources of its own. 65 tests pass, andcheck.shpasses.Hold for rc.33, like #19: an older server doesn't know
--check, and every pod would stop in its init container.--check(inbuxa/inbuxa-server#473) merged after rc.32 was cut, so this now holds for rc.33. The chart's default isserver.check.enabled: true, so on an rc.32 image every pod would stop inInit:Error. Changelog and values say rc.33 now.7d98dfaa43to939bd85a7a