Skip to content

Instantly share code, notes, and snippets.

Damien Duportal dduportal

Block or report user

Report or block dduportal

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View docker-whoami.yml
version: '3'
services:
webapp:
image: containous/whoami
# Move this directive under the "deploy:" if you are deploying to swarm instead of standalone Docker Engine
labels:
# Traefik v1
- "traefik.frontend.rule=Host:whoami.localhost"
# Traefik v2
View main.tf
provider "aws" {
region = "eu-west-2"
version = "~> 2.0"
}
variable "base_domain" {
type = "string"
description = "Base domain used for this experimentation"
default = "damienduportal.org"
}
View docker-compose.yml
version: '3.7'
services:
reverse-proxy:
image: traefik:${TRAEFIK_LATEST_STABLE}
command:
- "--docker"
- "--api"
ports:
- "80:80"
@dduportal
dduportal / README.md
Last active May 29, 2019
traefik-cloudbees-jenkins
View README.md

CloudBees Jenkins License Wizard Issue with Traefik and Firefox

Requirements

  • Docker Engine
  • docker-compose

Prepare Environment

With the docker-compose.yml file provided in this gist,

View minikube-traefik-depl-svc.yaml
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: traefik-ingress-controller
namespace: kube-system
---
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
View docker-compose.yml
version: '3.4'
networks:
front:
docker-sock:
services:
lb:
image: traefik:1.7.11
command:
@dduportal
dduportal / docker-compose.yml
Created Apr 16, 2019
Traefik Path examples
View docker-compose.yml
version: '2.4'
services:
lb:
image: traefik:1.7.10
command:
- "--docker.domain=localhost"
- "--api"
ports:
- "80:80"
@dduportal
dduportal / Q & A.adoc
Last active Apr 1, 2019
Q & A Online Meetup: Back to Traefik 2.0 - Gigawatts of Routing Power
View Q & A.adoc
@dduportal
dduportal / Q&A.adoc
Last active Feb 27, 2019
Q&A of Traefik Online Meetup #1: Keep the Routing Simple
View Q&A.adoc

Q&A of Traefik Online Meetup #1: Keep the Routing Simple

Question: Doesn’t the web container need to use dynamic ports, and not port 80?

Answer: A container doesn’t need to publish/forward to any port on the outside. It listens on a port, for example, port 80, from its own private IP address, inside the Docker private network. The value of Traefik is to route requests from the outside on a chosen port, for example, port 80 or 443, of the public address, to the private IP address of the web server. Traefik watches for Docker’s API to get this private IP, and for any change of this private IP (e.g. on a container reboot). Also, you can have as many containers as you want, listening on their own port 80 without any conflict: useful for blue/green deployments, for example. You can find more information here: https://docs.Traefik.io/v1.7/basics/#concepts.


Question: Could you create the Jenkins link also with a Host:jenkins.demo.containous.cloud, and no other option (i.e. no tweak on Jenkins, no

View helm-rbac-config.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: tiller
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: tiller
You can’t perform that action at this time.