Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

sysadmin_guide: add SOP for deploying new coreos-cincinnati version

Browse source 
This adds the step needed after building the new image to actually roll
it out.
This commit is contained in:
Jonathan Lebon 2022-06-27 16:05:37 -04:00
parent 43acdf5d71
commit e70bfc2c68
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
modules/sysadmin_guide/pages/coreos-cincinnati.adoc
View file

@ -66,6 +66,20 @@ a new container image:
* schedule a new build by running
`sudo rbac-playbook -t build openshift-apps/coreos-cincinnati.yml`
=== Deploying a new version
Once the target commit has been built into a container image, these are
the steps to deploy the new image:
* update the `fcos_cincinnati_deploy_git_sha` playbook variable in
`roles/openshift-apps/coreos-cincinnati/vars/staging.yml`
* update the `fcos_cincinnati_deploy_git_sha` playbook variable in
`roles/openshift-apps/coreos-cincinnati/vars/production.yml`
* commit and push the update to the `fedora-infra/ansible` repository
* SSH to `batcave01.iad2.fedoraproject.org`
* run `sudo rbac-playbook openshift-apps/coreos-cincinnati.yml` using
your FAS password and your second-factor OTP
== Things that could go wrong
=== Application build is stuck