Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate the provisioning of kubectl in security-scan based on the server's k8s version #310

Open
andypitcher opened this issue May 31, 2024 · 0 comments
Assignees

Comments

@andypitcher
Copy link
Contributor

andypitcher commented May 31, 2024

Context:
With Rancher Manager version support ranging from k8s 1.23 to 1.31, we can't rely on a uniq kubectl version when building and running the security-scan. Since one kubectl can only cover up to three k8s versions. See kubectl version skew policy.

To do:
Alternative 1:

  • Use kubelr

Alternative 2:
Develop a Go script to do the following:

  • Connect to the server to check the version, then pick what kubectl version to choose.
  • Have a place (and naming) for multiple kubectl binaries.
  • Auto select the closest kubectl version to the api server (semver helps there).
  • Install kubectl version at runtime
@andypitcher andypitcher self-assigned this Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant