►
From YouTube: Kubernetes kops office hours 20181221
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
Hello:
everyone:
it
is
Friday
December,
2012,
December,
21st,
2018,
I
tried.
This
is
like
the
last
office
hours
of
2018
for
cups,
bring
on
2019
lots
of
great
things.
Coming.
We
have
an
agenda.
Thank
you
to
Mike
for
placing
the
link
in
the
chat.
Please
do
or
feel
free
to
add
your
name
as
an
attendee,
and
we
do
have
one
four
things
on
the
agenda,
so
we
can
get
straight
in
there,
but
if
you
would
like
to
make
sure
we
cover
something,
please
do
you
add
it
onto
the
agenda.
A
B
Go
memory
test
we're
probably
both
wrong,
so
Justin
I
sat
down
at
Q
Khan
and
tried
to
work
out
how
to
actually
migrate
from
B
to
calico
v2,
a
net
CD
at
C
DV
to
up
to
at
CD
v3
and
calico
v3.
We
managed
to
do
it
on
a
toast
cluster,
with
downtime
on
the
nodes.
The
we
came
away
with
a
few
PRS
I
think
that
we
need
to
get
in
to
do
that
successfully.
B
So
we
had
to
just
pull
those
and
it
containers
out
so
I,
just
I'm,
not
sure
what
the
plan
is
there.
If
we're
gonna
I
think
we
decided
we
could
either
I
delete
the
data.
So
we
try
to
do
that
so
not
migrate.
The
data
that
the
Calico
data
is
part
of
the
CD
v3
upgrade
or
we
were
looking
at
just
for
plate,
changing
those
init
scripts
yeah.
A
B
A
A
Then
we'll
be
in
a
much
better
shape.
We
might
still
need
DNS
for
cilium,
which
is
another
CNN
provider
which
talks
to
Etsy
D,
but
maybe
we
may
relay
down
the
hard
line
and
say
no,
but
yes,
I,
think
I.
Think
the
the
good
news
is
that
we
do
have
an
approach.
It
seems
like
we
were
able
to
figure
out
with
some
help
and
the
bad
news
is.
It
does
require
like
a
bounce
of
all
notes,
and
it
requires
possible
notes.
At
the
same
time,.
B
A
All
right
is
there
anything
else
we
want
to
talk
about
on
there,
or
should
we
carry
on
no
I
think
we're
good
there,
okay
I'm
trying
to
open
up
this
link.
So
the
next
item
on
the
agenda
is
a
111
final.
Is
the
release
ready
to
go
I
believe
I
believe
it
is?
We
were
waiting
for
111
I
think
we're
waiting
for
111,
5,
Lambert,
111
6
landed
very
soon,
so
I
think
anyway.
The
the
upstream
version
we
were
waiting
for
landed
is
that
a
this
is
a
new
yeah.
This
is
the
this.
A
Other
than
this
issue
I
think
we
are
relatively
okay.
The
good
news
is
this
morning,
so
sort
of
leading
into
the
next
issue
this
morning,
I
did
we're
trying
to
get
to
like
more
automated
releases
and
faster
releases,
and
all
of
that
and
I
am
splitting
up
the
current
release
process
into
creating
the
commits
and
then
hopefully,
CI
goes
and
builds.
That
and
then
we,
gentlemen
need
to
tag
the
CI
output
and
promote
it
I
think
anyway.
So
there
are,
there
are
three
open
commits
right
now
there
is
one
ten
one.
A
There
is
one
11
zero.
There
is
112
zero
alpha
one
there.
The
complexity
about
about
113
and
114
is
that
currently
they
use
a
lot
of
criminais
API
machinery,
so
huge
shoutout
to
Rodrigo,
who
did
the
112
move
bump,
but
if
we
can
get
off,
if
we
get
on
to
see
our
DS,
we
should
have
less
dependence
on
the
machinery
and
then
we
should
be
able
to
do
the
other.
The
other
branch
is
more
readily,
but
we're
still
working
to
get
there.
A
A
Hoping
we
don't
too
Ciardi
that
we
don't
have
to
worry
about
it,
but
yes,
series
are
actually
really
really
nice
for
other
reasons
as
well
like
they
actually
unblocked
up
servers
but
anyway,
so
we
have
111
0,
which
I
think
is
ready
to
go.
There
is
some
final
jury
picks
which
were
just
I,
think
they're
all
approved
in
og
TN.
Now
thank
you
Mike,
and
so
we
they
want
to
merge
and
then
I
think
we
can
tag
it
and
hopefully
more
that's
automatically
built,
but
we'll
see.
E
A
A
B
B
It's
always
been
with
ephemeral,
storage,
so
I
think
I
think
there's
another
issue
with
a
ephemeral
storage
reporting
that
it's
full
when
the
node
first
comes
up
and
that's
that's
causing
that
and
then
that
bug
doesn't
ever
pick
up
to
pick
up
the
change
that
the
ephemeral
storage
isn't
actually
full,
so
I
think
there's
two
things
going
on
there,
but
it's
unless
you're
using
the
ephemeral
storage
limits.
It's
probably
not
an
issue.
A
B
A
Out
yeah
thanks
for
the
heads
up
on
that,
that's
great,
but
yes,
the
I
guess.
The
good
news
is
that
then
111
zero
is
more
less
ready
to
go
in.
We
are
some
final
PRS
and
then
we
will
hopefully
little
Christmas
present,
maybe
make
a
Christmas
present
and
then
the
next
issue
on
the
agenda
was
112.
113,
114,
alphas,
I.
Think
we've
covered
this.
E
Don't
know
a
better
term
than
this,
but
I
was
thinking
like
when
we're
you
know
you
know
putting
in
a
bunch
of
these
PRS
and
I
was
like.
Oh,
we
need
to
update
the
readme
I
think
it
was
Chris,
love
created,
the
compatibility
chart
and
I
was
adding
another
column
and
I
was
like.
Oh
man.
This
thing
is
just
getting
too
wide,
you
know,
and
maybe
we
should
start
at
least
communicating
that
people
really
should
be
on
cops.
E
Then
people
can
kind
of
at
least
start
feeling
their
way
towards
you
know:
hey
everyone
has
some
old
clusters
here
and
there
that
you
don't
really
want
to
upgrade,
but
you
know
we're
not
really
supporting
that
as
much
anymore.
I,
don't
know
if
anyone
has
thoughts.
Oh
and
I
also
made
no
part
of
that.
It's
there's
the
important
statement
of
why
and
I
didn't
mention
that
just
now,
kubernetes
supports
three
minor
versions,
so
that
right
now
is
thirteen
twelve
and
eleven.
E
So
technically
110
isn't
even
supported
anymore,
but
the
patch
support
they
did
put
that
CVE
patch
out,
because
I
think
it
came
out
right
as
one
thirteen
was
being
cut.
But
that's
why,
for
that
most
recent
major
CVE,
they
didn't
cut
it
for
anything.
You
know
one
nine
or
below.
So
you
know
we
have
this
weird
balancing
act.
A
A
We
do
have
a
mechanism
to
strongly
encourage
people
to
update
which
is
still
over
writable
but
like
at
least
like
it
ends.
I
can
Enver
like
have
to
sit
like
something
like
I
know
what
I'm
doing
or
something
like
that
or
on
my
own
head.
But
so
we
could
use
that
to
push
people
to
1:10
I.
Do
like
the
idea
of
doing
in
the
docks
where
you're
effectively
like
steering
people
away
from
the
older
releases,
because,
yes,
we
we
we
definitely
have.
A
We
have
et
testing
for
the
actively
supported
versions
and
in
theory
we
try
not
to
break
it,
but
I.
Don't
think,
and
we
have
integration
tests.
Sorry
have
unit
test
coverage
to
make
sure
that
we
haven't
like
changed
the
specs
of
any
of
our
like
update
cluster
things
where
we
go
and
generate
the
terraform,
but
it
is
still
possible
that
we
would
ask
I
mean
it's
still
very
possible
that
we
would
break
an
older
version
of
kubernetes
with
a
newer
version
of
cops.
A
I
would
guess
that
most
people
probably
stick
with
the
older
version
of
cops
when
they're
running
an
older
version
communities,
but
that's
not
ideal
I
there,
hopefully
bundles
bundles,
are
the
answer.
There
I
think
where
we
actually
have
some
way
to
get
get
away
from
the
like
tying
of
cops
to
the
CNI
providers,
for
example,
whether
it's
you
not
provider
versions
I
like
I,
like
what
you've
done
in
the
pic
sure
the
docs
were
you
sort
of
truncated
bill
burdens
and
I
think
just
certainly
a
case
to
recommend
four
one.
A
C
C
E
E
E
A
A
A
Well,
somebody
that
looks
great
done.
Thanks,
Mike
Ryan,
oh
yeah,
the
nvme
time
out
I
forgot
about
this
one
I'm
sorry
I
mean
me
time
out.
Ebs
Rita
goes
read-only.
This
is
a
bug
you
mentioned
to
me.
I
have
not
yet
seen
you.
B
Know
the
Debian
stretched
by
default
has
a
in
has
an
nvme
nvme
time
out,
I
think
of
30
seconds
or
something
set.
Aws
recommends
maxing
that
to
whatever
the
highest
the
kernel
actually
on
that
kernel
version
actually
allows.
There
was
another.
There
was
actually
another
PR
in
that's
mine
that
I
put
in
I
need
catch.
The
fact
there
was
another
one,
but
it
had
an
error
in
it.
So
I
didn't
work,
so
that
is
the
fix
for
it.
B
A
A
A
B
A
A
A
B
A
B
A
Since
we
should
yeah,
we
should
fix
that
I'm
actually
debating
whether
we
should
use
the
OS
packages
at
all
to
install
docker,
but
that's
tangential.
So
in
other
words,
we
just
always
uninstalled
the
OS
docker
and
then
reinstall
yeah,
this
I
guess.
Maybe
we
just
let
we're
rapidly
approaching
the
era
of
container
D.
So
it
may
eventually
cease
to
be
an
issue.
Yep
I,
just.
D
A
A
I
can't
remember
the
details,
but
like
there's
a
version
which
isn't
packaged
by
docker,
and
so
we
installed
a
roll
tour
file
anyway,
and
it
seems
like
it
just
as
it
makes
a
lot
of
the
different.
The
the
weird
differences
that
otherwise
have
to
deal
with,
so
be
nice
to
go,
specify
just
a
URL
to
a
version
of
docker.
The.