►
From YouTube: K8s SIG Docs Meeting 20191029
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
A
A
Oh
that
chip,
awesome
thanks,
Zach
and
welcome,
welcome
everybody
glad
to
see
some
new
faces
here:
I'm
Jim
angel
nice
to
meet
you
and
so
moving
on
our
this
week's
PR
Wrangler
is
Brad,
so
cool
stepping
in
for
Andrew
Chen,
who
is
absent,
Thank
You
bread
for
for
taking
on
that
responsibility.
I
know
you're
pulling
a
double
duty.
So
much
appreciate
it.
Oh,
what's
that.
A
A
A
E
A
Throw
some
things
from
last
week
that
I
heard
about
from
the
asia-pacific
meeting
and
just
wanted
to
get
a
quick
status
update
on
some
of
them
for
this.
This
meeting
as
well
so
I,
know.
Last
week,
Zac
you
talked
about
doxy.
Do
you
want
to
give
a
quick
refresher
over
that
I
see,
there's
no
updates,
but
just
a
quick
sink
sure.
D
D
I'll
ask
them
to
start
doing
the
work,
and
hopefully
we'll
have
some
test
sites
that
we
can
use
for.
Group
testing
and
the
gold
on
all
of
this
is
I
would
really
love
to
have
this
done
before
Christmas
and
have
it
all
done
by
the
end
of
the
year,
and
if
we
can
align
it
nicely,
it
might
be
possible
to
have
sites
available
and
testing
to
like
find
in
fixed
bugs
for
the
contributor
day
at
a
coupon,
North
America.
A
Be
great
to
do
a
little
sprint
on
this.
If
we
get
some
progress
for
North
America,
but
I
just
saw
the
reminder
saying
it
was
20
days
away,
I
think
it's
yesterday
or
the
day
before
it
kind
of
scared
me
I,
still
think
cube,
Kaunas
ways
away,
but
I
think
it's
gonna
come
quicker
than
we
all
know
so.
Moving
on
Brad,
last
week
you
talked
about
a
potentially
Java
Java
micro
services
tutorial
on
catty
coda.
Is
there
something
that
you'd
be
willing
to
present
today
or
I?
Don't
want
to
catch?
You
yeah.
A
C
B
So
I
have
two
things
to
show:
can
you
guys
see
my
screen?
Yep,
okay.
I
have
two
things
to
show.
First,
one
is
the
actual
cat,
a
coda
tutorial.
The
second
one
is
the
landing
page.
How
all
the
other
tutorials
have
a
landing
page
from
which
the
users
gets
some
background,
knowledge
and
jump
into
the
actual
tutorial
from
unless
you
guys
feel
otherwise.
I'll
actually
start
with
the
tutorial
as
I
do
think.
B
B
B
B
We
do
well
just
to
make
sure
the
user
are
up
and
they
are
so.
We
can
grab
the
IP
and
okay.
So
we
make
two
invitations
via
curl
note
that
we
are
passing
in
the
user
and
password
as
part
of
the
command
first,
one
to
the
system
properties
and
then
the
second
one
to
the
system
service,
just
to
show
that
these
two
services
are
up
and
what
they're
returning
and
then
here
is
the
last
call
to
the
system
properties
service,
and
it
shows
that
the
X
app
name
is
returning
system.
B
So
this
is
kind
of
the
start
of
of
the
micro
service,
as
is
what
you
have
and
then
the
rest
of
the
tutorial
builds
on
it
so
step
three.
This
is
where
it
goes
through
and
actually
modifies
the
Java
code.
So
we
ask
the
user
to
add
the
CDI
request
to
or
to
inject
a
CDI
the
app
name
that
we
saw
in
the
previous
step
so
that
it
will
be
configurable.
B
The
next
step
does
something
very
similar,
but
instead
of
the
proper
random
property.
In
this
case,
it
is
that
user
and
password
that
we
saw
previously,
which
is
hard-coded
currently
right
here,
and
instead
we
are
going
to
again
use
micro
profile
config
to
inject
those
properties.
This
time
from
kubernetes
secrets.
B
So
next
we
go
over
actual
config
map
and
kubernetes
secrets,
so
we
set
up
a
config
map
for
that
system,
app
name
property,
to
change
it
to
my
system
and
or
not
change
it,
but
to
set
it
to
my
system.
And
then
we
set
up
a
secret
and
we
specified
the
user
name,
Bob
password
Bob
PWD.
That
was
previously
hard-coded
in
the
actual
code
instead
now
be
set
in
the
secret,
and
we
explain
you
know
kind
of
give
it
a
little
bit
of
a
background
about
what
config
maps
are.
B
And
then
we
update
the
Yama
file
to
now
actually
retrieve
the
config
map
and
secrets
or
the
properties
that
we
said
in
the
previous
steps,
so
that
micro
profile
config
can
then
pick
them
up
in
the
Java
code
and
use
them
and
leverage
them.
So
we've
updated
it
and,
as
we
can
see,
we
have
app
name
coming
from
the
config
map
that
we
set
on
retrieving
the
key
name
and
then
similarly
a
same
thing
for
secret
for
password
and
username.
B
C
B
B
B
I,
don't
know
why
my
okay.
C
B
B
Is
just
the
the
home
page
with
microscope?
As
you
can
see,
many
different
companies
support
the
standard.
Think
of
it
as
a
as
the
Java
EE
spec,
which
is
now
the
Jakarta
EE
spec
since
eclipse
has
taken
it
over,
but
with
a
hyper
focus
on
micro
services
and
cloud
native
and
rapid
iterative
development.
C
And
again,
the
goal
here
is
to
try
and
increase
increase
the
the
ecosystem
of
kubernetes
by
providing
tutorials
that
will
hopefully
accelerate
getting
a
large
number
of
Java
and
j2ee
programmers
that
are
out
there
able
to
bridge
from
their
world
to
then
understanding
the
micro
services
to
then
seeing
how
it
all
rent
runs
and
end
on
kubernetes.
So
you
know
Jim
and
Zach.
C
That
was
really
the
goal
of
the
work
and
then
obviously
you
know
we
wanted
to
deliver
the
tutorial
exactly
like
all
the
other
tutorials
so
built
on
pata,
Kona,
nice,
easy
steps
per
stage
and
and
I
you
know,
would
love
to
have
feedback
on,
because
you
know
I
think
you
know
we
gave
the
team
an
ambitious
goal
of
being
able
to
to
go
after
that
that
ecosystem,
the
Java
programmer
ecosystem
and
help
bring
them
into
our
cloud
native
world
and
I
think
they
did
a
pretty
good
job.
I
was
really
impressed.
C
B
A
B
C
E
Yes,
yep
yeah,
it
might
be
helpful
for
most
coming
from
Lecce
suzuki
when
it
is
not
familiar
with
kubernetes
walk,
show
them
how
to
see
TV.
Ladies
basketball,
maybe
you
could
have
do
the
curl
copy
in
the
URL.
I
was
getting
restless
I
get
paid,
but
sometimes,
if
you
can
go
to
the
browser
for
the
Java
components,
it
can
give
a
visual
to
the
to
the
developers
of
what's
happening
on
the
coop
Adobe
side.
C
B
Yeah
we
could
try
to
do
that.
I
think
the
main
concern
there
is
that
we're
already
having
cut
a
quota,
three
different,
unique
views
being
shown
so
throwing
a
fourth
one
in
there
to
display
the
browser
might
be
well,
hopefully
not
overwhelming
to
the
user
without
be.
My
only
concern
is
to
is
to
not
provide
too
many
windows
to
the
user,
but
I
do
like
the
idea
of
providing
something
more
visual
than
command
line.
C
And
along
those
lines
you
know
Zack
and
Jim.
The
thought
is,
you
know,
is
this
something
where
we
could
put
it
in
a
certain
where
we
could
start
formal
reviews
where
people
can
start
reviewing
it
and-
and
you
know
again,
we
think
it's.
We
think
it's
appropriate
to
be
added
as
another
tutorial
to
the
list.
Tutorials
we
have
you
know.
Obviously
this
is
not
vendor
specific.
This
is
meant,
for
you
know
getting
an
open-source
community
to
embrace
kubernetes
and
we're
hoping
you
know
the
that's
what
came
across
right.
Then.
C
D
D
I
think
an
issue
would
be
more
for
the
like.
Does
this
for
long
and
I
I
think
that's
pretty
straightforward,
so
I
think
really.
The
discussion
at
this
point
is
more
about.
How
would
what
would
this
actually
look
like
in
implementation?
Where
would
the
code
for
this
catechu
de
tutorial
live
I
mean?
Obviously
we
can
like
structure
it's
similar
to
how
tutorials
living
function
in
the
documentation
now,
but
can
you
say
more
about
where
you
imagine
the
tutorial
for
this
tutorial
living.
B
D
E
D
D
D
Not
sure
and
that's
the
discussion
that
would
need
to
come
up.
Okay,
regardless
of
the
the
it
looks
like
a
high-quality
tutorial,
but
that's
a
it
raises
a
larger
question
about
what
do
we
want
our
own
best
practices
of
our
tutorial
to
tutorial
content
to
look
like,
and
this
would
be
the
first
time
we've
discussed
it.
So
I
can
guarantee
lively,
but
not
necessarily
like
lightning-fast
consensus
on
it.
C
B
C
And
the
beauty
of
is
worth
flexible
right.
If
it
makes
sense
one
place,
I
don't
think
McCall
cares
if
it
makes
sense
another
place.
I,
don't
think
we
care
at
all
in
the
call.
We
just
want
to
do
what
makes
sense
and
it's
you
know
it
was
kind
of
that
first
of
a
kind
to
go
pioneer
and
do
another
tutorial,
I
guess
different
from
the
other
ones.
C
So
hopefully
these
are
all
good
questions.
I
know
they're,
tough
questions
and
stuff,
but
hopefully
they're
the
kind
of
know.
We
always
talked
about
wanting
to
increase
the
amount
of
content
and
the
Docs
that
you
know
will
will
get
different
areas
excited.
So
hopefully
these
are
all
good
questions,
not
like.
Oh
now.
What
do
we
do
right?
C
D
It
is
the
are
good
questions.
It's
it's
timely
and
so,
and
I
recall
I'm,
trying
to
offer
a
lot
of
transparency
about
why
we
seem
maybe
maybe
hesitant,
as
opposed
to
outright
enthusiastic,
which
I
think
it's
a
your
tutorial
deserves
enthusiasm.
It's
really
cool,
but
the
the
mixed
reaction,
you're
getting
is
is
not
from
any
not
from
any
hesitation
about
the
tutorial
per
se
and
more
about
the
oh
well,
this
this
will
be
new
for
us
yeah.
C
E
One
of
those
one
of
the
dangers
is
I
mean
we've
all
been
with
these
open-source
projects
that
look
really
cool
and
you
go
dive
in
on
the
tutorials
and
the
links
are
broken
because
that
open
source
project
points
to
a
place
that
used
to
be
awesome
and
hot
and
have
great
tutorials
and
then
over
time
it
fades
away.
So
not
posting
it
on
Cooper,
neza
IO,
you
know,
might
lead
to
some
of
those
same
issues,
things
getting
old
if
it's
just
not
not
posted
by
okay
I!
Oh
that's
my.
D
B
Will
say,
speaking
about
more,
we
actually
do
have
another
at
least
one,
that
we
are
actively
working
on.
We
just
kind
of
wanted
to
go
one
at
a
time.
Presenters
get
feedback,
see
how
it
might
get
it
on
the
site
and
then
it'll
be
that
much
easier
for
us
to
make
sure
we
don't.
We
do
all
the
right
things
for
the
second
one
and
the
second
one
is
using
micro
profile
health
to
do,
readiness
and
liveness
configuration
with
kubernetes,
and
it
was
actually
supposed
to
be
our
original
tutorial
that
we
were
going
to
bring
forward.
B
C
We
probably
want
to
have
discussions
with
Ben
and
get
his
input
right
and
see
what
he
thinks
is
best
I
mean
I
have
no
idea
what
he'll
say
if
he'll
say
oh,
this
should
just
be
with
all
the
other
ones.
Everyone
cool
with
that
or
maybe
he'll
say
something
different
I
have
no
idea,
but
but
but
Zack
and
Gemma.
You
think
we
should
just
bring
him
in
and
try
and
get
his
advice
on
what
to
do
or
yes,.
D
C
Yeah,
no
definitely
public
and
definitely
with
all
the
stakeholders
out
there.
So
you
know
I
just
want
to
thank
McCall
and
his
team.
They
worked
a
long
time
on
this
and
I
think
it.
It
puts
us
in
any
place
of
having
you
know
some
tough
but
kind
of
cool
questions
to
go
answer
right.
It
shows
the
vitality
of
Kubb
Docs
and
you
know
I,
don't
know
if
people
saw
it.
C
Documentation
got
a
really
big
thumbs
up
at
the
European
open
source
summit
with
the
Google
keynote
speaker
talking
about
how
the
best
projects
that
really
do
well
in
open
source
are
the
ones
that
have
the
best
Doc's.
So
we
should
all
feel
pretty
proud
about
that.
It's
kind
of
a
good
day
all
around
awesome.
D
A
A
D
D
Their
initial
content
localized
at
the
language
labels,
get
started
with
teams
and
members,
so
they've
passed
all
the
hurdles
and
they're
not
actively
working
so
another.
We
have
another
localization
active
now
in
Vietnamese
and
I.
Think
we're
getting
very
close
with
Russian
I
need
to
double
check
that
their
K
org
PR
s
and
K
community
of
PRS
are
in
order,
but
I
I
think
I
recall
seeing
their
Russian
label
PR
in
k
test
intra
go
through,
so
we
are
very
close
with
a
Russian
content.
Pr
as
well.
D
I
also
wanted
to
circus
visibility
that
there
seems
to
be
like
an
initial
push
for
Arabic
I
haven't
seen
like
any
of
the
work
in
any
of
the
repositories
go
through,
but
there
is
now
an
official
channel
on
slack
for
that
team
to
coordinate.
So
it
looks
like
Arabic
content,
maybe
at
the
very
start
of
the
pipeline.
So
I
just
wanted
to
raise
visibility
that
we've
got
more
in
localizations
coming.
A
D
A
No,
that's
awesome.
Thank
you.
So,
moving
on
to
the
process
section
of
the
agenda,
this
is
just
gonna.
Carry
over
from
some
of
the
discussions
in
slack
and
from
the
last
meeting
is
finalizing
the
quarter
quarterly
meeting
date,
so
the
proposed
date
was
Thursday
November,
14th,
5:00
to
9:00,
Pacific
I,
know.
There's
some
feedback.
I
mean
it's
gonna,
be
hard
to
find
time
for
everyone
to
meet
where
it
makes
sense
for
everybody.
I,
don't
know
how
we
come
to
consensus
on
this.
D
D
D
D
We
we've
met
on
Thursday
evenings
in
the
past.
This
timeslot
seems
to
work
well,
I,
don't
want
to
wait
any
longer
than
November
14th.
So
there's
the
14th
doesn't
work.
The
option
is
really
to
go
earlier
because
after
that
is
Coupland,
North
America,
followed
by
US
Thanksgiving
and
then
we're
into
December
and
there's
no
point
so.
C
D
Meet
on
the
14th
of
November,
like
enthusiastic
agreement,
is
not
my
goal.
Anybody
who's
like
violently
opposed
or
just
like.
No,
we
absolutely
should
not
meet
on
that
there's
on
the
November
14th
and
here's
the
reason.
Why
is
there?
Anybody
who
like
has
a
really
strong
objection
to
that
particular
date.
A
You
see
cool
yeah
thanks
for
that,
thanks
for
the
context
on
on
the
discussion
too,
and
look
forward
to
the
meeting
so
the
next
time.
The
agenda
is
the
third
party
kind
of
kept
that
we
had
created.
So
this
is
the
captain.
Banister
SF
Tim
helped
create
alongside
a
lot
of
us
here
from
cig
docks
about.
D
So
I
think
I
think
that's
a
really
accurate
description,
Jim
that
this
calf
is
treading
water,
so
I
think
the
inertia
that
we're
specifically
fighting
against
is
that
this
is
a
really
easy
cat
to
bike
shed
and
it's
a
really
easy
cap
for
folks
to
have
strong
opinions
against,
but
not
for
so
like
it's
really
easy
to
say.
Well,
this
is
here's
the
thing
that
we'd
like
to
do.
Here's
our
specific
proposal
with
details
about
how
to
vet
accept
or
decline
third-party
content.
D
D
D
D
That's
not
going
to
get
us
to
where
we
can
accurately
reliably
tell
vendors,
know
and
accurately
reliably
tell
future
developers
what
criteria
they
need
to
meet
in
order
to
include
third-party
content,
so
yeah
just
providing
providing
a
really
clear
lazy
path
forward
and
providing
clear
expectations
about
how
to
how
to
bound
feedback
by
time,
if
nothing
else.
So.
Thank
you.
Thank
you
for
letting
me
talk
that
out.
E
Yeah
I
was
just
saying:
maybe
if
there
was
time
spent
on
designing
a
framework
for
vetting
third-party
content
and
a
lot
of
the
effort
won
into
the
methodology
for
how
something
is
is
approved
by
a
third-party
content
provider
that
would
yield
dividends
because
it
could
it
would
the
the
the
way
that
that
things
are
vetted
could
make
decisions
for
the
group,
as
opposed
to
it
being
like
a
snowflake
process
of
evaluating
every
I.
Think
you
said
bike
shedding.
E
D
D
C
I
have
to
apologize
because
I
was
doing
wrangling.
I
did
not
read
the
latest
version
for
the
getting
started
section.
Are
we
putting
a
stake
in
the
ground?
That
was
the
one
section
I
thought
you'll
get
tremendous
pushback
on.
If
you
try
and
pull
out
the
content
that
shows
how
the
different
distros
say
to
get
started.
Did
we
pull
that
out
of
this,
because
I
think
having
that
in
there
I
think
you're
gonna
hit
so
much
headwind?
It's
gonna
be
a
problem.
C
I
think
that
the
stronger
arguments
where
the
the
pages,
where
there's
some
weird
third-party
content,
that
you
seem
really
out
of
place
so
I,
don't
know
if
you
want
to
make
a
a
statement
like
well,
there
are
certain
safe
spaces
in
the
document
that
third-party
content
is
appropriate.
If
it
follows
certain
guidelines
and
then
there
are
certain
places
where
it's,
it
really
doesn't
seem
appropriate.
As
far
as
we
can
tell
I,
just
wasn't
sure
Jim,
you
know
what
stake
you
made
in
the
ground
regarding
the
third-party
content
for
getting
started.
A
Yes,
I
think
on
the
last
time
that
I
looked
at
the
cap
and
I
haven't
reviewed
it
in
the
past
couple
days.
It
seemed
like
there
wasn't
really
Stakes
being
put
in
the
ground
at
this
point.
There's
a
lot
of
examples
and
proposals
of
what
we're
seeing
and
what
we'd
like
to
do
to
move
forward
and
I.
Think
that
might
in
turn,
result
in
some
of
this
treading
water.
Is
there
it?
It
is
very
ripe
for
opinions
right
now,
I
believe
right.
C
Because
we
might
want
to
be
very
crisp
because
if
you
hit
somebody
who
has
that
impression
that
they
may
misinterpret
this
or
they
read
it
and
they
think
oh,
these
people
are
trying
to
throw
out
the
third
party
content.
No
way,
that's
never
gonna
happen.
You
might
be
able
to
have
a
one-line
statement.
That
says
you
know:
hey
we're
not
trying
to
change
these
sections
of
the
docs,
so
so,
hopefully
that
that
keeps
a
whole
bunch
of
folks
at
bay
and
not
wanting
to
rip
this
apart
necessarily.
D
D
C
You
get
any
feel
Zack
about
whether
they
would
appreciate
it
and
in
smaller
chunks,
like
smaller
cups,
or
did
then
give
you
the
impression
they
want
this
all
on
one
big
cap,
because
when
it's
all
in
one
big
cap,
I
worry
about
the
bike
shedding
and
and
all
that
that
can
occur.
If
there
were
certain
ways
that
we
had
three
smaller
caps,
where
we
said,
hey
I,
don't
know
just
thinking
out
loud
I,
don't
know.
If
that
would
help
or
not
I
didn't
know.
If
you
got
a
feeling
are
kinda
from
the
folks.
D
Right
now,
I
mean
we
so
I
pushed
for
us
to
have
the
same
to
have
this
car.
This
cap
be
the
same
conversation
about
third-party
content
and
dual
source
content
and
right
now
those
discussions
are
blending
in
ways
that
are
not
helpful
or
productive,
so
that
may
be
worth
while
that
may
be
worth
separating
out,
but
I
think
that's
a
really
good
specific
question
to
ask
in
the
cap
itself
about
how
to
drive
forward,
and
thankfully
Tim's
feedback
is
given
the
the
segue
for
that
question
to
be
timely,
inappropriate
so.