From 3de3df0772b7d520c0b0b3b31c72d36aa216a639 Mon Sep 17 00:00:00 2001 From: LucasSaintarbor Date: Tue, 16 Jan 2024 16:03:50 -0800 Subject: [PATCH] Replacing dollar sign placeholders --- .../troubleshooting.md | 22 +++++++++---------- .../upgrading-rancher-payg-cluster.md | 14 ++++++------ .../troubleshooting.md | 8 +++---- 3 files changed, 22 insertions(+), 22 deletions(-) diff --git a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/troubleshooting.md b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/troubleshooting.md index 1246bb82d50..2266debe877 100644 --- a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/troubleshooting.md +++ b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/troubleshooting.md @@ -14,10 +14,10 @@ kubectl get pods --all-namespaces If a pod is not in a `Running` state, you can attempt to find the root cause with the following commands: -- Describe pod: `kubectl describe pod $POD_NAME -n $NAMESPACE` -- Pod container logs: `kubectl logs $POD_NAME -n $NAMESPACE` -- Describe job: `kubectl describe job $JOB_NAME -n $NAMESPACE` -- Logs from the containers of pods of the job: `kubectl logs -l job-name=$JOB_NAME -n $NAMESPACE` +- Describe pod: `kubectl describe pod -n ` +- Pod container logs: `kubectl logs -n ` +- Describe job: `kubectl describe job -n ` +- Logs from the containers of pods of the job: `kubectl logs -l job-name= -n ` ## Recovering from Failed Pods @@ -33,13 +33,13 @@ 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 \ - --set rancherHostname=$HOST_NAME \ - --set rancherServerURL=https://$HOST_NAME \ - --set rancherReplicas=$REPLICAS \ - --set global.aws.accountNumber=$AWS_ACCOUNT_ID \ - --set global.aws.roleName=$ROLE_NAME +oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/suse//rancher-cloud-helm/rancher-cloud --install \ + --version \ + --set rancherHostname= \ + --set rancherServerURL=https:// \ + --set rancherReplicas= \ + --set global.aws.accountNumber= \ + --set global.aws.roleName= ``` ## Rancher Usage Record Not Found diff --git a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md index 0acc4b1e762..32d19738cac 100644 --- a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md +++ b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md @@ -8,14 +8,14 @@ To upgrade the deployed Helm chart to the latest version, run the following Helm ```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 \ - --version $UPGRADED_CHART_VERSION \ - --set rancherHostname=$HOST_NAME \ - --set rancherServerURL=https://$HOST_NAME \ - --set rancherReplicas=$REPLICAS \ +oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/suse//rancher-cloud-helm/rancher-cloud \ + --version \ + --set rancherHostname= \ + --set rancherServerURL=https:// \ + --set rancherReplicas= \ --set rancherIngressClassName=nginx \ - --set global.aws.accountNumber=$AWS_ACCOUNT_ID \ - --set global.aws.roleName=$ROLE_NAME + --set global.aws.accountNumber= \ + --set global.aws.roleName= ``` To check if the upgraded Helm chart deployed successfully, run the following Helm command: diff --git a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/troubleshooting.md b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/troubleshooting.md index a9d21f35bd0..91671240aed 100644 --- a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/troubleshooting.md +++ b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/troubleshooting.md @@ -46,10 +46,10 @@ kubectl get pods --all-namespaces If a pod is not in a `Running` state, you can attempt to find the root cause with the following commands: -- Describe pod: `kubectl describe pod $POD_NAME -n $NAMESPACE` -- Pod container logs: `kubectl logs $POD_NAME -n $NAMESPACE` -- Describe job: `kubectl describe job $JOB_NAME -n $NAMESPACE` -- Logs from the containers of pods of the job: `kubectl logs -l job-name=$JOB_NAME -n $NAMESPACE` +- Describe pod: `kubectl describe pod -n ` +- Pod container logs: `kubectl logs -n ` +- Describe job: `kubectl describe job -n -n ` ## Rancher Usage Record Not Found