Update chartsvc and chart-repo to v1.2.0 #902
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prydonius
changed the title
|
I just released v1.2.0 in Monocular and updated this PR to use that version, with this we should be able to fix the CI. Thanks @andresmgot! |
prydonius
approved these changes
Dec 22, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current chart-repo image cannot be pulled since
latestwas rebuilt yesterday. Apparently it's not possible to use thesha256of an old image (that behavior is different from the Docker Hub). I am changing the tag to uselatestuntil there is a new release.Note that Quay.io is under an incident: http://status.quay.io/incidents/72jyq4322h85 so I am not sure if the issue (not able to pull an old sha256) is actually caused by that incident.