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.

Sign up for GitHub

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

Jump to bottom

GCR as a main development docker registry #1065

Open
4 tasks
mcdoker18 opened this issue Oct 30, 2019 · 3 comments
Open
4 tasks

GCR as a main development docker registry #1065

mcdoker18 opened this issue Oct 30, 2019 · 3 comments
Assignees
@karbyshevds @maxkochubey
Labels
gcp infra
Milestone
1.1

Comments

@mcdoker18
Copy link
Contributor

mcdoker18 commented Oct 30, 2019 •
edited
Loading

We have to implement the following tasks:

  • Integrate our Jenkins pipelines with GCR
  • Cleanup nexus from old docker images and blob storage
  • Ensure that AWS and Azure has access to the GCR
  • Create a cleanup job for legion and test model docker images in GCR. Script example
@mcdoker18 mcdoker18 added this to the 1.1 milestone Oct 30, 2019
@kirillmakhonin
Copy link
Member

As I remember, we have a job for Nexus, can we patch it to scan GCP's GCR

@karbyshevds
Copy link
Contributor

can you please give me some tips to find out images that was produced during particular test run ?

@mcdoker18
Copy link
Contributor Author

@karbyshevds Model docker images have a cluster prefix, for example, gcr.io/blabla/gke-legion-ci/counter-3.3@sha256:09f83029aec33e5543404a35d24d2293d90e1d0467b49a16c363c5a878118059

@mcdoker18 mcdoker18 changed the title Cleanup GCR from model images GCR as a main development docker registry Nov 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karbyshevds karbyshevds

@maxkochubey maxkochubey

Labels
gcp infra
Projects
None yet
Milestone
1.1
Development

No branches or pull requests
4 participants
@karbyshevds @kirillmakhonin @mcdoker18 @maxkochubey