Repository navigation
|
https://github.com/k3s-io/kubernetes/tags such as for tag v1.23.4-k3s1 based on commit tag: 46139e9 as same with tag staging/src/k8s.io/sample-controller/v1.23.4-k3s1 on same commit tag: 46139e9 can anyone clean my question? |
Answered by
brandond
Mar 8, 2022
Replies: 1 comment
|
Upstream kubernetes moves a bunch of stuff out to individual packages when they tag a new release; check the docs at https://github.com/kubernetes/kubernetes/blob/master/staging/README.md Due to how go modules work, in order to replace all of these with the code in our fork, we have to tag each of the individual module versions in our fork. |
0 replies
Answer selected by
xiaods
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upstream kubernetes moves a bunch of stuff out to individual packages when they tag a new release; check the docs at https://github.com/kubernetes/kubernetes/blob/master/staging/README.md
Due to how go modules work, in order to replace all of these with the code in our fork, we have to tag each of the individual module versions in our fork.