►
From YouTube: kubeadm office hours 2019-09-19
A
A
A
Think
that
that
we
can
move
on
on
priorities,
dopamine
prepared
our
list
of
priorities,
I
just
I
just
did
a
really
small
changes
and
edition
and
group
up
to
them
in
three
groups.
One
is
carry
over
activities
that
we
are
activity,
data
that
we
are
somehow
already
doing,
and
we
want
to
complete
in
the
next
cycle.
The
other
is
new
activity
or
new
feature
that
we
want
to
that.
We
can.
A
We
might
have
consider
for
117
and
the
third
and
the
third
group
is
bedrock
activity
for
one
16
17,
which
is
basically
housekeeping
or
small
tasks
that
that
we
keep
going
time.
But
time
please
see
if
someone
has
some
say
video
or
something
that
wants
to
other
feel
free
to
add
in
one
of
this
group
or
at
the
bottom,
and
then
I
will
take
care
of
rearrange
things.
A
So
my
my
proposal
for
handling
planning
today
is
to
go
on
as
usual
to
to
go
on
ever
short
discussion
about.
Each
item,
try
to
assign
a
priority,
and,
and
at
the
end
we.
The
goal
of
this
group-
is
to
have
one
zero,
which
is
the
top
priority
for
next
cycle
and
the
only
real
thing
that
we
could
meet
as
a
group
to
achieve,
and
it
is
the
second
then
we
can
have
one
or
two
maximum
free
p1,
which
which
is.
A
A
Okay,
so,
let's
start
with
carrier
activity.
So
what
one
activity
that
started
one
or
two
cycles
ago
was
to
prepare
for
moving
Cooper
mean
out
of
three
and
a
lot
of
work
was
a
is
already
completed.
Some
some
work
is
still
ongoing,
but
the
rest'
still
has
something
to
do
in
order
to
to
comply
with
the
with
the
goal
that
we
agreed
with
sisig
architecture
that
is
to
move,
could
mean
out
of
three
during
the
one
in
eighteen
cycle
and
so
on.
A
There
are
some
major
topics
that
we
have
to
work:
to
get
done
for
being
able
to
move
cover
mineral
out
of
faith.
One
of
them
is
changing
our
could
mean
with
his
end
or
component
configure,
and
basically
because
a
component
configure
the
component
country
that
argue
that
we
are
using
our
import
for
kubernetes.
Today
we
are
using.
A
Ross
is
working
to
document
to
20
D
in
order
to
make
component
config
more
flexible,
especially
and
also
for
splitting
the
the
component
coffee
for
Cooper.
Let
the
management
of
the
component
come
from
kuba
later
to
the
manager
for
the
component
config
for
a
dog,
because,
basically
now
we
manage
only
the
Cooper
proxy
dawn
and
we
want
to
get
really
more
flexible
and
being
able
to
handle
potentially
any
of
the
configure.
B
A
A
A
Yes,
basically,
my
point
is
the
point
here
is
that
if
we
go
on,
if
we
don't
change
how
we
manage
with
the
component
configure,
it
will
be
difficult
for
cubed
mean
to
end
all
Adhan
that
are
different
from
the
Cooper
block.
A
A
E
A
A
C
A
A
A
I
I
would
like
to
get
it
out
of
the
way
so
to
to
really
take
some
time,
make
an
analysis
of
what
we
are
missing
and
possibly
completed
their
work,
so
I
would
like
to
where
they
eat,
doesn't
as
a
P,
1
or
P
1.5
or
P
2,
because
not
all
the
work
is
easy
now
and
we
need
some
help
from
the
C
windows
people
so
I
cannot
commit
the
team
because
it
is
not.
We
are
not
owners
of
this
full
work.
I.
B
F
E
F
A
C
G
A
C
A
A
A
C
B
B
A
A
A
H
A
A
A
We
have
a
trade
auto
who
trade
off
here
to
to
consider.
We
don't
want
to
change
the
configuration
to
frequent.
This
is
a
part
of
the
beta
contract.
From
the
other
side
we
are,
we
are
starting
to
see
a
list
of
item
or
possible
change
to
the
configure
that
that
are,
that
is
starting
to
get
a
consistent.
I
A
Cluster
API
booster
provider
could
mean
that
is
embedding
our
configure
into
the
iPhone
config,
because
we
discovered
that
the
coupon
being
configuration.
This
scenario
does
not
behave
properly,
because
in
some
cases
it
requires
the
user
to
specify
the
fault
followers
or
when
it
is
arraigned
error
that
it
renders
empty
default
pathways.
Even
if
the
devices
is
not,
the
fault
is
not
empty.
A
When
this
waveless
is
basically
are
basically
due
to
how
open
api
behaves
and
how
the
kebab
is,
there
assumes
that
that
they
immediately
and
optional
settings
have
to
be
configured,
and
I
think
that
is
important.
It
is
important
to
get
a
decent
result,
because
cluster
api
is
what
is
becoming
is
quickly
becoming
one
of
the
biggest
consumer
of,
but
me
so
I
want
to
be
sure
that
that
that
we
are
providing,
we
are
addressing
all
the
needs
or
all
the
concern
the
arise
from
from
this
other
project
of
Cisco
start.
This
is
one
point.
A
The
other
point
is
to
make
the
cupboard
mean
config
more
customized
friendly,
and
this
will
be
addressed
by
adding
object
meta
to
all
the
top
level
of
objects,
so
customer,
because
this
is
required
by
estimize
and
it
is
becoming
a
common
use
case
to
apply
customize
click
open
in
configure.
It
is
done
by
some
cluster
API
provider.
It
is
done
by
kind
and
all
of
them
ever
to
change
the
config,
adding
up
to
the
meter.
A
moving
object,
meta
before
passing.
Talk
about
me.
A
Requires
that
seed
or
a
dress
like
the
advertiser
address
and
my
became
basically
changed
from
one
value,
a
to
a
list
of
values.
Now
we
are
ending
this,
allowing
using
user
to
express
comma
separated
value
a
into
the
Sidra
or
into
the
advertiser
dress.
But
this
is
not
not
nice,
and
probably
we
should
compare
the
type
of
these
fields
to
string
from
string
to
list
of
strings.
A
A
A
I
also
write
at
this
point,
even
if
I
this
amanti
for
a
door
configuration.
This
is
a
longer
problem,
a
long-standing
problem
for
company,
because
we
are
letting
the
forest.
Instead,
we
are
giving
the
user
the
chance
Express
setting
for
kuba
proxy,
but
we
are
not
giving
the
user
a
similar
way
to
set
prax
settings
for
cor
DNS,
for
instance,
and
so
we
don't
have
a
consistent
semantics
for
letting
the
user
to
set
add-ons
configurations.
A
A
B
So
I
think
that
we
can
actually
try
and
go
for
bath
free
apart
from
this
list.
I
also
have
one
item
that
actually
came
up
to
me
yesterday,
which
is
basically
allowing
the
API
server
authorization
modes
to
be
specified
as
an
array
inside
of
the
cluster
configuration.
So
currently
we
have
a
weird
scheme
of
using
the
X
ARC's
to
extract
the
current
user.
Specifics
then
default
them
and
then
place
them
back
into
extracts,
and
this
a
little
bit
weird.
A
C
E
B
A
A
Think
that
we
can
move
to
the
next
one,
which
is
made
on
more
flexible.
We
already
talked
about
some
point
which
overlap
with
these
and
same
at
macro.
Tema
I
I
think
that
this
macro
team
team
up
at
the
end,
both
boys,
kappa
two
things.
One
is
maked.
On
customize,
the
body
in
cubed
mean
configure
I
left
this
phrases
from
Lumiere.
A
A
A
The
second
part,
is,
is
behind
the
scene,
so
assuming
that
the
user
is
passing,
he
can
choose,
he,
that
is
a
dawn,
is
behind
the
scene.
If
we
wanted
to
start
and
to
work,
to
get
kuba
demean
using
the
Adonis
toddler
might
be
as
a
alpha
feature
of
feature.
Gated
some
official
gated
start
using
the
Advanced
tab.
A
H
Agree
with
that
also
generic
question
realizing
is
so
anything
adding
this
to
the
API.
The
list
of
patterns
that
are
going
to
be
applied
is
kind
of
you
know
is
not
directly
tied
to
what
we
expose
on
qad
hem
different
faces,
because
I
wouldn't
like
to
see
different
faces
in
the
CLI
one
for
Cody,
innocent
or
poor
kid
person,
for
example,
I
would
prefer
to
see
just
one
upgrade.
H
A
My
opinion
is
that
more
flexibility
around
that
Dawn's,
he
is
something
that
the
user
battery
was
and
is
something
that
we
need,
and
it
is,
let
me
say,
or
chthonic,
orthogonal
to
the
change
for
the
to
the
configure
to
the
change
for
the
component
config.
So
it
is
a
topic
while,
where
I
would
like
to
clarify
all
the
pending
points,
because
there
are
from
the
coop
and
main
point
of
a
point
of
view,
there
are
still
many
pending
points
to.
A
I'm
kind
of
torn
I
I
would
like
to
push
this
work,
but
I
don't
feel
without
a
care
that
that
tries
to
figure
out
that
at
least
our
roadmap
to
get
there
or
whatever
is
a
priority.
What
is
included
in
in
our
for
what
we
follow
up?
I,
don't
know
if
it
is
filter
gate.
It
is
find
your
support,
I
rapid
environment
in
alpha
in
the
first
oralism,
but
that
is,
we
have
to
go
to
state
that
we
are
going
to
support.
I
got
an
environment
Sunday,
so.
A
D
A
I
put
the
priority
for
the
cap
a
little
bit
higher,
because
it's
the
first
thing
that
that
it
seemed
important
for
this
group
is
to
understand
to
better
understand
the
direction
of
this
okay.
We
have
10
min
left,
so
quick,
quick
overview
of
backlog
in
backlog.
We
have
a
cooper,
demeanor
upgrade
apply
phases
nice
to
have
a,
but
the
main
reason
for
for
working
this
is
to
skip
koppa
proxy
and
I
think
that
we
are
going
to
get
skip
Cooper
proxy
by
other
way,
so
I.