►
From YouTube: Kubernetes kops office hours 20190104
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
January,
4th,
2019,
happy
newest
year,
everybody.
This
is
cop's
office
hours.
We
have
some
new
people
so
welcome,
and
we
have
a
couple
of
things
on
the
agenda.
We
have
one
thing
which
I
put
on
there,
which
is
just
a
sort
of
quick
update
on
progress
and
with
our
releases,
and
then
someone
else
put
a
PR
about
external
egress,
so
we'll
cover
that
in
a
minute,
I,
don't
I'm
just
checking
whether
something
has
been
mentioned.
A
Yet
there
there
is
a
recommended
update
coming,
although
I
don't
think
it's
particularly
important
for
for
cops
users.
It's
supposed
to
have
landed
right
now,
but
I
haven't
seen
any
use
about
it
yet,
but
it's
not
particularly
it's
not
too
bad
I,
don't
think
so.
Keep
an
eye
out
for
that
later
on,
I
believe
cops
will
suggest
an
update,
but
it's
not
actually
particularly
critical
for
cops
users.
I,
don't
think
we
do
have
some
cops
releases
that
are
done.
We
have
one
ten
one.
A
We
have
one
eleven
zero,
both
of
those
are
out
and
we
are
working
on
112
alpha.
One
we've
talked
a
lot
about
like
trying
to
get
this
into
a
much
more
automated
and
faster
pattern,
and
so
the
sort
of
hold
up
on
112
alpha
one
is
that
we're
trying
to
get
it
basically
almost
entirely
automated,
and
so
there
a
couple
of
PRS
that
I've
linked
to
which
will
basically
make
that
a
much
easier
and
more
automated
and
in
theory,
community
process
like
right
now
that
process
is
not
very
community.
A
I
would
say
it's
that
I
have
to
do
the
builds
and
it's
when
I
say
so,
and
that's
not
really
what
we
want,
but
we've
sort
of
been
held
up
by
technical
considerations
and
we
are
addressing
those
technical
considerations.
I
guess.
So
there
is
a
open
PR
which
says
like
like
mark
112,
zero
alpha
one
and
we
basically
we
will
hopefully
merge
that
and
then
there
will
be
a
all
amazed,
job,
a
proud
job
which
will
build
other
release
binaries
from
that
into
I.
Think
it's
a
GCS
bucket,
but
it's
just.
A
You
know
the
same
way
that
we
do
all
our
CI
builds
in
our
built
automatically
to
a
GCS
bucket,
and
then
those
are
all
going
to
be
public
and
continuously
built.
Anyone
can
pull
one
of
those
any
time,
but
then
we
will
have
a
process
by
which
we
promote
one
of
those
builds
to
be
a
real,
build
or
sort
of
a
released,
build,
which
basically
should
be
just
copying.
A
The
binaries
from
the
bucket
from
the
CI
bucket
to
github
and
to
more
trusted
bucket
and
I'm
gonna
I'm,
going
to
start
off
with
a
script
which
I
will
probably
still
have
to
run
manually.
But
the
intention
is
that
we
will
get
that
to
be
a
script
which
will
be
triggered
by
probably
a
signed
tag
or
maybe
a
assigned
to
get
tagged
or
maybe
a
special
commit
in
a
different
repo,
which
is
basically
a
basically
says
like.
A
This
is
the
release
so
some
form
of
Education
like
that,
but
Bernice's
we're
getting
there
so
112
zero
alpha
one
should
be
soon.
But
there
are
some
blockers.
There
are
some
like
things:
we're
trying
to
get
sorted
out
first,
but
hopefully
to
a
19.
Will
be
the
year
of
automated
builds
for
cops
yay
exactly
all
right.
If
there's
nothing
else
on
that,
I
will
move
on
to
the
next
item.
I,
don't
know
who
put
it
on
the
agenda,
but
there
is
a
link
to
the
external
egress
PR
hey.
This
is
Arjun.
I
put
the
book.
B
Baron
so
we're
working
at
vibrant
health
on
a
couple
of
clusters
we
cook
with
cups
and
just
for
a
variety
every
business.
We
need
to
move
the
egress
control
system
to
AWS
and
let
native
us
do
its
thing
and
let
other
security
tables
do
it.
So
we
found
this
external
egress
PR.
That
I
think
you
just
had
started.
We
fixed
it
up
for
one
got
11
and
we
were
hoping
to
get
it
in
for
one
not
11,
with
1.11
out
we're
now
trying
to
make
sure
he
gets
commercial
on
12.
A
It's
basically,
we
currently
have
egress
lets.
You
specify
I,
think
that
gateway
the
next,
an
existing
that
gateway
mm-hmm,
and
this
would
be
a
another
magic
value
in
there,
which
basically
turns
off
cops
handling
of
egress
and
just
says
I'm
gonna
take
care
of
it.
So
I
presume
you
have
to
set
up
an
existing
subnet
or
maybe
go
in
afterwards
and
fix
it
up,
but
yeah
exactly
there.
B
A
A
How
do
you
like
encompass
the
variety
of
configurations
that
people
want
in
the
real
world
without
essentially
reproducing
it
and
I?
Think
this
is
a
nice
compromise
between
the
idea
that
a
lot
of
people
just
wanted
to
just
work,
but
a
lot
of
more
advanced
users
want
to
set
their
own
settings.
What
can
you
Rodrigo
there.
A
Okay,
well
yeah,
I,
yeah,
I,
think
I
think
we
should
tag
Rodrigo
and
I.
Guess
Mike
is
another
good
ones.
Have
a
look
at
that.
B
A
A
A
Okay,
all
right,
you
can
also
try
Trillian
chat
if
you
really
want
to,
but
otherwise
we
care,
we
can
definitely
cancel
or
stop
the
meeting
now
and
give
everyone
lots
of
their
Friday
back
all
right.
Oh
112
stability
for
cups,
112,
it's
an
alpha
but
I,
think
I
believe
it
to
be
fairly
usable.
We've
certainly
been
testing
it
and
it
seems
fine.
The
we've
certainly
been
et
testing
it
and
it
seems
fine.
A
The
biggest
blocker
is
that
we
as
part
of
the
sed
roadmap,
want
to
get
a
CD
manager
going,
which
is
not
necessarily
fully
baked.
Yet
there
are
like
two
or
three
items
on
the
list.
Still
kubernetes
112
seems
to
be
a
good
release
as
far
as
I
can
tell
perhaps
a
little
bit
more
stable
than
criminalizing
111.
Well,
like
you
raised
what
11
has
only
just
become
had
some
important
cherry
picks,
which
only
just
got
released,
but
they
were
already
in
112.
So
from
that
point
of
view,
112
seems
better.
C
C
A
I
think
you
had
an
open
issue
of
which
I'm
gonna
have
a
look
at
I
just
have
to
get,
and
then
the
Arjun
asked
in
chat
with
111
cast
with
Chron's
112
II
a
better
path.
The
the
general
answer
is
in
you
should
you
should
try
to
avoid
using
an
earlier
version
of
cops
with
a
newer
version
of
kubernetes,
because
when
a
flag
changes,
we
only
put
that
in
Mike
the
the
correct
flags
for
cups
for
queridos
112
are
only
in
cups,
112
and
higher.