Update to v1.17.9-k3s1

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

When for some reason, k3s crashes, and can't startup again, e.g. when
the data backend is not available (dqlite crashed, database server is
offline, ...), on openrc systems, supervise-daemon will try to restart
it, as per supervise-daemon(8):

    respawn-max:

    Sets the maximum number of times a daemon will be respawned during
    a respawn period. If a daemon dies more than this number of times
    during a respawn period, will give up trying to respawn it and exit.
    The default is 10, and 0 means unlimited.

Setting respawn-max to 0, makes sure a k3s process on openrc systems will
keep trying to come online, even if the database backend is offline for a
longer period of time.

This aligns the openrc service configuration with the systemd
configuration, which has

    Restart=always
    RestartSec=5s
Signed-off-by: Serge van Ginderachter <serge@vanginderachter.be>

backport 1.17: Replace juju/errors with pkg/errors

update CNI to v0.8.6-k3s1

Update k8s 1.17.6

update kine

Update k8s to v1.17.5

use mirrored images for traefik and coredns

Bump cri to 1.3.0-k3s.5

Add airgap image list to release artifacts

Update RPM systemd services for easy modification.

Modified installer produces a k3s-server and k3s-agent systemd
service, with env files located in /etc/rancher/k3s.

The k3s-server service may be started without modification but
k3s-agent requires a token and url modification to the
/etc/rancher/k3s/k3s-agent.env file for functionality.

The k3s-server service will conflict with the k3s-agent service,
so both may not be started at the same time.

Creates ./package/rpm/ repo dir for rpm specific resources and
relocates k3s.spec.

Use curl to send dispatch event to k3s-upgrade repo

Update k8s to v1.17.4-k3s1

Ask more clearly for K3s args and logs

[release-1.17] Backport add asterisk

In the bug report template, more clearly ask the user for K3s arguments and logs

Don't require selinux utils and require k3s_selinux