MariaDB is mentioned as supported in requirements, so adding to README too. Also raises a discussion earlier: https://github.com/k3s-io/k3s/issues/10686
Signed-off-by: Robert Silén <robert.silen@iki.fi>
* add droneignore, make trivial change to README for testing, updating drone config to use droneignore to skip CI when files are all matched
Signed-off-by: matttrach <matttrach@gmail.com>
* Update docs to include s390x arch
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Add s390x drone pipeline
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Install trivy linux arch only for amd64
This is done so that trivy is not installed for s390x arch
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Add s390x arch if condition for Dockerfile.test
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Add s390x arch in install script
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Add s390x GOARCH in build script
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Add SUFFIX s390x in scripts
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Skip image scan for s390x arch
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Update klipper-lb to version v0.3.5
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Update traefik version to v2.6.2
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Update registry to v2.8.1 in tests which supports s390x
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
* Skip compact tests for s390x arch
This is done because compact test require a previous k3s version which supports s390x and it is not available
Signed-off-by: Venkata Krishna Rohit Sakala <rohitsakala@gmail.com>
Before this change, we were copying a part of kube-router code to
pkg/agent/netpol directory with modifications, from which the biggest
one was consumption of k3s node config instead of kube-router config.
However, that approach made it hard to follow new upstream versions.
It's possible to use kube-router as a library, so it seems like a better
way to do that.
Instead of modifying kube-router network policy controller to comsume
k3s configuration, this change just converts k3s node config into
kube-router config. All the functionality of kube-router except netpol
is still disabled.
Signed-off-by: Michal Rostecki <mrostecki@opensuse.org>
Signed-off-by: Manuel Buil <mbuil@suse.com>
Fixed various issues in README.md.
This incorporates #2141, which should be closed because there are other spelling fixes in this PR.
- correct spelling
- correct grammar
- remove verbiage for stronger intent and clarity
- formatting consistency (e.g., spacing, numbered lists, etc.)
Signed-off-by: Vladislav Doster <mvdoster@gmail.com>
* Fix typo in README.md
Signed-off-by: Daniel Lemm <61800298+ffe4@users.noreply.github.com>
* Fix typo in CONTRIBUTING.md
Signed-off-by: Daniel Lemm <61800298+ffe4@users.noreply.github.com>
There are some issues and quirks in the markdown documentation files
suggested by the markdownlint project checker that might benefit from
being fixed, which this patch does.
Change-Id: I33245825e5bb543b5ce1732204984d4a0b169668
Signed-off-by: Joakim Roubert <joakimr@axis.com>
In the past, yes k3s did exclude all those legacy, alpha, non-default
features from Kubernetes source as you can see in
https://github.com/rancher/k3s/pull/113. But not anymore.
As you can see in the source code, most of legacy/alpha/non-default
features is available in k3s, and misleading README should be updated.
But please, don't get me wrong. I'm actually glad to see those features
enabled in k3s. :)
Reference:
https://github.com/kubernetes/kubernetes/compare/v1.16.3...rancher:v1.16.3-k3s.1
