►
From YouTube: Kubernetes SIG-Azure Community Meeting 06-28-2017
Description
A
All
right
welcome
everybody
to
the
second
meeting
of
sig
asier
and
going
to
be
a
pretty
short
meeting
today.
Right
now
we
have
an
open
demo
slot
for
the
first
ten
minutes.
If
anybody
is
really
interested
in
presenting
a
demo,
I
would
ask
that
if
you
could
enter
your
name
into
the
in
jeddah
and
notes
for
attending
today,
that
would
be
super
helpful.
It
helps
us
understand
how
thriving
or
not
thriving
a
particular
sig
is.
A
Second,
is
if
there
are
things
that
you
want
to
add
to
the
agenda
in
work
in
progress
that
you've
got
underway.
That
would
be
great
because
we
can
talk
about
it
if
you
want
and
any
PRS
that
need
attention,
a
review
and
any
specific
updates
that
you
have
for
releases
or
announcements,
so
the
the
the
agenda
doc
I'll
link
it
again
in
the
in
the
chat
it's
also
available
at
Billy,
/,
sig,
edger
and
basically
I.
This
is
world
editable,
so
you
can
go
ahead
and
add
your
topics
at
any
time.
A
B
This
is
Cal
here,
hi
Cal.
How
are
you
sure,
I
have
I,
have
completed
a
plugin
for
cable,
ok,
a
few
weeks
back,
and
it
has
been
on
my
repo
for
quite
some
time
now.
I'm
thinking
should
we
add
it
to
one
eight
action:
let's
review
it
for
sure
and
see
if
it's
a
good
candidate
for
1.8
it
I
can
send
you
the
link
to
the
code
and
I
can
put
together
a
demo.
B
A
A
Okay,
great
anybody
else
have
anything
work
in
progress
that
you
are
looking
at
for
1.8
and
also
it
would
be
good
to
mention
that
1.8
is
technically
a
stabilization
release,
so
the
bar
for
adding
features
to
1.8
is
going
to
be
a
slightly
higher
there's.
Also
the
work
that's
going
to
be
done
to
abstract
the
cloud
provider
out,
which
is
something
we
probably
need
to
talk
about
as
well,
because
that's
a
pretty
big
chunk
of
work
and
as
far
as
I
know,
it's
not
started.
A
So
I'm
adding
that
to
the
list
all
right,
so
moving
down
the
list
of
things
in
worked
in
progress,
we
are
still
working
on
support
for
a
sure,
managed
disks.
There
is
a
pull
request,
that's
linked
in
the
meeting
notes
and
basically,
if
anybody's
feeling
inspired,
please
review
that
check
it
out
comment
on
the
code
right
now,
the
majority
of
the
reviews
have
been
coming
from
woman
Jen
and
it
would
be
great
to
have
more
reviewers
on
that
code,
more
eyes,
the
better.
So
that's
my
request
there.
A
If
it,
you
know,
if
you
have
ideas
about
that,
that
would
be
great
to
have
those
secrets
management.
There
is
an
issue
that
Brendan
has
up
here.
Basically
dealing
with
how
secrets
are
stored
for
Azure
storage
driver
and
I
would
request
that
if
you
could
just
take
a
look
at
that
that
issue
and
add
any
pertinent
information
that
you
have
there.
A
B
C
Not
it's
not
really
related.
This
is
just
about
namespace,
the
secret
or,
as
your
files
goes
into,
rather
than
so
good
going
to
keep
all
that
could
go
to
whatever
storage
you
wanted,
but
it's
about
the
fact
that
the
secret
that's
just
mission,
the
actual
file
driver
is
different
or
it
isn't
visible
to
users
when
it
populations.
A
Okay,
so
get
your
altar
a
Cho
cloud
provider.
Breakout
is
really
interesting
because
that's
going
to
obviate
a
lot
of
this
work
that
we're
doing
and
it's
going
to
make
it's
a
gift
and
a
curse.
I
guess
because
it's
going
to
allow
us
to
tremendous
amount
of
control
and
flexibility
over
how
we
handle
the
cloud
provider.
But
this
is
a
reasonable
amount
of
work.
A
A
D
Well,
it's
not
yeah,
it
was
me
it
was
not
really
a
PR
but
okay,
more
of
a
question
to
see
if
what
the
expected
way
for
cluster
two
scaling
for
us
to
know
that
our
scaling
to
be
supported
eventually
is
going
to
be
ACS
only
outside
of
a
ACS
I.
Think
this
person
open
up
the
questions
regarding
is
tool,
which
is
the
cluster
to
scaler
I.
Think
thank
you
see.
A
A
E
Community
nonsense:
the
tool
is
relatively
tightly
scoped
and
useful,
so
it
would
be
nice
to
see
if
it
meets
your
operational
requirements
for
for
auto
scaling.
I.
Think
its
approach
is
generally
look
for
pods
in
a
pending
state
and
then
add
capacity
until
they
end
up
getting
scheduled,
which
I
think
is
going
to
be
there
like.
One
of
the
big
characteristics
it'll
be
interesting
to
see.
If
that
fits
with
what
you
need
to
have
done.
A
A
A
A
It
would
be
good
for
us,
as
a
sig,
to
review
that
documentation
as
well
to
see
if
there's
anything
that
could
be
impacting
azureus,
or
maybe
people
who
are
who
are
not
updated
or
want
to
update
and
experiment
with
that
version.
So
it
would
be
good
to
be
good
to
know
or
have
more
eyes
on
the
release.
Just
generally
speaking
the
documentation
one
six-six
was
released,
we
can
have
a
go.
That
is
a
it
had
two
security
fixes
in
it,
one
of
which
was
a
sure.
A
The
reporter
was
was,
was
kind
of
to
take
me
offline
and
we
we
got
this
thing
fixed
within
24
hours
and
printed
with
the
code
fix
on
that.
So
thank
you
very
much
Brendan
for
the
extremely
fast
response
and
getting
that
handled,
but
it's
good
to
know
that
we
have
a
solid
security
posture
in
place
and
that
we're
able
to
rapidly
remediating
that
could
be
in
the
cloud
provider
code.