Upgrade Domino

Before you perform an upgrade you must put Domino into maintenance mode. See the domino-maintenance-mode readme.
Run the installer with the same configuration as the one you used for installation, but with the version field set to the new version. See the configuration reference and the fleetcommand-agent release notes for Domino versions compatible with your installer.

Note	To back up Nucleus and Git before you upgrade, use the following: kubectl -n domino-platform create job upgrade-backup-nucleus-job --from cronjob/nucleus-backup kubectl -n domino-platform create job upgrade-backup-git-job --from cronjob/git-backup

See Upgrade fleetcommand-agent if you must upgrade to a newer installer version to upgrade to a Domino version.
1. Upgrade Domino
2. Retrieve the new Domino installer image from quay.io:
  docker pull quay.io/domino/fleetcommand-agent:v50.2
3. Create a copy of your domino.yml configuration file. Name it something like domino-orig-date.yml, to indicate when you modified the configuration.
4. To generate a new domino.yml configuration file, run the initialization command through the upgraded fleetcommand-agent image. This upgrades your existing configuration to the new template. The command assumes both .yml files are in your current directory.
  docker run --rm -it -v $(pwd):/install quay.io/domino/fleetcommand-agent:v50.2 init --file /install/domino.yml -t /install/domino-orig-date.yml
5. Copy custom values from your original configuration into the new file.
6. When the upgrade is complete, run the install script from the install process and change the spec.containers.image value to quay.io/domino/fleetcommand-agent:v50.2.