Fabiano Fidêncio ad45ab5d33 ci: k8s: Ensure k3s is deploy with --write-kubeconfig-mode=644 ...

Otherwise the /etc/rancher/k3s/k3s.yaml is not readable by other users
than root.

As --write-config-mode is being passed, and that's an option that has to
be passed to the `server`, -s is also added to the command line.

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

2023-09-07 23:12:55 +02:00

..

functional

gha: kata-deploy: Do the runtime class cleanup as part of the cleanup

2023-08-17 18:54:46 +02:00

integration

ci: k8s: Ensure k3s is deploy with --write-kubeconfig-mode=644

2023-09-07 23:12:55 +02:00

metrics

Merge pull request #7824 from dborquez/fix_memory_usage_initialization

2023-09-07 14:24:27 -06:00

.gitignore

tests: k8s: Leave runtimeclass_workloads/ alone

2023-07-25 15:45:44 -07:00

common.bash

tests: commob: Don't fail if yq is not part of the cache

2023-08-17 14:22:14 +02:00

gha-run-k8s-common.sh

tests: common: Ensure test_type is used as part of the cluster's name

2023-08-17 14:22:16 +02:00

install_go.sh

ci: Use function before each install_go.sh function

2023-07-21 16:54:27 +02:00

kata-arch.sh

ci: Do not take cross-build into consideration for kata-arch.sh

2023-07-21 16:54:27 +02:00