- 22 7月, 2020 12 次提交
-
-
由 priyawadhwa 提交于
Implement Warning type for JSON output
-
由 Medya Ghazizadeh 提交于
(Addons) Create a new command in every retry
-
由 Sharif Elgamal 提交于
* metadata addon works * Add code for metadata server image and makefile rules * remove log message * update to work with v1.13.11 * update readme * fix metadata addon stuff for newer codebase * buncha changes * just so many changes * ch-ch-ch-ch-changes * addon works * update readme * boilerplate * revert unrelated change * move server code to another repo * switch addon name to gcp-auth * metadata -> gcp-auth * missed one * automate finding of credentials * remove unnecessary comment * address comments * Update README.md * Update README.md * use mustload everywhere * swap selector condition * upgrade kube-webhook-certgen to 1.3 * move paths to constants * add notice to user on addon enable * adding addon documentation * move addons documentation inside handbook * remove old addons docs location Co-authored-by: NPriya Wadhwa <priyawadhwa@google.com>
-
由 Medya Ghazizadeh 提交于
Use preloaded tarball for cri-o container runtime
-
由 Sharif Elgamal 提交于
regenerate config on retry
-
由 Medya Ghazizadeh 提交于
Support more error messages for container inspect
-
由 Medya Ghazizadeh 提交于
update gopogh to have sorted test duration
-
由 Sharif Elgamal 提交于
-
由 Medya Ghazizadeh 提交于
fix typo
-
由 Priya Wadhwa 提交于
-
由 Priya Wadhwa 提交于
-
由 Medya Gh 提交于
-
- 21 7月, 2020 18 次提交
-
-
由 Shubham 提交于
Whenever a `kubectl apply` fails while enabling an addon, it is retried with exponential backoff. The command (type `*exec.Cmd`) that this retry function runs in created outside the function - which means that it is reused on every retry. This is a problem because `exec.Cmd` (https://godoc.org/github.com/pkg/exec#Cmd) states that "... Cmd cannot be reused after calling its Run or Start methods." This retry is a common case due to, say, a CRD and its resource being present in the same YAML file of the addon which causes a race condition where the resource is created before its CRD is created in the cluster - this race is fixed by subsequent retries. I've noticed this in the dashboard and the ambassador addon. Due to the above mentioned bug, minikube throws errors like `exec: already started` in every retry and the retry is never successful, manifests are never deployed and addon creation errors out. Related to #8138 #8119 #8372
-
由 Anders F Björklund 提交于
Pretty much the same as containerd, minus Restart
-
由 Medya Gh 提交于
-
由 Medya Gh 提交于
-
由 Medya Gh 提交于
-
由 priyawadhwa 提交于
Update external-provisioner for storage provisioner for Kubernetes 1.18
-
由 Medya Ghazizadeh 提交于
update golang version
-
由 Medya Ghazizadeh 提交于
Generate cri-o container runtime preload tarball
-
由 Medya Ghazizadeh 提交于
docker/podman: warn if allocated memory is below limit
-
由 Sharif Elgamal 提交于
-
由 Medya Ghazizadeh 提交于
Make sure to prepare the kic volume after creation
-
由 Medya Gh 提交于
-
由 Medya Gh 提交于
-
由 Anders F Björklund 提交于
Now that there is no more race between the containers for preparing the volume, we can use it for podman as well... Previously we risked ending up with not copying the contents of /var from the container image, which made it not work.
-
由 Anders F Björklund 提交于
The volume is created as empty, so make sure that we run a container to do the initial copy of /var from the image. This is to avoid race conditions later on, where the preload starts to use the created volume for packing up the tarball.
-
由 Medya Ghazizadeh 提交于
update roadmap 2020
-
由 Medya Gh 提交于
-
由 Medya Gh 提交于
-
- 19 7月, 2020 3 次提交
-
-
由 Medya Ghazizadeh 提交于
update releases.json to include v1.12.1
-
由 Medya Ghazizadeh 提交于
Fix documentation typo
-
由 Jose Donizetti 提交于
-
- 18 7月, 2020 7 次提交
-
-
由 minikube-bot 提交于
-
由 priyawadhwa 提交于
Release v1.12.1
-
由 Priya Wadhwa 提交于
-
由 Priya Wadhwa 提交于
-
由 Priya Wadhwa 提交于
-
由 priyawadhwa 提交于
Fix bugs which prevented upgrades from v1.0+ to v1.12
-
由 Thomas Stromberg 提交于
-