lab/chart/check-test.sh runs pods shaped like the chart's server pod, in a scratch namespace under restricted, with one part of the data layer broken on purpose: wrong PostgreSQL, S3 or NATS credentials, and NATS or S3 refusing the namespace. Each pod must stop in its init container with the right exit code and the part named in its termination message. All six pass with inbuxa/inbuxa-server#473.
The cases that block a service use an ingress policy in data that refuses only the scratch namespace. kindnet doesn't enforce egress rules here: a deny-egress policy in the scratch namespace left Garage reachable. The policy is removed at the end.
frontends-test.sh changes too. PORTS picks the local ports, and the test stops if a port is already taken. Before, the port-forward failed silently and the test talked to whatever was listening. Today that was another session's local server on 18080, which turned up as a confusing sign-in failure.
`lab/chart/check-test.sh` runs pods shaped like the chart's server pod, in a scratch namespace under `restricted`, with one part of the data layer broken on purpose: wrong PostgreSQL, S3 or NATS credentials, and NATS or S3 refusing the namespace. Each pod must stop in its init container with the right exit code and the part named in its termination message. All six pass with inbuxa/inbuxa-server#473.
The cases that block a service use an ingress policy in `data` that refuses only the scratch namespace. kindnet doesn't enforce egress rules here: a deny-egress policy in the scratch namespace left Garage reachable. The policy is removed at the end.
`frontends-test.sh` changes too. `PORTS` picks the local ports, and the test stops if a port is already taken. Before, the port-forward failed silently and the test talked to whatever was listening. Today that was another session's local server on 18080, which turned up as a confusing sign-in failure.
Runs pods shaped like the chart's server pod with one part of the data
layer broken on purpose: wrong PostgreSQL, S3 or NATS credentials, and NATS
or S3 refusing the namespace. Each must stop in its init container with the
right exit code and the part named in its termination message.
frontends-test: PORTS picks the local ports, and a port something else
already listens on stops the test: before, the port-forward failed quietly
and the test talked to whatever was there.
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.
lab/chart/check-test.shruns pods shaped like the chart's server pod, in a scratch namespace underrestricted, with one part of the data layer broken on purpose: wrong PostgreSQL, S3 or NATS credentials, and NATS or S3 refusing the namespace. Each pod must stop in its init container with the right exit code and the part named in its termination message. All six pass with inbuxa/inbuxa-server#473.The cases that block a service use an ingress policy in
datathat refuses only the scratch namespace. kindnet doesn't enforce egress rules here: a deny-egress policy in the scratch namespace left Garage reachable. The policy is removed at the end.frontends-test.shchanges too.PORTSpicks the local ports, and the test stops if a port is already taken. Before, the port-forward failed silently and the test talked to whatever was listening. Today that was another session's local server on 18080, which turned up as a confusing sign-in failure.