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

[jfrog-platform] 10.17.0 release #1855

Merged
merged 9 commits into from
Jan 24, 2024
Merged

[jfrog-platform] 10.17.0 release #1855

merged 9 commits into from
Jan 24, 2024

Conversation

chukka
Copy link
Collaborator

@chukka chukka commented Jan 24, 2024

PR Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • Chart Version bumped
  • CHANGELOG.md updated
  • Variables and other changes are documented in the README.md
  • Title of the PR starts with chart name (e.g. [artifactory])

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1838

Special notes for your reviewer:

@chukka chukka merged commit 69d8a1c into master Jan 24, 2024
1 check passed
@chukka chukka deleted the jp-10.17.0 branch January 24, 2024 14:46
@EvertonSA
Copy link

EvertonSA commented Feb 11, 2024

this change caused the following error on my instance, see #1860

Failed to pull image "jfrog-xxxx.xxxx.com/registry-1.docker.io/xxxx": rpc error: code = DeadlineExceeded desc = failed to pull and unpack image "jfrog-xxxx.xxxx.com/registry-1.docker.io/xxxx": failed to resolve reference "jfrog-xxxx.xxxx.com/registry-1.docker.io/xxxx": failed to authorize: failed to fetch oauth token: Post "https://jfrog-xxxx.xxxx.com:8443/artifactory/api/docker/registry-1.docker.io/v2/token": dial tcp 10.xxxx:8443: i/o timeout

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.

Current SecurityContext settings doesnot allow to run it secure on EKS
3 participants