►
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
A
I
know
I'm
behind
on
uploading
the
last
two
meetings
I'll
get
on
that
and
do
this
one
along
with
the
prior
two,
so
folks
can
catch
up
if
anybody's
interested
in
seeing
what
we
talked
about
in
the
last
two
meetings,
I
will
share
my
screen
so
right
now
it's
uni
peng
pay
I'll
share.
A
A
I
used
so
many
different
tools.
I
don't
know
how
to
use
zoom
anymore.
A
I
can't
find
it
right
now.
Oh
there
it
is
okay.
Somebody
joins
so
I'll.
Take
notes
too,
since
it's
just
the
two
of
us
and
okay.
A
So,
let's
start
first,
is
anybody
new
here?
No
you
and
me,
we
know
each
other.
I
added
your
request
that
you
reached
out
to
me
earlier
to
review
open
pull
requests
to
the
agenda,
but
first,
let's
see
is:
is
there
any
news
that
we
should
share
with
anybody
who's
watching
the
recording?
A
B
No,
but
we
are
fixing
a
few
bags
in
kubernetes
ripple
and
some
of
them
are
still
pending
on
approval,
so
if
we
could
make
them
molded,
then
that
should
be
some
some
news.
So.
B
Right
right,
so
the
the
this
query
is
all
the
traffic
prs
into
kubernetes
ripple,
the
oldest
one
is
from
january,
so
it
has
been
opened
for
a
few
months
but
still
didn't
get
approved.
The
second
one,
the
the
last
one.
There
needs
some
reverse,
so
I
think
andy
would
address
it
later,
but
for
the
child
pigs,
the
second
one
yeah.
So
we
have.
A
Yeah,
okay,
so
we're
waiting
for
probably
chef,
taco
or
andy
yeah,
okay
and
they
haven't
responded.
So
have
you
been
able,
you
probably
haven't,
been
able
to
show
up
to
any
of
the
cloud
provider
meetings?
I
haven't
either
they've
conflicted
with
a
bunch
of
other
work
meetings.
Lately
it's
been
very
hard
to
get
to
them,
so
I
will
reach
out
out
of
band
during
work
hours
to
to
andy,
and
why
am
I
forgetting
his
name?
A
It's
terrible
chef,
taco
and,
let's
see
if
we
can
get
some
attention
on
these
in
this
case,
what
is
the
the
user
impact.
B
The
impact
is
so,
for
example,
for
this
one
there
are
some
esl.
So
if
you
open
the
link,
not
all
node
posts
are
cleaned
up
on
a
bit
on
iovd
deletion.
B
So
we
should
ensure
all
the
bmss
cleaned
up
correctly.
B
A
B
Mounts
I
can
be
amount
easier,
so
they
should
be
waiting
for
for
six
storage
approval.
A
Okay,
yeah,
all
this
is
just
sort
of
getting
people's
attention.
This
one
looks
like
it
has
a
these
two
look
like
they
have
some
rebates
needed.
B
B
Not
yeah
probably
need
another
rebate,
because
the
test
job
has
been
change.
The
sets
yeah
so
so
those
jobs
would
keep
failing.
A
Okay,
I'll
I'll
think
cecile
online.
This
one.
A
A
A
B
B
One
is
to
fix
the
node
public
eye
pinocchio
issue
from
the
intense
metadata,
so
this
has
been
a
an
eco
for
a
long
time
because
the
when
we're
using
standard
load
balancer
the
ap
address
is
not
not
shown
from
the
intense
metadata.
But
now
all
this
data
is
available
within
a
different
endpoint.
It
is
inside
the
load,
balancer
endpoint,
so
so
the
pr
adding
another
http
request
to
instance,
method
service
was.
B
Not
cip
apis.
I
am
yes
intense
mandatory
here.
B
It's
it's
a
different
endpoint
to
provide
the
same
same
data.
Oh
interesting,.
B
A
B
Yeah,
so
the
first
three
are
same
in
different
branch.
You
must
120
and
121
yeah.
A
B
And
we
we
went
to
ensure
the
I
I
I
think
the
the
next
character
deadline
is
just
two
or
three
days,
so
it's
better.
We
could
get
approval
in
next
few
three
days.
If
not,
we,
then
we
would
need
another
month
for
for
the
charity,
for
the
for
the
patch
release.
A
Okay,
I
know
what
to
do
what
other
issues
should
we
discuss?
Are
there
should
we
take
a
look
at
the
test
boards
or
backlog.
B
Yeah,
I
I
think
we
should
take,
have
a
look
at
the
10th
grade,
so
I
think
the
the
ecs
there
there
are
some
long
running,
failing
filling
jobs,
for
example
the
capacity
I'm
not
sure
whether
they
have
been
fixed
or
not.
Now.
A
B
A
Oh
yeah,
that's,
okay,
so
it
should
look
good
from
now
so
in
another
day
or
so
this
should
okay,
so
the
ones
we
need
to
focus
on
are
the
kepsc
related
ones,
and
that's
not
surprising.
I
mean
we
just
created
these
so
yeah,
so.
B
B
B
Yeah,
I
agree
so.
A
B
A
So
I
I
wonder
if
we
should
have
a
separate
discussion
about
you
know:
triaging
these
kinds
of
failures,
I'll
chat
with
rita
and
ernest
about
that
tomorrow.
A
A
Well
I'll
talk
quickly,
also
about
the
we.
We
started
having
a
meeting
every
other
meeting
in
the
another
time
zone,
so
we've
had
one
instance
of
a
thursday
meeting,
that's
in
a
europe-friendly
time
zone,
and
so
anybody
who's
watching
the
recording
here
on
thursdays
check
the
community
calendar.
A
We
have
a
meeting
at
a
time-
that's
actually
friendly
to
europe
afternoons
and
just
morning
in
north
america,
and
we
did
get
a
new
participant
from
from
giant
swarm
who's,
starting
to
pay
attention
to
the
azure
cloud
provider,
he's
working
on
cluster
api
provider
for
azure
as
well
and
is
going
to
start
contributing
to
the
cloud
provider
and
that's
very
exciting,
and
we
want
to
support
him
in
doing
that.
A
B
Yeah
yeah
sure,
so
I
I
think
so
for
you
in
the
future.
If,
if,
if
there
are
any
new
error
related
issues,
the
new
new
ecu
should
be
opened
in
cloud
provider
ripple.
So
it
would
be
get
noticed
by
us
more
more
faster
because
they
are
less
much
less
easier.
In
your
separate
repo.