Ambassador is great!
Rating: 10 out of 10
IncentivizedUse Cases and Deployment Scope
Currently, we use Ambassador as a secondary ingress controller. It addresses our needs by facilitating adding dynamic routes for our incredible number of endpoints. That way it makes it very easy to get multiple parallel microservices we need to be deployed to support our testing and quality assurance needs.
Pros
- Simple syntax
- Easy to understand
- Easy to install
Cons
- Documentation is not updated
- Implementing external authentication doesn't always work as described in the documentation
- The Administration console is limited
Likelihood to Recommend
Ambassador is really well suited for scenarios were you need to give power and freedom to your developers so they can take advantage of the self-service approach. One of the few scenarios I can not recommend using Ambassador is in the case you are planning to not using Kubernetes as it is a solution designed to work specifically on that platform.