Update sonobuoy version for k8s 1.18 support

add profiling flag with default value of false

Signed-off-by: Brian Downs <brian.downs@gmail.com>

remove hard coded value from ProgramUpper

Signed-off-by: Brian Downs <brian.downs@gmail.com>

Configure default signer implementation to use ClientCA instead of ServerCA

Implement new k3s-root changes

update k3s-root to v0.5.0 and remove k3s specific modifications to k3s-root (as they have moved into k3s-root)
Signed-off-by: Chris Kim <oats87g@gmail.com>

fixed panic in network_policy_controller

Add retry backoff for starting network-policy controller

Replace juju/errors with nocode

Update GitHub bug_report template

Signed-off-by: niusmallnan <niusmallnan@gmail.com>

    I have rebooted a newly created k3s etcd cluster and this panic was triggered:

    ```
    k3s[948]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x45f2945]
    k3s[948]: goroutine 1 [running]:
    k3s[948]: github.com/rancher/k3s/pkg/agent/netpol.NewNetworkPolicyController(0xc00159e180, 0x61b4a60, 0xc006294000, 0xdf8475800, 0xc011d9a360, 0xc, 0x0, 0xc00bf545b8, 0x2b2edbc)
    k3s[948]:         /home/x/git/k3s/pkg/agent/netpol/network_policy_controller.go:1698 +0x275
    ```
Signed-off-by: Matthias Schneider <ms@wck.biz>

Signed-off-by: Craig Jellick <craig@rancher.com>

servicelb: fix ineffective toleration

Signed-off-by: Craig Jellick <craig@rancher.com>

Update Contribution Doc

Signed-off-by: Brian Downs <brian.downs@gmail.com>

Signed-off-by: Craig Jellick <craig@rancher.com>

Make packaged crictl work when using Docker

Signed-off-by: Brian Downs <brian.downs@gmail.com>

Signed-off-by: Brian Downs <brian.downs@gmail.com>

Simplify contributing doc

Always keep restarting k3s process by openrc

Make the contributing guide less prescriptive and include the
DCO.

Add contributing doc

* update helm controller to 0.6.3

* update klipper-helm to v0.2.7

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

Update stable channel to v1.18.4+k3s1

noderole.kubernetes.io/master -> node-role.kubernetes.io/master

update helm and vendor update