Migrate to Emissary 3.x
You can upgrade from any version of Ambassador Edge Stack or Emissary to any version of either by installing the new version in a new Kubernetes cluster, then copying over configuration as needed. This is the way to be absolutely certain that each installation cannot affect the other: it is extremely safe, but is also significantly more effort.
For example, to upgrade from some other version of Ambassador Edge Stack or Emissary to Emissary 3.x:
-
Install Emissary 3.x in a completely new cluster.
-
Create
Listener
s for Emissary 3.xWhen Emissary 3.x starts, it will not have any
Listener
s, and it will not create any. You must createListener
resources by hand, or Emissary 3.x will not listen on any ports. -
Copy the entire configuration from the Emissary 1.X cluster to the Emissary 3.x cluster. This is most simply done with
kubectl get -o yaml | kubectl apply -f -
.This will create
getambassador.io/v2
resources in the Emissary 3.x cluster. Emissary 3.x will translate them internally togetambassador.io/v3alpha1
resources. -
Each Emissary instance has its own cluster, so you can test the new instance without disrupting traffic to the existing instance.
-
If you need to make changes, you can change the
getambassador.io/v2
resource, or convert the resource you’re changing togetambassador.io/v3alpha1
by usingkubectl edit
. -
Once everything is working with both versions, transfer incoming traffic to the Emissary 3.x cluster.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.