mirror of https://github.com/kubernetes/kops.git
Merge pull request #4905 from sunlintong/slt-8
update vsphere-development-status.md
This commit is contained in:
commit
3e56125a2c
|
@ -14,13 +14,13 @@ P2: Rarely occurring issues and features that will bring vSphere support closer
|
|||
|
||||
**Notes:**
|
||||
|
||||
* Effort estimation inclues fix for an issue or implementation for a feature, testing and generating a PR.
|
||||
* There are a few issues that are related to startup and base image. If we can resolve "Use PhotonOS for vSphere node template" issue first and replace init-cloud with guestinfo, those issues **might** get resolved automatically. But further investination is needed and fixed issues will need verifications and testings.
|
||||
* Effort estimation includes fix for an issue or implementation for a feature, testing and generating a PR.
|
||||
* There are a few issues that are related to startup and base image. If we can resolve "Use PhotonOS for vSphere node template" issue first and replace init-cloud with guestinfo, those issues **might** get resolved automatically. But further investigation is needed and fixed issues will need verifications and testings.
|
||||
|
||||
|Priority|Task|Type (bug, feature, test|Effort estimate(in days)|Remarks|
|
||||
|--- |--- |--- |--- |--- |
|
||||
|P0|Kops for vSphere is broken kubernetes/kops#2729|Bug|1||
|
||||
|P0|AWS EBS is set as default volume provisioner, instead of vSphere kubernetes/kops#2732|Bug|1|Looks like the fix is available, need to be tested again before commiting https://github.com/vmware/kops/pull/70/files|
|
||||
|P0|AWS EBS is set as default volume provisioner, instead of vSphere kubernetes/kops#2732|Bug|1|Looks like the fix is available, need to be tested again before committing https://github.com/vmware/kops/pull/70/files|
|
||||
|P0|Package installation through nodeup causing delay in cluster deployment kubernetes/kops#2742|Bug|2|If we get the "Use PhotonOS for vSphere node template" done first, this one may just be avoided. Verification required.|
|
||||
|P0|Connection to api.clustername.skydns.local is failing kubernetes/kops#2744|Bug|1|This might be fixed by Abrar's PR in kubernetes already. Just need to verify.|
|
||||
|P0|Make update command, that includes scale up and down, work kubernetes/kops#2738. There are two possible ways to implement this- without auto scaling group (ASG) or with auto scaling group|Feature|4 days Assuming ASG is available. 4 days ASG is not available.|This effort estimation needs more analysis.|
|
||||
|
@ -73,7 +73,7 @@ List of all kops commands and how they behave for vSphere cloud provider, as of
|
|||
|get|instancesgroups||Yes|-|Gets list of intancegroups. If yaml output is specified, this output can be modified and used for 'kops replace' command.|
|
||||
|get|secrets||Yes|-|Gets list of secrets.|
|
||||
|import|cluster|kops import cluster --region=us-west-2 --name=v2c1.skydns.local nodes|No. Current implementation is very aws specific. Multiple aws services are queried to construct the api.Cluster object.|Yes|Imports spec for an existing cluster into the object store. While this functionality is good for importing and managing existing k8s clusters using kops, it doesn't seem like a high priority functionality at this point of time.|
|
||||
|replace||kops replace -f FILENAME|No|Yes|Outout of `kops get cluster name -oyaml` or `kops get ig name -oyaml` can be updated and passed to 'kops replace' command.|
|
||||
|replace||kops replace -f FILENAME|No|Yes|Output of `kops get cluster name -oyaml` or `kops get ig name -oyaml` can be updated and passed to 'kops replace' command.|
|
||||
|rolling-update|cluster||No. Current implementation is aws specific.|Yes||
|
||||
|secrets|create||-|-|Legacy command, points to 'kops create secrets'.|
|
||||
|secrets|describe||-|-|Legacy command, points to 'kops describe secrets'.|
|
||||
|
|
Loading…
Reference in New Issue