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

Support for VSphere Server 8 - multi factor authentication #2957

Open
pkandarpa-cs opened this issue Jul 17, 2024 · 1 comment
Open

Support for VSphere Server 8 - multi factor authentication #2957

pkandarpa-cs opened this issue Jul 17, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@pkandarpa-cs
Copy link

pkandarpa-cs commented Jul 17, 2024

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
We use the CSI provider in a Rancher based K8s cluster on-premise, and the VSphere Server is being upgraded to version 8, and is coming with an enforced multi-factor authentication step. Because of this change, we can no longer use the vsphere-csi-provider - which, obviously is a huge disruptor to production operations.
What you expected to happen:
Are there plans to help support MFA based VSphere Server auth? Is that even possible in this case because the supported multi-factor auth modes are documented here - https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-authentication/GUID-ACFFCBEC-6C1C-4BF9-9971-04AEE9362AFE.html

How to reproduce it (as minimally and precisely as possible):
.....

Anything else we need to know?: nope

Environment:

  • csi-vsphere version: rancher-vsphere-csi:102.2.0+up3.0.2-rancher1
  • vsphere-cloud-controller-manager version:
  • Kubernetes version: v1.26.8
  • vSphere version: 8
  • OS (e.g. from /etc/os-release):Red Hat Enterprise Linux 9.2 (Plow
  • Kernel (e.g. uname -a): Linux ...... 5.14.0-284.11.1.el9_2.x86_64 Create a SECURITY_CONTACTS file. #1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools:
  • Others: Rancher 2.7.9
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 17, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants