Reordering ImageStreams before BuildConfigs #42
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
|
LGTM - thanks for investigating and fixing |
|
@sabre1041 thanks again for your help here. |
This was referenced Nov 14, 2017
Merged
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.
Reordering ImageStreams before BuildConfig objects to avoid issues authenticating to Docker registry during image push.
It is important that ImageStreams be placed before BuildConfigs in order to properly attach the docker credentials to the destination registry. Otherwise a race condition will occur due to ImageStream resolution. If a build begins before resolving the destination, OpenShift will be unable to attach the proper .dockercfg secret which will result in an authentication error
This is being tracked in the following BZ and discussed in an issue in origin
CC: @sherl0cks @oybed