Best Practices for your Kubernetes Edge Architecture
Whether you’re starting fresh with Kubernetes or migrating an existing application, understanding the implications that Kubernetes has for your edge is an important but complicated task.
Kickstart your project by talking with an expert from our team. We’ve worked with a large number of organizations (from startup to enterprises) and helped them prepare their edge and API gateway strategy as they adopt Kubernetes. We’ll help you understand the best practices and how they apply to your unique architecture.
Topics AvailablePart I: Architectural Patterns and Recommendations
- Learn how Kubernetes impacts your application networking
- Understand common layer 4 load balancing techniques and evaluate where TLS termination best fits into your architecture
- Explore common use cases:
- Using an API gateway for continuous delivery
- Migrating an application from virtual machines (VMs) to containers and Kubernetes
- Tell us about your own!
- GitOps - why it has become a best practice within cloud native developer workflows, and how to implement it in your own workflow
- CI/CD systems - why you need them and how to integrate them
- Progressive delivery techniques - how to use canary releases and traffic shadowing for testing in production
- Security - why you should centralize authentication and authorization
- Cross cutting concerns - how to protect your system’s availability with rate limiting
- Learn how to minimize downtime by automating TLS cert management
- Understand the benefits and tradeoffs with Endpoint routing
- See how properly documenting and cataloging your API endpoints makes developer onboarding easier
- Explore the key edge metrics that you should be tracking, and learn how to track them effectively