* tests/vagrant: refactor vagrant smoke tests (#4484)
- updated `tests/TESTING.md`
- cgroup, snapshotter, and install tests all under tests/vagrant
- cgroup and snapshotter workflows trigger for all code changes on all branches (excluding markdown docs, install script, and other vagrant tests)
- install workflow triggers for relevant script and fixture changes, only on master or pull-requests that target it
- integration and unit test workflows should not trigger for install script changes nor anything under tests/vagrant
Co-authored-by: Jacob Blain Christen <jacob@rancher.com>
Signed-off-by: Jonnatan Jossemar Cordero <jonnatan.cordero@suse.com>
* Update CentOS 8 smoke vm's with vault repositories (#5092)
Update CentOS 8 smoke vm's with vault repositories
Problem: CentOS 8 reached its EOL alongside its public mirrors, making
all the smoke test fail at provisioning time.
Solution: Point all the CentOS repositories to vault.
Signed-off-by: Jonnatan Jossemar Cordero <jonnatan.cordero@suse.com>
Signed-off-by: Jonnatan Jossemar Cordero <jonnatan.cordero@suse.com>
* Update install GH action with release-1.22 branch
Problem: The install GH workflow enforces to be run agaisnt the main
branch as instead of a release one.
Solution: Update GH workflow and k3s install version accordingly to work
once it is run agaisnt release-1.22 branch
Signed-off-by: Jonnatan Jossemar Cordero <jonnatan.cordero@suse.com>
Co-authored-by: Jacob Blain Christen <jacob@rancher.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>
* Update gitignore
Signed-off-by: Derek Nola <derek.nola@suse.com>
* Add server flag to access nonlocal/nondefault k3s server (#5016)
Signed-off-by: Derek Nola <derek.nola@suse.com>
* Backport k3s-io#4861
Signed-off-by: Derek Nola <derek.nola@suse.com>
* Update to v1.22.6
Signed-off-by: Derek Nola <derek.nola@suse.com>
* Update tags to k3s-io for v1.22.6
Signed-off-by: Derek Nola <derek.nola@suse.com>
Kubernetes Metrics Server version upgrade with the following changes:
Remove elevated permissions cap_net_bind_service from metrics-server
Fix bad architecture metadata
Fix reporting inconsistent number of nodes, caused by using invalid Kubelet node start time metric
Fix reporting partial container metrics for pod
Signed-off-by: Farukh Khan <farukhkhan21@gmail.com>
Closes a gap in test coverage. Also fixes an issue where args and hooks
from previous test runs were not being reset for subsequent runs.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 52e450f033)
This failed if the build metadata contained a period, as in v1.23.0-rc.0
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 247298a20d)
If you don't explicitly close the etcd client when you're done with it,
the GRPC connection hangs around in the background. Normally this is
harmelss, but in the case of the temporary etcd we start up on 2399 to
reconcile bootstrap data, the client will start logging errors
afterwards when the server goes away.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 8ad7d141e8)
* Move runc and k3s-root versions into versions.sh
* Remove commented-out cruft from build script
* Other minor tweaks
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
(cherry picked from commit 8737e2e13f)
Derek Nola