Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion upgrading/automated_upgrades.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -436,7 +436,9 @@ files before running the upgrade. Otherwise, your manual changes may be
overwritten by default values during the upgrade, which could cause pods to not
run properly or other cluster stability issues.
+
In particular, if you made any changes to `admissionConfig` settings in your
Additionally, verify the following settings:

.. If you made any changes to `admissionConfig` settings in your
master configuration files, review the
`openshift_master_admission_plugin_config` variable in
xref:../install/configuring_inventory_file.adoc#configuring-ansible[Configuring
Expand All @@ -445,6 +447,10 @@ Your Inventory File]. Failure to do so could cause pods to get stuck in
configured previously (as described in
xref:../admin_guide/overcommit.adoc#configuring-masters-for-overcommitment[Configuring Masters for Overcommitment]).

.. If you manually manage the cluster's *_/etc/origin/master/htpasswd_* file,
add `openshift_master_manage_htpasswd=false` to your inventory file to prevent
the upgrade process from overwriting the *_htpasswd_* file.

After satisfying these steps, you can review the following sections for more
information on how the upgrade process works and make decisions on additional
upgrade customization options if you so choose. When you are prepared to run the
Expand Down