Reduce the verbosity of the log

Changelog for 0.6.1:

• PR #48 Reduce the verbosity of the log by @viveksyngh

Commits
d96d59f Reduce the verbosity of the log by @viveksyngh
8963edd Update README.md by @alexellis
e116c96 Update README.md by @alexellis
59d745d Update chart to latest version by @alexellis
839ae12 Pre-cache go modules by @alexellis

Generated by Derek

Move to Go modules and Kubernetes 1.17 Go client

Changelog for 0.6.0:

• Move to Go modules
• Remove dep
• Use K8s Go 1.17 client
• Remove vendor folder so that codegen works.

Thanks @stefanprodan for the tip on serializer.DirectCodecFactory
having moved.

Generated by Derek

Update inlets-pro download URL

Changelog for 0.5.7:

• PR #42 Add civo provisioner by @adamjohnson01
• PR #41 Add provisioner for AWS EC2 by @adamjohnson01

Generated by Derek

Fix download URL for inlets-pro on exit-node

Changelog for 0.5.6:

• PR #36 Fix README by @utsavanand2
• PR #40 Fixes inlets-pro binary link by @utsavanand2

Generated by Derek

Patch fix for GCE provisioner

Changelog for 0.5.5:

• PR #34 Fix Google Compute link and update vendor dep by @utsavanand2

Generated by Derek

Add GCE provisioner

Changelog for 0.5.4:

• PR #33 Add Google Compute Engine as provisioner for exit-node by @utsavanand2

Generated by Derek

The GCE provisioner gives access to the F1-micro in us-central-1 which can be part of the free tier.

Update default versions of inlets/pro

Changelog for 0.5.3:

Generated by Derek

Allow client-image override for inlets-pro

Changelog for 0.5.2:

Generated by Derek

Allow client-image override for inlets-pro

Changelog for 0.5.1:

• Allow client-image override for inlets-pro

Generated by Derek

Fix for issue with invalid ownerReference

Changelog for 0.5.0:

• PR #29 Add build status badge by @utsavanand2

Generated by Derek

Fix bug in ownerReference

The ownerReference had the wrong type, kind and group - that of
the tunnel and not that of the service which caused the tunnel
to be created. Tested e2e and shown to be fixed, the problem
was observed when rebooting a machine running kubeadm or an RPi
running k3s.

Thanks to @stefanprodan for helping me to find this and to
@utsavanand2 for confirming the issue.