Skip to content

Confirm the correct kubeconfig is being used #2635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Confirm the correct kubeconfig is being used #2635

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions content/rancher/v2.x/en/upgrades/upgrades/ha/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,28 @@ If you installed Rancher using the RKE Add-on yaml, follow the directions to [mi

- **Review the [known upgrade issues]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/#known-upgrade-issues) and [caveats]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/#caveats)** in the Rancher documentation for the most noteworthy issues to consider when upgrading Rancher. A more complete list of known issues for each Rancher version can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums.](https://forums.rancher.com/c/announcements/12)
- **For [air gap installs only,]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap) collect and populate images for the new Rancher server version.** Follow the guide to [populate your private registry]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/populate-private-registry/) with the images for the Rancher version that you want to upgrade to.
- **Confirm the correct kubeconfig YAML file is configured**, follow the steps below to confirm the Rancher management cluster kubeconfig is configured.

Set the `KUBECONFIG` environment variable for the Rancher management cluster that is being upgraded.

```
export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
```

Verify that it contains the correct `server` parameter, it should point directly to one of your cluster nodes on port `6443`.

```
kubectl config view -o=jsonpath='{.clusters[*].cluster.server}'
https://NODE:6443
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to add a note for the use of localhost in case of k3s (where people did not replace it with their load balancer/node address)?

```

If the output from the command shows your Rancher hostname with the suffix `/k8s/clusters`, the wrong kubeconfig YAML file is configured. It should be the file that was created with RKE or K3s when creating the cluster to run Rancher.

Confirm that Rancher pods are running within the cluster.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is a separate step, should it be in the list above so it doesn't get overlooked?


```
kubectl get pods -n cattle-system
```

# Upgrade Outline

Expand Down