Split Manifest into individual job

[irish1986]

Proposed Changes

I have noticed working with this repo that I often end up adding more manifest and "goodies" features into it. Splitting manifest into individual files simplify adding new feature or debugging specific workload/

• Move kube-vip manifest into individual files
• Move metallb manifest and pool config into individual files
• I am not checking "Did not add any unnecessary changes" since this could be consider unnecessary.
• If this approach is approved, I plan to add more feature like longhorn, kured and others

Furthermore, I proposed to add system-upgrade workload as part of the default configuration. System-upgrade allows to automated K3S image update via various means. Also it is a good use case on why splitting manifest could be useful

• Add system-upgrade manifest (need to expand post install testing but this works)

Checklist

• [X] Tested locally
• [X] Ran site.yml playbook
• [X] Ran reset.yml playbook
• [ ] Did not add any unnecessary changes
• [X] Ran pre-commit install at least once before committing
• [X] 🚀

[timothystewart6]

Thanks! Looks like some lint! Also, wonder if you we can break this up into 2 PRs, one for reorg and one for system upgrade, that way each PR is limited to 1 change / feature and easy to roll back if needed. Thank you!

[irish1986]

can break this up into 2 PRs

I taught about that, will do later today or maybe next week after holidays rush.

And I'll check what happens with the linter, I suspect I might have linted the wrong branch locally before pushing upstream.

[irish1986]

I got mixed up in couple of changes and branches so I've decided the best is to close this PR and re-open it via a new PR. Sorry for the inconvenience just that I never had to split an existing PR.