pkg/errors is no longer maintained and archived

[sbueringer]

To be honest, I'm not sure what we want to do or if we want to do something, but just found out that pkg/errors is archived.

See: pkg/errors#245

/kind bug
/area dependency
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

[DiptoChakrabarty]

There are two options which I think can be done

• keep things as they are
• replace with native golang error wrapping which can be handled by the fmt and errors package

there might be more but these come to my mind

there are few issues regarding this in other repos kubernetes/release#2549

[sbueringer]

I have to think about it a bit more but the approach in kubernetes/release#2549 sounds like a reasonable option and obviously consistent with upstream Kubernetes.

[oscr]

@sbueringer What are your thoughts on this? Is this something we can start working on, but wait with prs until 1.2 is released?

[sbueringer]

I think we need more discussion before we should do anything.

I would especially like to hear the opinions of other maintainers on this as it's a pretty fundamental change

(@enxebre @CecileRobertMichon @fabriziopandini @vincepri)

[fabriziopandini]

I would align to whatever k/k does
@neolit123 any info WRT to ^^

[neolit123]

the Wrap(f) gives formatting consistency and avoids leakage of text: ... vs text : ... formatting diffs. stdlib has no answer.

k/k is not taking action for kubeadm for the time being, although there was a ticket somewhere.
unless k/k/kubeadm is forced to switch we can continue vendoring it.

[fabriziopandini]

/triage accepted

Let's keep this around to monitor the situation, but I will aling to k/k and not take action for the time being

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale