Use correct config for additional clusters

[XenoAura]

Fix: #5033

Description of the change

clientsetForConfig uses incorrect cluster config variable

kubeapps/pkg/kube/kube_handler.go

Lines 333 to 336 in 11c8792

	svcConfig := *config
	svcConfig.BearerToken = additionalCluster.ServiceToken
	svcClientset, err = a.clientsetForConfig(config)

Benefits

Correct behavior for getting a list of namespaces for additional clusters

Possible drawbacks

Applicable issues

• fixes Kubeops cannot return a list of namespaces in additional clusters #5033

Additional information

[netlify]

✅ Deploy Preview for kubeapps-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	037a2c4
🔍 Latest deploy log	https://app.netlify.com/sites/kubeapps-dev/deploys/6304ad2aed462a0009c9a7af
😎 Deploy Preview	https://deploy-preview-5034--kubeapps-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[vmwclabot]

@XenoAura, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

[antgamdia]

Thanks for the contribution @XenoAura ! LGTM, however, could you add a unit test so that we can avoid future regressions (we are planning to deprecate Kubeops and move the logic to the kubeapps-apis service) ?

Additionally, it seems the CircleCI checks are not passing (I mean, not failing, just that, sometimes, they don't get reported back, perhaps you need an empty commit or just merging main into your branch)

[antgamdia]

Forgot to actually +1 the changes 😅 , just waiting for the test to merge it.

[vmwclabot]

@XenoAura, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement.

[antgamdia]

Let me update the branch with the latest changes (mainly to trigger the CI checks, which were somehow stuck). Also, the CLA bot complained about the signing process, please let us know if you are facing any issues with it. Feel free to reach out to us in Slack.

[vmwclabot]

@XenoAura, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement.

[vmwclabot]

@XenoAura, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement.

[antgamdia]

@XenoAura , is there anything I can help you with the CLA issues the bot is reporting? Or maybe with the unit test?

[castelblanque]

After removal of kubeops (#5253), parts of the enclosing code used by this PR have been migrated and thus can not be applied.
Changes have been reworked in #5286.
Thanks to @XenoAura for the contribution and creating the issue #5033.