►
From YouTube: kubeadm office hours 2020-03-04
A
B
I
have
a
couple
of
organizational
cases
before
we
move
to
be
actual
technical
ones.
So
kick
on.
You
is
postponed
for
some
time
in
July
or
August
due
to
coronavirus,
and
there
is
a
link
to
the
unit's
foundation
page
for
this.
So
we
don't
know
yet,
what's
going
to
happen
to
the
cube
ATM,
the
dive
talks
or
whether
we
actually
are
going
to
attend
at
all-
and
this
is
probably
and
whether
this
is
going
to
happen.
B
So
we
should
probably
stay
tuned
to
doing
foundation
and
since
F
on
that-
and
my
next
PSA
is
that
next
week
u.s.
enters
daylight
saving
time,
and
this
is
probably
going
to
cause
some
changes
to
the
local
times
of
this
meeting
in
particular,
and
probably
the
rest
of
the
upstream
meetings.
So
better
check
was
starting.
Our.
A
Just
her
comment
about
Kip
call:
I
cancelled
my
hotel
and
flight
registrations,
but
I
didn't
cancel
my
conference.
Registration
and
I
suggest
that
everybody
does
the
same
once
the
dates
are
clear:
I
guess
we
can
book
flights
and
hotel
again.
If
you
know
if
there
is
going
to
be
a
conference
in
August
or
July.
C
A
C
B
The
ring
there
contains
actually
the
postponement.
It
is
Q
contra
high,
that
is
going
to
be
actually
canceled
keep
calm.
You
is
only
being
postponed,
but
that's
at
least
in
news.
For
now
there
is
also
every
chance
that
is
going
to
get
canceled
as
well,
depending
on
the
chrome,
/
virus
situation,
so
for
now
I.
Don't
think
that
anybody
actually
has
some
answers.
So
we
should
probably
just
stay
tuned
to
Twinings
foundation
and
CSF
pages
and
their
Twitter
accounts
and
see
how
this
actually
developed.
C
B
This
meeting
is
I
think
scheduled
on
some
of
the
US
yeah
I.
Think
it's
probably
you
according
to
US
Pacific
time,
and
this
basically
pins
it
to
this
specific
US
time.
So
for
the
u.s.,
it's
always
9
a.m.
Pacific
time,
but
for
the
rest
of
the
world,
which
shifts
differently
according
to
daylight
savings
time,
it's
going
to
be
slightly
different,
so,
for
example,
for
the
EU.
This
meeting
is
going
to
start
an
hour
earlier
than
usual
for
the
next
three
weeks.
Okay,.
A
Maybe
later
we
can
have
a
look
at
some
of
the
pending
PR
that
we
have
another
PC
is
that
this
is
a
major
change
that
is
being
done
by
the
working
group.
Kids
infra
is
that
G
cRIO
Google
containers
is
now
going
to
be
deprecated
in
favor
of
a
different
juicier
bucket.
So
the
recommendation
is
to
use
case
that
io
GC
GC
r,
o
da
yo.
A
Basically
this
is
a
DNS
redirect
that
is
going
to
point
to
the
new
pocket.
Once
it's
up
and
more
details,
you
can
find
here
so
me
and
sadyk
huy
already
updated
talked
you
medium
related
usages
of
google
containers.
So
we
are
clear,
but
just
want
to
point
out.
If
potential
users
of
cube
ADM
are
pinning
to
this,
they
should
adopt
I
have.
D
D
A
D
D
A
A
Its
website
change
is
a
URL
change,
so
basically,
everyone
who
downloads
from
this
particular
URL
mm-hmm
might
not
be
able
to
download
anymore,
because
new
kubernetes
image
releases
are
going
to
be
added
to
a
new
GCR
bucket.
Basically,
this
URL
for
some
images
might
be
coming
valid
at
some
point
in
time.
The
recommendation
is
to
start
using
this.
C
A
A
A
Basically,
they're
changing
the
the
spec
of
the
CSR
objects
to
include
a
signer
name.
What
is
happening
here
is
that
what
is
breaking
cube
ATM
here
is
that
the
cube
controller
manager
is
no
longer
going
to
be
able
to
sign
arbitrary
certificates
for
those
that
don't
know.
For
those
that
know,
we
have
this
command
that
can
be
used
with
a
flag
that
is
use
API.
A
C
F
C
A
A
F
A
If
the
point
is
that
is
still
going
to
continue
working
in
118,
it's
going
to
stop
work
in
119
when
the
supposedly
the
certificate
sepia
is
going
to
be
V
1.
But
your
previous
comment,
like
all
the
API
servers,
are
going
to
ignore
the
existence
of
a
field
that
isn't
known.
So
the
old
equation
is
going
to
ignore
this
field,
the
CSRs,
and
so,
if
cube,
a
DM
is
119
and
the
control
plane
is
118.
A
A
A
D
A
Now
this
change
is
going
to
prevent
that
cube.
Adium
supports
this
feature.
I
have
a
plan
already.
What
I'm
supposed
to
do?
The
idea
is
simply
to
fire
up
here
say
saying
that
in
the
future
release
we
are
not
going
to
basically
support
the
control
manager,
as
the
only
signer
for
certificates
that
are
basically
generated
using
CSR
users
may
have
to
use
external
signers
for
those
50
funds.
I
think.
D
A
E
A
A
D
A
A
F
A
D
A
We
are
trying
to
keep
a
command
that
is
aromatic
to
the
installation
that
qadian
has
by
default,
and
this
includes
the
controller
manager
which
can
be
leveraged
for
signing
certificates.
Any
external,
tooling,
is
our
scope
of
the
command,
but
you
can
still
use
the
external
side
are
here,
but
the
I,
don't
like
the
fragmentation
between
some
certificates
being
side
by
the
side
by
the
kiss
control
manager
and
something
side
by
side
by
this
external
cider,
I.
Think.
A
A
A
Basically,
the
idea
here
is
to
use
github
actions
and
then
based
on
the
actions
I
implemented
different
workforce,
like
some
of
them,
are
doing
synchronization
between
tags
and
branches
from
KK
I'm
not
going
to
give
a
full
demo
here
today,
but
I
just
wanted
to
say
that
I'm
having
pretty
good
progress
overall,
so
the
synchronization
of
branches
and
tax
works.
Fine
I'm
also
experiment
with
create
release.
A
So
this
is
not
exactly
something
that
I
wanted
to
do
in
terms
of
like
releasing
qadian
from
this
repository,
but
a
most-most
plane
with
the
concept
of
having
release
notes
attached
to
a
certain
tag.
So
if
you
go
to,
for
instance,
the
list
of
tags,
if
these
are
proper,
github
releases,
you're
going
to
see
the
release
notes
folded
in
here.
A
A
D
A
A
Yeah,
so
I
just
wanted
to
give
this
as
a
heads
up
at
some
point,
I'm
going
to
give
a
demo
showing
what
some
of
this
stuff
is
actually
doing
and
also
get
feedback.
If
you
want
to
maintain
this
I
have
a
bit
of
a
problem
with
directly
moving
this
code
to
seek
release
and
I
already
discussed
this
with
Tim
pepper,
because
so
currently
they
have
similar
tools.
For
instance,
if
I
go
in
my
CMD
here,
I
have
rip
rip
ofa's
forward.
A
A
A
B
A
I'm
definitely
going
to
give
a
demo
in
front
of
City
release
at
some
point
of
these
ups
and
we
can
think
about
like
get
their
feedback.
That
way
should
be
much
this
after
you
know,
Cabana
moves
out.
Do
you
do
they
want
this
cold
as
the
generic
code
for
any
component
that
moves
into
a
separate
repo,
I'm,
not
sure
so
we
have
to.
We
have
to
discuss
it
with
them.
A
G
A
So
we
have
good
for
discussions
in
terms
of
how
to
properly
release
key
by
diem
after
it
moves
out,
and
this
obviously
related
to
the
topic
of
building
comedian
first
and
it's
not
clear.
Yet
how
are
we
going
to
build
eBay
diem,
but
yes
to
the
release
process?
Question
sick
release
still
want
to
own
the
release
of
comedian
and
they
want
to
release
it
as
part
of
the
artifacts
for
each
release.
A
The
tool
in
itself
in
here
I
still
don't
have
an
answer
if
they
want
to
own
it,
because
it's
like
this
tooling
for
projects
that
want
to
fold
the
kubernetes
release,
release
tagging
in
branching
but
be
part
of
the
Kuwaitis
releases
as
artifacts
you
can.
Oh
don't
want
to
do
that.
They
just
want
to
be
part
of
the
release,
but
they're
going
to
follow
a
separate
version
so,
like
so
like
these
tools
do
not
mother
to
them.
Maybe
they
have
interests
in
this
particular
one
which
is
leveraging
the
release,
notes
functionality.
B
So
the
finger
talk,
we
should
probably
also
involve
into
this
conversation.
Six
CLI
and
the
coop
cut
all
folks
in
particulars,
simply
because
I
think
that
they're,
probably
the
next
ones
that
would
have
to
come
up
with
similar
solution
so
selling
this
solution
to
them.
It's
probably
going
to
be
the
key
to
selling
it,
to
seek
release.
A
Yeah
definitely
can
contact
someone
from
6gy
to
have
a
look
at
this.
Unfortunately,
they
have
like
everyone.
Pretty
much
in
this
project
have
limited
bandwidth
and,
to
be
honest,
it's
it
used
to
be
like
this.
There
is
possibility
of
sig
release
to
orchestrate
the
discussions
in
meetings
instead
of
the
commedia
maintenance,
but
sure
I
can
definitely
send
an
email
through
the
6000
meaningless
to
say:
hey,
we
have
a
bunch
of
tools,
you
might
have
interesting
interest
in
some
of
them.
D
A
D
A
A
A
A
A
A
A
A
So,
every
time
we
parse
the
flags
for
the
API
server
in
terms
of
authorization
mode,
we
print
a
warning,
no
matter
what,
if
the
basic
the
flag
contains
the
defaults,
we
always
print
this
warning,
and
this
is
the
PRI
changing
that,
with
a
comparison
function,
first
check
if
things
are
the
same
or
not,
but
I
requested
a
door.
Remember
what
I
requested.
Oh.
A
A
D
A
H
H
A
H
D
H
C
B
H
H
A
A
H
H
B
A
Yeah,
it's
really
hard
to
justify
issues
that
are
not
like
important
zone
or
critical
regions.
I
heard
cases
where
a
huddle
arguments
about
important
zone
to
be
in
share
picked.
For
instance,
we
had
a
bug
in
alpha
feature
which
was
completely
preventing
downfall
feature
from
working,
so
I
made
an
argument
with
the
releasing
hey.
This
is
not
critical
because
it's
alpha,
but
without
this
patch
we
cannot
even
use
the
feature,
but
for
important
long-term.
It's
really
hard
to
make
an
argument.
So
maybe
what
we
have
to
do
is
set
of
city.
A
A
D
D
A
E
A
A
A
A
A
A
A
So
we
haven't
done
this
in
a
long
time.
We
haven't
looked
at
our
issues,
so
I
wanted
to
look
at
least
at
the
180
muscle
to
see
what
priorities
we
have
here
so
giving
conferences
tomorrow.
I,
don't
think
we
can
do
anything
here,
except
for
shifting
all
tickets
to
the
next
milestone
pretty
much,
except
for
maybe
docks,
because
the
docks
deadline
is
still
to
come.
A
I'm
going
to
shift
this
to
the
next
mouthful,
this
is
API
changed.
Shifting
to
the
next
milestone,
stop
calling
being
sleep.
This
is
your
scene
I
wanted
to
work
on
that,
but
he
I
don't
think
he
has
time
for
this
anymore
due
to
internal
priorities,
so
I'm
going
to
an
assign
him
with
an
odd
help
wanted.
A
Move
it
to
the
next
cycle
after
that
learn
my
mode.
We
definitely
cannot
do
about
anything
about
this.
For
now
to
billion
flux,
environment
file
contains
deprecated
keyword,
Fox,
it's
a
long-standing
issue,
but
actually
I'm
liking.
How
the
our
picture
with
in
terms
of
corporate
Fox
is
much
clearer
nowadays.
Maybe
somebody
takes
this
next
cycle.
We
can
pretty
much
finish
the
work
here
and
stop
using
some
of
these
flags
that
applied
both
to
the
config
him
yeah,
both
on
the
command
line.
Configure
the
same
time.
A
Although
usage
of
so
this
is
yeah
I'm
going
to
move
this
connect
cycles
well,.
A
This
nice
discussion
overlap
between
keep
config
phase
and
Alfred
about
this
needs.
Discussion
provide
workouts.
This
is
complicated
topic
to
resolve
even
one
day
moving
the
config
to
next
cycle.
All
right
turns
off
windows
support
we're
actually
doing
some
pretty
good
work
been
more
singing
absurd.
She
out
doing
this
in
the
separate
repository
for
cube
ADM.
So
this
is
the
flag
with
her
story,
the
pr
we
discussed
earlier.
It's
really
nice
graph.
We
don't
need
it
really.
A
So
it's
not
super
critical
for
us,
because
Ben
moss
implements
the
workaround
they
pretty
much
stomp
the
default
cube,
ATM
environment,
flag,
so,
environment
file.
This
is
the
repository
for
anybody.
Who's.
Take
a
look.
The
things
look,
looking
pretty
good
for
getting
the
new
support
for
Windows,
slash
comedian
to
beta
in
this
cycle.
A
I,
don't
see
any
major
blockers
at
this
point.
Sorry
there
is
one
potential
Walker
and
that
same
plan
tests
it's
quite
complicated
to
test
this
because
of
you
have
to
have
a
running
infrastructure
somewhere
that
supports
both
Linux
and
windows.
We
are
still
discussing
with
coastal
epi
folks
were
how
to
get
started
with
their
provider,
but
the
other.
There
are
chances
that
this
is
going
to
be
beta
in
were
a
team
that
were
configured
to
attest
this
very
Arvind
Empire
in
there
we're
basically
going
to
potentially
not
have
any
more
actions
for
this.
A
A
D
A
Question
for
a
survey
I'm
going
to
ask
in
the
wider
sea
coastal
a
cycle
meeting
is
whether
we
want
to
even
have
the
survey
giving
like
release
outside
of
sync
of
the
Keep
Calm
event.
Maybe
we
just
want
to
get
the
survey
as
soon
as
possible.
Instead
of
waiting
to
four
hours,
you
know
potentially
delaying
the
survey
or
what
that's
all
it's.
The
topic,
for
example,
meeting
just
wanted
to
mention
this
here,
because
this
is
where
we
have
the
tracking
issue.
A
A
A
A
Housekeeping
tax
I'm
working
dogs-
it's
a
nice
to
have
opener,
see
this.
We
cannot
do
anything
about
it
like
today,
contain
deployment
scenarios
edge.
This
complicated
topic,
nice
discussion,
satisfied
Lily,
said
that
he's
working,
dads
I'm
going
to
detective,
not
sure.
If
he's
continuing
to
work
on
this,
maybe
we
can
have
it
for
113
one
minute
remaining.
B
B
I
think
that
the
best
option
we
can
do
at
this
point
is
probably
just
change
the
the
error
message
a
little
bit,
but
this
actually
required
some
sort
of
pretty
nasty,
very
working,
this
easel
yeah,
so
for
the
now
being,
and
that
this
actually
exists
as
a
book
ever
since
it
was
actually
introduced
as
an
option
to
cube
ATM
in
it,
and
this
was
several
cycles
ago.
This
is
the
first
time
they
actually
reported.
I,
don't
think
it's
not
a
priority.