Firstly, you must install the Ambassador Operator:
- Load the Ambassador Operator CRD with the following command:
kubectl apply -f https://github.com/datawire/ambassador-operator/releases/latest/download/ambassador-operator-crds.yaml
- Install the Ambassador Operator in the
ambassador
namespace with the following command:To install the Ambassador Operator in a different namespace, you can specify it inkubectl apply -n ambassador -f https://github.com/datawire/ambassador-operator/releases/latest/download/ambassador-operator.yaml
NS
and then run the following command (that will replace theambassador
namespace by$NS
):NS="custom-namespace" curl -L https://github.com/datawire/ambassador-operator/releases/latest/download/ambassador-operator.yaml | \ sed -e "s/namespace: ambassador/namespace: $NS/g" | \ kubectl apply -n $NS -f -
Then you can create a new AmbasasadorInstallation
Custom Resource named ambassador
as described in the users guide.
You can install the AES Operator from the Operator Hub, where makers of Kubernetes operators can share their configurations with the community. To install from this site:
- Navigate to operatorhub.io and search for “Ambassador Edge Stack.”
- Click on the tile.
- Click the Install button and follow the directions to finish the installation.
- Once the new Operator is working, you can create a Custom Resource called
ambassador
and apply it as described in the usage guide.
You can also install the AES Operator from a Helm Chart.
- Install Helm 3
- Add this Helm repository to your Helm client
helm repo add datawire https://getambassador.io
- Create namespace
ambassador
where AES will be installedkubectl create namespace ambassador
- Run the following command:
This command deploys the Ambassador Operator in the
helm install -n ambassador ambassador-operator datawire/ambassador-operator
ambassador
namespace on the Kubernetes cluster in the default configuration (it is recommended to use theambassador
namespace for easy upgrades). - Once the new Operator is working, create a new
AmbasasadorInstallation
Custom Resource namedambassador
as described here.