From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: minikube: update to 1.28.0.
Date: Tue, 07 Feb 2023 03:03:55 +0100 [thread overview]
Message-ID: <20230207020355.5VmT8wgBF3s_rXqYYdJLcvPDn2rTIhL_jI_gGWzZ0gQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40427@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
There's a closed pull request on the void-packages repository
minikube: update to 1.28.0.
https://github.com/void-linux/void-packages/pull/40427
Description:
I tested the changes in this PR: **briefly**
```
ag@server ~ ❯ minikube start
* minikube 1.28.0 on Void
- MINIKUBE_IN_STYLE=false
- MINIKUBE_HOME=/zpool/vm/minikube
* Automatically selected the kvm2 driver
* Starting control plane node minikube in cluster minikube
* Downloading Kubernetes v1.25.3 preload ...
> preloaded-images-k8s-v18-v1...: 385.44 MiB / 385.44 MiB 100.00% 55.16 M
* Creating kvm2 VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
* Preparing Kubernetes v1.25.3 on Docker 20.10.20 ...
- Generating certificates and keys ...
- Booting up control plane ...
- Configuring RBAC rules ...
* Verifying Kubernetes components...
- Using image gcr.io/k8s-minikube/storage-provisioner:v5
* Enabled addons: storage-provisioner, default-storageclass
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
ag@server ~ ❯ virsh list
Id Name State
--------------------------
1 minikube running
ag@server ~ at ⎈ minikube ❯ k get no
NAME STATUS ROLES AGE VERSION
minikube Ready control-plane 69s v1.25.3
```
prev parent reply other threads:[~2023-02-07 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 1:45 [PR PATCH] " Goorzhel
2022-11-10 1:53 ` Goorzhel
2023-02-07 2:03 ` Goorzhel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230207020355.5VmT8wgBF3s_rXqYYdJLcvPDn2rTIhL_jI_gGWzZ0gQ@z \
--to=goorzhel@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).