You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using spf13/viper should be a good option for this.
Context
In my case, I would like to check my cluster.yml into a Git repository and deploy the cluster via GitHub Actions.
There are a few implementation details, which I would like input on:
Should the CLI API be a config flag for k3sup install --config cluster.yaml?
Your Environment
What OS or type or VM are you using for your cluster? Where is it hosted? (for k3sup install/join)
I am using manually provisioned baremetal machines hosted on-premise. The hardware includes:
Raspberry Pis (arm64)
Intel Atom N2600 Netbook (amd64)
Operating System and version (e.g. Linux, Windows, MacOS):
$ uname -a
Linux dfr-rtcm4-0 5.4.0-1042-raspi #46-Ubuntu SMP PREEMPT Fri Jul 30 00:35:40 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
Linux mdn-e1230-0 5.4.0-99-generic #112-Ubuntu SMP Thu Feb 3 13:50:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
"Be part of the solution"
Subject to approval, are you willing to work on a Pull Request for this issue or feature request?
Yes
No
Editor's note: The link to the CONTRIBUTING.md is broken as it points to the old inlets repository.
The text was updated successfully, but these errors were encountered:
The Rancher Kubernetes Engine allows for a
cluster.yaml
configuration file, which is then used to bootstrap a cluster viarke up
.Expected Behaviour
Users can provide a configuration file, e.g.
cluster.yaml
, which describes the connection information for the nodes.Current Behaviour
Currently, it is required to perform additional shell scripting around
k3sup
to bring your cluster up declaratively.Are you a GitHub Sponsor (Yes/No?)
Possible Solution
For my use-case I would need something like the following at least:
Using
spf13/viper
should be a good option for this.Context
In my case, I would like to check my
cluster.yml
into a Git repository and deploy the cluster via GitHub Actions.There are a few implementation details, which I would like input on:
k3sup install --config cluster.yaml
?Your Environment
What OS or type or VM are you using for your cluster? Where is it hosted? (for
k3sup install/join
)I am using manually provisioned baremetal machines hosted on-premise. The hardware includes:
Operating System and version (e.g. Linux, Windows, MacOS):
"Be part of the solution"
Subject to approval, are you willing to work on a Pull Request for this issue or feature request?
Editor's note: The link to the
CONTRIBUTING.md
is broken as it points to the old inlets repository.The text was updated successfully, but these errors were encountered: