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

Pin to minikube releases #1843

Open
mattmoor opened this issue Dec 17, 2021 · 0 comments
Open

Pin to minikube releases #1843

mattmoor opened this issue Dec 17, 2021 · 0 comments
Labels
area/internal bugs related to kaniko development workflow dependencies Pull requests that update a dependency file kind/enhancement New feature or request meta/integration-tests priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@mattmoor
Copy link
Collaborator

Actual behavior
The current logic floats to the latest release of minikube.

Expected behavior
We should ping to a minikube release and bump it over time to avoid a release randomly breaking CI.

This came up in #1842

cc @imjasonh

@mattmoor mattmoor mentioned this issue Dec 17, 2021
4 tasks
@aaron-prindle aaron-prindle added priority/p3 agreed that this would be good to have, but no one is available at the moment. area/internal bugs related to kaniko development workflow area/documentation For all bugs related to documentation meta/integration-tests dependencies Pull requests that update a dependency file kind/enhancement New feature or request and removed area/documentation For all bugs related to documentation labels May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/internal bugs related to kaniko development workflow dependencies Pull requests that update a dependency file kind/enhancement New feature or request meta/integration-tests priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

2 participants