From 73bd9bec118c58cce955f1776183662521b7ec08 Mon Sep 17 00:00:00 2001 From: Benjamin Gilbert Date: Mon, 13 Mar 2023 23:50:31 -0400 Subject: [PATCH] docs/upgrading-openshift: document password_hash field in 4.13 --- docs/upgrading-openshift.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/upgrading-openshift.md b/docs/upgrading-openshift.md index 7c32cac7..5632a7e4 100644 --- a/docs/upgrading-openshift.md +++ b/docs/upgrading-openshift.md @@ -52,6 +52,26 @@ passwd: There are no breaking changes between versions 4.12.0 and 4.13.0 of the `openshift` configuration specification. Any valid 4.12.0 configuration can be updated to a 4.13.0 configuration by changing the version string in the config. +The following is a list of notable new features, deprecations, and changes. + +### User passwords + +The `passwd.users` section enabled the `password_hash` field, which sets the password hash for an account. The `users` section continues to support only the `core` user. + + +```yaml +variant: openshift +version: 4.13.0 +metadata: + labels: + machineconfiguration.openshift.io/role: worker + name: core-password +passwd: + users: + - name: core + password_hash: $y$j9T$nQ... +``` + ## From Version 4.11.0 to 4.12.0 There are no breaking changes between versions 4.11.0 and 4.12.0 of the `openshift` configuration specification. Any valid 4.11.0 configuration can be updated to a 4.12.0 configuration by changing the version string in the config.