►
From YouTube: kubernetes kops office hours 20190301
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,
March,
1st,
happy
March.
This
is
cops
office
hours.
I,
am
your
host
moderator
facilitator,
just
in
Santa,
Barbara
I
work
at
Google
reminder
this
meeting
is
being
recorded
and
will
be
put
on
the
internet,
and
so
please
be
mindful
of
that
and
respect
just
be
a
record
of
contact
which
was
found
to
be
a
good
person.
We
do
have
an
agenda
I
think
the
link
is
in
the
calendar.
Invite
ended
in
the
chat.
A
If
you
do
have
items
you
want
to
talk
to
talk
about,
please
do
add
them
to
the
end
of
the
list
or
to
the
list,
and
we
will
get
to
them.
We
don't
have
a
ton
on
there.
Just
say
I
think
there's
three
things
I
put
on
there
I'll
jump
into
them,
I
guess
so.
The
first
one
I
think
is
hopefully
good
news.
Everyone
which
is
I
think
we're
like
we're
getting
back
on
track.
A
We
I
did
111
one
I
cut
that
release
this
morning
or
yeah
finally
cut
it
this
morning
and
thanks
to
everyone
that
contributed
to
that,
in
particular
on
the
CDE
fix,
which
was
sort
of
the
big
pain.
Point
that
and
then
we
are,
will
do
the
112
alpha
pretty
soon
because
of
the
CB
fix,
which
we'll
talk
about
in
a
minute
I.
Think
probably
people
will
want
to
move
to
112
sooner
rather
than
later
so.
A
There
is
also
an
issue
where
the
where
the
current
master
branch
needs
a
custom
upload.
So
there
is
no.
The
master
branch
is
expecting
a
112
alpha.
One
refinery
to
be
uploaded:
it
isn't
uploaded
right
now
and
that's
breaking
some
people,
so
that
would
get
fixed
at
the
same
time.
Sorry
about
that
that
was
my
mistake
and
then
the
there
is
a
there
is
a
I
put
up
a
doc
talking
about
the
run,
C
fix,
mostly
because
the
the
fixes
that
were
out
there
were
a
bit
of
a
challenge.
A
A
That
is
a
reasonable
fix.
It's
not
perfect.
If
you
are
doing
things
which
I
believe
to
be
unlikely,
you
will
want
to
either
upgrade
to
112
or,
if
you
or
use
the
hotfix,
which
basically
downloads
a
patch
version
of
run,
C
or
just
upgrade,
to
a
new
version
of
docker
I,
think
which
one
of
those
three
you
choose
is
more
or
less
up
to
you
personally,
I
probably
would
do
the
newer
version
of
docker,
because
I
think
Rodrigo.
You
said
you
have
been
doing
that
anyway
and
you've
had
good
results.
Yeah.
A
That
thank
you.
That
is
a
good
reason
to
do
that,
and
that
is
probably
also
safer
than
running
a
random
binary.
If
people
really
want
to
run
run
see
the
patch
version,
I
did
do
a
work-in-progress
PR,
where
I
sort
of
package
that
up
so
we
could
start
packaging
that
it
just
becomes
a
big
pain
point
in
the
release
to
start
managing
that
and
I.
Think
the
the
meta
point
is
I'd
agree.
We
should
get
to
a
container
D
where,
where
the
life
cycle
more
closely
aligns
with
kubernetes.
A
A
Good
yeah,
the
I
mean
a
used
to
be
the
case
that
some
of
the
newer,
some
of
the
leading-edge
versions
of
docker
were
had
some
bugs
stalker
has
the
docker
package
has
become
better
at
not
having
those,
but
that's
why
certain
versions
of
communities
are
still
validated
against
certain
versions
of
docker
and
if
they
should
work,
but
you
never
know.
So.
That's
great.
A
Thank
you
for
thank
you
for
confirming
that
and
something
I
person
I'm
excited
about
is
the
third
thing
I
had
on
there
was
that
we
have
the
beginnings
of
mirroring
support
so
right
now
all
the
assets
are
served
from
a
single
s3
bucket
and
we
are
moving
that
to
the
CN
CF
and
likely
will
have
multiple
buckets
with
sort
of
smart
mirror.
That
sort
of
thing
eventually,
but
to
get
that
going,
I
have
put
in
the
first
bit
of
marrying
support.
A
It's
pretty
basic
I
tried
doing
something
more
advanced
and
it
was
a
bit
of
a
mess.
Oh,
how
I
did
something
very
basic
and
for
112
right
now,
I
think
we
just.
We
just
have
the
github
release
in
there
as
sort
of
another
mirror,
so
that
even
if
something
goes
wrong
with
vs3
bucket
that
there
is
another
source
for
it,
and
the
idea
is
that
these
are
only
mirrors.
We
only
pull
from
those
when
we're
pulling
by
hash
and
we
tolerate
them
being
down
so
right.
Now
there
is
no.
A
There
is
nothing
on
that
URL
right
now
in
github,
so
we
are
definitely
tolerating
it
being
down
if
we're
still
passing
tests
and
eventually
we'll
move
the
canonical
source
to
the
CN
CF
location.
But
we
could
then
have
multiple
mirrors
that
are
wherever
you
want,
including
I
guess,
private
s3
buckets
or
something
like
that.
If
you
want
to
do
isolation,
cool
and
we
have
two
items
on
the
agenda
from
Brian
round,
you
wanna
address
them
totally.
C
Yeah
mortgage
questions
is:
do
we
have
a
full
changelog?
I
was
just
looking
for
the
changelog
for
one
dot
11.1
I
I
mean
I,
pulled
up
the
tag
and
went
through
the
commit
history
to
sort
of
figure
out
what
was
in
there.
But
is
there
a
way
we
can?
It
seems
like
that.
We,
like
most
projects
or
lagged
behind
on
change
logs.
A
C
A
B
A
A
Sorry,
you
sound
so
good,
okay
and
then,
but
we
also
need
a
binary
location,
so
I'm
also
working
on
that
or
in
sort
of
like
working
on
that
in
that
in
that
group,
that
will
mean
we
are
able
to
do
we're.
Getting
we're
getting
closer
and
I
think
is
the
answer
and
then
I
think
we'll
still
have
to
well.
A
A
Guess,
essentially
that
that
you,
you
say
like,
for
example,
one
11.1
is
going
to
be
is
going
to
correspond
to
this
particular
get
shot,
for
example,
and
the
way
you
say
that
is,
you
have
a
file
which
has
those
mappings
and
we
do
a
PR
to
commit
that
that
goes
through
the
normal
approval
process,
either
in
the
same
repo
or
in
a
meta
repo,
and
it's
image
for
wrote,
okay,
I'm
trying
to
find
this
thing
apply.
Sorry,
so
that's
that!
Might
that
is
reasonable
and
we
might
going
to
do
that.
A
But
yes,
how
we
trigger
those
builds.
I,
don't
know,
I,
don't
think
anyone
has
a
great
answer
for
it.
Yet,
okay,
just
let
us
know
if
there's
anything,
we
can
do
to
help
you
out
with
that
awesome.
There
I
mean
if
you
always
if
anyone
that
wants.
If
anyone
wants
to
get
involved
in
this,
this
is
working
group
Kate's
info,
which
hope
they
will
have
more
luck.
Finding
yes,
I'm
gonna
paste
this
in
our
in
our
notes.