baalajimaestro/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Improve doc on sensitive data stored into labels/tags

Browse source
This commit is contained in:
Emile Vauge 2024-07-11 14:40:07 +02:00 committed by GitHub
parent f32884d9b8
commit 127c0a7542
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 40 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/content/routing/providers/consul-catalog.md
View file

@ -12,6 +12,14 @@ A Story of Tags, Services & Instances
Attach tags to your services and let Traefik do the rest! Attach tags to your services and let Traefik do the rest!
One of the best feature of Traefik is to delegate the routing configuration to the application level.
With Consul Catalog, Traefik can leverage tags attached to a service to generate routing rules.
!!! warning "Tags & sensitive data"
We recommend to *not* use tags to store sensitive data (certificates, credentials, etc).
Instead, we recommend to store sensitive data in a safer storage (secrets, file, etc).
## Routing Configuration ## Routing Configuration
!!! info "tags" !!! info "tags"

8
docs/content/routing/providers/docker.md
View file

@ -12,6 +12,14 @@ A Story of Labels & Containers
Attach labels to your containers and let Traefik do the rest! Attach labels to your containers and let Traefik do the rest!
One of the best feature of Traefik is to delegate the routing configuration to the application level.
With Docker, Traefik can leverage labels attached to a container to generate routing rules.
!!! warning "Labels & sensitive data"
We recommend to *not* use labels to store sensitive data (certificates, credentials, etc).
Instead, we recommend to store sensitive data in a safer storage (secrets, file, etc).
## Configuration Examples ## Configuration Examples
??? example "Configuring Docker & Deploying / Exposing Services" ??? example "Configuring Docker & Deploying / Exposing Services"

8
docs/content/routing/providers/ecs.md
View file

@ -10,6 +10,14 @@ A Story of Labels & Elastic Containers
Attach labels to your containers and let Traefik do the rest! Attach labels to your containers and let Traefik do the rest!
One of the best feature of Traefik is to delegate the routing configuration to the application level.
With ECS, Traefik can leverage labels attached to a container to generate routing rules.
!!! warning "Labels & sensitive data"
We recommend to *not* use labels to store sensitive data (certificates, credentials, etc).
Instead, we recommend to store sensitive data in a safer storage (secrets, file, etc).
## Routing Configuration ## Routing Configuration
!!! info "labels" !!! info "labels"

8
docs/content/routing/providers/nomad.md
View file

@ -12,6 +12,14 @@ A story of Tags, Services & Nomads
Attach tags to your Nomad services and let Traefik do the rest! Attach tags to your Nomad services and let Traefik do the rest!
One of the best feature of Traefik is to delegate the routing configuration to the application level.
With Nomad, Traefik can leverage tags attached to a service to generate routing rules.
!!! warning "Tags & sensitive data"
We recommend to *not* use tags to store sensitive data (certificates, credentials, etc).
Instead, we recommend to store sensitive data in a safer storage (secrets, file, etc).
## Routing Configuration ## Routing Configuration
!!! info "tags" !!! info "tags"

8
docs/content/routing/providers/rancher.md
View file

@ -12,6 +12,14 @@ A Story of Labels, Services & Containers
Attach labels to your services and let Traefik do the rest! Attach labels to your services and let Traefik do the rest!
One of the best feature of Traefik is to delegate the routing configuration to the application level.
With Rancher, Traefik can leverage labels attached to a service to generate routing rules.
!!! warning "Labels & sensitive data"
We recommend to *not* use labels to store sensitive data (certificates, credentials, etc).
Instead, we recommend to store sensitive data in a safer storage (secrets, file, etc).
!!! important "This provider is specific to Rancher 1.x." !!! important "This provider is specific to Rancher 1.x."
Rancher 2.x requires Kubernetes and does not have a metadata endpoint of its own for Traefik to query. Rancher 2.x requires Kubernetes and does not have a metadata endpoint of its own for Traefik to query.