►
From YouTube: Kubernetes SIG Cloud Provider 2019-10-16
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
B
C
D
D
See
us
I
know
we
finally
had
you
know
we
had
a
massive
influx
of
pirates
coming
in
from
a
narrative
team
of
the
emirate
is
responsible
for
storage,
so
we're
we're
getting
to
a
situation
where
we
actually
have.
You
know
a
fully
functional
CSI
driver
for
these
period.
I'd
uses
all
the
new
bells
and
whistles
of
the
latest
version
of
the
sphere,
so
kudos
to
the
HDI
team.
Is
the
M
word
for
doing
that?
B
To
hear
awesome
all
right
extraction,
migration,
I
know:
we've
been
having
discussions
about
getting
the
caps
done,
so
we
did
get
the
beta
approval
for
the
network,
see
and
in
fact,
just
recently,
we've
had
another
cloud
providers
start
working
on
that.
So
we
have
a
contributor
named
shade.
One
who's
been
doing
some
work
there.
So
that's
awesome,
I,
don't
know
if
anyone
else
has
anything
there.
E
A
Yeah,
so
we
have
a
initiative
so
for
folks,
I'm,
just
extra
context
for
its
this
types,
regions
and
zones
we're
using
kubernetes
labels
prefix
with
beta,
because
when
we
first
created
them
years
ago,
we
thought
they
were.
We
were
kind
of
beta
testing
those
labels
now
that
they
are
used
by
pretty
much.
You
know
all
kubernetes
clusters.
We
want
to
G
them
by
just
removing
that
beta
prefix.
So
that's
a
cap
on
that
push
to
implementable
at
this
time
and
we
will
be
working
on
migrating
labels
to
GA
in
a
backwards
compatible
way.
B
A
A
A
I
think
I
need
to
go
through,
which
ones
don't
have
owners
like
I
think
some
of
them
have.
So
when
I
said
that
some
of
them
don't
have
owners.
What
I
meant
was
some
of
them
are
signed,
but
they
may
not
be
assigned,
like
the
person
assigned,
may
not
be
the
best
person
to
work
on
it
at
this
point,
so
we
may
want
to
reassign,
but
we
need
to
yeah
go
through
that
and
figure
out
which
issues
need
to
be
reassigned.
A
B
E
E
G
Yeah
thanks
guys,
so
this
is
just
me
trying
to
understand
why
I'm
why
this
is
doing
this
and
I
apologize.
I
haven't
been
at
the
cloud
provider,
the
sick
cloud
provider
meetings
for
a
while,
so
I
thought
that
we
were
pulling
everything
out
of
the
kubernetes
repo.
But
is
it
this
this
kind
of
seems
that
we're
going
back
on
that
and
I've
read
and
response
and
I
guess
I
just
don't
understand.
A
A
A
And
I
don't
want
to
talk
too
much
about
staging,
but
pretty
much.
It
just
allows
us
to
work
with
all
these,
like
external
repos
in
one
place,
but
then
it
allows
us
to
publish
it
into
actual
separate
repos
that
can
be
consumed
by
other
things,
and
so
we
moved
all
the
yeah.
So
we
moved
all
the
cloud
providers
here
and
happen.
A
So
now
all
the
coronaries
import
the
cloud
providers
in
here,
but
then
we
published
this
exact
repo
to
this
repo
out
here
and
the
main
reason
for
doing
that
is
to
allow
the
adaptive
providers
to
optionally
import
exactly
the
exact
same
provider.
They
have
in
the
core
of
kubernetes
repo
without
maintaining
duplicate
providers,
and
it's
completely
optional,
like
you,
don't
have
to
follow,
you
don't
have
to
import
what's
here,
but
what
we're?
A
What
we
were
finding
is
that
a
lot
of
provide
actually
want
to
pour
over
the
exact
same
provider
implementation
from
what
was
entry
to
out
of
tree,
and
so
this
is
just
giving
you
the
option
to
pull
in
what
was
in
tree
so
like,
for
example,
and
this
year
we
decided
we
actually
want
to
rewrite
the
provider,
and
so
we
we're
not
importing
this
repo
we're.
Just
we
just
built
rebuilt
it
from
scratch
that.
H
B
So
one
other
side
benefit
that
that
wasn't
mentioned
is
that
we
have
in
kubernetes
certain
specialized
pre-commit
rules
about
build
dependency
direction.
So
what
this
allows
us
to
do
is
say
that
things
in
sorry.
Let
me
make
sure
I
get
this
right
way
around
things
in
staging
are
not
allowed
to
depend
on
anything
that
is
considered
to
be
kubernetes
private,
which
is
the
state
of
the
world
once
should
be
the
state
of
the
world
once
these
things
get
pulled
all
the
way
out,
so
by
moving
them
as
far
as
staging.
B
Well,
it's
not
technically
outside
of
kubernetes.
Yet
it
allows
us
to
make
sure
that
certain
build
dependencies
that
would
be
problematic,
don't
get
introduced.
So
it
does
provide
that
sort
of
additional
file
it's
in
that
holding
area,
so
that
we
know
that
it
can
actually
be
taken
out
entirely,
and
it
should
still
continue
to
build
without
introducing
a
dependency
on
anything
that
is
kubernetes
private.
G
A
Yeah,
it's
a
it's!
It's
a
standalone
repo
that
is
just
being
synced
from
the
kubernetes
publishing,
but
from
what's
in
staging
and
so
any
changes,
any
updates
to
the
provider
are
still
happening
from
the
main
tree,
but
you're
importing
it
from
an
external
and
at
some
point
in
the
future,
we're
gonna
cut
off
the
publishing
functionality
so
that
this
repo
becomes
standalone.
You
remove
it
from
what's
inside
kubernetes,
kubernetes
and
then
from
there.
A
A
H
The
references
like
the
the
references
to
anything
and
kate
skates
is
gonna
go
away
as
soon
as
we
can
get
it
gone.
It's
just
much
easier
for
me
to
pull
those
out
momentarily
just
to
get
it
working
and
then
we
can.
We
can
get
rid
of
them,
rewrite
them
so
at
the
bottom
that
the
route
controller
service
controller
stuff,
like
that.
A
G
H
I
explain
this
is
this
is
my
opinion
on
this?
We
initially
were
doing
this
and
then
at
some
point
we
had
sort
of
copied
the
code
over
here,
but
then
we
started
diverging,
and
that
was
something
that
I
didn't
want
to
happen.
So
I
want
people
when
we
actually
do
this.
Migration
I
want
people
to
be
able
to
migrate
to
the
external
cloud
provider
and
use
the
exact
same
code
and
then
once
we
do
that
and
actually
stopped
accepting
commits
on
the
entry.
H
G
A
A
A
A
Okay,
cool,
let's
know
and
I,
think
let
me
just
check
real
quick
what
the
answer
folks
are
doing
just
so.
We
have
a
good
idea
of
where
everyone's
at
okay
cool,
so
they're
importing
it
so
it
so
it's
going
to
be
Google,
Amazon
and
Microsoft
for
for
the
next
little
while
importing
that.
So
that's
good
to
know
all
right
cool
since
Walters
having
like
issues
I
just
keep
going
with
this,
so
I
think
we're
at
the
end
of
our
agenda.
Folks
have
anything
else
they
want
to
discuss.
Otherwise
we
just
end
and
early.
H
A
Based
on
what
you
see,
you
want
to
give
us
a
quick
update
on
like
quick
update
on
that
cap,
because
I
haven't
read
it
the
release.
I
don't
know
like.
Is
it
just
going
to
be
like
a
shirt
secret
resource
for
the
creds
or
are
we
doing
like?
Are
we
exacting
into
something
for
the
creds
like
what
was
what
was
the.
H
A
Because
I
haven't
even
I,
haven't
been
following,
what's
happening
with
this
kept,
but
so
it's
clear
like
we're
not
like.
We
missed
a
117
kept
that
line
right.
Sure.
A
H
A
handoff
explicitly
so
he
did
this
this,
so
maybe
either
you
or
I
could
sync
with
them
and
see.
She's
gonna
keep
working
on
it
or
not.
Okay,
yeah,
let's
sync
offline.