mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
Apply suggestions from code review
Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Lucas Saintarbor
co-authored by
Billy Tat
Billy Tat
parent
dc7d68c3b2
commit
193603e209
+1
-1
@@ -61,7 +61,7 @@ eksctl create iamserviceaccount \
|
||||
|
||||
:::note
|
||||
|
||||
Rancher Prime utilizes cert-manager to issue and maintain its certificates. Rancher will generate a CA certificate of its own, and sign a cert using that CA.
|
||||
Rancher Prime utilizes cert-manager to issue and maintain its certificates. Rancher will generate a CA certificate of its own, and sign a certificate using that CA.
|
||||
|
||||
:::
|
||||
|
||||
|
||||
+2
-2
@@ -5,8 +5,8 @@ title: Prerequisites
|
||||
Before using Rancher Prime on AWS as a pay-as-you-go (PAYG) offering, you need the following resources, information, and tools:
|
||||
|
||||
- A Rancher-compatible EKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. Please refer to [Creating an EKS cluster](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#creating-an-eks-cluster-for-the-rancher-server) for bringing up an EKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress installed on the EKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#5-install-an-ingress) for instructions on how to deploy Ingress-INGINX on an EKS cluster.
|
||||
- Get the Load Balancer IP. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#6-get-load-balancer-ip) and Save the EXTERNAL-IP.
|
||||
- An ingress installed on the EKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#5-install-an-ingress) for instructions on how to deploy Ingress-NGINX on an EKS cluster.
|
||||
- Get the Load Balancer IP. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#6-get-load-balancer-ip) and save the EXTERNAL-IP.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN) and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#7-set-up-dns) for instructions on how to setup DNS. This DNS is setup to point at the EXTERNAL-IP saved.
|
||||
- Installation requires you have the following tools available and properly configured to access your AWS account, and your EKS cluster:
|
||||
- `aws`
|
||||
|
||||
+3
-3
@@ -33,8 +33,8 @@ Fix the problem and run:
|
||||
|
||||
```shell
|
||||
helm upgrade -n cattle-rancher-csp-deployer-system rancher-cloud --create-namespace \
|
||||
oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/suse/{{repository}}/rancher-cloud-helm/rancher-cloud --install \
|
||||
--version {{chart_version}} \
|
||||
oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/suse/$REPOSITORY/rancher-cloud-helm/rancher-cloud --install \
|
||||
--version $CHART_VERSION \
|
||||
--set rancherHostname=$HOST_NAME \
|
||||
--set rancherServerURL=https://$HOST_NAME \
|
||||
--set rancherReplicas=$REPLICAS \
|
||||
@@ -53,7 +53,7 @@ Error from server (NotFound): cspadapterusagerecords.susecloud.net "rancher-usag
|
||||
To resolve the error, run:
|
||||
|
||||
```shell
|
||||
kubectl get cm -n cattle-csp-billing-adapter-system csp-config -o yaml
|
||||
kubectl get configmap -n cattle-csp-billing-adapter-system csp-config -o yaml
|
||||
```
|
||||
|
||||
If a configuration is not listed, you can attempt to find the root cause by checking the pod status and log. See [Jobs and Pods](#jobs-and-pods) for more details.
|
||||
|
||||
+1
-1
@@ -24,7 +24,7 @@ To check if the upgraded Helm chart deployed successfully:
|
||||
helm ls -n cattle-rancher-csp-deployer-system
|
||||
```
|
||||
|
||||
:::note
|
||||
:::warning
|
||||
|
||||
PAYG customers will have constraints on getting updates to the offer based on the latest version SUSE has published to AWS, which may trail slightly behind the latest Rancher release.
|
||||
|
||||
|
||||
+2
-2
@@ -41,7 +41,7 @@ On the **Rancher Configuraion** tab, specify the following informaiton:
|
||||
|
||||
:::
|
||||
|
||||
1. Using the slide bar, select the number of **Replicas**.
|
||||
1. Using the slider, select the number of **Replicas**.
|
||||
1. Choose and confirm a **Bootstrap Password**. During the first login, you will use the bootstrap password to authenticate to the Rancher dashboard.
|
||||
:::note
|
||||
|
||||
@@ -68,7 +68,7 @@ On the **Extensions + applications** page, the **Provisioning State** may show *
|
||||
|
||||
## Log into the Rancher Dashboard
|
||||
|
||||
You may now login to Rancher dashboard by pointing your browser to the Rancher server URL *https://<Rancher hostname\>*, where *Rancher hostname* is the [hostname](#rancher-configuration) you have chosen when configuring Rancher.
|
||||
You may now login to Rancher dashboard by pointing your browser to the Rancher server URL *https://$RANCHER_HOSTNAME*, where *Rancher hostname* is the [hostname](#rancher-configuration) you have chosen when configuring Rancher.
|
||||
|
||||
:::note
|
||||
|
||||
|
||||
+1
-1
@@ -5,5 +5,5 @@ title: Prerequisites
|
||||
Before using Rancher Prime on Azure as a pay-as-you-go (PAYG) offering, you need the following resources, information, and tools:
|
||||
|
||||
- A Rancher-compatible AKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. The Rancher Prime PAYG offering can only be installed onto clusters in regions where both the AKS and Azure Container Apps service are available. See the [Azure documentation](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=container-apps,kubernetes-service®ions=all) for details. Please see [Creating an AKS cluster](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#3-create-the-aks-cluster) for bringing up an AKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress installed on the AKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#5-install-an-ingress) for instructions on how to deploy Ingress-INGINX on AKS cluster.
|
||||
- An ingress installed on the AKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#5-install-an-ingress) for instructions on how to deploy Ingress-NGINX on AKS cluster.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN) and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#7-set-up-dns) for instructions on how to setup DNS.
|
||||
|
||||
+1
-1
@@ -60,7 +60,7 @@ Error from server (NotFound): cspadapterusagerecords.susecloud.net "rancher-usag
|
||||
To resolve the error, run:
|
||||
|
||||
```shell
|
||||
kubectl get cm -n cattle-csp-billing-adapter-system csp-config -o yaml
|
||||
kubectl get configmap -n cattle-csp-billing-adapter-system csp-config -o yaml
|
||||
```
|
||||
|
||||
If a configuration is not listed, you can attempt to find the root cause by checking the pod status and log. See [Jobs and Pods](#jobs-and-pods) for more details.
|
||||
|
||||
Reference in New Issue
Block a user