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>
This change sets kernel option CONFIG_DEBUG_INFO_BTF so that BTF type
information is generated, which is necessary for eBPF-based tooling such
as Tetragon to work. Additionally, for x86_64 only, it adds the recommended
option CONFIG_BPF_KPROBE_OVERRIDE to also support policy enforcement.
Setting CONFIG_DEBUG_INFO_BTF also requires setting
CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT. Setting
CONFIG_BPF_KPROBE_OVERRIDE also requires setting
CONFIG_FUNCTION_ERROR_INJECTION.
minikube would not start a cluster successfully with docker driver
and
crio runtime due to missing dbus packages
Adding dbus packages to the kicbase image build
lets minikube start to complete successfully.
Signed-off-by: Michael Adam <obnox@samba.org>
Co-authored-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
The Gluster project has not has a release in a few years, maintenance
slowed down to the point it is almost standing still. Heketi as
component for deploying parts of the storage platform has been archived
in 2023.
Providing the storage-provisioner-gluster addon might give users the
wrong expectations. There is no guarantee Gluster is working with recent
minikube versions.
Updated ingress-dns addon Pod template to align with current
deployment requirements:
* Added hostPort mapping for UDP 53
* Mounted ConfigMap for configurable DNS settings
* Introduced dns-nodata-delay-ms option via ConfigMap
- Switched default ingress-dns image reference from
gcr.io/k8s-minikube/minikube-ingress-dns to
kicbase/minikube-ingress-dns (multi-arch build available
on Docker Hub).
- Left legacy image mapping in aliyun_mirror.json for
backward compatibility, while adding new kicbase mapping.
Signed-off-by: Kartik Joshi <karikjoshi21@gmail.com>
* iso: Enable VirtioFS for x86_64 and aarch64
The Virtio Filesystem[1] allows guests to mount file systems from the
host.
Testing with krunkit show 10 times faster read throughput:
minikube krunkit - 9p:
$ time cp /mnt/models/mistral-7b-instruct-v0.2.Q4_K_M.gguf model
real 0m34.330s
user 0m0.019s
sys 0m1.959s
podman krunkit - virtiofs:
$ time cp /Users/nir/Downloads/models/mistral-7b-instruct-v0.2.Q4_K_M.gguf model
real 0m3.245s
user 0m0.006s
sys 0m1.035s
We must have virtiofs for playing with AI workload in krunkit. It can be
nice improvment for vfkti and qemu, and should be available in ohter
hypervisors.
[1] https://virtio-fs.gitlab.io/index.html
* Updating ISO to v1.36.0-1753487480-21147
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>
* iso: Minimal kernel for arm64
Create default arm64 config and disable stuff that we cannot use in
a VM.
This chagne was generated by:
1. Create defualt arm64 config
cd out/buildroot/output-aarch64/build/linux-6.6.95
make ARCH=arm64 defconfig
make ARCH=arm64 menuconfig
(exit saving changes)
2. Disable features that we don't need in the minikube VM:
- Platform suppport
- all platforms
- Device drivers
- Multimedia support
- Sound support
3. Updated our linux defconfig
cd out/buildroot/output-aarch64
make linux-update-defconfig
4. Normalize the config
make linux-menuconfig-aarch64
(exit saving changes)
With this config qemu, vfkit, and krunkit boot with --no-kubernetes, and
graceful shutdown works in vfkit and krunkit (using --restful-uri).
We cannot start kubernetes yet since some features are not available in
the default architecture config.
* iso: Add configs removed by defualt config
This restores the configs removed by updating from the default
architecture config. These configs are required for kubernetes support.
After adding the removed configs, run `make linux-menuconfig-aarch64` to
normalize the config and remove multimedia and sound card support again.
* iso: Unbreak go packages build
Adding go.work seems to break podman build. The workspace is needed only
for running the update commands so let's disable it when building the
iso.
We may need much bigger change to ensur that the workspace is used only
when running the update go commands, or remove it. This change fixes
only the iso build.
* Updating ISO to v1.36.0-1752940814-21089
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>
* iso: Update kernel to 6.6.95 for x86_64
Generated by running `make iso-menuconfig-x86_64` and updating kernel
version to longterm kernel 6.6.95 and kernel headers to 6.6.x, and then
running `make linux-menuconfig-x86_64` to update the linux config.
Additinally update hyperv-daemons package to use kernel 6.x.
* iso: Update kernel to 6.6.95 for aarch64
Generated by running `make iso-menuconfig-aarch64` and updating kernel
version to longterm kernel 6.6.95 and kernel headers to 6.6.x, and then
running `make linux-menuconfig-aarch64` to update the linux config.
* iso: Enable VirtIO GPU for krunkit driver
The krunkit driver exposes the host GPU via VirtIO GPU, enabling AI
workloads in the guest.
* Updating ISO to v1.36.0-1751445739-20995
---------
Co-authored-by: minikube-bot <minikube-bot@google.com>