k3s
Here are 434 public repositories matching this topic...
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
-
Updated
Mar 26, 2022 - Java
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
-
Updated
Mar 29, 2022
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
-
Updated
Mar 30, 2022 - Jinja
-
Updated
Mar 29, 2022 - Python
-
Updated
Mar 30, 2022 - Shell
-
Updated
Feb 18, 2022 - Jinja
-
Updated
Mar 12, 2022 - HTML
-
Updated
Mar 30, 2022 - Go
-
Updated
Mar 26, 2022 - Dockerfile
Environment
Device and OS: amd64 ubuntu
App version: latest
Kubernetes distro being used: k3d
Other:
Steps to reproduce
- if your
~/.git-credentialshas a typo, thecredentialParserwill identify the error but still creates tries to capture the password
Expected result
- skip that cred
Actual Result
anic: runtime error: invalid memory address or nil po-
Updated
May 15, 2021 - C
-
Updated
Mar 30, 2022 - Jinja
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".
-
Updated
Mar 28, 2022 - Go
-
Updated
Feb 14, 2022 - Jinja
-
Updated
Feb 18, 2022 - Shell
-
Updated
Oct 12, 2021 - Roff
-
Updated
Mar 3, 2021 - Shell
-
Updated
Mar 5, 2021
-
Updated
Mar 22, 2022 - HCL
-
Updated
Mar 23, 2022 - Shell
-
Updated
Mar 22, 2021 - Shell
Improve this page
Add a description, image, and links to the k3s topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the k3s topic, visit your repo's landing page and select "manage topics."
Expected Behaviour
Change the default cron spec in --etcd-snapshot-schedule-cron (default: "0 */12 * * *"):