►
From YouTube: CAPZ Office Hours 03-05-2020
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
All
right
now,
they're
recording,
please
adhere
to
the
commodities
code
of
conduct
and
then
there
for
CN
CF
code
of
conduct.
They
have
one
I
hope.
That's
all
I'm
supposed
to
say
be
nice
to
people
anyway.
Add
your
name
to
the
meeting
agenda
of
the
notes.
If
you're
here,
I'll
paste
it
in
the
chat
thanks
for
coming
guys,
so
she's
think,
since
things
have
been
so
crazy,
okay
and
so
today,
we're
gonna
go
through
our
open
discussion
items
and
see
where
we
end
up.
A
B
I,
this
is
my
first
meeting
hi.
B
A
All
right
cool
so
now
I
think
we're
ready
to
actually
start
soda.
Okay.
So
first
thing
we
created
a
doodle
poll
for
a
kanji
office
hours
on.
If
we
you
guys
want
more
times
to
be
included,
just
go
ahead
and,
like
just
ping
me
on
soccer,
let
me
know,
but
if
not
go
ahead
and
fill
it
out,
we're
trying
to
find
something
that
matches
for
more
people
and
the
UTC
time
zone
or
any
other
time
zone.
So
we
might
just
keep
it
at
the
same
time.
A
A
In
the
chat,
cool
I
think
Stephen
just
put
his
own
link
up
there.
So
yeah
any
give
everyone
that's
good.
Oh
okay,
yeah!
We
should
be
good
little
figure
it
out.
A
D
What
was
it
again?
Oh
yeah,
okay,
yeah,
just
FYI
as
Cathy,
is
releasing
new
upstream
release.
Candidates
for
the
0.30
release,
we're
trying
to
stay
pretty
close
with
those
and
so
we're
at
arson.
3
now
so
let
us
know
a
few
notice
and
breaking
changes
and
I
hope.
I
wasn't
cutting
out
yeah,
okay,
good
all
right
and
that's
it
awesome.
A
Thank
you.
Alright.
The
next
thing
we're
gonna
discuss
that
Hanson
proposal.
I,
think
that
is
that
David
say
yours.
Yep
I
put
that
on
there
putting.
A
E
Super
thanks
for
the
time
to
discuss
this.
Well,
it's
so,
of
course
we
added
the
label
for
proposal,
so
anybody
please
please
enter
enhance
my
proposals,
but
also
beyond
that
this,
this
particular
enhancement
proposal,
it
kind
of
seems
logical
that
the
Pepsi
provider
and
other
providers
that
integrate
with
like
cloud
infrastructure,
really
the
providers,
take
some
abstract
model
and
then
transform
that
model
into
some
declarative
state
for
for
the
cloud
provider
or
whatever.
Whatever
your
end,
resources
are
so
like
II,
just
you
can
have
a
like
virtual
machines
network
infrastructure.
E
E
Cluster
API
provider
becomes
like
super
simple:
it
has
only
a
dependency
on
the
API
server.
It
is
itself
just
to
transform
so
take
in
state
transform
state
drop
it
in
API
server.
To
me
that
makes
testing
cap
C
seem
a
heck
of
a
lot
easier
and
just
writing
new
functionality
a
little
bit
easier,
particularly
when
we
have
these
dependencies
of
the
SDKs
for
each
cloud
its
each
each
one
has
their
own
kind
of
videos
and
Chrissie's.
If
we
can
factor
that
out,
I
think
it
would
be
greatly
helpful.
E
Great
great
question,
so
the
first
step
in
something
I'm
actually
pursuing
right
now,
I
think
is-
is
figuring
out
putting
together
basics
for
infrastructure
provider
like
what
would
that
actually
look
like
and
what
what
would
those
resources
look
like?
How
would
be
interaction
between
cap,
Z
and
then
infrastructure
provider?
Look.
Are
there
some
big
anomic
that
we
would
we
need
to
look
at
so
I
think
the
first
thing
is
putting
together
some
CR
DS
and
an
API
that
caps
nee
could
take
advantage
of,
for
maybe
a
small
subset
of
resources.
E
D
E
D
And
another
question:
I
guess
that's
more
of
a
question
for
everyone
else
here,
but
do
we
think
that
for
this
kind
of
proposal,
like
I
know
there
was
it
wasn't
really
clear?
Last
time
when
we
talked
about
how
we
should
do
the
proposal
process,
do
we
think
an
issue?
It's
like
a
discussion
comments
is
enough
or
do
we
want
to
go
further
and
do
like
a
dock
or
like
even
a
cat.
What
do
people
think.
F
I
I
think
if
the
issue
has
enough
discussion,
there's
probably
enough
if
there's
like
a
bigger
design
considerations
that
may
be
like
adopt
for
people
to
collab
collaborate
on,
but
that
for
this
case
here
since
I
will
have
like
a
follow-up.
You
are
to
show
like
apos
here
or
something
feels
like
the
issues.
Probably
enough
conversation
on
it.
Like
I,
don't
know
what
I'll
see
we
put
in
a
dog.
A
A
Well,
so
I
guess
the
next
step,
for
this
would
be
like
a
PR.
Is
that
what
I'm
hearing
we're
ready
to
kind
of
see
those
CDs
come
into
play?
Also,
Richard
commented
with
the
aid
of
a
service
operator
and
I.
Google
also
has
their
infra
like
their
config
connector.
It's
something
that
we're
definitely
looking
at
with
an
azure
like
how
do
we
consolidate
all
of
these
different
operators
that
we
have?
So
it
is
an
ongoing
discussion
internally,
but
yeah.
E
So
I
think
Jason
was
just
the
one
that
said
that
yeah
yeah
I
think
that
makes
sense
they
they
can
be
separate
repos
and
just
have
a
dependency
on
the
API
structure.
I
think
that
would
be
reasonable,
definitely
have
an
open-source,
though
that's
one
of
the
things
that,
like
totally
worries
me
about
like
a
config
connector,
is
I
would
love
to
see.
Other
providers
take
a
dependency
like
this,
but
it
would
be
really
scary
if
that
dependency
is
purely
divers,
not
open
source
is
not
source
available.
So
right,
it's
worrying
me
did
you
have.
E
F
E
It
would
be
kind
of
nice
to
be
able
to
iterate
quickly
on
it
and
then
because
I
mean
honestly
I
think
if
we
get
an
infrastructure
provider,
it
has
to
be
something
that
is
able
to
be
generated,
is
able
to
be
up-to-date
with
constantly
so
part
of
that
is
going
to
be
a
fair
amount
of
R&D
I
think,
but
once
once
it
gets
once
it
gets
done.
That
would
be
a
really
fantastic
thing
to
donate,
like
that
would
be
going
to
get
it
just
here.
It
is
take
it
since
yeah
yeah.
F
D
A
D
Yeah
I
just
wanted
to
talk
a
little
bit
about
what
I'm
you
know.
What's
top
of
my
mind
right
now
what
I'm
working
on
and
which
also
made
me
think
we
should
go
through
the
project
board
after
this,
and
just
like
briefly
touching
on
anything
that's
merged
in
the
last
two
weeks
and
anything
that's
in
progress
right
now.
D
But
yes,
so
the
custom
Koreans
build
thing.
Basically,
the
idea
behind
this
is
I
want
to
be
able
to
use
cluster
API
user
to
test
upstream
kubernetes,
and
so
that's
both
to
run
conformance
tests
and
also
to
eventually
you
know,
maybe
be
able
to
use
cluster
API
for
some
of
those
sake,
as
urates
has
good
jobs,
because
right
now,
a
lot
of
them
use
a
chaos
engine
and
we
just
want
to
have
you
know
both
options
and
I.
D
D
D
G
D
At
right
now,
I
think
there's
three
ways
to
kind
of
achieve.
What
wants
the
first
one
is
to
build
a
custom
image
you
with
that
kubernetes
like
upstream,
build
and
put
that
in
the
image
directly
and
then
deploy
cabs
II
as
usual.
The
second
one
is
use
an
existing
image,
but
then
well
both
of
the
other
two
are
sort
of
less
last-mile,
but
basically
be
able
to
take
an
existing
image
that
has
a
different
cover
names
version
installed
and
then
in
like
the
setup,
so
in
the
comedian
can
think
passing
a
freaky
Radium
commence.
D
That
basically
replaces
the
current
version,
it's
salt,
so
it
pulls
the
new
image
and
then
like
installs
it,
and
that's
definitely
wrong
that.
So
that's
what
I'm
thinking
right
now,
please
take
a
look.
Let
me
know
if
you
have
questions
or
thoughts
or
if
you're
confused
about
what
I'm
working
on
this.
A
A
A
Okay,
so
maybe
we
can
go
through
the
backlog
a
little
bit
and
then
train
move
stuff
and
then
try
and
move
some
of
the
two
dues
and
in
progress
and
see
if
those
are
still
relevant,
because
they
see
this
enhancement
proposal
where
that's
technically
I'm
gonna
put
that
as
a
to
do
until
we
get
a
PR
for
that.
A
D
Of
them
is
actually
in
progress,
but
it's
not
in
here
it's
already
in
the
right
column,
okay,
but
something
great
that
had
happened
this
week.
I
think
it
just
merged
actually,
but
we
switched
to
using
the
upstream
cluster
API
test
framework
so
before
that
Xavier
had
done
some
really
good
work.
To
like
add
the
capability
to
use
the
framework,
but
because
we
weren't
using
v1
alpha
3.
Yet
we
can
actually
use
the
real
framework.
D
D
A
D
A
D
F
A
D
Yeah
yeah
I
was
sort
of
looking
at
that
I'd
still
to
do
because
I
kind
of
paused
on
working
on
it
to
work
on
their
customers,
Cabrini's
build
yeah.
A
A
D
A
D
A
I'll
just
help
for
the
future
add
ipv6
support
to
seola.
You.
A
B
B
F
B
D
So
actually
some
of
the
people
might
seem
far
involved
in
doing
the
work
inconvenience
upstream
to
any
Blighty.
Six
and
I
know
that
that
was
a
block
until
NASA
we
only
had
dual-stack
any
books
for
some
of
our
other
projects
and
they're,
just
starting
to
add
single
stack
right
now,
so
yeah
I
think
you're
right
about
118.
A
F
I
was
looking
at
this
one
I.
Don't
think
this
is
really
anything
to
work
on.
It's
like
describing
the
behavior
that
of
how
clustering
API
works.
It
just
has
to
wait
for
the
sink
rate,
to
reconcile
and
then
find
changes.
I
posted
a
comment
to
ask
like
the
person
who
created
the
issue,
but
he
hasn't
applied
so
okay.
A
D
A
Well,
I'll
just
keep
it
there,
since
it's
the
same
any,
maybe
after,
like
maybe
at
the
next
meeting.
If
we
don't
see
movement
on
some
of
these,
we
can
swap
them
out
to
the
backlog
and
kind
of
do
it
like
that.
Oh
wait
so
in
progress.
I
would
assume
that
all
of
these
are
correct,
but
let's
just
go
through
it
anyway.
Remove
examples
and
switch
at
cluster
template
Cecille
yeah,
that's
in
progress
right
now,
cool
and
then
enable
three
nodes:
AoE
tests,
yeah
cool,
unable
validation,
conversion
and
default,
seeing
webhooks.
D
G
D
A
Yeah,
the
more
I
do
this,
the
more
I'll
get
used
to
which
issues
we
see
I
resigned
and
where
they
are
okay,
get
cluster
cuddle,
Beauty
working
with
cat,
see.
D
Yeah,
that's
the
issue
that
goes
with
that.
First
pull
request:
yeah!
Also
I!
Didn't
you
skip
those
service
team,
intestine
yeah,
so
that
one
we're
actually
really
really
close,
because
we
got
a
lot
of
really
good
help
on
this
and
I
think
there's
only
one
left
out
of
13
yeah.
F
D
B
A
Okay
and
then
supported
by
a
cluster
with
using
a
custom,
Korea's
build
I
know,
so
you
were
working
on
this
right.
Yep,
cool,
okay,
we'll
keep
those
in
progress,
son
and
then
review
in
progress.
You
always
look
okay,
you
just
put
them
there
and
then
done
should
just
all
be
done.
Okay,
and
is
there
anything
missing.
A
So
the
I
think
we
can
do
that
later,
though.
Okay,
thanks
guys,
that
was
great,
now
I-
think
we're
like
actually
up-to-date
with
this
and
it'll,
be
really
easy
to
keep
it
cleaned
each
meeting
and
while
things
are
happening,
okay,
let's
see
if
we
have
I'm
gonna
stop
sharing
for
now
everyone
knows
koukin
was
delayed,
so
all
of
our
talks
will
be
happening
later
and
was
there
anything
else
anyone
wanted
to
talk
about.
D
I
just
want
to
add:
if
anyone
who's,
you
know
joining
the
meeting
and
kind
of
just
watching
the
progress
of
those
projects
and
wants
to
see
things
happen,
please
open
issues
and
put
them
in
the
backlog.
So
we
know
kind
of
like
what
things
are
missing
and
who
wants
what
that'd
be
really
helpful.
Yeah.
A
Cool
productive
meeting
guys
thank
you
and
we'll
see
you
hopefully
in
two
weeks,
but
sign
up
on
that
doodle
poll
and
we'll
lovely,
add
the
new
meeting
time
and
the
day
is
or
github
repo,
because
I
know
right
now.
That's
not
Express
on
our
like
first
page
for
uni,
but
we'll
add
that
once
we
come
to
a
conclusion,
yeah.