Umbrella issue: github archived dependencies (2023 Jan)

[pacoxu]

/sig architecture
/area code-organization
/kind cleanup

Opened issues for tracking these deps in those repo and github.com/pkg/errors is tracked in #113627.

archived repos: auto-updated per month (the list needs to be updated manually at the moment.)

• github.com/pkg/errors
• • Track in Remove dependency on github.com/pkg/errors #113627
• • github.com/pkg/errors is archived microsoft/hcsshim#1614
• • github.com/pkg/errors is archived google/cadvisor#3227
• • github.com/pkg/errors is archived kubernetes-sigs/kustomize#4964
• • Wait Next Release github.com/pkg/errors is archived system-validators#33
• • Remove dependency on github.com/pkg/errors aws/aws-sdk-go#4683
• • Wait Next Etcd Release? 3.5.8+ https://github.com/etcd-io/raft/pull/20/[v3.5.6] & upgrade cockroachdb/datadriven to v1.0.2 to remove archived dependencies etcd-io/etcd#15225
• • Remove dependency on github.com/pkg/errors uber-go/zap#1218 ( github.com/go-logr/zapr and https://github.com/grpc-ecosystem/go-grpc-middleware depend on it.)
• • remove gotest.tools dependency moby/ipvs#29 & upgrade gotest.tools to v3.4.0 to drop pkg/errors dependency moby/ipvs#28 & Update to new release of moby/ipvs #115079
• github.com/getsentry/raven-go
• • github.com/getsentry/raven-go is archived etcd-io/raft#19 : after upgrading cockroachdb/datadriven to v1.0.2, this can be fixed in etcd/raft. Pending on etcd/raft next release.
• github.com/google/shlex
• • google/shlex is archived kubernetes-sigs/kustomize#4963
• github.com/form3tech-oss/jwt-go
• • upgrade etcd dependencies to v3.5.6 #114921
• • Pending on Switch vendored etcd to v3.5.6 #114403 after upgrade to v3.5.6 this will be fixed.
• github.com/PuerkitoBio/urlesc
• • Wait Next Release PuerkitoBio/urlesc is archived kubernetes-sigs/kustomize#4962
• • PuerkitoBio/urlesc is archived kube-openapi#356

Originally posted by @pacoxu in #114912 (comment)

• go mod graph will involve multi-versions of common and client_golang prometheus/common#431: github.com/pkg/errors will always be in go.sum.

[k8s-ci-robot]

@pacoxu: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[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.