Fix Calico upgrade job to use the correct version

[tmjd]

No description provided.

[k8s-ci-robot]

Hi @tmjd. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mikesplain]

Can you also bump the version here:

kops/upup/pkg/fi/cloudup/bootstrapchannelbuilder.go

Lines 648 to 649 in 5b34d3d

	"k8s-1.7-v3": "3.3.1-kops.2",
	}

In this case since it looks like it was already bumped, just change it from 3.3.1-kops.2 to 3.3.1-kops.3to have kops pick it up as a change

[mikesplain]

Ahh yes, since jobs can't be updated as themselves 👍

[mikesplain]

/ok-to-test

[mikesplain]

@tmjd seems like we should likely cherry-pick this into 1.11 as well, thoughts?

[caseydavenport]

@tmjd thanks for cleaning up my mess. this LGTM!

[tmjd]

@mikesplain Yes this should be cherry-picked to 1.11.

[mikesplain]

Thanks @tmjd!
/lgtm
/approve
/cherry-pick

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mikesplain, tmjd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mikesplain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment