Overview
Traefik Enterprise combines API gateway and modern ingress functionality in a distributed, highly available architecture. The centralized control plane and data plane ensure your APIs and microservices are secure, accessible, and configured appropriately, regardless of your infrastructure or architectural strategy.
Highlights
- Traefik Enterprise centralizes access control and traffic management to simplify teams workflows while making it easy to add advanced capabilities (rate limiting, distributed Let s Encrypt, etc.) through turnkey middleware, custom plugins, and third-party integrations.
- Dynamic configuration, automated service discovery and routing, flexible rate limiting, and high availability features enable application teams to deploy quickly with zero downtime and ensure peak performance and availability.
- Because Traefik Enterprise is compatible with any environment, whether cloud, legacy, or hybrid, application teams can adopt new technologies and services quickly.
Details
Pricing
Dimension | Description | Cost/12 months |
---|---|---|
EE MC-1 License | Traefik Enterprise Mission Critical 1-Yr Cluster License | $45,000.00 |
EE PRO-1 License | Traefik Enterprise Professional 1-Yr Cluster License | $30,000.00 |
Vendor refund policy
We don't have a refund policy. All purchases are final.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Traefik Enterprise - Container
- Amazon ECS
- Amazon EKS
- Amazon ECS Anywhere
- Amazon EKS Anywhere
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Additional details
Usage instructions
https://doc.traefik.io/traefik-enterprise/installing/kubernetes/gitops/
Installing with the GitOps endpoint GitOps practices are a set of workflows and practices that make Git the source of truth for infrastructure configuration management.
Kubernetes only
For now, Traefik Enterprise can be only be installed using GitOps practices on Kubernetes.
Installation To install Traefik Enterprise without the teectl CLI, an HTTP request can be made to generate the required installation manifests, which can then be applied directly to a Kubernetes cluster.
First, your Traefik Enterprise license needs to be specified in a Kubernetes Secret, in the namespace in which you plan to install Traefik Enteprise.
kubectl create namespace traefikee kubectl create secret generic $CLUSTERNAME-license --from-literal=license="$TRAEFIKEE_LICENSE" -n traefikee
As a convenience, a sample declarative file that can be used with kubectl apply has been provided below:
apiVersion: v1 kind: Namespace metadata: name: traefikee namespace: traefikee
apiVersion: v1 kind: Secret type: Opaque metadata: name: default-license namespace: traefikee stringData: license: myLicenseString
The next step is to create a ConfigMap containing your Traefik Enterprise static configuration. Traefik Enterprise will watch this configuration and automatically update all of its proxies whenever the ConfigMap's data is edited.
kubectl create configmap --from-file=static.yaml $CLUSTERNAME-static-config -n traefikee
As a convenience, a sample declarative file that can be used with kubectl apply has been provided below:
apiVersion: v1 kind: ConfigMap metadata: namespace: traefikee name: default-static-config data: static.yaml: | entryPoints: http: address: ":80" https: address: ":443"
providers:
kubernetesCRD: {}
api:
dashboard: true
Now that your license has been applied and your static configuration is in a ConfigMap, you can query the installer service to generate an installation manifest, which you should review and make any changes that are needed:
Applying the installation manifest curl "https://install.enterprise.traefik.io/v2.10 " --output manifest.yaml
Once you have reviewed the manifest, the next step is to apply it using kubectl
:
kubectl apply -f manifest.yaml The installation service supports multiple options to customize your installation (namespace, cluster name, etc.).
Custom Installation Parameters
Here are the options that can be specified using query parameters to customize the generated install manifest:
- cluster string (default: default) : The cluster name
- namespace string (default: traefikee) : The namespace in which to install
- clusterdomain string (default: cluster.local) : The cluster domain (required for service mesh)
- controllers integer (default: 1) : The number of controllers
- proxies integer (default: 2) : The number of proxies
- mesh boolean (default: false) : Enable service mesh
- kubedns boolean (default: false) : The cluster has KubeDNS installed
- withoutcrds boolean (default: false) : Do not output the CRD part of the manifest
- withoutresources boolean (default: false) : Do not output the Resources part of the manifest
- staticconfig string (default: static.yaml) : The name of the static configuration file in the ConfigMap
The following command gets an installation manifest that has service mesh enabled, for a cluster that uses KubeDNS, and will install a cluster named staging in the traefikee-staging namespace:
Example: kubectl apply -f "https://install.enterprise.traefik.io/v2.10?cluster=staging&namespace=traefikee-staging&mesh&kubedns "
Support
Vendor support
24/7/365 Global Support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Though it has a steep learning curve, Traefik has powerful tools for routing among docker containers
Extensive proxy for all use cases!
The comprehensive documentation provided by Traefik is another major advantage. It’s well-organized, detailed, and covers virtually every possible use case. Whether you’re just getting started or diving deep into complex scenarios, the documentation is a reliable resource. It walks you through configurations, best practices, and even troubleshooting, ensuring that you can make the most out of Traefik's extensive capabilities.
Moreover, Traefik is incredibly flexible and can be used in almost any environment or use case. It supports a wide range of orchestrators like Kubernetes, Docker, and more. This versatility allows it to fit seamlessly into various infrastructures, from small-scale setups to large, complex systems. Whether you need to manage traffic for a single application or a sprawling microservices architecture, Traefik is equipped to meet the challenge.
Overall, Traefik’s extensive configuration options, robust documentation, and wide applicability make it an indispensable tool for anyone looking to efficiently manage their network traffic in a scalable and secure way.
However, once you get past the initial learning curve, the flexibility and control that Traefik offers are unmatched. The comprehensive documentation helps mitigate this complexity, guiding you through the setup process and helping you understand how to tailor Traefik to your specific needs. With time and experience, you'll likely find that the initial complexity is a small price to pay for the robust and customizable infrastructure that Traefik enables.
Efficient and Flexible Service Management with Traefik
For me, Traefik’s ability to dynamically discover and configure new services is a game-changer. It eliminates the need for manual configuration every time a new service is added, which not only saves time but also reduces the risk of configuration errors. Additionally, its built-in support for HTTPS with real signed certificates ensures that all my applications are secure without extra hassle.
Fast and powerful reverse proxy with everything you need for your containerized infrastructure
One of the best parts about Traefik is that it includes a ton of functionality baked into the service, like automatic SSL certificate generation for your web applications and middleware to manipulate incoming requests. You don't need to deal with plugins or additional software nor modify your applications, and configuring them is straightforward. Having a lot of these systems in a single place helps managing things a breeze. The included dashboard is also useful to see your complete setup.
Debugging issues can be a bit of a challenge at times, especially when involving more complex setups of routers and middleware. With all the points where something can go wrong and sometimes-unclear error logs, fixing problems when they arise can take quite some time to deal with.
- Managing routing rules for microservices to allow me to handle where my incoming traffic goes.
- Simple service discovery for new Docker containers which lets me add new microservices without needing additional configuration.
- Automatic SSL certificate generation so I don't have to worry about renewing them.
- Easy-to-add middleware options for rate limiting and basic authentication when needed.
Traefik streamlines our delivery by providing efficient traffic routing and service discovery
1. 自动服务发现与配置: Traefik能够自动发现服务,并根据配置生成路由规则。这大大简化了微服务架构下的服务管理。
2. 多后端支持: Traefik支持多种后端,包括Docker、Kubernetes、Mesos等,可以轻松集成到不同的环境中。
3. 丰富的路由规则: Traefik提供了灵活的路由规则配置,可以根据域名、路径、请求头等多种条件进行路由。
4. 插件机制: Traefik的插件机制非常强大,可以扩展其功能,例如认证、授权、日志、监控等。
5. 高性能: Traefik基于Go语言开发,具有高性能和低延迟的特点。
1. 配置复杂性: 虽然Traefik提供了自动配置功能,但对于复杂的路由规则和高级功能,配置仍然可能比较复杂。
2. 学习曲线: 对于初学者来说,掌握Traefik的所有功能和配置选项可能需要一定的时间。再加上,Traefik书籍较少,尤其是在中文社区,资料相对来说有点匮乏