k3s

Manually keeping all dependencies up to date can be a time consuming task which can easily be automated.

One possible solution for this is renovatebot which periodically checks for new versions and can create a pull request for each update found.

It can easily be deployed on kubernetes via helm and works with [gite

Expected Behaviour

Change the default cron spec in --etcd-snapshot-schedule-cron (default: "0 */12 * * *"):

--k3s-extra-args '--etcd-snapshot-schedule-cron * * * * *'

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener

Is your feature request related to a problem?

Yes I would like to install and maintain vcluster using only homebrew like all my other packages on macos

Which solution do you suggest?

Having either a tap in your organization or send vcluster on the main homebrew repository

Which alternative solutions exist?

Install manually. The problem is that I would like to receive updates using

What we need

In the case of using openelb as the Kubernetes load balancing implementation, the allocation of openelb external-ip-pool can only be viewed on the terminal interface by accessing Kubernetes resources with kubectl. However, more and more kubernetes users are using specific dashboards to operate and manage clusters or workloads, such as KubeSphere. Therefore, the current usage is n

Is your feature request related to a problem? Please describe.

Some (potential) users are not able to change the size of their home partition when standing up a virtual instance to work on. When working with them we had to manually edit the file where the cachePath was defined so we could point it to a place with actual space.

Describe the solution you'd like
A global flag for spe

Some clusters can be stopped when k3x is started. Users could think the current cluster should be ready, but they would really need to "start" it. We should show a warning saying something like "the current cluster is stopped".