healthcheck | Write simple healthcheck functions for your Flask apps

So change your .env to contain

When a backend service's health check parameters are inferred from a serving Pod's readiness probe, GKE does not keep the readiness probe and health check synchronized. Hence any changes you make to the readiness probe will not be copied to the health check of the corresponding backend service on the load balancer as per 2.

In your scenario, the backend is healthy when it follows path ‘/’ but showing unhealthy when it uses path ‘/api’, so there might be some misconfiguration in your ingress.

I would suggest you to add the annotations: ingress.kubernetes.io/rewrite-target: /api so the path mentioned in spec.path will be rewritten to /api before the request is sent to the backend service.

sail down --rmi all -v

Old volumes was deleted and ploblem was solved.

So please use v1.1.4 instead of v1.1.1

Also make sure that you have mounted crypto config correctly, try to access this path inside the container /tmp/crypto/peerOrganizations/acme.com/tlsca/tlsca.acme.com-cert.pem

Try to change tlsCACerts path to use peer tls ca.crt /tmp/crypto/peerOrganizations/acme.com/peers/peer1.acme.com/tls/ca.crt

You have mentioned that the same configurations works with hyperledger fabric v2, if you have tried it locally not on the same server so I please disable the firewall on the server and give it a try

To check if you can reach domain and port please try this

cat > /dev/tcp/peer1.acme.com/7051

Check this https://support.bluemedora.com/s/article/Using-Bash-to-test-if-a-TCP-port-on-a-remote-system-is-open

Although you can create a TestModule and simply import your module as you have done above, I would only consider doing that when the module contained a single component (even then I wouldn't as I don't think its very good practice).

The more components you bring into your test:

• The more moving parts you need to manage
• The more you have to mock
• The less portability you have with the unit and its test
• The more aspirin you ingest trying resolve self induced headaches that occur every time you modify its parent module

Nests TestingModule enables you to "rig" up an independent module with the bare minimum needed to test your component in isolation. It simplifies your test setups and mock creation/management.

Always try to look at unit testing as a stand alone, independent processes. Limit the scope and dependencies wherever possible to make testing as effective and easy as possible.

Here is an example of the approach I take for unit testing a service where I mock out its dependencies:

The solution was to add http headers and a status code to the response: