[Bug]: Cannot build v0.6.2 using GOPROXY direct

[jpmcb]

What happened?

This is more of an FYI since this was addressed in v0.6.3: I am unable to build v0.6.2 via GOPROXY=direct since there is a GitHub repository that looks like it has been locked / made private.

❯ GOPROXY=direct go build ./cmd/aws-iam-authenticator
go: k8s.io/kubernetes@v1.22.0 requires
        github.com/storageos/go-api@v2.2.0+incompatible: reading github.com/storageos/go-api/go.mod at revision v2.2.0: git ls-remote -q origin in /home/ubuntu/go/pkg/mod/cache/vcs/f4474392d641b836e8296e236f2861d83ba42188d7ff117e30acb6b06774a32d: exit status 128:
        remote: Repository `storageos/go-api' is disabled.
        remote: Please ask the owner to check their account.
        fatal: unable to access 'https://github.com/storageos/go-api/': The requested URL returned error: 403
go: downloading github.com/prometheus/client_golang v1.11.0
go: downloading github.com/aws/aws-sdk-go v1.44.107
go: downloading k8s.io/apimachinery v0.23.0-alpha.0
go: downloading github.com/spf13/cobra v1.1.3
go: downloading github.com/spf13/viper v1.7.0
go: downloading gopkg.in/yaml.v2 v2.4.0
go: downloading github.com/sirupsen/logrus v1.8.1
go: downloading k8s.io/client-go v0.22.0
go: downloading k8s.io/sample-controller v0.22.0
go: downloading sigs.k8s.io/yaml v1.2.0
go: downloading k8s.io/component-base v0.22.0
go: downloading github.com/gofrs/flock v0.7.0
go: downloading k8s.io/api v0.22.0
go: downloading github.com/manifoldco/promptui v0.9.0
go: downloading golang.org/x/time v0.0.0-20210723032227-1f47c861a9ac
go: downloading github.com/fsnotify/fsnotify v1.4.9
go: k8s.io/kubernetes@v1.22.0 requires
        github.com/storageos/go-api@v2.2.0+incompatible: reading github.com/storageos/go-api/go.mod at revision v2.2.0: git ls-remote -q origin in /home/ubuntu/go/pkg/mod/cache/vcs/f4474392d641b836e8296e236f2861d83ba42188d7ff117e30acb6b06774a32d: exit status 128:
        remote: Repository `storageos/go-api' is disabled.
        remote: Please ask the owner to check their account.
        fatal: unable to access 'https://github.com/storageos/go-api/': The requested URL returned error: 403

Since there is a code dependency on k8s.io/kubernetes@v1.22.0 (which then pulls in github.com/storageos/go-api), the build fails.

But, looks like in v0.6.3, this was fixed and the k8s.io/kubernetes@v1.22.0 code dependency was removed. I'm not really sure what's going on with that storageos/go-api GitHub repo ... I've only ever seen that when a repo was made private or was locked down by github manually. This doesn't appear to be a problem for upstream Kubernetes 1.22 since they vendor in all their dependencies.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.