coreweave/traefik

coreweave/traefik

Description: The Cloud Native Application Proxy - On CoreWeave Cloud

Language: Go

License: MIT

Stars: 0

Forks: 0

Open issues: 0

Created: 2024-09-30T19:34:06Z

Pushed: 2025-01-27T15:55:57Z

Default branch: coreweave

Fork: yes

Parent repository: traefik/traefik

Archived: no

README:

 

Traefik (pronounced _traffic_) is a modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components (Docker, Swarm mode, Kubernetes, Marathon, Consul, Etcd, Rancher, Amazon ECS, ...) and configures itself automatically and dynamically. Pointing Traefik at your orchestrator should be the _only_ configuration step you need.

---

. [Overview](#overview) . [Features](#features) . [Supported backends](#supported-backends) . [Quickstart](#quickstart) . [Web UI](#web-ui) . [Documentation](#documentation) .

. [Support](#support) . [Release cycle](#release-cycle) . [Contributing](#contributing) . [Maintainers](#maintainers) . [Credits](#credits) .

---

:warning: Please be aware that the old configurations for Traefik v1.x are NOT compatible with the v2.x config as of now. If you're running v2, please ensure you are using a v2 configuration.

Overview

Imagine that you have deployed a bunch of microservices with the help of an orchestrator (like Swarm or Kubernetes) or a service registry (like etcd or consul). Now you want users to access these microservices, and you need a reverse proxy.

Traditional reverse-proxies require that you configure _each_ route that will connect paths and subdomains to _each_ microservice. In an environment where you add, remove, kill, upgrade, or scale your services _many_ times a day, the task of keeping the routes up to date becomes tedious.

This is when Traefik can help you!

Traefik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world -- without further intervention from your part.

Run Traefik and let it do the work for you! _(But if you'd rather configure some of your routes manually, Traefik supports that too!)_


Features

• Continuously updates its configuration (No restarts!)
• Supports multiple load balancing algorithms
• Provides HTTPS to your microservices by leveraging Let's Encrypt (wildcard certificates support)
• Circuit breakers, retry
• See the magic through its clean web UI
• WebSocket, HTTP/2, GRPC ready
• Provides metrics (Rest, Prometheus, Datadog, Statsd, InfluxDB)
• Keeps access logs (JSON, CLF)
• Fast
• Exposes a Rest API
• Packaged as a single binary file (made with :heart: with go) and available as an official docker image

Supported Backends

• Docker / Swarm mode
• Kubernetes
• Marathon
• Rancher (Metadata)
• ECS
• File

Quickstart

To get your hands on Traefik, you can use the 5-Minute Quickstart in our documentation (you will need Docker).

Web UI

You can access the simple HTML frontend of Traefik.


Documentation

You can find the complete documentation of Traefik v2 at https://doc.traefik.io/traefik/.

A collection of contributions around Traefik can be found at https://awesome.traefik.io.

Support

To get community support, you can:

If you need commercial support, please contact Traefik.io by mail: .

Download

• Grab the latest binary from the releases page and run it with the sample configuration file:

./traefik --configFile=traefik.toml

• Or use the official tiny Docker image and run it with the sample configuration file:

docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik

• Or get the sources:

git clone https://github.com/traefik/traefik

Introductory Videos

You can find high level and deep dive videos on videos.traefik.io.

Maintainers

We are strongly promoting a philosophy of openness and sharing, and firmly standing against the elitist closed approach. Being part of the core team should be accessible to anyone who is motivated and want to be part of that journey! This [document](docs/content/contributing/maintainers-guidelines.md) describes how to be part of the [maintainers' team](docs/content/contributing/maintainers.md) as well as various responsibilities and guidelines for Traefik maintainers. You can also find more information on our process to review pull requests and manage issues in this document.

Contributing

If you'd like to contribute to the project, refer to the [contributing documentation](CONTRIBUTING.md).

Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project, you agree to abide by its terms.

Release Cycle

• We usually release 3/4 new versions (e.g. 1.1.0, 1.2.0, 1.3.0) per year.
• Release Candidates…