k3s

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

Add the build status from GitHub Actions to the set of README badgets

Current Behaviour

I removed it because it was pointing at Travis, which we no

Add events and logs in key places during service processing, such as allocate and release EIP, GoBGP synchronization Nexthop, Layer2 mode selection Node

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".

Now that the framework is in place for ephemeral E2E tests we should add more, with the goal being the eventual elimination of the GitLab-based E2E testing using the e2e.sh shell script.

• Let's start making the GitHub Actions based tests required in PRs through the Branch Protection Rule in the repo settings
• E2E tests should all run in parallel to minimize the time it takes to run them