►
From YouTube: 20190612 scl cluster api office hours
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
We
have
a
stuff
at
the
top
of
our
meeting,
invite
which
is
basically
how
to
engage
so
if
possible,
if,
when,
where
possible,
try
to
use
the
hand,
raise
item
or
feel
free
to
turn
your
camera
and
just
raise
your
head,
basically,
whatever
c4
there
with
that
I
added
some
things
to
Jeddah
at
first
but
I'm.
Looking
for
group
topics
because
there
was
no
agenda
played
so
I
was
gonna
monologue
for
a
little
bit,
I'll,
be
sure
to
screen.
A
Alright,
so
for
those
who
don't
know
me,
my
name
is
Tim
Sinclair
I
am
one
of
the
co-chairs
for
supercluster
life
cycle
I've
been
taking
a
hands-off
approach
for
quite
some
time
on
Cluster
API
and
let
the
sub-project
visas
workers
kind
of
do
their
their
business
they're.
Given
a
bunch
of
issues
and
things
that
have
occurred
over
the
last
couple
of
months,
I've
talked
with
the
Supraja
coders,
as
well
as
the
co-chairs
for
sequence
for
life
cycle.
A
You
know,
I'm
gonna,
help,
moderate
I,
think
this
sub
project
for
a
while
tell
folks
feel
comfortable
and
get
into
rhythm
again,
then
from
there,
probably
in
that
back
off,
so
Who
am
I.
Why
am
I
doing
this?
The
first
and
foremost
thing
is
to
kind
of
bias
towards
action
right
now.
The
the
sub
project
is
kind
of
gone
through
a
little
bit
of
a
paralysis
for
a
while
discussing
large,
changing
features
that
they
wanted
to
do.
A
A
I
also
want
to
get
out
of
the
idea
of
design
by
committee.
If
we
have
some
broad
views
of
how
we
want
to
go
in
certain
directions,
let's
love
the
issues
and
agree
or
disagree
upon
finite
specific
items.
Instead
of
trying
to
boil
the
ocean
again
so
incremental
step
wise,
explicit,
greater
than
implicit
write,
it
down,
write
it
down
and
write
it
down
in
horrific
detail
and
I'll.
A
Try
to
hold
everyone
accountable
to
that
right,
myself,
included,
sometimes
I
know
I
can
I
can
preach
on
a
soapbox
and
chuck
is
very
adamant,
sometimes
about
you
know,
creating
those
things
back
to
me.
So
it's
a
good
idea
to
keep
me
accountable
to
I'm
going.
Then
anyone
else
be
respectful
to
have
fun.
A
So
that's
how
I'm
going
to
try
to
run
things
so
so,
hopefully,
with
that
I
just
want
to
give
a
couple
other
PSAs
we
did
a
grooming
initial
grooming
session
for
v1
outfits
you,
according
to
the
plan
that
was
publicized
and
discuss
or
I,
don't
know
it's
very
simple.
We're
gonna
do
another
grooming
session,
this
Friday
for
those
who
are
interested.
You
know
the
gory
details
it
what
it
means
to
walk
through
all
the
issues.
A
A
Taniya
talked
during
the
grooming
session
that
it
might
be
a
good
idea
to
do
a
coat
on
it
and
for
those
who
are
interested,
the
request
was
made
to
push
that
code
on
it
until
next
week.
Typical
way,
we've
done
this
in
the
past
is
we've
literally
had
somebody
open
up
an
editor
and
somebody
opened
up
github
bug
page
as
you
walk
through
with
the
editor.
You
talk
things
out
loud
and
you
open
up
issues
along
the
way.
It's
a
good
way
to
get
familiar
with
the
code.
A
It's
also
a
great
way
to
you
know
to
get
engaged
with
helping
to
fix
some
bugs
and
chop
the
wooden
liquor
in
water.
So
if
you're
interested
in
that
I
will
send
out
another
session
for
next
week,
Tamia
good
I
can't.
Last
but
not
least,
there
is
a
machines,
States
and
bootstrapping
PR.
That
was
the
proposal,
death
mishap
and
he
had
known.
A
And
certain
other
groups
of
people
it
has
pushed
as
a
PR
knows
for
comments.
We
will
probably
hold
the
PR
for
a
little
while
as
long
as
we
deem
necessary-
and
we
will
come
back
to
the
group
where
you
can
merge
something,
and
it
doesn't
mean
that
we
can.
We
need
to
stop
the
train
right
now.
Some
of
those
things
are
non-controversial.
D
D
A
In
general,
there
is
well-defined
precedent
in
Renee's
community
for
how
to
handle
this
and
I'll
be
following
that
precedent.
So,
at
the
end
of
the
day,
it's
the
people
who
are
owners
and
approvers
are
the
ones
who
actually
can
make
the
final
decision
of
call.
If
you
want
to
get
in
the
owners
of
girls-
and
you
got
a
chocolate
in
clear
water
and
you
can
always
it's
it's
like
binding
voting
in
the
traditional
models
right.
A
Those
who
have
the
binding
votes
get
the
final
say,
but
you
can
always
vote
independently,
but
they're
like
Plus,
Ones
or
minus
ones.
Non-Binding
and
I
would
expect
approvers
of
the
group
to
respect
those,
if
there's
a
overwhelming
majority
ones,
to
respect
that
as
well.
People
should
not
act
unilaterally,
so
I'm
gonna
be
following
that
person.
I'm
sorry,
my
my
your
things
were
not
working
before,
but
they
are
no.
C
C
A
E
Yes,
so
in
in
developing
the
cluster
API
upgrade
tool
that
has
been
posted
a
couple
of
times
on
the
cluster
api
channel.
We
figured
it
would
be
good
to
have
a
testing
framework
and
to
do
that,
we
pretty
much
needed
a
cluster
api
provider
with
kind
as
the
backend.
That
seems
like
something
that
we
could
also
use.
Okay,
so
I
had
a
question
about
where
it
should
live.
It
seems
like
we're
a
couple
it
could
live
either
inside
foster,
API
or
could
live
outside
cluster
API.
There
are
a
lot
of
quick-cook.
E
E
So
if
an
API
changes
or
if
you
know
a
function,
changes
or
whatever
you
have
you're
forced
to
update
the
the
provider,
the
kind
provider
on
the
on
the
flip
side,
the
dependency
it's
it's
kind
of
confusing
to
have
a
sub
project
inside
of
a
project.
That's
got
already
like
got
its
own
doctor
file
and
things
like
that.
So
it
could
be
a
little
bit
confusing
on
the
flip
side,
if
it
lives
outside
of
cluster.
A
P
I
would
be
just
like
any
other
provider
that
we
have
like
AWS
or
using
P.
A
F
Bits,
thank
you.
So
I
have
two
things
on
the
agenda
like
the
first
one
is
just
a
look
at
general
status
update
on
the
butcher
PR
around
50%
of
the
comment
haven't
been
kind
of
resolved
and
like
I
will
go
through
the
rest
this
afternoon
to
make
sure
the
like.
E
A
That's
all
we
actually
have
for
an
agenda.
We
are
a
pretty
short
agenda
today.
Are
there
other
topics
that
folks
want
to
discuss?
If
so,
please
just
add
them
to
the
document.
We'll
walk
through.
C
A
I
had
a
conversation
with
Doug
I
wanted
to
create
a
larger
dock
and
I
started,
creating
a
larger
dock,
but
we
decided
to
break
up
the
dock
into
two
separate
things.
One
was
lexicon
his
values
through
scope,
but
there
was
also
another
fourth
thing,
which
is
like
design
principles
of
what
we're
trying
to
do
and
I
have
not
finished
that
I.
A
C
C
A
C
Right
I
think
we
just
got
two
requests
from
releasing
that
we
should
do
some
kind
of
status
updates
of
the
release
not
like
it
doesn't
have
to
be
tied
like
like
Austria
API,
isn't
tied
to
the
convenience
release
schedule,
but
something
that
just
what
we've
been
doing
generally
so
I
was
thinking
like
if
we
have
the
come.
If
it's
easy
in
kubernetes
community
also
follow
what
we're
doing
is
the
original
proposal
or
G
don't
kept
up
to
date
anymore,
so
it
stuff
like
that.
But
that's
for
meta.
B
B
B
If
there's
any
feedback,
you
know
to
two
things.
That
I
would
say
is
that
you
have
people.
People
do
come
by
with
implementation
questions
or
somebody
came
by
yesterday
was
working
on
a
new
implementation
targeting
v1
alpha
one,
and
you
know
we
were
able
to
sort
of
you
know,
look
into
the
code.
It's
kind
of
you
know,
give
give
I
think
a
quicker
or
sort
of
intro
than
would
be
possible,
maybe
from
slack
or
some
other.
B
A
In
church
and
fashion,
what
I
think
I
would
do
in
public
a
sangria,
so
after
I'm
done,
I
would
say
log
an
issue
and
send
it
to
the
mailing
list.
I
think
those
are
two
ways
to
get
broader
feedback
on
if
those
times
work
and
whether
or
not
people
are
Co
as
different
times
so
I
think
maybe
opening
up
an
issue
to
the
main
repository
for
the
time
being
for
lack
of
a
better
tool.
G
G
However,
I
think
that
what
later
became
more
into
more
important
was
once
I
tried
to
fix
something
in
the
working
any
issue.
The
basically
the
decoder
base
is
flourish
and
is
complex
and
I
have
the
in
this
case,
I
work
together
with
another
person.
Just
because
we
decided
to
work
together.
We
have
our
own
private
chat,
but
I
think
that
probably
this
is
the
most
interesting
object.
G
That
is
this
officer
work
we
have
if
we
want
more
people
to
join
work
on
the
issues,
because
he's
got
me
for
a
newcomer
discussing
an
issue
over
the
github
is
like
forever
and
the
slack
it's
probably
not
really
good
for
discussing
called
experience,
so
I
think
summary.
I
found
it
useful
at
the
beginning
and
later
on,
I
will
have
to
use
it
probably.
A
No
once
twice
three
times:
okay.
Well
then
I'll
say
thanks.
Everyone
I
think
the
plant
of
record
is
I,
will
send
out
emails
for
folks
who
want
to
walk
along
both
the
the
grooming
and
the
gory
details
there,
as
well
as
the
gory
details
of
June,
Code
walkthrough,
probably
sometime
next
week,
if,
if
someone's
interested
in
being
the
being
the
person
who
walks
through
the
code
or
wants
to
help
me
with
that
effort,
I
think
that'd
be
a
good
way
for
broader
exposure,
and
you
know
your
hands
in
there.