🚀 Are you ready to amplify your skills in leadership and driving the best #SaaS & Infrastructure products to market? 🥇 Please consider applying to the Head of Product role—we'd love to chat with you!
For details and to apply 👉 https://t.co/sOAlWFASIm #traefik
Today we are announcing the GA release of #Terraform 1.0. This marks a major milestone for interoperability, ease of upgrades, and maintenance for your automation workflows for what has become a standard for cloud provisioning. #HashiConf https://t.co/Ciqz0txdrT
Understanding Cilium Network Performance
- eBPF vs iptables
- Cilium vs Calico
- Throughput, Req/s, Connection/s, Latency, & CPU
- Wireguard vs IPsec
https://t.co/8cWhbEJs9n
🔔 Share your opinion about Traefik & Win one of 5 $100 Amazon gift cards, 10 Traefik hoodies, and 20 Traefik Labs t-shirts 🎁 https://t.co/QXabdFPqJ5
#traefik
Traefik turns 5 years old today! We’re celebrating by giving Traefik's home a new name:
Welcome to Traefik Labs!
Read the full story: https://t.co/fal22PX6WH
#traefik
🎉 Release Candidate for Traefik v2.3 is out! The release includes:
- Plugins!
- Pilot integration
- ECS provider
- K8S IngressClass
Please test it out and let us know of any issues: https://t.co/9TEdwN67Bd
🎊 Announcing Maesh 1.2 - Now with support for UDP, custom proxy nodes and a more efficient installation! https://t.co/0Q8f30Jlo0 #servicemesh#kubernetes
Je ne vais pas vous mentir, aujourd'hui c'est mercredi ! 🐒 Et j'ai le plaisir de recevoir @michaelmatur de @containous, avec qui j'ai discuté de @traefik et de M(a)esh. Un sujet passionnant à retrouver sur https://t.co/1AZgLd1qiS
Traefik Enterprise Edition Demo. There's a lot to love about Traefik Enterprise Edition. Take a look:
https://t.co/INBfnGawmh #traefik#kubernetes#golang
✏️Tech Writers, look here 👉 Join a fun, distributed, modern team, and show the world what you've got! If you love open source, match the required qualifications, and believe in the power of a great team, please apply today.🥇 https://t.co/XKpuJcOHaA
Ouch @github, why squash & merge should take authorship of the commit? Why deploying this without prior notice? You just broke our @traefik workflow 😭
Hey @github, when merging a PR, and using the "squash and merge" method, the commit apparently now gets authored by the user that initiated the merging action. Which is very wrong both from a moral and legal POV. Can you explain what's going on please?