►
From YouTube: OKD Working Group 2020 10 13 Full Meeting Recording
Description
OKD Working Group 2020 10 13 Full Meeting Recording
Diane Mueller co-chair, OKD-WG
https://okd.io
A
All
right,
so
I
I
know,
and
and
I
know
christian
and
I
was
just
gonna
touch-
base
with
everybody.
I
was
getting
christian
vedim
and
charo
queued
up
to
record
a
a
talk
for
the
openshift
commons
gathering
and
from
what
I
can
tell
from
the
slack.
It
didn't
happen
this
morning,
but
you've
got
to
reschedule
date
within
trado
tomorrow.
A
Do
that
and
I
saw
the
slide
that
came
through
and
the
you
know
we're
going
to
do
whatever
demos
you
want
to
do,
but
also
incorporate
a
demo
of
deploying
or
using
the
cr
the
code
ready
container
and
that
was
that'll,
be
part
of
the
openshift
commons
gathering,
which
is
going
to
be
on
november
17th.
The
first
day
of
kubecon,
north
america
and
stay
tuned
today
is
my
day
to
update
the
schedule
for
that
event.
A
B
A
D
A
A
A
And
boy,
so
this
it's
a
short
on-ramp
so
by
the
end
of
the
month,
but
there's
a
competition
to
show
the
best
openshift
web
console
customizations
using
openshift4
mechanisms
and
the
most
I've
ever
done
to
the
console
is
change
a
logo.
So
I
am
not
going
to
enter
this
contest,
but
I'm
going
to
throw
down
a
challenge
to
see
if
we
can
get
a
little
more
visibility
of
okd
by
having
someone
who
is
deploying
okd
out
there
to
share
whatever.
A
But
if
you,
if
you're
interested,
I
have
failed
at
that.
As
we
all
know,
however,
we
are
getting
them.
We
are
getting
some
swag
for
commons
and
okd
put
into
the
cool
school
stuff
store
at
open
at
red
hat,
which
means
hopefully
by
christmas.
I
can
send
you
all
a
present
yay
or
for
okay
d4,
but
that
is
a
process
and
it
is
not.
I
obviously
I'm
not
in
marketing.
A
So
I
don't
know,
but
this
is
this
deck
that
I
dropped
in
here.
If
someone
could
check
and
make
sure
you
can
see
it,
if
not
I'll,
make
a
pdf
version
of
it
available,
it
just
walks
you
through
all
of
the
new
features
and
what's
coming
down,
and
it's
really
cool
and
you
know
lots
of
good
stuff
around
the
console
and
getting
started.
So
if
you're,
I
don't
know
at
dado
neil,
if
you're
using
any
of
this
stuff
to
make
it
look
wonderful
or
at
bcit
bruce.
C
A
I
always
had
my
own
logo
for
it,
so
I
knew
I
was
in
my
version
of
it.
That
was
that
was
my
my
signal.
So
so
there
I've
done
my
duty.
I've
promoted
the
contest,
and
that
was
that
was
that.
So
the
other
thing
I
was
going
to
say
is-
and
I
I
didn't
find
out
the
date
and
time
of
it
yet,
but
there
is
a
birds
of
a
feather
hour,
long
slot
that
we've
been
allocated
by
the
powers
that
be
at
kubecon
or
okd
working
group.
A
So
as
soon
as
I
do
that
I
will,
and
if
you
win
the
console
project-
maybe
well
we'll
we'll
demo
that
too,
but
there's
it's
an
opportunity
to
do
an
introduction,
probably
repeat
the
same,
slides
that
we're
going
to
use
in
the
gathering
and
do
outreach
to
the
kubernetes
community
at
that
event.
So
that's
that's
a
really
big
deal
so
we'll,
as
we
get
closer
to
it,
we'll
figure
out
how
to
structure
that
day-
and
you
know
showcase
all
of
you
guys
to
our
best
abilities
done
that
okay.
A
C
C
D
D
Was
there
a
somebody
referred
to
an
issue
being
being
open
about
that?
Could
you
drop
a
link
to
that
in
the
chat?
Yeah
yeah?
So
I'm
looking
at
the
lib
machine
code
or
the
docker
machine
repo,
which
is
where
the
lib
machine
code
lives?
Virtualbox
is
still
there,
but
it
yeah.
So
the
virtualbox
driver
is
still
there
as
well
as
the
vmware
ones,
the
google
ones,
the
hyper
v
ones,
all
the
other
ones.
G
D
G
Yeah
yeah,
I
mean
my
guess
is
from
looking.
I
I
mean
I
I
I
don't
know
enough
to
be
able
to
give
too
much
of
a
guess,
but
it
just
looks
like
the
vm
starts
and
whatever
the
communication
needs
to
happen
between
the
external
process
and
the
vm.
Just
never
quite
happens.
I
can
literally
just
get
stuck
on
creating
code,
the
code
ready
container
vm,
it
creates
the
vm,
the
vm
starts
and
then
nothing
happens.
I
haven't
tried,
leaving
it
overnight.
D
I've
been
trying
to
figure
out
what
the
licensing
is
for
red
hat
code,
ready
containers
and
have
not
gotten
an
answer
for
that.
So
I
haven't
touched
it
yeah,
it's
a
little.
I
I
think
it's
a
little
annoying
you.
If
you
set
up
a
red
hat
developer
account,
you
can
use
code
ready
containers
for
free,
you
use,
but
you
have
to
create
a
pull
secret
from
your.
Your
red
hat
developer.
Account.
G
G
D
G
D
60
days
yeah,
so
I
I
reached
out
to
my
red
hat
account
person
to
ask
like
what
the
what's
the
deal
here,
because
this
is
directly
opposing
what
drc
is
documented
to
do
and
what
code
or
any
containers
on
red
hat
developer
says
it's
supposed
to
be
done
and
it
it
basically
blocks
people
from
actually
using
it.
So
I
haven't
tried
the
red
hat
crc,
because
I
can't
run
it
because
it
cut
it
keeps
creating
eval
cert
email
subscriptions,
and
I
can't
do
that.
D
B
A
D
Last
time
I
tried
it
worked
fine,
it
worked
fine
for
me
on
fedora
32,
so
I
haven't
tried
on
33,
yet
I'm
actually
honestly
a
little
scared,
because
the
changes
to
how
dns
works
by
default
make
it
so
that
I'm
a
little
unsure
whether
the
the
libert
dns
things
hacks
that
crc
uses
will
work.
I
haven't
tried
yet-
and
I
that's
that's
on
my
to-do
list,
but
it
worked
in
32.
E
D
A
A
The
the
cicd
build
projects
that
that's
getting
on
so
that
charo
isn't
building
them
by
hand,
and
so
that's
our
next
ask
and
I
don't
know
charo
if
you've
had
any
more
conversations
with
them.
I
think
it
was
on
me
to
set
up
a
meeting
with
everybody,
and
I
have
not
done
that
because
my
schedule
didn't
permit
it.
D
Yes,
it
is,
I
I
have
had
a
some
more
chat
conversations
with
with
the
code
ready
team,
so
so
I've
gotten
introduced
to
several
people.
Actually
one
of
them
reached
out
to
me
when
they
stumbled
across
my
repo.
So
so
we
got
the
conversation
going
there.
The
other
thing
we
need
to
we
need
to
figure
out,
which
is
an
internal
red
hat
thing
is
branding
for
our
code.
Ready
container
code
ready
is
a
as
a
trademark
kind
of
like
jboss
or
openshift.
D
I
A
F
I
A
I'm
going
to
push
back
and
say
that
this
is
branding
that
they
we
should
get
permission
to
use
code
ready.
So
I
I
will
have
a
conversation
with
the
powers
that
be
because
I
think,
especially
if
it's
in
the
build
process
and
it's
you
know
it's
part
and
parcel
of
it
and
we,
you
know,
I
know
internally
at
red
hat,
I'm
having
conversations
with
the
developer
evangelist
team
that
wants
to
use
more
of
this
stuff
in
their
their
evangelizing
and
getting
onboarding
people.
A
So
if
it's
called
something
different,
that's
going
to
not
make
them
happy.
So
I'm
going
to
see
if
I
can
get
a
little
internal
leeway
to
to
use
it,
so
that
was
part
of
my
hesitating
on
booking
all
those
meetings.
I
wanted
to
have
that
conversation
with
the
pms
first,
so
I'll
work
on
that.
But
if
you
guys
are
okay
with
ready
to
code,
I
think
that's
fine
with
me
too,
if
we
end
up
getting
pushback.
So
that
was
that.
E
C
C
A
Yeah,
what
I'm
going
to
do
is
I'm
going
to
ask
christian
and
vadim
I'll
talk
to
them
today
in
slack
or
anything,
to
get
put
a
little
update
on
the
working
group
list
and
see
if
we
can
get
that,
but
the
goal
would
be
to
have
it
just
be
part
of
the
the
build
process
for
open
shift
to
also
push
push
them
out
to
a
catalog
for
for
our
use,
rather
than
having
to
rebuild
them.
So
that
was
that
was
kind
of
my
goal
and
yeah.
A
D
Yeah
and
they
and
they
have
to
coordinate
you,
you
know
it's
the
same
effort
that
we're
doing
right
now,
with
code
ready
containers
multiplied
by
the
number
of
operators,
because
every
operator
has
its
own
team,
its
own
ci
setup.
In
fact,
there's
not
even
unfortunately
a
standard
pattern
for
how
these
operators
are
assembled
and
built
right,
so
some
of
them
might
be
built
with
helm
at
their
core.
Some
of
them
are
built
with
a
container
registry
written
in
go
with
their
core
and
and
others
follow
other
patterns.
C
But
I
have
a
good
news:
we
made
a
workshop,
a
three-week
workshop
with
okd
and
three.
I
think
main
operators
are
serverless
service
mesh
and
the
openshift
pipelines.
We
built
the
openshift
pipelines
on
our
own
and
also
see
serverless
from
the
get
repos.
We
did
not
simply
mirror
red
hat
images
and
yeah.
The
first
days
worked
rather
smooth.
The
problem
was
not
that
the
operators
did
not
work,
but
that's
the
examples
from
the
trainer
did
not
exactly
match
the
version,
but
this
is
no
big
thing.
C
The
problem
is
that
we
build
it
on
our
own
from
source,
and
my
boss
does
not
like
that
idea
to
to
publish
that
in
the
company.
Despite
of
that,
we
have.
We
have
launched
the
okd4
cluster
for
our
company
today
and
now
all
our
people
are
yeah
can
work
with
that.
It's
it's
rather
stable
and
it's
working
in
an
air
gap,
environment
and
so
on,
and
I
would
love
to
have
this
openshift
pipelines
operate
in
the
catalogs
that
we
only
have
to
click
on
the
button.
J
D
But
with
that
said,
joseph
I've
actually
got
now
some
working
examples
of
doing
a
disconnected
install
with
community
images
for
the
operators
for
rook
ceph,
open
data
hub,
which
you
see
on
the
screen
there
pipelines
with
with
all
of
the
cluster
tasks
and
serverless
k
native.
This
was
actually
a
a
project,
an
internal
red
hat
project
that
I
stumbled
into,
because
some
folks
reached
out
needing
some
help
with
some
stuff
turned
out.
D
It's
a
client
that
is
in
a
very,
very
highly
disconnected
environment
due
to
the
nature
of
their
business,
and
they
they
wanted
to
do
a
machine
learning
workshop,
which
needs
all
of
those
components.
I
just
referenced
so,
as
I
finish,
writing
up
how
I
made
it
work
in
their
completely
disconnected
environment
I'll,
be
using
those
as
the
pattern
for
our
openshift
recipes.
Our
okd
recipes.
A
We
might
not
remind
you
this
wasn't
about
prompt
thinking
you
to
get
that
other
one
done,
but
I
just
wanted
to
say
that
we
we
do
have
a
space
for
this
and
what
we're
gonna,
what
I'm
gonna
work
with
charon
2,
probably
this
week
and
we'll
push
a
note
out
to
the
okd
working
group
on
how,
if
you
have
another
recipe,
how
to
add
it
to
this
right
now,
each
one
of
these
and
my
internet
access
is
really
a
little
slow
here.
This
one
they
go
to
a
readme
file
with
the
instructions
here.
A
So
it's
not
it's
not
it's
not
perfect,
but
it
is
a
way
to
do
that
and
to
filter
it,
and
everything
is
in
github,
github.com,
slash
openshiftokd
and
you
just
have
to
make
a
pull
request
and
we'll
put
the
instructions
in
in
the
okd
workspace,
and
it
is
very,
very
slow
here.
So
I
apologize,
you
probably
aren't
even
seeing
this
yeah,
my
internets
are,
are
slowing
down
yep
you're,
not
seeing
this
anyways
there'll
be
it'll,
be
in
yes,
thank
you.
A
The
question
that
I
think
charo
and
I
had
still
was,
if
we,
if
we
should
be
linking
out
to
say
charo's,
github
repo
or
if
we
should
be
making
a
repo
inside
somewhere
in
the
okd
dot,
io
repo
or
in
another
repo
under
openshift,
to
put
all
of
these.
But
those
are
the
three
ones
that
charo
has
so
far.
But
I'm
guessing
that
each
of
you
have
others
yeah.
I
don't
know
it
seems
like
a
good
idea.
J
D
Absolutely
maybe
we
should
consider.
I
don't
know
if
this
has
been
thought
about,
but
like
maybe
we
should
have
an
organization
or
openshift
community
stuff
to
be
collected
into
one
place
because
stuffing
it
all
into
the
open
shift,
github
org
is
making
it
really
hard
to
find
stuff.
It's
getting
too
big
as
an
organization
and
maybe
just
having
like
an
open
shift.
Community
github
org
put
all
that
in
will
make
it
a
lot
easier
and
much
more
discoverable
yeah.
I
was
actually.
D
G
D
A
A
A
So
michael
we'll
see
you
later
so
so
that's
I
think
the
communities
of
practice
one
sounds
like
a
good
idea
as
long
as
it's
open
and
public
and
anyone
external
can
can
create
that
can
access
and
make
a
pull
request
so,
but
for
now,
what
I
would
say
is
if
you
have
one
that
you
want
me
to
add
in
to
the
current
page.
You
know,
for
you
know,
maybe
for
any
of
the
deployments
that
we
did
in
the
okd
marathon
or
anything
along
that
nature
or
something
else.
A
Just
let
me
know-
and
I
will-
and
with
listen,
probably
coaching
from
charo
link
to
it
and
we'll
get
it
get
up
and
going
because
I
would
love
to
have
you
know
a
few
more
in
there
and
to
be
able
to
reference
that
in
the
in
the
okd
working
group
presentations
and
at
the
birds
of
a
feather
in
november
and
encourage
people
to
do
that.
So
we've
got
to
figure
out.
D
Well,
I
don't
have
anything
public
specifically
for
datto,
but
like
I
could
probably
look
at
some
of
the
stuff
that
we've
had
so
far
and
and
start
talking
about
like
if
there's
somewhere,
to
put
it,
maybe
putting
it
there
and
and
having
it
public
for
people
to
to
see
and
contribute
to
it's
just.
There
hasn't
been
a
reason
for
us
to
do
that
so
far,
because
there's
really
nowhere
to
put
it
and
nowhere
to
advertise.
A
D
D
It
is
kind
of
working,
but
we
also
have
like
we've
done
another
recipe
where
we
did
upi
on
openstack,
because
our
openstack's
ridiculously
old,
and
so
the
ipi
doesn't
work.
So
there's
there's
a
couple
of
things
like
that
that
we've
got
floating
around
that
we
could
possibly
clean
up
and
actually
share.
A
Well,
jamie
is:
is
there
a
remi
fi,
I'm
looking
at
your
github,
I'm
I'm
trying
very
slowly
to
get
to
your
repub
reap
github
repo,
but
for
that
the
okd
openshift
upi
script.
Is
there
a
decent
readme
file,
or
is
it
just
the
code
because
I
think
the
one
key
here
is
what
I'd
like
to
do
is
point
to
a
decent
readme
file
that
that's
the
only.
A
A
little
bit,
I
think,
that's
one
prerequisite
I
would
ask
for-
is
that
what
I'd
like
to
link
to
is
not
the
actual
repo
but
to
the
readme
file,
and
I
see
your
remit
file.
There
is
just
very
short,
so
if
you
could
look
at
maybe
what
charo's
got
or
examples
in
the
rook
ceph
disconnected
or
the
tecton
one
and
just
a
little
bit
more
verbosity
there.
A
That
would.
That
would
be
helpful
because
I
might
I
I
worked
on
years
ago
at
active
state,
the
python
cookbooks
and
what
they
did
was
they
grabbed
like
a
little
snippet
of
code
or
something
it
was
a
little
bit
more
visual
than
what
I
have
on
the
okdio
site
right
now,
and
I'm
just
thinking
that
maybe
my
next
step
is
to
figure
out
how
to
show
the
readme
file
for
each
of
these
things
or
a
snippet
of
the
readme
file,
and
some
of
that
is
what
you're
describing.
J
A
J
C
F
D
A
D
H
H
I
A
Yeah
yeah,
okay
sub
names,
so
I
think
we
have
to
be
tread
a
little
carefully
on
this
one,
because
I
I
yeah
I'd
part
of
me
wants
to
take
what's
open
right
now,
the
okd
landing
page.
I
want
to
move
it
into
wherever
this
is
too
so
that
it's
not
separate
out
there
in
openshift-cs,
which
is
you
know,
community
sites
or
something
like
that
yeah.
A
D
And
then
I
mean
the
worst
case
thing
is
that
the
stuff
that's
currently
in
the
openshift
group?
The
worst
case
thing
is
that
the
stuff
that's
in
the
openshift
group
today
stays
there
and
we
just
have
new
stuff
in
the
in
the
in
the
okd,
cop
or
okd
community
or
whatever
the
tech.
We're
going
to
call
this,
because
the
the
real
problem
is
that,
because
everything's
all
jumbled
up,
it's
a
little
difficult
to
find
what
we're
looking
for
yeah.
D
The
the
reason
I
would
at
strongly
advocate
for
creating
a
separate
space
for
these
is
that
right
now,
everything
under
github,
slash,
open
shift
is,
is
really
the
ecosystem
of
the
openshift
product
itself.
Right,
it's
the
distribution
of
kubernetes,
it's
it's
o
it's!
What
okd
is
built
from
it's.
What
ocp
is
built
from
what
we're
talking
about
here
with
our
call
it
communities
of
practice,
call
it
communities,
you
know
what
whatever
we
name
it.
D
A
Yeah
but
there's
also
it's
confusing,
because
there
is
some
community
stuff
inside
of
the
openshift
repo.
So
I'm
I'm
wondering
if
maybe
we
just
create
a
a
github
repo
that
is
the
okd
cookbook
and
have
recipes
under
it.
To
start
with,
and
as
bruce
pointed
out,
communities
of
practice
is
an
internal
red
hat
thing
too.
So
I'm
thinking
okd
dash
cookbook
and
then
just
leave
it
at
that.
For
now
and.
D
H
A
Okay,
all
right
well,
you're
good
and
let's
let's
do
that
and
then
we
can
make
pull
requests
there
and
then
that's
what
we'll
link
to
in
the
in
the
okd.io
but
yeah
yep.
I
think
that'll
work
we'll
see,
but
let's
float
it
by.
I
don't
think
anyone's
gonna
get
offended
by
an
okd
cookbook
and
then
then
we
can
publish
it
as
an
actual
book
and
we
can
all
make
residuals
and
retire,
not
that
anybody
who
ever
created
a
python
cookbook
ever
has
gotten
to
retire.
A
So
don't
don't
bank
on
that
so
cool
all
right
is
there?
Are
there
other
things
to
do
here?
Yeah,
I
think
joseph
yeah,
that's
I'm
kind
of
leaning
towards
that.
But
let's,
let's,
let's
keep
scattering
on
the
on
the
group
mailing
list
here,
let's
get
the
first
one
done.
If
we
can
get
that
techton
one
done
sorrow
this
week
and
the
documentation
on
on
how
what
the
best
practice
is
for
linking
to
it
and
making
a
pull
request
we'll
make
that
we'll
start
making
that
happen.
A
B
Hey
everyone
this
is,
I
just
wanted
to
so.
Basically,
I'm
from
the
knight
community
team
in
reddit,
and
so
we
are
trying
to
find
solutions
to
easily
deploy
okd
on
all
platforms,
but
right
now
I'm
focusing
on
bay
battle
api.
So
there
are
plenty
of
options
but
like
we
wanted
to
go
with
upstream,
ideally,
metal
cube,
but
right
now
we
are
pursuing
dev
scripts.
B
Since
that
is
much
closer
to
ocp,
I
mean
like
open
shift,
and
so
basically
there
are
so
we
try
to
use
dev
scripts
change,
some
images
up
to
the
upstream
components
and
and
the
rest
of
it.
We
had
to
use
the
downstream
one
since
there
weren't
any
available
in
the
kitty
group.
So
I
mean
we
weren't
able
to
deploy
it,
but
we
did
achieve
some
success
so
right
now
there
is
no
issue
open.
B
You
know,
okay,
I
think
that
is
tracking
the
images
that
are
necessary
to
install
it
successfully
and
which
might
not
have
their
upstream
counterparts,
so
I'm
working
to
with
some
of
the
developers
and
community
members
to
make
that
possible.
If,
if
we
can
build
those
up
upstream
images
and
from
what
I
found
so
far,
it
looks
like
they
don't
require
that
much
work
because
they
didn't
have
the
any
dependency
or
like
complicated
those
kind
of
relations
that
would
require
us
to
do
significant
work
for
them.
B
At
least
some
of
them
seemed
like
just
some
using
some
scripts
and
we
could
simply
switch
the
image
from
rel
to
centos
or
any
other
upstream
base
image.
So
I
was
wondering
like
if
anyone
is
has
any
experience
with
something
similar
or
are
they
working
on
some
of
that
building
upstream
images
for
the
downstream
ones
which
are
not
available.
A
A
A
H
B
D
A
B
Yeah,
so
basically,
the
idea
was
to
have
some
easy
to
deploy
up
stream
solutions.
So,
as
a
first
step,
dev
skips
sounds
like
a
good
idea.
That's
an
upstream
project
and
since
it's
able
to
deploy
open
shift
without
like
it
like
with
a
bit
of
work,
we
should
be
able
to
use
it
for
okay
as
well.
But
the
major
issue
we
are
hitting
is
the
missing
upstream
images
and
which
is
why,
like
it's
failing
at
the
bootstrap
as
space?
B
B
I
don't
know
like
how
we
are
doing
that
in
okay,
but
but
many
of
those
had
the
upstream
images
available
in
metal,
cubes
repository
image
repository
so
that
so,
but
like
few
of
them
didn't
have
that
and
I
thought
like
if
we
can
build
those
and
so
and
another
reason
for
dev
scripts
using
dev
scripts
was
like
at
least
so.
First
of
all,
I
faced
issues
with
the
installer.
B
B
So
I
did
around
a
bit
here
and
there
and
finally,
like
went
with
building
a
news
like
installer
from
the
federal
course
branch
in
the
openshift
installer,
which
I
think
okd
uses.
And
so
at
least
I
was
able
to
eliminate
that
problem.
But
still
like
the
installation
is
not
going
to
100.
So
I've,
I'm
tracking,
that
in
a
document
and
I'll
see
if,
if
there
is
anything,
maybe
I'll
drop
a
mail
into
the
okay
working
group.
Regarding
the
update.
E
B
A
B
B
So
then
I
can
just
submit
a
pr
few
ps
and
that
that
would
be
a
good
option
to
have,
because
working
with
metal
cube
to
be
honest,
would
be
a
difficult
at
this
point,
at
least
because
even
with
vanilla
kubernetes,
I
had
issues,
especially
in
bare
metal.
They
did.
I
mean
like
bare
metal,
more
or
less
as
many
times
many
separate
issues
but
anyways.
So
I
thought
like
first,
let's
work
with
dev
scripts
and
then
we
can
think
on
further
steps.
D
B
B
A
A
A
That's
where
I
know
your
point
yeah,
I
knew
I
I'd
heard
your
name
before
and
talk
chatted,
okay,
cool
and
sorry
about
the
the
internet
connection.
It's
not
you!
It's
me
I'm
in
a
a
wonky
place
today,
so
my
internet's
not
great,
but
it
took
a
few
minutes
with
the
cni,
not
cma
and
michael.
I
I
don't
know,
look
at
that
acronym
perfect,
all
right!
So
that's
where
we're
at
today
is
there
anyone
else
hiding
on
this
call
with
a
secret
agenda
item.
G
E
I've
been
yeah
the
we
focus
on
operators,
but
the
the
the
various
you
know.
Images
and
templates
are
also
useful
and
I
was
playing
with
some
of
the
the
old
temples
operator
ones
that
I
saved
as
per
charlo's
suggestion
before
I
turned
off
the
samples
operator
and
they
there,
there
are
some
that
give
you
the
option
of
using
community
resources.
E
E
E
A
D
A
A
All
right,
you
only
get
back
five
minutes
of
your
day
and
I
put
the
registration
link
for
the
console
competition.
If
you
bruce,
because
I
know
you
have
students
and
they
would
love
hoodies,
so
take
a
look
at
that,
and
I
will
pdfi
is
the
slide
deck
that
explains
it
all
and
then
put
post
the
link
in
that
to
the
working
group
meeting
in
20
minutes
after
I
get
another
cup
of
coffee.
D
A
So
everybody,
wherever
you
are
stay
safe,
enjoy
and
we'll
see
you
on
the
working
group
mailing
list
and
or
on
in
kubernetes
and
slack
and
so
just
reach
out.
If
you
don't
hear
from
somebody
who
promised
you
something
which
usually
is
me
yeah,
the
slight,
you
won't
be
able
to
see
the
slides
bruce
until
I
get
permission
from
serena
who
built
the
slides
to
share
them.
So
that's
going
to
take
me
20
minutes
and
a
cup
of
coffee
and
a
few
bribes.
D
A
A
That
would
be
great
if
we
could
get.
You
know
a
number
of
people
from
okd
working
group,
and
maybe
your
class
or
whatever
doing
cool
customizations.
I
don't
know,
make
it
look
like
a
tick
tock
console
who
knows
we'll
see
all
right
folks
we
never
get
in
in
less
than
an
hour.
So
I
just
enjoy
talking
to
you
all
too
much,
and
I
talk
too
much.
A
So
thank
you.
We'll
see
you
in
two
weeks
or
sooner,
and
I
will
also
send
out
a
couple
of
notes
on
some
of
the
agenda
items
like
the
the
birds
of
a
feather
for
kubecon
and
when
that's
going
to
happen,
so
people
can,
if
you're,
going
to
kubecon
and
sign
up
for
that,
because
I
know
you
have
to
have
registered
for
kukan
to
get
into
that.
So.