Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade distribution to 2.8 #16190

Closed
wants to merge 2 commits into from

Conversation

darend
Copy link

@darend darend commented Jan 6, 2022

what

Upgrade the distribution package to 2.8

why

Harbor is currently on 2.7.1 which was released in 2019. Full release notes available here https://github.com/distribution/distribution/releases/tag/v2.8.0

EDIT: IRSA support not included in this release

See distribution/distribution#3552 (comment)

The 2.7 release uses an out of date AWS SDK which does not support the AWS AssumeRoleWithWebIdentity required for deployments under Kubernetes that use IRSA. This was fixed in the 2.8 release, see distribution/distribution#3097. Support for IRSA is of growing importance. It is the recommended solution when running Kubernetes on AWS

Unfortunately while distribution has a 2.8 branch they have not made a release. I pinned the upgrade to the last commit of the 2.8 release branch

IRSA Documentation:

This fixes goharbor/harbor-helm#725

Copy link

@sakomws sakomws left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lg

@sydorovdmytro
Copy link

There is some progress on the official 2.8 release distribution/distribution#3552

@zyyw
Copy link
Contributor

zyyw commented Jan 10, 2022

It states I pinned the upgrade to the last commit of the 2.8 release branch, while the code change of this PR is pointing to 2.7.2,

github.com/docker/distribution v2.7.2-0.20211123191640-3b7b53456922+incompatible

@darend
Copy link
Author

darend commented Jan 10, 2022

@zyyw thanks for catching that. Im running into some limitations with go get.

When attempting to pin to a specific commit it is silently falling back to the previous release. The go get docs do not explicitly state that you can pin to a commit...

# pins to github.com/docker/distribution v2.7.2-0.20211123191640-3b7b53456922+incompatible
go get github.com/docker/distribution@3b7b534569220c840993aad03e3eafe54b923f4d

I am also unable to pin to the release/2.8 branch. go get says you can pin to a branch but this specific branch appears to violate a naming convention

❯ go get github.com/docker/distribution@release/2.8
go get: github.com/docker/distribution@release/2.8: invalid version: version "release/2.8" invalid: disallowed version string

@darend darend changed the title Upgrade distribution to 2.8 WIP - Upgrade distribution to 2.8 Jan 18, 2022
@darend
Copy link
Author

darend commented Jan 21, 2022

Distribution cut a 2.8 Beta release but has not back ported the IRSA fix that we need into it

@chlins
Copy link
Member

chlins commented Feb 11, 2022

@darend Distribution has released v2.8.0 version recently. https://github.com/distribution/distribution/releases/tag/v2.8.0

Signed-off-by: Daren Desjardins <darend@gmail.com>
Signed-off-by: Daren Desjardins <darend@gmail.com>
@darend darend changed the title WIP - Upgrade distribution to 2.8 Upgrade distribution to 2.8 Feb 11, 2022
@darend
Copy link
Author

darend commented Feb 11, 2022

@chlins It is updated to 2.8

@MinerYang
Copy link
Contributor

MinerYang commented Mar 4, 2022

Hi @darend ,

We have just bumped up github.com/docker/distribution to v2.8.0+incompatible in the PR #16460
We would close this one and appreciate your contribution sincerely!

Best,
Miner

@MinerYang MinerYang closed this Mar 4, 2022
@darend darend deleted the upgrade-distribution branch March 4, 2022 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Harbor-registry which set store data on S3 seems not works with service account (IAM role) on EKS
7 participants