chore: move to Traefik organization.

Co-authored-by: Romain <rtribotte@users.noreply.github.com>

docs/content/user-guides/crd-acme/03-deployments.yml

@@ -68,7 +68,7 @@ spec:
     spec:
       containers:
         - name: whoami
-          image: containous/whoami
+          image: traefik/whoami
           ports:
             - name: web
               containerPort: 80

docs/content/user-guides/crd-acme/index.md

@@ -51,7 +51,7 @@ Also note the RBAC authorization resources; they'll be referenced through the `s
 
 ### Services
 
-Then, the services. One for Traefik itself, and one for the app it routes for, i.e. in this case our demo HTTP server: [whoami](https://github.com/containous/whoami).
+Then, the services. One for Traefik itself, and one for the app it routes for, i.e. in this case our demo HTTP server: [whoami](https://github.com/traefik/whoami).
 
 ```yaml
 --8<-- "content/user-guides/crd-acme/02-services.yml"

docs/content/user-guides/docker-compose/acme-dns/docker-compose.yml

@@ -31,7 +31,7 @@ services:
       - "/var/run/docker.sock:/var/run/docker.sock:ro"
 
   whoami:
-    image: "containous/whoami"
+    image: "traefik/whoami"
     container_name: "simple-service"
     labels:
       - "traefik.enable=true"

docs/content/user-guides/docker-compose/acme-dns/docker-compose_secrets.yml

@@ -46,7 +46,7 @@ services:
       - "/var/run/docker.sock:/var/run/docker.sock:ro"
 
   whoami:
-    image: "containous/whoami"
+    image: "traefik/whoami"
     container_name: "simple-service"
     labels:
       - "traefik.enable=true"

docs/content/user-guides/docker-compose/acme-http/docker-compose.yml

@@ -26,7 +26,7 @@ services:
       - "/var/run/docker.sock:/var/run/docker.sock:ro"
 
   whoami:
-    image: "containous/whoami"
+    image: "traefik/whoami"
     container_name: "simple-service"
     labels:
       - "traefik.enable=true"

docs/content/user-guides/docker-compose/acme-tls/docker-compose.yml

@@ -23,7 +23,7 @@ services:
       - "/var/run/docker.sock:/var/run/docker.sock:ro"
 
   whoami:
-    image: "containous/whoami"
+    image: "traefik/whoami"
     container_name: "simple-service"
     labels:
       - "traefik.enable=true"

docs/content/user-guides/docker-compose/basic-example/docker-compose.yml

@@ -18,7 +18,7 @@ services:
       - "/var/run/docker.sock:/var/run/docker.sock:ro"
 
   whoami:
-    image: "containous/whoami"
+    image: "traefik/whoami"
     container_name: "simple-service"
     labels:
       - "traefik.enable=true"

docs/content/user-guides/docker-compose/basic-example/index.md

@@ -35,7 +35,7 @@ This will also be used as a starting point for the other docker-compose guides.
 
 ## Details
 
-- As an example we use [whoami](https://github.com/containous/whoami) (a tiny Go server that prints os information and HTTP request to output) which was used to define our `simple-service` container.
+- As an example we use [whoami](https://github.com/traefik/whoami) (a tiny Go server that prints os information and HTTP request to output) which was used to define our `simple-service` container.
 
 - We define an entry point, along with the exposure of the matching port within docker-compose, which basically allow us to "open and accept" HTTP traffic: 
 

docs/content/user-guides/marathon.md

@@ -105,7 +105,7 @@ As such, there is no way to handle this situation deterministically.
 
 Finally, Marathon health checks are not mandatory (the default is to use the task state as reported by Mesos), so requiring them for Traefik would raise the entry barrier for Marathon users.
 
-Traefik used to use the health check results as a strict requirement but moved away from it as [users reported the dramatic consequences](https://github.com/containous/traefik/issues/653).
+Traefik used to use the health check results as a strict requirement but moved away from it as [users reported the dramatic consequences](https://github.com/traefik/traefik/issues/653).
 
 #### Draining
 
@@ -117,4 +117,4 @@ However, implementing this fully within Traefik seems like a non-trivial underta
 
 Additionally, the approach is less flexible compared to a custom termination handler since only the latter allows for the implementation of custom termination sequences that go beyond simple request draining (e.g., persisting a snapshot state to disk prior to terminating).
 
-The feature is currently not implemented; a request for draining in general is at [issue 41](https://github.com/containous/traefik/issues/41).
+The feature is currently not implemented; a request for draining in general is at [issue 41](https://github.com/traefik/traefik/issues/41).