You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Example: A ready-to-deploy MKE configuration file is not ready-to-deploy. This is an outdated version of the config that is no longer valid. Some of the fields no longer exist. We should update this to be the current output of mkectl init or eliminate it altogether since we go on in the page to point users to mkectl init command which will always be the latest version
The commands on the page tell users to name their config mke.yaml. We should change this to be the default config that is read by mkectl: mke4.yaml We should look for other config usage throughout the docs and do the same.
This was found as part of: https://mirantis.jira.com/browse/BOP-1223
The create cluster page has a few things that need to be updated
mkectl init
or eliminate it altogether since we go on in the page to point users tomkectl init
command which will always be the latest versionmke.yaml
. We should change this to be the default config that is read bymkectl
:mke4.yaml
We should look for other config usage throughout the docs and do the same.The text was updated successfully, but these errors were encountered: