[fix] kubeconfig merge with wrong order

[zzswang]

issue

#316 (comment)

Description

• merge kube config files in wrong order
• reproduced with raw kubectl command

How Has This Been Tested?

• k3sup install with 3 nodes
• remove k3s
• resetup with 3 nodes, now it works fine

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s
• I have added tests to cover my changes.
• All new and existing tests passed.

[derek]

Thank you for your contribution. I've just checked and your commit doesn't appear to be signed-off. That's something we need before your Pull Request can be merged. Please see our contributing guide.
Tip: if you only have one commit so far then run: git commit --amend --signoff and then git push --force.

[zzswang]

@alexellis

Will we merge this pr recently?
Or I still need to do the merge manually.

[alexellis]

Hi @zzswang, I'll tend to prioritise issue that relate to a clearly defined problem. I still think this is a user error rather than something in k3sup, and don't understand the negative effects of changing this order.

If k3sup is something that creates value for you and saves you time, please consider becoming a GitHub sponsor so that I can continue to support users like yourself with their bespoke support requests.

I've commented on your issue. Can you clarify?

Alex

[zzswang]

commented in the issue

#316 (comment)