add a zh doc introducing the new features of kubekey #1053
Conversation
ks-ci-bot
added
the
kind/documentation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 24sama The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ks-ci-bot
added
approved
Signed-off-by: 24sama <leo@kubesphere.io>
| iso: | ||
| localPath: | ||
| url: https://github.com/pixiake/k8s-dependencies/releases/download/v1.0.0/centos-7-amd64-rpms.iso | ||
| kubernetesDistributions: # Define the kubernetes distribution that will be included in the artifact. |
There was a problem hiding this comment.
How many k8s distributions does KK support?
There was a problem hiding this comment.
|
|
||
| 第一种方式需要了解该配置文件中不同字段的更多信息，请参考 [manifest-example.md](../manifest-example.md)。 | ||
|
|
||
| 以下内容仅针对于第二种由 kk 实现的生成文件的方式。 |
There was a problem hiding this comment.
方法二是对已有集群的配置信息进行扫描然后生产一个新的 manifest？
There was a problem hiding this comment.
是的。类似于./kk create config --from-cluster --kubeconfig xxx 从已有集群生成一个config配置文件
There was a problem hiding this comment.
没有要求，kk 根据默认路径或者指定的kubeconfig连接上集群，然后就执行扫描集群信息的操作了。
|
/lgtm |
|
LGTM label has been added. Git tree hash: 67c94aae6596e9a6faf2bc991e1d1d52e977607c
|
|
/cherrypick release-2.0 |
|
@24sama: new pull request created: #1081 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: 24sama leo@kubesphere.io
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Add a zh doc introducing the new features of kubekey.
Please take a look at this PR, thanks.
/cc @kubesphere/sig-installation @kubesphere/sig-docs
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: