feat: add kube-linter tool

[tvcsantos]

Description

This PR adds kube-linter cli tool to arkade. KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.

Motivation and Context

• I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer (required)

I would be nice to have kube-linter cli tool included on arkade. KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.

How Has This Been Tested?

Added tests to get_test.go and also run ./hack/test-tool.sh kube-linter.

If updating or adding a new CLI to arkade get, run:

go build && ./hack/test-tool.sh TOOL_NAME

Logs attached below:

arkade_kube_linter.log

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)

Documentation

• I have updated the list of tools in README.md if (required) with ./arkade get --format markdown
• I have updated the list of apps in README.md if (required) with ./arkade install --help

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 tested this on arm, or have added code to prevent deployment

[alexellis]

Thanks for the PR. @Jasstkn could you review please?

[Jasstkn]

looks like kube-linter doesn't support ARM at all, therefore this test is redundant.

I think that we need to hardcode the arch64 as the only supported architecture in the template and remove the redundant test. @alexellis what are your thoughts here?

[tvcsantos]

You are right I will remove it ;)

[Jasstkn]

@tvcsantos can I also ask you to update your branch from master?

[tvcsantos]

@tvcsantos can I also ask you to update your branch from master?

Will do that. Ty

[derek]

Thank you for your contribution. unfortunately, one or more of your commits are missing the required "Signed-off-by:" statement. Signing off is part of the Developer Certificate of Origin (DCO) which is used by this project.

Read the DCO and project contributing guide carefully, and amend your commits using the git CLI. Note that this does not require any cryptography, keys or special steps to be taken.

💡 Shall we fix this?

This will only take a few moments.

First, clone your fork and checkout this branch using the git CLI.

Next, set up your real name and email address:

git config --global user.name "Your Full Name"
git config --global user.email "[email protected]"

Finally, run one of these commands to add the "Signed-off-by" line to your commits.

If you only have one commit so far then run: git commit --amend --signoff and then git push --force.
If you have multiple commits, watch this video.

Check that the message has been added properly by running "git log".

[tvcsantos]

All done. If you need something extra ping :)

[Jasstkn]

LGTM 🚀

[alexellis]

@tvcsantos just need a rebase on the README file now, thanks.

[derek]

Thank you for your contribution. unfortunately, one or more of your commits are missing the required "Signed-off-by:" statement. Signing off is part of the Developer Certificate of Origin (DCO) which is used by this project.

Read the DCO and project contributing guide carefully, and amend your commits using the git CLI. Note that this does not require any cryptography, keys or special steps to be taken.

💡 Shall we fix this?

This will only take a few moments.

First, clone your fork and checkout this branch using the git CLI.

Next, set up your real name and email address:

git config --global user.name "Your Full Name"
git config --global user.email "[email protected]"

Finally, run one of these commands to add the "Signed-off-by" line to your commits.

If you only have one commit so far then run: git commit --amend --signoff and then git push --force.
If you have multiple commits, watch this video.

Check that the message has been added properly by running "git log".

[tvcsantos]

@tvcsantos just need a rebase on the README file now, thanks.

Done ;)

[tvcsantos]

@tvcsantos just need a rebase on the README file now, thanks.

Done ;)

okay not done. I will do it in a bit :D. Having some troubles with the signoff :D

[tvcsantos]

Now all good :). If you need something ping me 👍

[alexellis]

Looks like we have 6x commits now, so if you follow my video it will walk you through how to squash them all down:

https://www.youtube.com/watch?v=8j0H6urZ-bU

But before you do that, rebase master with git pull origin master -r - or if master is your branch, add an upstream remote:

git remote add upstream https://github.com/alexellis/arkade
git pull upstream master -r

[tvcsantos]

Looks like we have 6x commits now, so if you follow my video it will walk you through how to squash them all down:

https://www.youtube.com/watch?v=8j0H6urZ-bU

But before you do that, rebase master with git pull origin master -r - or if master is your branch, add an upstream remote:

git remote add upstream https://github.com/alexellis/arkade
git pull upstream master -r

Okay I got it you only want one commit. Done ;) sorry for the delay

[alexellis]

Thanks Tiago. Looking forward to your next PR.