Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSIMigration failed due to missing csi flags #1317

Closed
syjabri opened this issue Apr 16, 2021 · 1 comment
Closed

CSIMigration failed due to missing csi flags #1317

syjabri opened this issue Apr 16, 2021 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@syjabri
Copy link

syjabri commented Apr 16, 2021

What happened:
I want to migrate from the openstack in-tree to the external cloud provider using kubeone, the migration part is not done and the volumes still point to the old in-tree cloud provider.

What is the expected behavior:
After enabling csimigration, an additional feature-gates field should be added to the controller-manager and apiserver "CSIMigration=true,CSIMigrationOpenStack=true,ExpandCSIVolumes=true".
And after the migration is done, an annotation should be automatically added to the persistent volume pv.kubernetes.io/migrated-to: cinder.csi.openstack.org, also the --cloud-provider=external and --cloud-config fields should be removed from the kubeadm flag file.
How to reproduce the issue:

  1. Add the external field in the kubeone.yaml configuration file as mentioned here
cloudProvider:
    openstack: {}
    external: true
  1. Then run kubeone upgrade --force
  2. An openstack-cloud-controller-manager is deployed in the kube-system namespace
  3. After that deploy the Cinder CSI Plugin manually.
  4. Added csiMigration: true in the kubeone configuration file .
  5. Re-Run kubeone upgrade --force

Information about the environment:
KubeOne version (kubeone version): v1.2.1
Operating system: Flatcar
Provider you're deploying cluster on: Openstack

@syjabri syjabri added the kind/bug Categorizes issue or PR as related to a bug. label Apr 16, 2021
@kron4eg
Copy link
Member

kron4eg commented Apr 19, 2021

Unfortunately the feature you are looking for (you can track it here #616) was never implemented in the first place, so it can't be a bug. Closing as "duplicate".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants