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

Allow oauth proxy imagestream to be used by specifying the namespace/… #1035

Merged
merged 2 commits into from
Apr 22, 2020
Merged

Conversation

objectiser
Copy link
Contributor

…name

…name

Signed-off-by: Gary Brown <gary@brownuk.com>
@codecov
Copy link

codecov bot commented Apr 22, 2020

Codecov Report

Merging #1035 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1035   +/-   ##
=======================================
  Coverage   64.23%   64.23%           
=======================================
  Files          83       83           
  Lines        6627     6627           
=======================================
  Hits         4257     4257           
  Misses       2229     2229           
  Partials      141      141           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd7c72c...729755e. Read the comment docs.

Signed-off-by: Gary Brown <gary@brownuk.com>
@objectiser objectiser changed the title WIP: Allow oauth proxy imagestream to be used by specifying the namespace/… Allow oauth proxy imagestream to be used by specifying the namespace/… Apr 22, 2020
@rubenvp8510
Copy link
Collaborator

Small comment, this looks good.

I tested in my local environment, with and without specify an image stream and it works correctly, I was able to create all-in-one and production strategies, no seeing errors on logs.

return
}

image := fmt.Sprintf("%s:%s", imageStream.Status.DockerImageRepository, imageStream.Status.Tags[0].Tag)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it OK to assume that we will always use the first tag? I would say that the answer is yes, at least for now, but not sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, the comment on the type indicates that the first tag is the current one.

Tags are a historical record of images associated with each tag. The first entry in the TagEvent array is the currently tagged image

@objectiser objectiser merged commit cea1081 into jaegertracing:master Apr 22, 2020
@objectiser objectiser deleted the ocpoauth branch April 22, 2020 20:48
@objectiser
Copy link
Contributor Author

@rubenvp8510 Thanks for testing this!

jpkrohling pushed a commit to jpkrohling/jaeger-operator that referenced this pull request Dec 15, 2020
jaegertracing#1035)

* Allow oauth proxy imagestream to be used by specifying the namespace/name

Signed-off-by: Gary Brown <gary@brownuk.com>

* Add ImageStream type only to the Scheme

Signed-off-by: Gary Brown <gary@brownuk.com>
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.

2 participants