* fix kubevirt addon curl
Signed-off-by: Adil <179269350+adilwiser@users.noreply.github.com>
* add github action to auto-update kubevirt version
Signed-off-by: Adil <179269350+adilwiser@users.noreply.github.com>
---------
Signed-off-by: Adil <179269350+adilwiser@users.noreply.github.com>
* chore: update KubeRegistryProxy and Gvisor addon images and KubeRegistryProxy registry host.
* chore: Update KubeRegistryProxy image tag to include 'v' prefix.
* Remove the kube-registry-proxy version update workflow, script, and Makefile target.
* fix: make Azure VM cleanup more robust in functional workflow by explicitly deleting VM and associated resources.
* Always build the auto-pause binary on the host
Avoids needing the minikube source code for building kicbase
In the future it would be possible to use "kicbase-artifacts"
* Don't use minikube as the kicbase build context
Only build what is in the deploy/kicbase directory
Make sure to build or copy everything from minikube
* Simplify the build target for iso auto-pause
Make this more like the "minikube" targets
Unlike kicbase, this is dynamically linked?
* Updating kicbase image to v0.0.48-1767060456-22354
* Updating ISO to v1.37.0-1767060032-22354
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>
* Merge the patches directory separated by arch
For some reason these were duplicated before.
But they both had the same (obsolete) content?
* Use patches for go.hash instead of copying
It is now possible to provide hash files.
Use that, instead of modifying buildroot.
* Remove patches for obsolete package versions
* Clean up the go.hash file to match upstream
* Updating ISO to v1.37.0-1766949326-22348
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>
Co-authored-by: Medya Ghazizadeh <medyagh@users.noreply.github.com>
* ISO: upgrade crictl and crio to v1.35.0
* Kicbase: Update CRIO and CRICTL versions to v1.35
* auto updater: bump crictl version to v1.35.0 and extend version management to additional Prow integration scripts.
* chore: update crictl version to v1.35.0 in Prow integration scripts
* chore: remove empty line
* switch crio-bin to download pre-built static binaries instead of building from source.
* remove crio-shutdown service link (depricated)
* update crio.service to match upstream with minikube flavor
* build: Adjust crio and pinns binary installation source paths.
* Updating ISO to v1.37.0-1766811082-22332
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>
Update YAKD addon to pull images from ghcr.io/manusa instead of
docker.io/marcnuri. This aligns with the upstream project's new
container registry location.
* Addon portainer: Upgrade to version 2.27.7
* Add update portainer
* CI: Add portainer workflow
* change Makefile to run update-portainer to hack folder
Buildroot seems to prefer binary releases so we need to keep both source
and binary releases hashes. The tool ensures that for we have all the
hashes for the specified version.
The previous update script assumed building from source tarball, using
the tag (e.g. v2.1.4). But now we install a binary release, and the
makefile use the version without the "v" prefix (e.g. 2.1.4).
Change the update command:
- to use the tag without the prefix when replacing the version
- to update the hash file with the binary release checksum
With this change we need to download the tarball and compute the hash
twice, twice, since the x86_64 and aarch64 tarballs are different.
This was done by running:
make update-inspektor-gadget-version
ig-crd.yaml is removed because this was removed by Inspektor Gadget in
v0.42.0 (released in July).
See:
1d81a61312
Signed-off-by: Alban Crequy <alban.crequy@gmail.com>
Add special case handlers in get_version.go for components that require
non-standard version extraction methods:
- docsy: Extract git submodule commit hash
- kubernetes: Read DefaultKubernetesVersion from constants
- kubeadm-constants: Parse latest version from kubeadm images map
- kubernetes-versions-list: Count and summarize supported versions
- site-node: Use existing node version extraction from netlify.toml
Remove all entries from noVersionCheck map in update_all.go to enable
before/after version comparison for these components.
This allows 'DEP=component make get-dependency-version' commands to work
for all components, improving the auto-updater workflow.
* add update all go script
* add update all make target
* add update all make target
* standardize the component name for look up
* standardize amd amd component name
* rename all hack update go code to match component name to standardize
* delete extra folder
* update makefile with new standard filenames
* update component name amd
* fix amd gpu name
* skip amd for now till broken
* fix cilium helm update
* standard name for cloud spanner emulator
* standard crio name
* set max to 100
* delete old folder
* skip docsy for update all
* return error if fail to apply
* docsy versoin
* update files with go-github
* update file names
* move all make targets to same location
* standard name for golang comp
* skip istio addon
* skip kicbase version since it is not related
* skip kubeadm constant too
* skip kubernetes version too
* run components that dont support before/after
* update kubeadm constant
* skip kubeadm constant on non linux
* add kubernetes_versions_list to not support before/after
* list preload version as one of the internal jobs
* list preload version as one of the internal jobs
* simpllify the code
* use log for printing
* add boiler plates
* add gh workflow
minikube-bot
Adil Ansari
Medya Ghazizadeh
Medya Ghazizadeh
Medya Ghazizadeh
Anders Björklund
Marc Nuri
zhengtianbao
Nir Soffer
Nir Soffer
caesarsage
Predrag Rogic
ComradeProgrammer
Alban Crequy
Laxman Gupta