bump go to 1.17

[ddymko]

Description

Bumping go from 1.16 to 1.17

Ran a build against VKE and everything worked as expected

May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.356068    5363 node_controller.go:390] Initializing node b-2f8540eeb363 with cloud provider
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.578367    5363 node_controller.go:492] Adding node label from cloud provider: beta.kubernetes.io/instance-type=voc-c-2c-4gb-75s-amd
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.578404    5363 node_controller.go:493] Adding node label from cloud provider: node.kubernetes.io/instance-type=voc-c-2c-4gb-75s-amd
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.578411    5363 node_controller.go:515] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/region=ewr
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.578419    5363 node_controller.go:516] Adding node label from cloud provider: topology.kubernetes.io/region=ewr
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.589682    5363 node_controller.go:454] Successfully initialized node b-2f8540eeb363 with cloud provider
May 12 15:11:55 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:55.589887    5363 event.go:291] "Event occurred" object="b-2f8540eeb363" kind="Node" apiVersion="v1" type="Normal" reason="Synced" message="Node synced successfully"
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.398310    5363 node_controller.go:390] Initializing node b-071ab9157f5b with cloud provider
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.617828    5363 node_controller.go:492] Adding node label from cloud provider: beta.kubernetes.io/instance-type=voc-c-2c-4gb-75s-amd
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.617860    5363 node_controller.go:493] Adding node label from cloud provider: node.kubernetes.io/instance-type=voc-c-2c-4gb-75s-amd
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.617866    5363 node_controller.go:515] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/region=ewr
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.617871    5363 node_controller.go:516] Adding node label from cloud provider: topology.kubernetes.io/region=ewr
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.626306    5363 node_controller.go:454] Successfully initialized node b-071ab9157f5b with cloud provider
May 12 15:11:58 vultr vultr-cloud-controller-manager[5363]: I0512 15:11:58.626603    5363 event.go:291] "Event occurred" object="b-071ab9157f5b" kind="Node" apiVersion="v1" type="Normal" reason="Synced" message="Node synced successfully"
May 12 15:12:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:05.488417    5363 controller.go:265] Node changes detected, triggering a full node sync on all loadbalancer services
May 12 15:12:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:05.488491    5363 controller.go:741] Syncing backends for all LB services.
May 12 15:12:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:05.488512    5363 controller.go:748] Successfully updated 0 out of 0 load balancers to direct traffic to the updated set of nodes
May 12 15:12:08 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:08.761857    5363 controller.go:265] Node changes detected, triggering a full node sync on all loadbalancer services
May 12 15:12:08 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:08.761903    5363 controller.go:741] Syncing backends for all LB services.
May 12 15:12:08 vultr vultr-cloud-controller-manager[5363]: I0512 15:12:08.761914    5363 controller.go:748] Successfully updated 0 out of 0 load balancers to direct traffic to the updated set of nodes




May 12 15:13:59 vultr vultr-cloud-controller-manager[5363]: I0512 15:13:59.950289    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:13:59 vultr vultr-cloud-controller-manager[5363]: I0512 15:13:59.950406    5363 controller.go:912] Adding finalizer to service default/vultr-lb-https
May 12 15:13:59 vultr vultr-cloud-controller-manager[5363]: I0512 15:13:59.951848    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:14:00 vultr vultr-cloud-controller-manager[5363]: E0512 15:14:00.288174    5363 controller.go:310] error processing service default/vultr-lb-https (will retry): failed to ensure load balancer: load-balancer is not yet active - current status: pending
May 12 15:14:00 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:00.288269    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: load-balancer is not yet active - current status: pending"
May 12 15:14:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:05.289045    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:14:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:05.289503    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:14:05 vultr vultr-cloud-controller-manager[5363]: E0512 15:14:05.477617    5363 controller.go:310] error processing service default/vultr-lb-https (will retry): failed to ensure load balancer: load-balancer is not yet active - current status: pending
May 12 15:14:05 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:05.477738    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: load-balancer is not yet active - current status: pending"
May 12 15:14:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:15.478542    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:14:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:15.478806    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:14:15 vultr vultr-cloud-controller-manager[5363]: E0512 15:14:15.644221    5363 controller.go:310] error processing service default/vultr-lb-https (will retry): failed to ensure load balancer: load-balancer is not yet active - current status: pending
May 12 15:14:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:15.644305    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: load-balancer is not yet active - current status: pending"
May 12 15:14:35 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:35.645439    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:14:35 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:35.645750    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:14:35 vultr vultr-cloud-controller-manager[5363]: E0512 15:14:35.807891    5363 controller.go:310] error processing service default/vultr-lb-https (will retry): failed to ensure load balancer: load-balancer is not yet active - current status: pending
May 12 15:14:35 vultr vultr-cloud-controller-manager[5363]: I0512 15:14:35.807988    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Warning" reason="SyncLoadBalancerFailed" message="Error syncing load balancer: failed to ensure load balancer: load-balancer is not yet active - current status: pending"
May 12 15:15:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:15:15.808569    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:15:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:15:15.808912    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:15:15 vultr vultr-cloud-controller-manager[5363]: I0512 15:15:15.973425    5363 loadbalancers.go:184] Called UpdateLoadBalancers
May 12 15:15:16 vultr vultr-cloud-controller-manager[5363]: I0512 15:15:16.447456    5363 controller.go:953] Patching status for service default/vultr-lb-https
May 12 15:15:16 vultr vultr-cloud-controller-manager[5363]: I0512 15:15:16.447660    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuredLoadBalancer" message="Ensured load balancer"


May 12 15:16:01 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:01.104732    5363 controller.go:403] Ensuring load balancer for service default/vultr-lb-https
May 12 15:16:01 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:01.105662    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuringLoadBalancer" message="Ensuring load balancer"
May 12 15:16:01 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:01.279214    5363 loadbalancers.go:184] Called UpdateLoadBalancers
May 12 15:16:01 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:01.741051    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="EnsuredLoadBalancer" message="Ensured load balancer"

May 12 15:16:21 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:21.691508    5363 controller.go:388] Deleting existing load balancer for service default/vultr-lb-https
May 12 15:16:21 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:21.691846    5363 event.go:291] "Event occurred" object="default/vultr-lb-https" kind="Service" apiVersion="v1" type="Normal" reason="DeletingLoadBalancer" message="Deleting load balancer"
May 12 15:16:22 vultr vultr-cloud-controller-manager[5363]: I0512 15:16:22.240205    5363 controller.go:927] Removing finalizer from service default/vultr-lb-https

Related Issues

Checklist:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you linted your code locally prior to submission?
• Have you successfully ran tests with your changes locally?