►
From YouTube: Kubernetes SIG-Azure Community Meeting 07 12 2017
Description
A
All
right
welcome
everybody
to
sig
asier.
It
is
Wednesday
July
12
and
we
are
meeting
to
discuss
all
things
about
asher
and
kubernetes.
So
if
you
are
looking
for
something
else,
you're
in
the
wrong
place,
if
you're
looking
for
as
you're
in
the
right
place,
so
here
we
go.
The
the
meeting
agenda
is
that
Dahle
/
sig
azure,
as
you
want
to
go
to
that
document,
take
a
quick
look.
A
It's
interesting
there's
a
lot
of
different
work.
Efforts
currently
happening
on
this
different
teams
within
Microsoft
and
visual
studio
team
is
working
on
various
aspects
as
well.
So
part
of
what
I'm
trying
to
do
is
make
sure
that
everybody
who's
working
on
the
various
aspects
of
integration,
with
key
Balt
and
as
your
Active
Directory
you're
all
talking
to
one
another
and
that
we're
coordinating
our
PRS
and
issues
so
part
of
that
undoubtedly
is
going
to
lead
to
a
features.
A
Repo
entry
for
I'm
assuming
it'll
be
1.8,
but
it
may
it
may
not
depending
on
how
it
goes,
but
hopefully
we'll
get
in
one
eye
and
moving
down
cloud
provider
breakout.
This
is
now
getting
a
little
bit
wider
vision
and
traction,
essentially
the
the
things
that
I've
posted
here.
There's
one
example,
which
is
the
me
Sosa
breakout,
there's
also
Rancher
labs,
has
a
breakout
that
is
actually
written
by
Siddhartha
money.
The
guy
who
wrote
the
original
proposal
and
striving
that
forward.
A
So
I'll
find
the
link
to
the
Rancher
breakout,
but
the
cloud
provider
for
Rancher
actually
lives
in
the
Rancher
repo,
and
so
when
we
do
our
cloud
provider
breakout
we're
going
to
have
such
as
your
slash,
you
know
as
your
CP
or
something
so
that
we
can
manage
the
code
ourselves
and
I'll
simply
be
a
call
from
the
control
plane
to
our
code
there.
So
so
take
a
look
at
those
issues.
I'd
link
to
issue
48
690,
which
is
the
main
tracking
issue
for
that
work.
A
There's
a
pretty
ambitious
effort
to
get
cloud
provider
breakout
into
beta
for
1.8,
while
I'm
seeing
a
lot
of
people
interested
in
that
work
and
talking
about
getting
it
done.
I,
don't
see
a
lot
of
work
actually
getting
done
so
I'm
going
to
be
tracking
that
closely
I'm,
not
exactly
sure
if
that's
going
to
hit
data
and
1.8
or
not,
but
I
believe
we
need
to
stay
ahead
of
that
and
on
top
of
that
curve
and
we're
looking
at
different
groups
within
Microsoft
and
elsewhere
that
we
could
leverage
to
get
some
that
work
done.
A
B
Just
wanted
to
share
this,
mostly
mostly
mostly
hopefully,
fingers
crossed
the
azure
sdk
Travis
going
in
and
then
after
that,
I
could
look
through
the
managed
disc
PR,
which
is
based
on
that
and
I'm
okay
with
and
ready
to
merge
it.
But
if
anyone
else
wants
to
take
a
look
at
the
managed
disc
er,
please
do
it
so
in
the
next
two
days
we're
going
to
try
and
get
that
it
I.
A
Great
thanks,
Brent,
all
right
so
PR
is
needing
attention
review.
We're
not
going
to
go
through
these
in
great
detail,
but
I
just
wanted
to
point
these
out.
Doc's
pull
4080
to
is
that
is
a
change
to
semana
related
documentation
regarding
services
and
how
you
annotate
the
load,
balancer
IP
stuff
to
get
internal
load
bouncer.
A
C
C
The
nodes
will
all
kind
of
go
into
not
ready
state
for
like
15
to
17
minutes,
and
then
the
couplet
will
reconnect
and
everything
will
come
back,
and
it
just
reminded
me
of
the
issue
that
you
had
potentially
with
nodes
going
into
not
ready.
So
I
wanted
to
highlight
that,
and
it
looks
like
some
work
may
be
going
into
client
go
to
change
the
way
that
the
TCP
connection
to
the
API
service
happens,
and
it
looks
like
it's
a
kind
of
across
the
board.
D
I'm
glad
to
see
if
we
could
turn
in
the
PR
manually
in
our
stack
to
see
if
it
actually
helps
to
be
honest,
I
haven't
really
seen
it
for
the
last,
maybe
month
or
the
last
time.
I
discussed
it
so
I'm,
not
too
sure.
So
maybe
something
occurred
on
the
either
side.
I'm,
not
really
seeing
any
errors
about
my
API
being
troubled.
A
A
So
yeah,
ok,
well
good!
Well,
we'll
keep
an
eye
on
that,
and
if
we
hear
more
about
that,
I'll
track
this
issue
and
we'll
make
sure
that
we're
staying
on
top
of
that
release
updates
really
quickly.
1.8
is
steaming
forward.
The
release
team
is
organizing.
If
you
are
interested
in
a
release
role
and
want
to
know
more
about
it,
you
can
definitely
contact
me
and
I
will
fill
you
in
there's.
Also
a
spreadsheet
available.
You
should
find
that
where
nominations
are
happening
for
different
roles
and
I
have
don't
link
to
that.
A
Yes,
self
nominate
if
you're
interested
in
getting
involved
in
the
release
process.
If
you
do
just
be
mindful
that
it's
a
it's,
a
relatively
a
big
commitment
in
some
cases
but
I
think
it's
an
absolutely
fantastic
thing
for
us
to
get
more
involved
in
and
yeah
and
whoever's
taking
notes
anonymous
drafts.
Thank
you
from
the
bottom.
My
heart.
A
A
Ok,
lastly,
so
we
talked
about
the
cloud
provider
break
out
a
little
bit
and
there
is
an
interesting
thread.
That's
going
on
about
this.
This
thing
that
was
originally
envisioned
as
cig
cloud.
Now,
it's
sort
of
working
group
cloud
and
more
focused
on
the
minutiae
of
the
cloud
provider.
Breakout
I
posted
to
a
link
to
the
thread
might
want
to
just
look
it
over
and
see
what
people
are
thinking
there.
There's
there's
probably
some
proposals
that
are
going
to
come
through
in
regards
to
that
as
well.
A
But
at
any
rate,
the
plan
is
just
to
kind
of
keep
an
eye
on
on
where
that's
going
and
not
have
that
in
any
way
stopped
us
from
moving
forward
on
our
own
breakout
work,
but
to
just
be
mindful
that
there's
the
the
governance
around
that
may
be
shifting
and
we
just
need
to
keep
an
eye
on
it.
So
that's
a
lot
of
the
work
there.
Does
anybody
have
any
other
announcements
they'd
like.
B
People
have
cycles
to
take
a
look
at
are
interested.
I
would
definitely
love
some
eyes
on
that
PR,
it's
just
the
very
first
beginnings
of
it,
but
but
given
that
it's
shaping
the
way
that
we'll
do
it,
it's
getting,
people
clocks
will
be
great.
Where
do
we
find
up
here?
I
can't
remember
the
number
up
top
of
my
head.
If
you
look
and
see
ours
that
are
authored
by
me,
okay,
it,
it
says
something
like
initial
use,
of
instance,
metadata
server
or
something
like
that.
I
can
also
put
it
in
the
notes.