►
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
Let's
see
this
is
a
meeting
of
the
azure
provider
for
cloud
provider
so
project-
and
this
is
the
meaning
of
that
follows
the
CNCs
rules
of
conduct.
So,
let's
all
be
nice
to
each
other
and
it's
being
recorded
and
will
be
posted
to
YouTube
I'm,
going
to
quickly
paste
the
link
to
the
notes
document
into
the
chat
and
if
you
could
just
add
your
name
to
the
attendees
and
thank
you
jack
for
taking
notes.
A
C
C
C
C
A
B
B
C
A
B
It
doesn't
sound
like
we're
engaged
very
much
so
that
sounds
like
the
answer
is
yes,
I
would
imagine,
any
level
of
active
engagement
would
probably
move
the
needle.
So
the
question
is:
do
we
do
we
do?
Are
we
incentivize?
Do
we
want
to
as
a
single
cloud
writer?
Do
we
care
about
the
velocity
of
this
very
slow
moving
train
I
mean
if
this
trains
are
moving
for
years?
At
this
point,
right.
B
A
A
They're
aligned
for
all
of
the
cloud
providers
I
think,
but
the
other
question
is
is
if,
if
somebody
has
the
mental
and
time
bandwidth
to
stick
their
nose
in
at
this
late
hour
into
this
particular
back
in
interface
or
whether
we
should
just
wait
for
it
to
land
and
then
proceed
I,
don't
know
it's
inside
understand
it.
I
can't
make
any
judgments
about
whether
or
not
there's
anything
happening
there.
That
will
be
good
or
bad
for
the
azure
cloud
provider
in
particular.
A
C
At
least
this
PR
is
going
to
introduce
the
new
cid
and
then
it's
gonna
introduce
all
the
spec
that
require,
and
then
the
assumption
is
each
cloud
provider
creates
their
own
repo
and
then
makes
the
changes.
That's
required.
The
way
extract
the
credential
provided
out
from
in
three-quarter
fee
so
similar
to
how
we've
been
doing
out
of
three
further
a
couple
of
releases.
I
think
this
will
also
span
probably
one
or
two
more
releases
and.
B
C
C
A
B
It
so
those
big
three
just
listed
we're
all
in
the
same
boat.
Together
we're
dragging
their
feet
to
get
out
of
get
out
of
tree
okay,
I
understand
right,
I
mean
it
certainly
seems
based
on
my
anecdotal
observation
of
how,
as
your
specific,
it
seems
like.
There
has
long
been
a
very
tight
coupling
between
kubernetes
releases
and
as
your
fixes,
and
that
has
concrete
negative
ramifications,
because
the
kubernetes
release
process
is
very
structured.
B
I
mean
I
think
possibly
it's
just
up
to
us
to
you
know
internally,
raise
like
sort
of
concrete
pros
and
cons
of
continuing
to
delay.
I
think
we've
got
lots
of
data,
you
know
so
many
of
the
wait.
So
many
of
our
actions
over
the
past
two
or
three
years
have
been
concretely
affected
by
the
fact
that
we
are
intrigued.
A
So
I
I
would
love
to
prioritize
the
finishing
of
getting
out
of
tree.
It's
just
not
clear
to
me
that
you
know
we're
waiting
for
this
PR
tool
and
about
the
registry
external
registry,
whether
or
not
we
can
actually
contribute
to
that
PR
landing
correctly.
It
seems
like
it's
sort
of
at
the
95%
done
and
where
our
summary
base
and
testing
I
don't
know
that
we
can
actually
materially
move
it
forward.
C
C
A
B
Does
that
make
sense
what
I'm
saying
in
ish
and
Craig?
So
the
fact
that
is
there's
this
new
out
a
tree,
credential
provider,
just
I,
assume
that
there's
long
been
a
credential
provider
that
you
just
get
for
free
by
being
a
part
of
the
kubernetes
project
right,
and
this
is
forcing
that
functionality
to
be
cloud
provider.
Specific
I,
I,.
B
Velocity
like
to
me
as
an
as
an
engineer.
Those
benefits
are
very
clear,
not
having
a
1/18
specific
version
of
the
Azure
cloud
provider
or
one-seventeen
specific
version,
but
instead
being
able
to
kind
of
you
know,
do
that
plumbing
on
our
own,
according
to
our
own
requirements
and
our
own
velocity,
our
own
engineering
investments.
That
seems
massively
beneficial.
A
B
A
A
A
Based
on
this
assessment
that
from
looking
at
the
issue,
one
can
only
infer
that
all
of
these
issues
are
on
tracks
were
being
complete
by
119
and
that
the
credential
provider
extraction
is
still
waiting
on
the
other
PR
and
then
we'll
we'll
hear
back
from
big
fan
books
about
whether
that
is
our
correct
assessment.
Okay,.