[BUG] generate_addon_csi.sh uses wrong kubeconfig server

[dfaltum]

Describe the bug
If you're following this guide, you may experience some trouble with the generated kubeconfig.

To Reproduce
If you run this script via Rancher provided kubeconfig or via SSH from the Harvester CP node, the following line will give you an incorrect kubectl server. For example:

++ kubectl config view -o 'jsonpath={.clusters[?(@.name == "default")].cluster.server}'
+ ENDPOINT=https://127.0.0.1:6443

Expected behavior
The kubeconfig file should contain an IP address that is reachable from outside of the cluster.

[Vicente-Cheng]

Hi @dfaltum,

Thanks for raising this issue.
I do some checks with that.

I would like to know where you executed this script.
On the Harvester cluster or the downstream cluster?

I thought the document was not very clear because the purpose was that we should run this script on the downstream cluster. And using the kubeconfig of the host harvester cluster.

[dfaltum]

Hi @Vicente-Cheng,
First, I've tried the script with an SSH login to the Harvester cluster. I also tried using the Harvester kubeconfig file provided by Rancher. So both approaches are problematic.

[Vicente-Cheng]

Hi @dfaltum,

Thanks for the explanation.
I checked with the latest kubeconfig download from the rancher UI.

You are right. This should be fixed by your PR.
Thanks again for your fix!

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#1363

[dfaltum]

harvester/harvester-csi-driver#40 merged