Giter Club home page Giter Club logo

mesh-helm-chart's Introduction

Traefik

Build Status SemaphoreCI Docs Go Report Card License Join the community support forum at https://community.traefik.io/ Twitter

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, Consul, Etcd, Rancher v2, Amazon ECS, ...) and configures itself automatically and dynamically. Pointing Traefik at your orchestrator should be the only configuration step you need.


. Overview . Features . Supported backends . Quickstart . Web UI . Documentation .

. Support . Release cycle . Contributing . Maintainers . Credits .


⚠️ 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!)

Architecture

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 2.X)
  • Keeps access logs (JSON, CLF)
  • Fast
  • Exposes a Rest API
  • Packaged as a single binary file (made with ❤️ with go) and available as an official docker image

Supported Backends

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.

Web UI Providers

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:

  • join the Traefik community forum: Join the chat at https://community.traefik.io/

If you need commercial support, please contact Traefik.io by mail: mailto:[email protected].

Download

./traefik --configFile=traefik.toml
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 describes how to be part of the maintainers' team 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.

Please note that this project is released with a Contributor Code of Conduct. 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 are available before the release (e.g. 1.1.0-rc1, 1.1.0-rc2, 1.1.0-rc3, 1.1.0-rc4, before 1.1.0).
  • Bug-fixes (e.g. 1.1.1, 1.1.2, 1.2.1, 1.2.3) are released as needed (no additional features are delivered in those versions, bug-fixes only).

Each version is supported until the next one is released (e.g. 1.1.x will be supported until 1.2.0 is out).

We use Semantic Versioning.

Mailing Lists

Credits

Kudos to Peka for his awesome work on the gopher's logo!.

The gopher's logo of Traefik is licensed under the Creative Commons 3.0 Attributions license.

The gopher's logo of Traefik was inspired by the gopher stickers made by Takuya Ueda. The original Go gopher was designed by Renee French.

mesh-helm-chart's People

Contributors

charlie-haley avatar kevinpollet avatar mmatur avatar ornell avatar skwair avatar tommoulard avatar wlun001 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mesh-helm-chart's Issues

Configurable Jaeger PodDisruptionBudget

Installing the chart with the default values results in jaeger workload created with a hardcoded replica: 1 and a PodDisruptionBudget with minAvailable: 1.
This prevents operations such as draining the node which could occurs during node maintenance or upgrade.
It would be great if we could configure the PodDisruptionBudget in a way that we can:

  • set minAvailable
  • set maxUnavailable
  • disable/enable it

Cheers and thanks for the great work.

Use apiextensions.k8s.io/v1 CustomResourceDefinition

Currently, we are using apiextensions.k8s.io/v1beta1 for CustomResourceDefinition however this is deprecated and from k8s v1.22+ it will be removed. We need to make changes so that from v1.21 we start using apiextensions.k8s.io/v1

If you run helm install traefik-mesh traefik-mesh/traefik-mesh on v1.20 cluster it will give the below warning:

W0810 11:35:34.854762   15294 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

Traefik Proxy + Mesh

Why traefik proxy is deployed alongside this helm chart? It does have its own helm chart and I quite do not understand the reason for having it here. Would be nice to have an option to disable it.

Do not deploy metrics and tracing Helm charts by default

Feature Request

Proposal

Currently, the metrics and tracing sub-charts are deployed by default on Maesh installation. The purpose of the Helm chart is to install Maesh and to provide the necessary configuration options to be able to use supported metrics and tracing libraries, and not to provide production-ready stacks for metrics and tracing.

Therefore, the metrics and tracing sub-charts must not be deployed by default but should be kept for testing and demonstration purposes.

Metrics and Tracing install fails on ARM: "exec format error" due to incompatible images version-pinned

While following the documentation to install Traefik-mesh via this Helm chart, I found that the pods created for prometheus-core and jaeger kept failing with the error "exec format error".

After searching on dockerhub the images used in the chart values, I noticed that the tags pinned for some of them are only available for amd64. By changing these images with newer ones through the Helm "set" parameter, the install succeeds with no errors.

The following command is enought to make the install functional on arm64

helm install traefik-mesh traefik/traefik-mesh \
--set metrics.image.configmapReload="jimmidyson/configmap-reload:latest" \
--set tracing.image.jaeger="jaegertracing/all-in-one:latest"
  • The image for jimmidyson/configmap-reload (v0.2.2) used by the prometheus deployment is from 6 years ago and started supporting arm since version 0.3.0
  • The image for jaegertracing (1.18) is from 3 years ago and started supporting arm (64bit only) since version 1.24

I personally also upgraded the grafana image used with the latest main without finding any issue at the moment

Fix the supported Kubernetes version

Bug

Currently, the documentation says that the minimal Kubernetes version supported is v1.16. Because of the apiVersion upgrade for Kubernetes v1.22, the minimal version supported is not the right one.

The kubeVersion value should also be added to the chart manifest to enforce the minimum version supported.

Remove deprecated usage of v1beta1 PodDisruptionBudget

Feature request

When deploying Traefik in Kubernetes v1.21+, the following message is displayed:

W1230 09:39:52.108313   36728 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W1230 09:39:52.112154   36728 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

The PodDisruptionBudget should be updated to v1 before the release of Kubernetes v1.25.

HA mesh controller

Hello,

Just a general question but is it possible to run multiple replicas of the mesh controller? I see the pdb is currently set to have 1 pod minimally available, but that is pretty strict because it holds up rolling updates of nodes and evictions of that pod. Thanks!

Install fails on K8s < v1.19 clusters.

Greetings, I am in the middle of exploring service mesh offerings on our on-premise Kubernetes infrastructure running Kubernetes v1.18.8 and would like to try-out traefik mesh as we are already using traefik for our ingress (it works great!) I have attempted deployment using the latest helm release (traefik-mesh/traefik-mesh v1.4.0) but the helm install leaves the controller pod in a CrashLoop state as seen below:

traefik-mesh-controller-6c688948bf-hggvm   0/1     Init:CrashLoopBackOff   4          113s  

I see the following logs in the traefik-mesh-prepare init container:

kubectl -n traefik-mesh logs traefik-mesh-controller-5d888dcc67-5578q -c traefik-mesh-prepare
2020/10/06 03:34:04 command prepare error: unsupported SMI version: unable to find group "split.smi-spec.io" version "v1alpha3", got "v1alpha1"

TraffikSplit is served from v1alpha1 in k8s < v1.19, hence the init container fails with the error indicated above.

The helm deployment works fine if I attempt to deploy on a cluster running with k8s v1.19.

k8s v1.18.8

$ kubectl explain ts
KIND:     TrafficSplit
VERSION:  split.smi-spec.io/v1alpha1

DESCRIPTION:
     <empty>

k8s v1.19.0

kubectl explain ts
KIND:     TrafficSplit
VERSION:  split.smi-spec.io/v1alpha3

DESCRIPTION:
     <empty>

So the chart will only work on k8s v1.19 onwards and I believe we need to make changes here to make it compatible with k8s < v1.19. Thanks!

Update Helm Chart labels

Feature Request

Proposal

The project is currently using a set of labels on each resources defined in the Helm Chart:

  • app
  • component.

Kubernetes documentation recommends the use of the following labels:

  • app.kubernetes.io/app
  • app.kuberentes.io/component
  • app.kubernetes.io/managed-by
  • app.kubernetes.io/part-of

Workarounds

Keep it like that.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.