🐘 Standardize on new YAML parser effort #132056
Description
A lot of our community ecosytem has been using the following packages from @niemeyer:
For a while, we have had a fork of these two packages:
- https://github.com/kubernetes-sigs/yaml/tree/master/goyaml.v2
- https://github.com/kubernetes-sigs/yaml/tree/master/goyaml.v3
Recently @ingydotnet has started an effort to revive the parsers here:
https://github.com/yaml/go-yaml
The following packages are now available as a result:
This new effort has already consolidated the patches we carried as part of:
yaml/go-yaml#2
So what do we want to do here/now?
Proposal in this issue is that we should switch over to the new packages both in kubernetes/kubernetes and other repositories that we host/consume/support. For a period of time, we will have multiple parsers (even if they have the same identical code). But over time as more folks switch over to the new "official" this should trail off. We should use our unwanted-dependencies.json to drive down / deprecate all the older ones over time.
/area code-organization
/sig architecture