ce0ab00360
We use constants.OldestKubernetesVersion for testing the oldest version and limiting --kubernetes-version when starting the clusters. Our tradition is testing 6 releases back from current version, but we were testing 14 release back (1.20.0). For upgrading containerd to latest version (v2.1.4) we need to upgrade to a newer release. Upgrade constants.OldestKubernetesVersion to 1.28.0 which seems to pass all tests. legacyVersion() used in version_upgrade_test.go was 1.26.0. The comment in file mention that this should be release from the last 6 month. We do see failures in the relevant tests (TestRunningBinaryUpgrade) in many builds so I bumped it as well to 1.32.0 (2 releases back from current). In preload_test.go we tested --kubernetes-version=1.24.4 which is not compatible with containerd v2. Use legacyVersion() instead so we don't need to maintain another version. We had many example of --kubernetes-version in the docs using older version which are not supported. Replace all example with current version to minimize future maintenance. We need to automated this later so updating the version in minikube will also update the examples. With this change we have 2 places to update kubernetes versions: - constants.*KubernetesVersion - legacyVersion() |
||
|---|---|---|
| .github | ||
| .openvex/templates | ||
| cmd | ||
| deploy | ||
| enhancements | ||
| hack | ||
| images/logo | ||
| installers | ||
| pkg | ||
| site | ||
| test | ||
| third_party | ||
| translations | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.yaml | ||
| .markdownlint.json | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| SECURITY-INSIGHTS.yml | ||
| SECURITY.md | ||
| SECURITY_CONTACTS | ||
| code-of-conduct.md | ||
| default.profraw | ||
| go.mod | ||
| go.sum | ||
| go.work.sum | ||
| netlify.toml | ||
| sonar-project.properties | ||
| test.sh | ||
| ver.md | ||
README.md
minikube
minikube implements a local Kubernetes cluster on macOS, Linux, and Windows. minikube's primary goals are to be the best tool for local Kubernetes application development and to support all Kubernetes features that fit.
Features
minikube runs the latest stable release of Kubernetes, with support for standard Kubernetes features like:
- LoadBalancer - using
minikube tunnel - Multi-cluster - using
minikube start -p <name> - NodePorts - using
minikube service - Persistent Volumes
- Ingress
- Dashboard -
minikube dashboard - Container runtimes -
minikube start --container-runtime - Configure apiserver and kubelet options via command-line flags
- Supports common CI environments
As well as developer-friendly features:
- Addons - a marketplace for developers to share configurations for running services on minikube
- NVIDIA GPU support - for machine learning
- AMD GPU support - for machine learning
- Filesystem mounts
For more information, see the official minikube website
Installation
See the Getting Started Guide
📣 Please fill out our fast 5-question survey so that we can learn how & why you use minikube, and what improvements we should make. Thank you! 👯
Documentation
See https://minikube.sigs.k8s.io/docs/
More Examples
See minikube in action here
Governance
Kubernetes project is governed by a framework of principles, values, policies and processes to help our community and constituents towards our shared goals.
The Kubernetes Community is the launching point for learning about how we organize ourselves.
The Kubernetes Steering community repo is used by the Kubernetes Steering Committee, which oversees governance of the Kubernetes project.
Community
minikube is a Kubernetes #sig-cluster-lifecycle project.
-
#minikube on Kubernetes Slack - Live chat with minikube developers!
Join our community meetings: