C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
c12s-kubespray/roles/kubernetes-apps/ingress_controller/ambassador/README.md
kongxs 922de32290
spelling mistakes (#7664) 
Signed-off-by: kjinan <2008kongxiangsheng@163.com>
2021-05-31 05:46:26 -07:00

1.9 KiB
Raw Blame History

Installation Guide

Ambassador

The Ambassador API Gateway provides all the functionality of a traditional ingress controller (e.g., path-based routing) while exposing many additional capabilities such as authentication, URL rewriting, CORS, rate limiting, and automatic metrics collection.

Ambassador Operator

This addon deploys the Ambassador Operator, which in turn will install Ambassador in a kubespray cluster.

The Ambassador Operator is a Kubernetes Operator that controls Ambassador's complete lifecycle in your cluster, automating many of the repeatable tasks you would otherwise have to perform yourself. Once installed, the Operator will complete installations and seamlessly upgrade to new versions of Ambassador as they become available.

Configuration

  • ingress_ambassador_namespace (default ambassador): namespace for installing Ambassador.
  • ingress_ambassador_update_window (default 0 0 * * SUN): crontab-like expression for specifying when the Operator should try to update the Ambassador API Gateway.
  • ingress_ambassador_version (default: *): SemVer rule for versions allowed for installation/updates.
  • ingress_ambassador_multi_namespaces (default false): By default, Ambassador will only watch the ingress_ambassador_namespace namespace for AmbassadorInstallation CRD resources. When set to true, this value will tell the Ambassador Operator to watch all namespaces for CRDs. If you want to run multiple Ambassador ingress instances, set this to true.

Ingress annotations

The Ambassador API Gateway will automatically load balance Ingress resources that include the annotation kubernetes.io/ingress.class=ambassador. All the other resources will be just ignored.