mirror of https://github.com/rancher/ui.git
parent
80c47468fe
commit
a8952b2e20
|
|
@ -43,6 +43,7 @@
|
|||
{{t
|
||||
"clusterNew.import.command.instructionGkeCluster"
|
||||
appName=settings.appName
|
||||
docsBase=settings.docsBase
|
||||
htmlSafe=true
|
||||
}}
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -3652,7 +3652,7 @@ clusterNew:
|
|||
detail: Choose the Google Project ID and Cloud Credential that will be used to launch your cluster.
|
||||
next: 'Next: Configure Cluster'
|
||||
projectId:
|
||||
help: TBD - Needs to match Project Id in Credential
|
||||
help: Must to match Project Id from Credential JSON
|
||||
label: Google Project ID
|
||||
title: Google Account Access
|
||||
alphaFeatures:
|
||||
|
|
@ -3898,7 +3898,7 @@ clusterNew:
|
|||
label: Preemptible nodes (beta)
|
||||
warning: Preemptible nodes will live at most 24 hours.
|
||||
privateCluster:
|
||||
details: GKE private clusters is an advanced and unique use case which requires a special GKE configurations. Before enabling private clusters ensure you have read through the <a href="{docsBase}/cluster-provisioning" target="_blank" rel="nofollow noopener noreferrer">docs TBD</a> for instructions on configuring GKE so private nodes may communicate with {appName}.
|
||||
details: GKE private clusters is an advanced and unique use case which requires a special GKE configurations. Before enabling private clusters ensure you have read through the <a href="{docsBase}/cluster-provisioning/hosted-kubernetes-clusters/gke/" target="_blank" rel="nofollow noopener noreferrer">GKE cluster provisioning docs</a> for instructions on configuring GKE so private nodes may communicate with {appName}.
|
||||
privateEndpoint:
|
||||
help: Control plane may only be accessed via the private IP.
|
||||
label: Enable Private Endpoint
|
||||
|
|
@ -4100,7 +4100,7 @@ clusterNew:
|
|||
import:
|
||||
command:
|
||||
instructionEksCluster: You are creating an EKS cluster that has private API access only. {appName} requires network access to the Kubernetes endpoint to complete cluster creation; You must manually run one of the following commands.
|
||||
instructionGkeCluster: You are creating a private GKE cluster, nodes in a private cluster do not have public IP addresses. For {appName} to finish setting up your cluster it must be able to speak to your nodes. Follow these <a href="https://rancher.com/docs/rancher/v2.x/" target="_blank" rel="nofollow noopener noreferrer">instructions TBD</a> to configure GKE in a way which allows this access.
|
||||
instructionGkeCluster: You are creating a private GKE cluster, nodes in a private cluster do not have public IP addresses. For {appName} to finish setting up your cluster it must be able to speak to your nodes. Ensure you follow these <a href="{docsBase}/cluster-provisioning/hosted-kubernetes-clusters/gke/" target="_blank" rel="nofollow noopener noreferrer">private cluster provisioning instructions</a> to configure GKE in a way which allows this access.
|
||||
instructions: 'Run the kubectl command below on an existing Kubernetes cluster running a supported Kubernetes version to import it into {appName}:'
|
||||
instructionsAdminRole: >-
|
||||
<b>Note:</b> If you want to import a Google Kubernetes Engine (GKE) cluster (or any cluster that does not supply you with a kubectl configuration file with the ClusterRole <b>cluster-admin</b> bound to it), you need to bind the ClusterRole <b>cluster-admin</b> using the command below.<br/><br/>Replace <b>[USER_ACCOUNT]</b> with your Google account address (you can retrieve this using <b>gcloud config get-value account</b>). If you are not importing a Google Kubernetes Engine cluster,
|
||||
|
|
|
|||
Loading…
Reference in New Issue