This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
Docs - workload clusters #1086
Merged
Docs - workload clusters #1086
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
owner/docs
stmcginnis
reviewed
Jul 15, 2021
|
|
||
| 1. Make a copy of the management cluster configuration file and save it with a new name. | ||
| 1. Open the new YAML cluster configuration file in a text editor. | ||
| 1. Set a name for the cluster in the `CLUSTER_NAME` variable. If you do not specify a `CLUSTER_NAME` value in the cluster configuration file you must pass it as the first argument in the `tanzu cluster create` command. The `CLUSTER_NAME` value passed to the `tanzu cluster create` command overrides the `CLUSTER_NAME in the configuration file. Workload cluster names must be must be 42 characters or less, and must comply with DNS hostname requirements as amended in [RFC 1123](https://tools.ietf.org/html/rfc1123). |
There was a problem hiding this comment.
Missing closing backtick for the last instance of CLUSTER_NAME in this bullet.
|
|
||
| ## Before You Begin | ||
|
|
||
| - Copy the configuration file: When you deploy a workload cluster, most of the configuration for the cluster is the same as the configuration of the management cluster. The easiest way to obtain an initial configuration file for a workload cluster is to make a copy of the management cluster configuration file and to update it. Locate the YAML configuration file for the management cluster |
There was a problem hiding this comment.
Since there are multiple sentences in this bullet, it would be good to end the last sentence with a period.
| 1. Optional: Specify the number of worker nodes for the cluster in the `WORKER_MACHINE_COUNT` variable. | ||
| 1. Optional: Deploy a workload cluster in a specific namespace. | ||
| If you have created namespaces, you can deploy workload clusters to those namespaces by specifying the `NAMESPACE` variable. If you do not specify the `NAMESPACE` variable, Tanzu Community Edition places clusters in the `default` namespace. Any namespace that you identify in the `NAMESPACE` variable must exist in the management cluster before you run the command. <!--For information about creating namespaces in the management cluster, see [Create Namespaces in the Management Cluster](../cluster-lifecycle/multiple-management-clusters.md#create-namespaces).--> You must provide a unique name for all workload clusters across all namespaces. If you provide a workload cluster name that is already in use in another namespace in the same instance, the deployment fails with an error. | ||
| 1. Optional: To configure a workload cluster to use an OS other than the default Ubuntu v21.04, you must set the `OS_NAME` and `OS_VERSION` values in the cluster configuration file. The installer interface does not include node VM OS values in the management cluster configuration files that it saves to `~/.tanzu/tkg/clusterconfigs`. |
There was a problem hiding this comment.
I believe it's actually Ubuntu 20.04, not 21.04.
| - Three worker nodes, with names similar to `my-prod-cluster-md-0-2vsr4`. | ||
|
|
||
| ## Set the Kubectl Context to the Workload Cluster {#context} | ||
| Tanzu Community Edition does not automatically set the kubectl context to a workload cluster when you create it. You must set the kubectl context to the workload cluster manually by using the kubectl config use-context command. Complete the following steps: |
There was a problem hiding this comment.
Just a suggestion, but it might be good to format kubectl config use-context.
|
@stmcginnis, thanks for review, - updates done. If there are no further updates can you merge it pls. |
stmcginnis
approved these changes
Jul 15, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@stmcginnis
This replaces PR: #909
909 was a PR in to the
docsbranch,. I have completed suggested updates in 909. I have closed that PR now and this PR merging tomainreplaces itAdding workload cluster content
closes: #907