search

elastisys / compliantkubernetes-kubespray

Apache License 2.0
28 stars 7 forks source link

Upgrade no longer handles custom cluster prefix #311

Closed Elias-elastisys closed 1 year ago

Elias-elastisys commented 1 year ago

Describe the bug All Kubespray functionality has up to this point handled any name/prefix to the cluster naming.

When we run multi wc to one sc we named the clusters wc-staging and wc-prod to avoid confusion, but the new automated upgrade steps seem to have hardcoded the naming to just wc and sc

The docs still seem to indicate that you can initialize an environment with any prefix.

To Reproduce Steps to reproduce the behavior:

  1. Initialize an environment with a name other than just wc and sc
  2. Try to run ck8s-kubespray upgrade v2.22 prepare
  3. See error

Expected behavior I would expect the CLI to still work with any naming as before.

Or the removal of docs indicating that a custom name can be used.

Version (add all relevant versions):

Additional context Add any other context about the problem here.

crssnd commented 1 year ago

closing in favour of https://github.com/elastisys/compliantkubernetes-kubespray/issues/314