Resultado de búsqueda
Traefik will consider HTTP (s) servers healthy as long as they return a status code to the health check request (carried out every interval) between 2XX and 3XX, or matching the configured status. For gRPC servers, Traefik will consider them healthy as long as they return SERVING to gRPC health check v1 requests.
14 de feb. de 2024 · It uses Protocol Buffers as the interface description language, and provides advanced features such as bidirectional streaming and flow control, cancellation, and timeouts. Traefik v3 now supports gRPC-Web, which adds the capability to call a gRPC service from a web app within a browser. Additionally, Jeremy Jacque added gRPC healthchecks ...
traefik --help # or docker run traefik[:version] --help # ex: docker run traefik:1.5 --help Command: bug¶ Here is the easiest way to submit a pre-filled issue on Traefik GitHub. traefik bug Watch this demo. Command: healthcheck¶ This command allows to check the health of Traefik. Its exit status is 0 if Traefik is healthy and 1 if it is ...
11 de abr. de 2022 · In such cases, Traefik Proxy must not terminate the TLS connection but forward the request as is to these services. To configure this passthrough, you need to configure a TCP router, even if your service handles HTTPS. version: "3.9". services: # ... my-tcp-app: image: traefik/whoamitcp:v0.2.1. labels:
Configuration Example. Docker & Swarm. # As a Docker Label whoami: # A container that exposes an API to show its IP address image: traefik/whoami labels: # Create a middleware named `foo-ip-allowlist` - "traefik.tcp.middlewares.foo-ip-allowlist.ipallowlist.sourcerange=127.0.0.1/32, 192.168.1.7" # Apply the middleware named `foo-ip-allowlist` to ...
Attached to the routers, pieces of middleware are a means of tweaking the requests before they are sent to your service (or before the answer from the services are sent to the clients). There are several available middleware in Traefik, some can modify the request, the headers, some are in charge of redirections, some add authentication, and so on.
Traefik uses the Kubernetes API to discover running services. To use the Kubernetes API, Traefik needs some permissions. This permission mechanism is based on roles defined by the cluster administrator. The role is then bound to an account used by an application, in this case, Traefik Proxy. The first step is to create the role.
