https://github.com/pcfens/traefik-localplugins

A demo of local plugins in Traefik
https://github.com/pcfens/traefik-localplugins

Last synced: about 1 month ago
JSON representation

A demo of local plugins in Traefik

• Host: GitHub
• URL: https://github.com/pcfens/traefik-localplugins
• Owner: pcfens
• Created: 2021-12-16T20:54:41.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-03-02T22:13:31.000Z (almost 3 years ago)
• Last Synced: 2024-10-26T22:10:41.748Z (2 months ago)
• Language: Dockerfile
• Size: 16.6 KB
• Stars: 2
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Traefik Local Plugins

=====================

A demo of Traefik local plugins running in Kubernetes.

To demonstrate that the local plugin is running we'll block exploits against log4j.

To test the ondemand plugin, the service we're testing against will be shut down if it's idle

for an hour (that value can be chagned at the bottom of `k8s-demo/whoami.yaml`).

## Prerequisites

This demo can be run in any k8s cluster that isn't already using Traefik, but to follow

along with this README, you'll need:

* This repository cloned locally

* [kind](https://kind.sigs.k8s.io/)

* A web browser

* cURL

## Running the Demo

First, start everything up, including your local Kubernetes cluster

```bash

kind create cluster --image=kindest/node:v1.23.0

kubectl apply -k k8s-demo/

```

Wait about a minute for things to get stable. When things are done, you should

have 4 running pods.

Once things are up, you'll want at least 3 terminal windows:

1. Port-forward the Traefik main ingress port

  

  `kubectl port-forward svc/traefik-ingress 8000:80`

2.  Port-forward the [Traefik dashboard](http://localhost:8080/dashboard/) (login with admin/password)

  

  `kubectl port-forward svc/traefik-admin 8080`

3. A place to run cURL commands:

Running `curl -v -H 'Host: example.com' -H 'User-Agent: ${${lower:j}ndi:ldap://127.0.0.1/a}' http://localhost:8000` should fail with the response code `500`.

Running `curl -v -H 'Host: example.com' http://localhost:8000` will return a 200 with

some information about the request as expected, since you're not trying to exploit anything

If you let things sit idle for an hour or so, you'll see a startup page when you visit

http://localhost:8080 in your browser. The shutdown is useless for demoing the log4j filter,

but it works well to demonstrate multiple local plugins running at the same time.

## Cleaning Up

When you're done, you can run `kind delete cluster` and the cluster we created will be turned off.