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.

Sign up for GitHub

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

Jump to bottom

Added the known issues to a newly created file, FAQ.md #64

Merged
merged 2 commits into from
May 6, 2020
Merged

Added the known issues to a newly created file, FAQ.md #64

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f866aa8
Added known issues to the newly created FAQ.md file
May 2, 2020
5970d52
Update FAQ.md
dsu-igeek May 6, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Known Issues

## v1.0.0
1. Restore fails if the K8s node VMs are placed in any sub-folders of vSphere VM inventory.
1. Workaround: move node VMs to the top level of VM inventory. (for users of release v1.0.0)
2. Solution: the issue was resolved in the master branch at commit 1c3dd7e20c3198e4a94a5a17874d4c474b48c2e2.
2. The restore might place the restored PVs in a vSphere datastore which is imcompatible with the StorageClass
specified in the restored PVC, as we don't rely on the StorageClass for the PV placement on restore in the release v1.0.0.
A fix to the PV placement based on the StorageClass can be expected in the next release.
3. The plugin v1.0.0 has issues with some variants of Kubernetes on vSphere.
1. In a TKG cluster, the vSphere CSI credential secret, i.e., VC credential,
is named `csi-vsphere-config` in the `kube-system` namespace, which is different than the expected
`vsphere-config-secret` in the `kube-system` namespace. As a workaround, add another secret, `vsphere-config-secret`,
with VC credential available in the secret `csi-vsphere-config`. Some more tips on using this workaround:
[Issue #63](https://github.com/vmware-tanzu/velero-plugin-for-vsphere/issues/63).
1. Make sure to use quotes to wrap around the value of each key-value pair in the `csi-vsphere.conf`
when constructing `vsphere-config-secret`.
2. Make sure to add one more key-value pair, `port = "443"`, under the `VirtualCenter` section.
As far as we know, the `port` key is absent from the `csi-vsphere.conf` of the secret `csi-vsphere-config` in TKG.