rancher/helm-controller ➡ k3s-io/helm-controller

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

rancher/flannel ➡ k3s-io/flannel
rancher/go-powershell ➡ k3s-io/go-powershell

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

rancher/etcd ➡ k3s-io/etcd

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>

rancher/kine ➡ k3s-io/kine

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

Add davidnuzik (David Nuzik) to the list of maintainers

Signed-off-by: David Nuzik <david.nuzik@rancher.com>

Add Oats87 (Chris Kim) to the list of maintainers for K3s

Signed-off-by: Chris Kim <oats87g@gmail.com>

Mark v1.19.4+k3s1 as stable

- rancher/cri ➡ k3s-io/cri
- rancher/cri-tools ➡ k3s-io/cri-tools
- rancher/containerd ➡ k3s-io/containerd

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

This change set replaces these go.mod replacement directives with references to k3s-io repositories.

- rancher/kubernetes
- rancher/nocode

Part of https://github.com/rancher/k3s/issues/2189Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

Signed-off-by: MonzElmasry <menna.elmasry@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

* Remove unused release.sh and DAPPER_HOST_ARCH
* Reliably use ARCH from version.sh
* Export GOARCH and GOARM so that they are used by `go build`
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Enhance install.sh to help with k3s upgrade and uninstall scenarios

Change from file check to yum check for uninstall script
Co-authored-by: Jacob Blain Christen <dweomer5@gmail.com>

Signed-off-by: Chris Kim <oats87g@gmail.com>

* v1.19.3+k3s3 contains a critical fix for kine. Refer to the release notes for details.
Signed-off-by: David Nuzik <david.nuzik@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Do not relabel container /dev/shm when it is host /dev/shm.
Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

Removing the cfg.DataDir mutation in 3e4fd7b4 did not break anything, but
did change some paths in unwanted ways. Rather than mutating the
user-supplied command-line flags, explicitly specify the agent
subdirectory as needed.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

As per documentation, the cloud-provider flag should not be passed to
controller-manager when using cloud-controller. However, the legacy
cloud-related controllers still need to be explicitly disabled to
prevent errors from being logged.

Fixing this also prevents controller-manager from creating the
cloud-controller-manager service account that needed extra RBAC.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Mark the latest v1.19.x release as stable

Addresses rancher/k3s#2240
Signed-off-by: Jacob Blain Christen <jacob@rancher.com>

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

* Update sonobuoy version
* Use upstream tag for Kubernetes version instead of replacement tag
    Allows building against upstream alpha/beta/rc releases
* Use env variable for sonobuoy version
* Bump version for QA e2e tests
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Related to #2205
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Related to rancher/rke2#474

Note that anyone who customizes the data-dir path will have to set
CRI_CONFIG_FILE to the correct path when using the wrapped binaries
(crictl, etc). This is better than dropping files in the incorrect
location.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Disable configure-cloud-routes and external service/route programming support when using k3s stub cloud controller

Resolves warning 3 from #2471
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Resolves warning 2 from #2471.

As per https://github.com/kubernetes/cloud-provider/issues/12 the
ClusterID requirement was never really followed through on, so the
flag is probably going to be removed in the future.

One side-effect of this is that the core k8s cloud-controller-manager
also wants to watch nodes, and needs RBAC to do so.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Resolves warning 1 from #2471
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Related to #2455 and containerd/containerd#4684

These were not meant to be enabled by default, break images with many
layers, and will be disabled by default on the next containerd release.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

The --disable/--no-deploy flags actually turn off some built-in
controllers, in addition to preventing manifests from getting loaded.
Make it clear which controllers can still be disabled even when the
packaged components are ommited by the no_stage build tag.
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>

Support k3s-selinux rpm install more effectively

Add additional conditional logic to install.sh to prevent errors on Fedora or systems when run as non-root
Signed-off-by: Chris Kim <oats87g@gmail.com>

/bin/rm is less portable. On some distros, like nixos, it doesn't exist
at all.
Signed-off-by: Euan Kemp <euank@euank.com>

Make etcd use node private ip

Signed-off-by: Ranjib Dey ranjib@linux.com