[aws-vpc-cni] Update to v1.6.3

[max-rocket-internet]

Please merge #205 first so that version v1.6.2 is not skipped.

As far as I can see there's no other required changes apart from the image tag: https://github.com/aws/amazon-vpc-cni-k8s/commits/master/config/v1.6/aws-k8s-cni.yaml

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[max-rocket-internet]

Please review @jaypipes 🙂

[jaypipes]

We need to do a release/git tag for the 1.6.2 change (which will trigger a chart release/publish). I'll do that today (we've got a pile of merges to aggregate into a repo release) and then merge this and do another git tag.

[max-rocket-internet]

We need to do a release/git tag for the 1.6.2 change (which will trigger a chart release/publish)

I think I've asked this before but why not just have that CI process triggered on every merge to master? Then you don't need to remember to create a release and everyone can access the new chart versions after the PR is merged 🙂

[TBBle]

@max-rocket-internet Per aws/amazon-vpc-cni-k8s#758 (comment) that will be happening in https://github.com/aws/amazon-vpc-cni-k8s when the true-source of the amazon-vpc-cni Helm chart moves there.

[max-rocket-internet]

@jaypipes can we get that release and then merge this PR and then another tag? We're waiting on version 1.6.3 to fix CNI pod restarts.

[max-rocket-internet]

@jaypipes can we merge?

[mogren]

Thanks, lgtm!