►
From YouTube: 09 Project Quay - Joey Schorr (Red Hat)
Description
OpenShift Commons Gathering @ Kubecon/NA San Diego November 18 2019
Joey Schorr (Red Hat)
A
Who
here
knows
what
Quay
is
raise
your
hands?
Excellent?
Who
here
is
ready
for
lunch?
Excellent,
so
I'm
gonna
try
to
make
this
as
long
as
possible.
I
kidding
I'm
gonna
try
to
go
quickly
here.
I'm,
not
gonna,
keep
too
much
your
time.
Five
minutes
max.
So
just
go
through
this.
My
name
is
Shirley
Shore
I'm,
the
former
co-founder
and
now
tech
lead
of
the
Quai
team
and
I'm
gonna
just
go
a
little
bit
into
the
history
of
Quay
and
some
of
the
cool
stuff
we're
announcing
today.
A
So
what
what
is
Quay
Quay
was
the
first
enterprise
grade
container
registry.
Ever
we
actually
launched
Quay
Oh.
This
is
an
example.
From
early
2014,
we
launched
in
October
2013
at
a
doctor,
meetup
in
New,
York
City,
actually
the
same
doctor
meetup,
where
we
would
meet
Alex
Povey,
who
would
eventually
acquire
us
later
on,
which
was
a
cool
little
fact
Wade,
and
we
were
actually
the
first
private
container
registry
on
the
internet
even
before
docker
hub.
A
So
when
we
launched
Quay,
you
can
see
here,
there
was
a
pretty
big
focus
on
secure
hosting
for
private
doctor
repositories,
and
this
was
because
at
the
time
there
was
no
other
solution
for
private
ones.
There
was
only
the
docker
public
index.
We
quickly
grew
from
there
and
by
GRU
I
mean
customers,
not
us.
A
It
was
just
myself
and
my
co-founder,
so
it
was
a
two-man
job
for
a
very
long
time
and
then
in
the
summer
of
2014,
we
were
acquired
by
core
OS
and
we
grew
with
them
since
then,
and
grew
out
the
Quai
team,
and
then
we
were
acquired
by
Red
Hat
in
2018
and
then
IBM
in
2019
I've
had
the
same
job
for
four
companies.
It's
actually
pretty
fun,
so
this
was
way
back
in
early
2014,
and
this
is
Quetta
day.
Not
much
has
actually
changed.
A
It's
actually
the
same
code
base
that
has
grown
up
organically
over
time
and
on
a
mark
of
that
code
base.
What
is
project
way
well
project
way
is
the
open
sourcing
of
our
entire
code
base,
nine
thousand
nine
hundred
commits
of
which
I
wrote
about
six
thousand
of
them.
If
I
had
to
guess
so
it's
been
a
very
long
time.
A
This
is
a
we're
looking
at
over
six
years
of
development
effort
and
as
per
you
know,
red
hats,
commitment
to
open
source
project
way
is
the
open
source
project
behind
the
quake
container
registry
I
should
mention
the
source
code
that
we
open
sourced,
and
that
is
project
way.
Today
is
the
code
that
runs
on
quad
at
I/o
and
is
the
code
that
is
read
hack
way.
There
is,
as
of
this
moment,
no
upstream
versus
downstream.
A
So
the
important
parts
sourcing
contributing
the
project
waste
source
code
is
hosted
in
github
at
getup,
comm,
slash,
Kwai,
slash,
clay
or
QQ.
Please
take
a
look.
We
did
do
something
a
little
interesting.
We
squashed
the
commit
history
because
there
was
a
lot
of
commits
and
err.
They
were
just
myself
and
my
former
co-founder
like
railing
against
random
things.
A
So,
rather
than
having
to
go
through
at
hand
to
edit
9000
commits
we
cleared
the
history,
but
we
kept
the
empty
commits
so
that
the
people
who
did
contribute,
even
when
it
was
private
product,
we're
still
there
in
terms
of
recognition
and
then
since
then,
of
course,
we
are
what
we
will
have
full
commit
history.
We
also
have
clear
so
who
here
knows
what
Claire
is
excellent
for
those
who
don't
know
Claire
is
our
open
source
security
index
Aaron
scanner,
it
scans
for
package
based
vulnerabilities
found
in
container
images.
A
Claire
can
be
found
at
github.com,
/
Kwai,
slash
Claire,
it
works
tightly
with
Kwai,
but
it
is
not
required
to
use
Kwai
with
it.
So
there
have
been
a
number
of
integrations
of
Claire
by
other
providers
on
Amazon.
If
I
recall,
launched
support
for
this
I
believe
it
was
no
more
than
two
weeks
ago
and
I
believe
there
been
some
work
done
by
Google
as
well,
so
we
have
a
lot
of
contributors
there
as
well
and
there's
a
new
version
of
Claire
Claire
v4.
Yes,
we
have
currently
Claire
v2
and
we're
working
on
Claire
v4.
A
There's
history
there,
but
Claire
v4
is
currently
being
developed
as
the
more
modern
version
of
Claire.
So
we're
always
looking
for
interested
parties
there
as
well
documentation
for
project
way
can
be
found
at
Doc's
top
project.
We
do
you
don't
need
the
slash
welcome,
but
it's
a
good
entry
point.
I
should
state
for
the
record.
These
Doc's
are
evolving
over
time.
They
started
as
a
duplication
of
our
redhead
quad
ox
a
couple
of
weeks
ago,
and
our
docs
team
is
working
diligently
to
spruce
them
up
and
change
them.
A
So
if
you
see
references
like
rel
is
required
to
run
redhack
way
for
Red
Hat
way.
That
is
true
for
a
project
way.
It
is
not
so
don't
let
that
be
an
excuse
not
to
run
project
way
on
your
own
laptop.
As
long
as
you
can
run
a
container,
you
can
run
project
way
because
we
serve
it
as
a
container
image.
There's
a
docker
file
in
the
root
you
can
just
use
to
build
some
things.
I
should
talk
about
I'm,
going
to
put
a
big
asterisk
on
this.
A
Anything
on
here
is
speculative
me
is
subject
to
change.
I
am
NOT
the
product
manager.
So
if
my
p.m.
emails
me
after
this
talk
and
says,
hey
why'd,
you
commit
to
this
I'm
not
committing
to
anything,
but
this
is.
These
are
the
things
that
we're
likely
to
do
in
the
New
York
for
term
future.
The
first
big
one
is
code
cleanup
after
a
recent
data
model.
A
Migration
for
those
who
don't
know
and
I'm
gonna
go
very
briefly
into
this,
but
there
have
been
three
different
versions
of
the
docker
protocol
for
pushing
and
pulling
container
images
and
Quade
today
supports
all
three
simultaneously
full
backwards
and
forwards
compatible
we're
the
only
registry
product
on
the
market
that
has
done
so
and
will
likely
continue
to
do
so.
But
in
order
to
migrate
between
the
older
api's
and
the
newer
api's,
we
had
to
migrate
our
data
model
and
we
had
to
do
that
on
Quay
dot,
IO,
with
a
billion
plus
images
without
any
downtime.
A
This
is
like
trying
to
replace
the
engine
and
the
wheels
of
your
car
without
stopping
on
a
on
the
auto
bottom,
and
so
I
intend
to
give
a
really
cool
talk
about
this
in
the
future.
There's
a
lot
of
really
cool
history
here
and
a
lot
of
very
subtle
technical
detail,
but
suffice
to
say
there
will
be
a
PR
coming
for
me
in
the
next
two
months
or
so
that's
going
to
delete
a
very
large
section
of
the
Quai
code
and
I'm
very
excited
about
it.
So
that's
number
one.
A
The
second
one
is
additional
modes
for
registry
mirroring,
we
should
actually
say
repository
marrying,
but
I
mistyped.
It
quai
launched
a
feature
in
Quay
3.1,
which
went
out
a
month
or
two
ago,
which
was
a
repository
marrying
where
you
can
now
set
up
a
quay
repo
to
mirror
the
contents
or
a
subset
of
contents
from
another
repository
posit
ori.
I
also
need
to
learn
to
speak
english,
whether
within
the
same
registry
or
another
registry.
A
So
you
could,
for
example,
have
your
on-prem
Quay,
mirror
images
from
Quay,
Oh
or
docker
hub
or
another
on
Prem
Quay,
you
could
have
a
production
names
based
mirror
so
a
subset
of
tags
from
a
staging
namespace.
Things
like
that
we're
gonna
be
adding
additional
modes
and
additional
rules
for
registry
mirroring
repository
mirroring
right
now,
it's
by
tag,
reg
X,
but
we're
gonna,
be
adding
label
matching,
and
a
few
other
really
cool
things
to
allow
you
to
have
very
fine
and
powerful
green
control.
A
New
build
manager
support
a
quoit
has
built
in
support
for
building
backer
files.
You
can
give
us
a
docker
file
via
directly
uploading
it
or
hooking
it
up
to
your
github
or
gitlab
or
bitbucket,
or
just
even
your
custom,
get
in
call
us
a
video
of
webb
book.
The
bill
manager
for
that
on-premises
uses
just
build
workers
connected
to
Quay,
but
as
the
world
adopts
kubernetes,
we
have
a
kubernetes
based,
build
system
that
we
actually
use
for
Quay
IO,
and
the
plan
is
to
formally
support
that
for
OpenShift
customers.
A
So
you
can
just
hook
an
open
shift,
cluster
to
york
way
and
util
use
open
shift
to
do
the
builds
and
then
finally-
and
this
is
the
most
speculative,
but
also
the
most
fun
part.
In
my
opinion,
the
Quay
API
was
originally
designed
when
the
world
was
a
little
less
complicated
and
was
a
little
less
based
on
manifests
and
more
based
on
images.
We've
added
manifests
support
to
our
existing
version.
One
API
the
quake
continues
to
support.
A
Today,
however,
the
plan
is
to
build
a
new
API
one
that
is
faster
and
doesn't
have
some
of
the
craftiness
of
the
older
versions
and
to
hopefully
revamp
our
UI
to
make
use
of
that.
You
new
API
for
better
performance
and
efficiency
in
additional
feature
gains.
Quai
is
one
of
the
few
registry
products
on
the
market
that
is
fully
automated.
A
Every
single
operation
and
action
that
is
possible
in
the
UI
is
driven
by
a
fully
documented
Roth
based
REST
API,
and
so
this
will
be
the
next
generation
of
that
and
we're
always
asking
for
feedback
on
it
as
well.
So
that's
the
that's.
Some
of
the
upcoming
work
we
have
there's
quite
a
bit
more
I
would
suggest
taking
a
look
at
the
Red
Hat
way.
Roadmap
as
well
next
month
is
likely
when
Red
Hat
way
3.2
will
be
launched
and
there
will
be
the
very
first
integration
between
quai
and
OpenShift
in
our
container
security
operator.
A
Work
which
will
allow
you
to
automatically,
via
installing
the
container
security
operator
in
OLM,
see
the
security
status
of
your
running
pods
in
your
open
shift
console
if
they
were
pulled
from
any
version
of
quai
that
is
connected
to
Eclair
with
no
additional
setup.
There
will
be
no
off
token
management,
no
connectors
it'll,
just
work,
so
I
would
recommend
taking
a
look
at
our
room
app
there
as
well
and
that'll.
Be
a
big
nice
feature.
Coming
up,
don't
forget
to
store
our
repos
on
github.
A
B
So
that
took
a
whole
lot
of
work
to
get
to
there
and
I
just
wanted
to
quickly
thank
Joey
and
the
whole
entire
quai
team
and
I
know
Joey
doesn't
drink.
So
we
have
a
glass
of
water
for
you.
But
if
you
could
join
us
Joe
and
we
could
have
a
toast,
because
this
took
a
lot
of
work
and
come-come
here
and
is
Evan.