►
From YouTube: Red Hat Quay Overview
Description
Introduction to Red Hat Quay container and application registry with Quay 3.3.
Learn more at: https://www.openshift.com/products/quay
A
Welcome
to
this
overview
presentation
on
redhead
Quay
records,
industry
leading
enterprise
container
registry,
as
kubernetes
and
Catina
platforms
become
the
new
standard
for
cloud
native
application.
Development
container
image
registry
is
become
critical.
Part
of
emergence
of
the
deployment
pipeline
container
image
registries
are
the
place
where
images
are
stored
and
are
the
place
where
orchestrators
are
pulling
images
from
to
be
able
to
deploy.
Containers
container
orchestrators
require
continued
image
registry,
while
rated
Quay
certainly
is
a
container
registry.
It
goes
far
way
on
that.
A
Quay
is
an
industry-leading
trusted
and
open-source
registry
platform.
It's
developed
in
strong
collaboration
with
a
broad
open
source,
customer
and
ecosystem
community,
where
the
quay
runs
on
any
infrastructure,
boson,
pram
or
public
cloud
and
works
with
any
OCI
compliant
tool,
but
works
best
with
write.
It
up
shift
one
of
its
key
strengths.
It's
is
it's
nearly
unlimited
scalability.
A
You
can
run
Quay
on
your
laptop
or
on
your
data
center
to
serve
a
handful
or
few
hundreds
of
images,
but
you
can
also
use
it
to
serve
billions
of
images
to
thousands
of
clusters
and
thousands
of
users
as
we
do
with
query
or
every
single
day.
Quay
is
built
for
real
enterprise
use
cases
where
content
governance
is
secured.
Here
are
two
major
focus
areas.
It
includes
a
built
in
one
durability,
scanning
fine-grained,
access
control,
model
and
multi-tenancy
model,
and
several
other
capabilities
to
federate
content
across
your
clusters,
data,
centers
and
even
regions.
A
You
can
run
it
for
your
own
in
your
own
data
center
on
public
cloud
or
use
our
hosted
SAS
offerings
querido,
and
we
will
take
care
of
all
operational
aspects
for
you
whether
Quay
is
built
to
support
to
deaf
set
office
environments.
It
helps
you
to
control
how
content
is
flowing
into
and
then
used
inside
your
environment,
Quaker
managed
a
central
kontin
english
point
for
explicitly
whitelisted
and
trusted
content.
This
allows
you
to
explicitly
define
which
content
from
redhead
others
of
the
vendors,
your
suppliers
or
the
open
source
community
can
be
used
within
your
environment.
A
The
fine-grained
access
control
model
allows
you
to
configure
both
Quay
and
open
shipped
in
a
way
that
reflects
your
organizational
setup
and
workflows
the
more
you
shift
left
your
security
approach.
The
more
important
it
is
to
enable
developers
to
have
access
to
the
information
which
is
needed
in
order
to
take
care
of
security
aspects
already
in
various
stages
of
the
software
development
lifecycle
was
it's
very
efficient
and
fast
vulnerability.
A
Scanning
Cray
helps
to
detect
vulnerable
images
already
in
early
stages
of
a
CI
CD
pipeline,
using
the
integration
into
the
company's
platform
and
visualization
inside
the
object
console.
It
helps
to
detect
security
issues
with
images
both
running
and
address
easily
when
a
requires
used.
What's
API,
the
information
stored
in
quei
can
be
used
by
all
interested
parties
in
a
def
psychics
environment
throughout
the
entire
lifecycle.
A
Quai
is
built
to
run
and
geographically
dispersed
setups
across
multiple
data,
centers
or
regions.
Once
the
content
to
plenty
uses
the
foundation
for
your
business,
application
has
been
explicitly
whitelisted
burrowed
into
the
environment,
both
to
your
application
and
repository
mirroring
can
be
used
to
distribute
the
content
even
further
to
all
your
data,
centers
and
clusters
running
on
Prem
or
on
public
cloud
in
various
regions
across
the
globe
has
used
them
many
customers,
with
globally
dispersed
deployments.
A
The
content
can
be
exposed
using
a
single
globally
shared
web
history
to
speed
up
the
excess
to
the
binary
blobs
in
those
regions.
Whisk
waste
to
your
replication
feature,
images
that
are
pushed
to
one
questons
are
replicated
to
other
instances,
so
that
image
pools
happen
from
the
local
data
center
nearby
storage,
alternatively,
or
side
by
side.
With
to
your
application,
the
repository
incapability
can
be
used
to
mirror
the
entire
or
a
specific
subset
of
the
content
between
multiple
Quetta
plans.
A
This
also
allows
you
to
have
team
or
reach
specific
registry
wide
configurations
such
as
country,
specific
setups,
or
if
they
need
to
be
owned
by
dedicated
teams
of
the
organization.
By
having
this
additional
layer
of
manageability
when
getting
content
into
and
distributing
quantum
Fuquay,
customers
can
get
an
additional
level
of
freedom
and
independence
for
distributed
registries.
The
fine-grained
access
control
allows
you
to
define
which
content
can
be
used
by
one
and
where
and
is
aligned
to
your
specific
governance
requirements.
A
The
container
registry
is
an
important
part
of
your
software
development
tool
chain,
used
by
many
different
tools
for
the
entire
lifecycle.
A
key
requirement
for
an
enterprise
registry
Darfur
is
that
it
allows
you
to
integrate
it
into
your
existing
environment
and
then
it
helps
you
to
automate
the
workflows
as
much
as
possible.
During
your
build
stage,
you
can
leverage
Cray,
build
automation,
use
your
own
audio,
bashir
bills
and
pipelines
after
the
images
have
been
built
and
stored
in
registry.
Several
capabilities
of
query
helps
you
to
manage,
secure
and
distribute
them
in
a
very
efficient
manner.
A
When
the
software
finally
has
been
deployed
to
your
clusters
and
runs
in
your
production
environment.
The
deep
integration
into
the
kubernetes,
an
overshift
platform
helps
you
to
leverage
quays
enterprise
features
from
directives
in
your
restoration
platform.
Automation
and
integration
are
critical
success
factors,
and
this
includes
both
built-in
workflows
and
external
automation.
Using
VAP
is
robbing
accounts
webhooks
and
the
API
allows
you
to
easily
integrate
quai
into
all
other
tools.
You
are
using
today
or
plan
to
use
in
the
future.
A
It's
very
easy
to
deploy
and
get
started
with
quays
default
settings
on
a
developer
laptop
but
probably
Cray
runs
even
better
inside
your
data
center,
using
the
crane
operator
to
manage
deployment
and
registry
lifecycle
each
grade
appointment
is
also
highly
scaleable.
Sin
square
is
deployed
as
a
container
and
can
scale
horizontally
horizontally
as
needed
before
the
final
product
version
is
shipped.
A
It's
battle-tested
at
scale
on
Cueto,
one
of
the
largest
registries
out
there
greater
than
ourselves
hundreds
of
millions
of
images
at
a
rate
of
tens
of
millions
of
requests
to
thousands
of
customers
daily
and
it's
using
the
same
code
base
as
well.
That
cray-cray
is
designed
and
used
by
many
large
customers
and
their
organizations.
The
multi-tenancy
model
allows
to
clearly
separate
concerns
and
responsibilities,
but
also
allows
matrix
organizations
as
well.
A
Responsibilities
can
be
organized
using
craze
organizations,
teams
and
users,
and
fine-grained
permissions
can
be
mapped
to
your
organizational
structure
to
grant
access
to
a
specific
repositories,
as
used
by
many
customers
with
globally
dispersed
deployments.
The
content
can
be
exposed
using
a
single
global
shared
registry
to
speed
up
the
excess
to
the
binary
blobs
with
quest
JIRA
application
feature,
alternatively,
or
side
by
side
with
JIRA
application.
The
repository
mirroring
capability
can
be
used
to
mirror
the
entire
or
subset
of
the
content
between
multiple
deployments.
A
Lifecycle
environments
can
be
separated
by
our
organization's
or
distinct
repositories
and
lifecycle.
Environment
promotion
can
be
automated
by
the
quay
api
or
directly
from
within
your
CI
CD
pipeline
retic
way
also
allows
you
to
integrate
your
existing
identity
infrastructure
and
supports
multiple
identity
providers,
including
LDAP,
Active,
Directory
or
AEC.
All
relevant
actions
are
locked
and
visualized
within
equals
interface
as
well.
A
Kwe
is
built
on
a
cloud
native
architecture
and
is
deeply
integrate
without
the
shift
in
common
areas.
Quay
runs
on
any
infrastructure
and
works
with
any
tools
that
follows.
The
open
container
initiative
standards,
however
running
Quay
on
open
shift,
allows
additional
benefits
such
as
scalability.
Since
Quay
can
leverage
the
cluster
compute
capacity
to
manage
expected
amount,
simplified
networking
using
diverse
ingress
options
was
well
established
patterns
for
any
application
deployed
to
the
platform
cieaura
to
hero.
A
Operators
which
encode
the
operational
knowledge
of
the
lifecycle
and
management
of
a
community's
native
application
play
an
important
role
not
only
for
the
company's
ecosystem,
but
also
for
resident
way
in
particular.
Currently,
there
are
three
different
cuneus
operators
to
drive
the
integration
into
the
colonists
platform.
The
Quai
operator
automates
deployment
a
day
to
management
of
grades
off
the
container
security
operator,
brings
Square
Quay
and
Clair
vulnerability
scanning
metadata
to
kubernetes
object.
A
Kubernetes
cluster
admins
and
developers
can
monitor
unknown
container
image
wounded,
abilities
on
a
cluster
project
or
pod
level
directive
from
within
the
powerful
OpenShift
console.
The
kwai
bridge
operator
is
designed
to
streamline
the
user
experience
for
Oakridge
of
customers.
If
Quay
is
used
as
their
container
registry
of
choice
already
before
Quay
has
been
entirely
open
source
in
2019,
we
only
develop
the
product
in
strong
collaboration
with
our
customers
and
ecosystem
partners.
A
This
includes
sharing
early
designs
of
time's,
was
customers
and
partners
to
get
feedback
as
early
as
possible
after
we
verified
in
surveys
or
workshops
that
the
feature
design
will
meet
the
customer
or
partner
needs.
We
finally
started
developing
decode
the
documentation
and
test
cases.
Of
course,
after
the
new
feature
has
passed
or
cutest,
we
make
it
available
to
selected
namespaces
at
creditor
or
to
verify
that
it
works
at
scale
and
to
guess
an
additional
early
feedback
from
those
high-touch
customers.
A
Once
this
has
been
stabilized
again,
we
blew
the
final
product
deliverables
and
make
them
available
to
Orion
customers.
In
addition
to
that,
we
sometimes
build
features
which
are
required
for
massive
scale
deployments
of
quai,
as
we
do
is.
Quite
a
tour
one
of
the
five
biggest
waitress
was
out
there.
Those
enhancements
are
then
made
available
as
a
product
feature
as
well,
given
the
huge
amount
of
on-prem
customers,
one
inquiry
at
a
huge
scale
as
well.
This
includes
features
such
as
the
Quay
usage
locks
and
elasticsearch,
but
also
includes
operational
aspects.
A
We
added
to
the
product
based
on
the
experience
made
by
our
Zoe
team,
which
operates
quite
at
all.
Of
course,
we
not
only
build
and
ship
new
a
version
if
a
new
feature
comes
out,
but
also
ship,
regular
updates
for
vulnerabilities
and
bugs
which
are
impacting
our
customers.
The
entire
developing
model
of
Quay
is
1%
upstream.
First,
we
develop
against
the
gate
branch
which
is
available
to
the
community
as
well,
and
the
ship
upstream
builds
at
the
end
of
each
script.
A
It's
entirely
open
and
transparent,
given
the
usage
of
one
single
JIRA
project
for
both
the
upstream
and
our
commercial
product,
world
project
way
is
the
extreme
project
representing
the
code.
That
powers
were
that
Cray
in
coral,
more
than
150
contributors
are
helping
us
to
build
better
software,
which
is
used
by
thousands
of
customers
of
all
sizes.
Around
the
globe,
but
it
creates
trusted
by
many
organizations
of
all
sizes
and
backed
by
red
heads
decades
of
expertise.
A
Ratchet
Quay
is
available
in
two
different
flavors.
You
can
use
whetted
Quay
as
a
private
registry
running
in
your
own
data
center
on
public
lot.
This
offers
more
direct
control
and
freedom,
giving
you
the
direct
access
to
change
or
fixed
components,
as
you,
like.
The
registry
also
sit
behind
your
firewall,
so
the
security
is
easier
to
audit
and
monitor
by
going
with
an
on-prem
registry.
Also
save
on
bandwidth
and
storage
and
deployments
are
local,
but
there
is
a
trader
for
that.
Freedom
and
control,
which
is
having
to
do
the
maintenance
in
scaling
yourself.
A
In
contrast
to
other
products
developed
for
end-users,
Rathod
is
running
and
operating
its
own
product
as
a
software
service
offering
that
hosted
or
version
quello,
as
I
said
earlier,
so
of
hundreds
of
millions
of
images
at
a
weight
of
tens
of
millions
of
requests
through
thousands
of
customers
every
single
day
using
retina.
That
all
means
that
wet
head
is
taken
care
of
operating
crave
for
you,
since
the
same
codebase
is
used
for
both
weather,
Korea
and
cuerda.
The
feature
set
is
nearly
exactly
the
same
proposed.
A
The
same
applies
to
support,
provide
a
Parrothead
for
both
types
of
customers.
In
addition
to
the
monthly
paid
plans
on
Cuero
which
granted
access
to
private
repositories,
all
public
repositories
are
free
and
unlimited
to
empower,
especially
all
the
open
source
communities
who
are
using
Twitter
or
to
distribute
their
own
open
source
software
on
all
rated
crave
product
pages.
You
can
start
an
evaluation
period
and
get
access
to
the
product
and
wet
heads
about
winning
customer
portal,
including
knowledge,
videos
and
documentation
for
those
who
don't
want
to
locally
deploy
and
run
quite
revelaed.