►
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
Okay,
I've
started:
recording
welcome
to
the
hazard
provider,
understood
club
provider
sub-project
meeting
the
first
attempt
I'm
sure.
Is
it's
hard
to
say
it's.
It's
our
first
attempt
of
having
this
meeting
at
this
time
and
I'm
very
happy
to
see
that
we
have
a
number
of
people
joined,
we'll
ignore
the
five
of
us
are
in
the
same
room
together.
So
in
this
meeting
this
is
conducted
under
the
CN
CF
code
of
conduct
and
in
summary,
it
means
be
good
people
to
each
other.
This
meeting
is
being
recorded
and
will
be
posted
to
the
internet.
A
So
don't
say
anything.
You
wouldn't
want
your
mom
to
hear
with
that.
I
am
going
to
paste
the
tender
notes
document
into
the
chat
and
ask
if
anybody
wants
to
volunteer
to
beads
I
already
did
that
that's
nice
and
please
add
your
name
to
the
attending
and
ask
if
anybody
wants
to
volunteer
to
be
the
note-taker
for
this
session.
I
can
update
well,
thank
you
Steven.
So.
B
C
B
You
should
go
rather
room
and
introduce
ourselves
real,
quick,
so
I
guess
we
can
go
first
since
you've
already
started
speaking,
go
for
it,
ready,
rambling,
so
hi,
my
name
is
Steven
Augustus
I
am
one
of
the
former
chairs
of
signature.
Now
the
sub
one
of
the
sub-project
owners
for
a
provider
Adger
under
Sid
cloud
provider,
also
one
of
the
signatures
and
sig
release
chair
so
hey.
A
E
A
F
A
C
C
A
B
A
G
A
A
C
C
B
Sorry
we
were
jokesters
today,
so
okay,
so
for
context
for
people
who
are
on
the
call.
Yes,
the
goal
overall
is:
there
are
several
providers
that
exist?
What
we
call
entry
kubernetes
right
so
intrigued,
ooh
brunette,
is
essentially
anything
that
you
would
consider
to
be
within
the
kubernetes
kubernetes
repo
right.
So
we
kind
of
have
you
know
from
the
start
of
the
project,
we've
kind
of
had
something
of
a
mono
repo
situation
going
on.
B
We've
done
a
lot
of
work
over
the
last
few
years
to
start
to
trim
some
of
that
fat
migrate
them
out
into
migrate,
various
sections
of
code
out
into
their
own
repos.
So
recent
you
know
recent
things
are
you
know
the
some
of
the
volume
providers
cubed
CTL
is
is
going
to
be
one
of
the
ones
that
are
soon
coming
out
of
entry
cube.
Adm
is
also
something
that
they're
they're
pulling
pulling
out,
but
on
our
side
one
of
the
larger
efforts
is
our
side,
as
in
cloud
providers.
B
Overall,
I'm
I'm
at
VMware
I
just
have
to
be
at
Microsoft.
Today
is
detangling
all
the
the
entry
cloud
code
from
the
from
the
entry
kubernetes
kubernetes.
So
that's
very
involved
because
of
the
ways
that
we've
coupled
ourselves
to
the
codebase.
So
some
of
those
ways
are
the
credential
providers,
the
way
that
we
handle
essentially
node
identity
in,
and
so
that
affects
the
way
that
we
bring
up
clusters.
There's
also
what
else?
The
storage
serve
some
some
other
stuff
that
we
have
handled
in
the
past,
the
things
that
are
and
package
util
mount.
B
So
basically,
we've
been.
You
know
over
the
past
few
cycles
figuring
out
exactly
what
what
requirements
the
entry
cloud
providers
have
that
are
pinned
to
all
of
the
entry
code
and
we've
gotten
quite
a
bit
of
the
way
there
and
I
think
we
have
like
three
or
four
real
things
left
to
pull
out
before
that.
B
That
would
then
enable
us
to
move
from
what
is
it
staging
slash
legacy
cloud
providers
after
blah
blah
blah
blah
blah
into
kubernetes
cigs
cloud
provider,
Patrick,
okay,
and
that
you
know
getting
you
know
getting
the
code
out
of
tree-
allows
us
to
move
a
lot
faster,
not
be.
You
know,
build
our
own
suite
of
tests
around
that
code
be
able
to
version
independently
from
the
kubernetes
version.
Versioning,
which
happens
on
essentially
a
quarterly
basis
and
lots
of
other
sweet
things
that
I'm,
probably
forgetting
but
but
yeah.
A
E
E
B
E
B
So
I'm
wondering
to
context
for
people
on
the
call
who
are
not
aware
of
what
caps
are.
Caps
are
kubernetes
enhancement
proposals.
These
are
basically
the
canonical
resource
for
proposing
change
to
the
project
right.
So
basically
you
you
type
up
the
cap
that
includes
your
your.
You
know
fun
table
of
contents.
The
you
know
the
the
really
sign-off
checklist,
which
is
a
set
of
things
that
the
release
team
expects
you
to
have
in
place
for
us
to
consider
an
enhancement.
B
An
enhancement
is
a
large
body
of
work
in
the
project,
as
opposed
to
a
feature
which
is
something
that
you
can
potentially
execute
on
within
one
cycle,
so
an
enhancement
can
be
composed
of
multiple
features,
but
anyhow,
this
is.
This
is
basically
one
to
describe
a
an
instance
metadata
service
right,
so
a
way
to
describe
the
the
attributes
of
a
node,
and
the
reason
this
is
important
is
because
it
comes
up
for
yeah.
B
Let's
also
link
the
cap,
I'm
gonna
get
it
right
there,
I'm
popping
that
the
kept
in
the
chat
and
we'll
pop
it
on
the
notes
as
well.
So
this
is
essentially
like
how
do
we
describe
in
it
right
and-
and
the
reason
this
is
important-
is
because
standard
like
by
standard.
The
way
we
were
describing
notes
was
based
on
information
that
we
were
getting
from
the
cloud
provider
plus
some
I
forgot
exactly
how
it
works.
B
Yeah,
it's
a
file
plus
it
can
be
a
file,
but
it
can
also
be
inferred
from
the
metadata
service
and
in
adder
two,
but
varying
cloud
providers
have
the
ability
to
infer
information
about
a
node
like
external
IP
addresses
or
something
right
from
there.
The
you
know
the
respective
metadata
services
right.
So
the
thought
behind
this
is
like
well
what
if
we
could
create
a
metadata
service
that
is
generally
useful
right,
which
allows
this
thing
with
which,
if
we
use
that
we
could
potentially
reduce
the
the
API
request
to
each
cloud
provider.
B
So
that's
in
discussion.
It
seems
like
things
like,
of
course,
this
is
when
I'm
assigned
to
review
okay,
so
yeah
so
I
think
we're
kind
of
in
a
holding
pattern
right
there.
We
need
to
come
to
the
psych
lab
provider
meeting,
but
we
need
to
get
appropriate
context
from
things
a
about
what,
where
this
is
that
yep.
A
A
B
B
G
F
A
B
B
B
A
B
C
B
Know
so
to
hang
Fay
and
Andy,
or
two
of
the
primary
maintained
errs
on
the
cloud
provider
Azure
of
work,
and
you
know
I'm
well,
I'm,
like
the
primers
in
container
for
the
cluster
API
after
stuff
and
like
there
are
common
patterns
that
come
up
over
and
over,
like
how
do
I
create
a
load
balancer
or
how
do
I
create
resource
groups
or
you
know,
or
security
groups,
or
so
on
and
so
forth.
Right
there
are
common
things
that
you
need
to
do
in
Azure
and
and
it's
starting
to
look
like.
D
B
I
mean
this
becomes
generally
useful
for
not
just
kubernetes
code,
but
you
know
think
if
you
have
the
opportunity
to
use
use,
Azure,
SDKs
and
in
different
venues,
say:
building
terraform
modules
right.
If
we
can
define
again
this
common
abstraction
layer
or
for
the
azure
sdk
I
think
it
would
be
generally
useful
to
both
the
kubernetes
community
and
everyone
else
right.
B
C
C
E
B
E
E
A
B
B
Now
we're
at
the
place
where
we
need
to
do
a
bridge
position
which
is
moving
the
moving
the
cloud
provider,
a
short
code
from
kubernetes
github.com,
slash,
kubernetes,
slash
cloud
provider,
Azure
to
Humber,
Nettie's,
github.com,
slash,
kubernetes,
cigs,
slash
cloud
provider,
Azure
right,
so
kubernetes
things
that
org
and
github
is
a
canonical
location
for
the
code
that
is
produced
from
any
any
sink
right.
There
is
a
difference
between
poor
code
and
sync
code,
and
a
lot
of
it
is
kind
of
vestigial
kubernetes
stuff.
B
C
B
B
In
terms
of
like
adoption,
for
you
know
the
the
out
of
tree
cloud
provider,
the
out
of
tree
cloud
providers,
essentially
ven
during
in
the
current
injury
provider
and
like
right
now
before
the
entry
provider
becomes
out
of
tree,
it's
probably
the
right
time
to
pull
the
trigger
on
that.
So
we
need
someone
who
has
repo
repo
admin
role.
That's
our
that's
everyone!
Really!
B
From
a
where,
so,
the
github
administration
team
is
a
sub
project
within
sig
contributor
experience
that
has
all
the
keys
of
the
castle
for
the
various
kubernetes
orgs.
So
that's
kubernetes,
kubernetes,
SIG's,
Serenity's,
client,
kubernetes,
CNI
tinker
Beck
yeah
concur
Bernays
security.
So
all
those
orgs
fall
under
the
github
administration
team
right,
so
we
essentially
be
moving
from
one
of
ours
to
one
of
ours.
Okay,
Oh
shouldn't
be
too
labor-intensive.
B
B
B
A
A
A
B
So
there
is
a
process
by
which
you
can
request
the
github
administration
team,
help
you
out
with
stuff
and
within
the
kubernetes
board
repo.
There
is
so
that's
true,
github.com
/
kubernetes
/
org.
If
you
want
to
check
that
we
go
out
and
that
repo
we
have
this
cool
tool
called
parabola
or
parabola
source
I,
don't
know
it's
pronounced,
but
it
contains
the
configs
for
all
of
our
repos
rate,
so
that
is
from
like
repo
of
that's,
like
from
org
settings
to
repo
settings
to
to
the
teams
that
live
in
our
github
orgs.
B
B
So
this
should
be
fairly
simple,
since
usually
one
of
the
things
that
hang
us
up
is
like
making
sure
that
a
repo
conforms
to
kubernetes
standard,
so
it
has
owners
files
have
security
contacts.
The
the
imports
within
the
repo
are
compliant
to
CNCs
licensing
policies.
So
on
and
so
forth,
and
and
then
finally,
that
the
the
migrator,
which
is
some
member
of
the
github
administration
team,
has
admin
access
to
the
repo
because
they
have
admin
access
everywhere.
B
A
B
G
B
So
a
lot
of
the
stuff
that
we
mentioned
and
you'll
see
occasionally
on
these
meetings
that
there
is
a
there's
kind
of
a
fuzzy
line
between
some
of
the
cloud
provider,
Azure
stuff
and
some
of
the
cluster
API
either
stuff.
That
has
been
done
purposely.
But
what
we
need
to
do
is
make
sure
that
everything
that
we're
thinking
about
internally
at
Microsoft,
where
are
that
Microsoft,
is
thinking
about
internally.
It
feels
weird
I'm
here
and
I'm,
not
here.
B
You
know
it's
probably
his
properly
tracked
upstream
right,
so
moving
into
moving
into
117
cleaning
up
any
project
tracking
boards
that
we're
working
on.
So
we
have.
We
have
the
cigar
board,
which
line
and
also
the
cluster
API
board.
The
cluster
API
board
is
in
as
a
repo
specific
one
might
consider
your
input.
Okay,
cool.
B
B
B
A
B
B
D
G
A
F
B
B
B
Right
so
it
sounds
like
this
was
useful
to
at
least
one
person,
which
is
a
start,
which
is
a
great
story,
so
we'll
we'll
keep
plugging
at
it
we're
so
the
meetings
alternate
times
every
two
weeks.
One
is
an
AIPAC
friendly,
which
is
this
slot.
It's
not
quite
every
two
weeks.
Every
slice
them
up
twice
him:
okay,
Oh
sending.
Would
yes
all
right.
A
So
it's
close
to
every
other.
It
turns
out.
It
was
harder
to
code
everything
really
with
the
time
changes,
calendars
and
we're
right.
Wasn't
it
wasn't
the
calendar?
It
was
the
tool
thanks.
It
was
our
tooling
for
that
anyway.
Thank
you.
All
for
joining
I
am
going
to
stop
the
recording,
bye
and
we'll
have
to
see
you
guys
in
a
couple
of
weeks
and
I
will
post
this
to
the
YouTube
channel
as
soon
as
I
can.
Thank
you
guys.
I
mean
I
thanks.