This is a compendium of common errors.
- The error occurs when a container is trying to make an https request but doesn't have any SSL certificates installed locally. Note that these do not have to be signed by a CA.
- This happens when a Dockerfile is created for the container
- This commonly occurs when addressing a service
foofrom a service
bar, both of which are within the cluster
Consider the following scenario:
foois externally accessible at
https://foo.example.comwith tls-termination and has the port 3000 open on the container.
- The right way to access the service
foofrom within the cluster is by targeting
- Note the http and https above.
- Addressing the service
foofrom within the cluster as
- In case it is imperative that some ingress rules and proxy conditions are to be applied to inbound traffic, take a look at this and this
- The most common cause is a port misconfiguration
- Verify that
livenessProbeare targeting the correct container port and that the container port is returning a
200for that probe
Please refer to Working with Cloudflare
Updated about 2 months ago