Overview
A customer may find it necessary to move an already deployed EYK application to a new cluster, as would be the case when moving an application that was undergoing acceptance testing to the production cluster.
Solution
Follow these steps to move an application from one cluster to a new cluster:
-
Working on the old cluster;
-
Get the environment variables on a .env file:
eyk config:pull
This will create a.env
file which will include all the environment variables currently in place. - Get a listing of the domains currently in place:
eyk domains
- Get a listing of the certificates in place:
eyk certs
-
Get the environment variables on a .env file:
-
Working on the new production cluster;
Use the EYKssologin
command to log in by executing:eyk ssologin https://eyk.clustername.accountname.ey.io
As documented in Getting Started with Engine Yard Kontainers and assuming that you are at the root of your application, follow these steps:
-
Add your ssh keys on the new cluster:
eyk keys:add ~/.ssh/id_rsa.pub
Note: edit to match your path and .pub file name - Get a listing of current remotes:
git remote -v
- Remove the already present eyk remote:
git remote rm eyk
- Create the application:
eyk apps:create appname
- Create the domains:
eyk domains:add domain.com
- Create the certificates:
eyk certs:add certname cert.crt private.key
- Attach the certificate on the domains added earlier:
eyk certs:attach certname domainame
- Update the environment variables:
eyk config:push
Which would automatically push the.env
variables to your application. -
Push the application code:
git push eyk
-
Add your ssh keys on the new cluster:
Comments
Article is closed for comments.