Update go-tpm version to v0.3.2 that supports arm64

[vinayakankugoyal]

Version 0.2.0 of go-tpm library did not support building for linux_arm64. See error below.

bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_arm64 //cmd/gke-exec-auth-plugin:gke-exec-auth-plugin 

workspace/vendor/github.com/google/go-tpm/tpmutil/poll_unix.go:28:33: undefined: syscall.SYS_POLL
Target //cmd/gke-exec-auth-plugin:gke-exec-auth-plugin failed to build
INFO: Elapsed time: 0.922s, Critical Path: 0.25s
INFO: 15 processes: 10 internal, 5 linux-sandbox.
FAILED: Build did NOT complete successfully

The failure above happens because v0.2.0 of the go-tpm library used syscall.SYS_POLL which is not supported in arm64 architecture. To workaround this golang has implemented a shim for poll on arm64 in https://go-review.googlesource.com/c/sys/+/24062/. This issue has been raised in go-tpm library google/go-tpm#146 and was fixed in google/go-tpm#147. Support for arm64 is only available starting v0.3.0 of the go-tpm library. So in order to build gke-exec-auth-plugin for arm64 we will need to update the version of the go-tpm library to v0.3.2.

All changes were produced by running the following command as recommended in the README.md

go get -u github.com/google/go-tpm && ./tools/update_vendor.sh

Tests were also updated because in go-tpm v0.3.0 validation was added to check that the magic value in the attestation data is always 0xff544347. We were not setting the value in our tests and so they were failing with the following error:

E0923 06:16:16.904904      12 node_csr_approver.go:506] deny CSR "TestValidators/validateTPMAttestation_with_API/good_0": parsing attestation data in CSR: incorrect magic value: 0

[vinayakankugoyal]

/assign @mikedanese

[vinayakankugoyal]

/ok-to-test

[vinayakankugoyal]

/retest

[cici37]

cloud-provider-gcp-tests cloud-provider-gcp-e2e-full is blocked by #273

[vinayakankugoyal]

cloud-provider-gcp-tests cloud-provider-gcp-e2e-full is blocked by #273

I think these failures have nothing to do with #273. cloud-provider-gcp-tests were failing because of new validation that was added to go-tmp. I have updated the description with the details of why the tests were failing.

[mikedanese]

/lgtm
/approved

[mikedanese]

/retest

[cici37]

cloud-provider-gcp-tests cloud-provider-gcp-e2e-full is blocked by #273

I think these failures have nothing to do with #273. cloud-provider-gcp-tests were failing because of new validation that was added to go-tmp. I have updated the description with the details of why the tests were failing.

I was trying to say that if you push another commit and trigger cloud-provider-gcp-e2e-full again, it will fail because of #273 like what happened now -_-. I will try to get it merge asap.

[cici37]

#273 is merged. Please fetch the latest changes which will unblock e2e failures. Thanks

[vinayakankugoyal]

/retest

[mikedanese]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mikedanese, vinayakankugoyal

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 [mikedanese]

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