►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro + Deep Dive: Azure SIG – Craig Peters & Pengfei Ni, Microsoft
In the SIG Azure Intro and Deep Dive, we’re going to tell you all about why SIG Azure exists and the team behind managing it. From there, we’ll talk about what’s happened over the last few releases, Kubernetes 1.14 and Kubernetes 1.15, as well as some of what’s planned for Kubernetes 1.16. Additionally, we’ll cover considerations for successful deployments of Kubernetes on Azure. Afterward, we’ll have a demo of provisioning Kubernetes on Azure, leveraging Cluster API for Azure, and discuss a little bit about why Cluster API is important to the ecosystem. Finally, and most importantly, we’ll talk all about some of the best ways to get involved with SIG Azure and all of the forums that we’re communicating on!
https://sched.co/OJZe
A
B
You
back
face
so
I'm
Craig
Peters
I
am
a
p.m.
program
manager
at
Microsoft
and
I
work
on
everything
that
is
container
infrastructure
and
upstream
open
source
container
infrastructure
software.
That
Azure
depends
upon,
and
so
kubernetes
is
a
key
part
of
that
and
the
azure
cloud
provider
and
all
the
related
software
is
part
of
what
I
work
on
my
background
is
actually
in
distributed.
Systems
and
output
source
I've
been
with
Microsoft
for
about
six
months
now.
Working
on
these
kinds
of
things
here
is
contact
information
for
myself
and
pink
Bay
yeah.
A
B
So
we
wanted
to
start
by
understanding
who
is
in
the
audience.
So,
first
and
foremost,
I
see
some
friendly
faces
from
the
Microsoft
Cruise,
so
everybody's
Microsoft
feel
free
to
say,
Here
I
am
we
we
contribute
to
making
sure
that,
as
your
runs
great
and
we'll
be
here
to
support
your
workloads
but
I
see
some
of
us
in
the
audience
who
are
not
so
I
want
to
kind
of
understand
who
you
are
at
some
level
and
what
you're
interested
in.
Why
are
you?
B
B
Does
anybody
do
that
you
do
fantastic
great
we've
got
a
couple
more
people
joining
come
on
in
glad
you're
here,
so
has
anyone
in
the
room
used
a
KS
engine,
we're
familiar
where
they
can't
engine
a
KS
engines,
an
open
source
project
that
creates
essentially
it's
a
template
generator
for
creating
as
your
resource
manager,
definitions
of
as
your
of
kubernetes
clusters?
On
azor,
so
any
of
you
familiar
with
that.
No
okay,
that's
good
to
know
how
many
of
you
have
used
as
your
kubernetes
service
to
run
your
clusters
couple:
okay,
everybody
else!
B
B
B
B
So,
let's
give
you
a
quick
introduction
to
who-
who
is
cig
user
and
what's
happening
with
it
so
see?
Geyser
is
a
is
in
the
kubernetes
community
if
you're
not
familiar
what
a
special
interest
group,
a
special
interest
group
is
a
community
of
people
who
are
responsible
for
maintaining
a
set
of
capabilities
in
the
kubernetes
eek
ecosystem.
In
this
case,
making
sure
kubernetes
runs
a
great
or
an
azure.
The
chairs
I'm,
a
newly
elected
co-chair
and
I
share
the
co-chair
responsibilities
with
Stephan
Augustus,
who
works
for
VMware.
B
Vmware,
of
course,
is
very
interested
in
making
sure
that
kubernetes
runs
great
across
all
of
the
platforms.
Vmware
works
with
and
ping
Fei
as
a
technical
lead,
along
with
Cal,
also
from
Microsoft
who
works
in
the
u.s.
very
closely
to
some
of
our
crew.
Here
you
can
learn
more
about
the
governance
of
seizure
from
this
link,
all
the
documentation
for
the
way
in
which
the
special
interest
groups
operate
are
available
online
on
github.
B
So
why?
Why
do
we
need
a
special
interest
group
for
specific
cloud
right
that
that's
a
really
valid
question,
and
the
answer
is
that
it
is
now
becoming
obsolete
to
have
a
special
interest
group
that
is
focused
on
a
cloud.
So
all
of
the
individual
cloud
providers
are
now
working
together
under
a
common
special
interest
group,
which
is
called
a
cloud
provider.
B
So
we've
come
to
a
common
agreement
among
the
kubernetes
community
that
cloud
providers
should
operate
in
a
common
way
so
that
when
people
are
running
their
kubernetes
clusters
on
different
clouds,
you
have
a
common
set
of
expectations
and
ways
in
which
you
work
with
it,
and
so
now
we're
going
to
transition
the
organization
and
governance
around
how
we
do
that
to
a
common
methodology
that
is
sig
cloud
provider
with
sub
projects
under
the
cloud
provider
for
each
of
the
related
six.
So
presumably
I
may
stay
involved
as
a
co-chair
of
the
sub
procedure
provider.
B
There
are
several
related
efforts
that
are
going
to
take
over
governance
of
some
of
the
sub
projects,
which
say:
gazar
has
been
responsible
for
up
until
now.
The
right
now
there's
a
an
effort
called
cluster
API
provider
as
your
that
is
going
to
move
under
the
sig
cluster
lifecycle
project.
That's
also.
The
same
thing
is
happening
for
the
GCP,
AWS
and
and
other
cloud
providers,
and
so
all
of
those
things
are
getting
consolidated.
There's
also
a
project.
A
sub-project
of
cig
azure
called
the
CSI
drivers,
Frasier
that
is
moving
under
as
a
sub
project.
A
B
A
B
Thanks
to
ping
Fei
for
the
Chinese
copies,
so
I'll
be
happy
to
answer
any
questions
about
the
transition.
Oh
there's
one
other
thing,
I
should
say
about
this
transition
about
the
governance,
and
that
is
that
today
there
is
a
very
active
slack
channel
called
seizure.
The
they're
kind
of
two
things
happen
in
that
slack
Channel.
Today
one
is
discussion
about
the
development
and
mechanics
of
management
of
the
azure
cloud
provider,
project
and
engineering
work.
The
other
kind
of
thing
that
happens
in
that
slack
Channel
is
user
support.
B
So
we
have
a
significant
number
of
people
who
use
Azure
and
go
to
the
sig
as
your
slack
channel,
to
get
help
both
from
sort
of
Microsoft,
but
also
from
their
peers
in
the
community
and
that's
a
fantastic
thing.
The
the
obviously
the
engineering
work
is
going
to
move,
understand
cloud
provider,
sig
clefts,
their
life
cycle
and
sig
storage,
the
user
support
things
are
going
to
move
under
a
new
kind
of
structure,
called
a
user
group.
B
A
Okay,
next
Iowa
Inc
employee
introduction
about
the
recent
accomplishment
of
cicada,
so
the
the
biggest
thing
that
we
would
welcome.
Maybe
in
the
future
two
or
three
releases
we
will
move
the
cloud
provider,
especially
all
the
coladas
specific
cost
would
be
out
ho
chi,
so
so
so
far
eager
the
The
Clapper
about
angel
had
already
started
at
the
worker,
and
we
have
already
said
happens
a
trip
over
here
and
it's
also
under
communities
auger
and
the
repo
name
is
color
profit
area.
A
So,
based
on
this,
we
have
also
set
up
some
intern
test
and
validated
its
functionality.
So
for
the
current
committed
call,
all
the
cloud
provider
implementation
have
been
moved,
achieve,
stager
so
and
so
others.
Digital
report
have
also
set
up
some
synchronized
accurate,
different
reports.
So
then
to
empower
for
for
the
clapper
area,
we
could
have
been
design
changes
and
we're
still
making
change
in
the
staging
directory
and
sync
outer,
and
the
vendor.
You'd
use
clarabelle
area,
okay,.
B
B
Say
a
couple
of
words
about
why
this
is
happening.
So,
if
you're
not
familiar
with
the
work
about
the
cloud
providers,
it
might
come
with
a
little
out
of
context.
Important
pieces
of
context
is
that
historically,
the
cloud
provider
code
organically
grew
up
in
the
kubernetes
kubernetes
repository.
The
strength
of
that
was
that
it
was
tightly
integrated.
The
ability
to
run
kubernetes
on
VMware
or
Azzurro,
GCP
or
prom
was
on
bare
metal
was
kind
of
built
into
kubernetes
itself
over
time.
B
That
has
become
very
unwieldy
to
manage
very
disparate
kind
of
implementations,
for
how
you
run
kubernetes
on
different
infrastructures.
In
that
core
codebase,
it
has
bloated
the
repository.
It
has
slowed
down
the
ability
for
the
cloud
providers
to
evolve
and,
most
importantly,
it
forces
the
release
of
changes
to
cloud
provider
code
to
be
in
lockstep,
with
the
release
of
kubernetes
yeah
moving.
B
The
cloud
providers
out
of
tree
into
their
own
repositories
allows
the
different
cloud
providers
to
have
their
own
release
cycles,
and
but
it
also
forces
us
to
pay
a
price,
which
is
that
we
have
to
deal
with
the
sort
of
compatibility
matrix
and
the
testing.
So
how
do
you
version
cloud
providers
say
independently
from
the
kubernetes
release,
so
that
is
all
work.
That's
ongoing
in
the
cig
cloud
provider
group
yeah.
A
Actually,
the
out
of
chiclet
provider
and
also
the
next
one
class,
the
api
provided
asia.
They
also
have
the
Timucua
so
cut
out
the
area
implementations
from
the
cocoa
bean
units
from
the
core
class
API.
So
then,
the
way
when
we
achieve
the
same
experience
across
different
clouds.
So
maybe
your
unionism
cross
cloud
solution,
for
example
your
China
business
using
other
cloud,
but
your
US
business
using
area.
So
you
can,
you
can
reuse
your
work
paste
on
the
same
solution,
but
the
the
detailed
implementation
are
different
on
different
clouds.
A
So
the
next
one
is
about
a
entrant
aciem
where
we
have
already
reached
the
end,
even
touching
for
cloud
private
cloud
provider,
asia
and
we
have
published
and
then
without
you
the
community
at
greater.
So
everyone
can
check
the
details
of
our
work
and
the
touching
is
based
on
a
case
engine.
So
so
we
use
it
has
an
engine
to
set
up
the
touching
environmental,
build
the
latest
releases
of
the
maybe
from
maxsa
branches
and
the
validated
various
of
very
high-tech
cases
such
as
commuted
confirming
test
serotypes,
low
test
and
so
on.
A
And
the
next
item
is
about
a
man
into
the
service
identity,
so
for
area
it
supports
many
many
ways
to
also
write
your
applications.
For
example
the
MSA,
the
you
design
MSI
the
servants
principle,
so
you
can
chose
any
one
and
but
but
for
fall
from
the
cupola
decide
so
completed
it
need
to
initialize
itself
and
read
it
itself
to
the
community
node
so
far
committed
we
supported
using
MSI
with
supporter,
so
in
principle
we
also
support
the
user
than
MSI.
A
But
since
the
legend
released
last
week
of
1.15,
we
also
support
initialized
itself
without
any
credential.
So
so
you
don't
need
this
MSI.
You
don't
need
service
principle.
The
coop
greater
only
initialized
itself
get
the
required
mission
from
the
contains
map
data.
So
it
knows
it
in
turn.
Ip
is
availability
zone
and
is
a
subscription
names,
so
it
could
could
get
all
of
those
mission
and
composed
the
provide
II
and
all
the
node
method.
A
Data
and
the
data
is
read
it
itself
to
the
communities
clutter
okay
under
the
next
one
is
about
the
disk
and
a
fire
plug
in.
So
if
this
can
notify
a
plug-in
are
also
depending
on
the
cow
area
cloud
provider
to
to
make
a
request
to
area
and
ergonomic
curator,
some
possessing
volumes
from
Asia,
so
so
it
is
Canada
fire.
We
have
a
set
up.
The
CS
drivers,
so
design,
then,
is
part
of
job
to
blade
to
to
do
to
shave
the
out
of
shake
our
provider.
A
So
we
have
a
setup
safe
drivers
for
this
tube
air
file
and
it'll
taste,
good
driver
and
a
way
we
we
have.
We
have
planned
the
cheese
that
has
the
intern
test
for
them
and
the
way
we
have
also
working
on
the
windows
Potter
into
CSI,
so
so
far,
CSI
it
for
sales
on
Windows.
This
do
some
more
issues.
We
need
to
stick
out
so
maybe
in
the
next
to
release
1.16
women
other
than
to
the
pod.
A
Okay,
I
know
the
next
is
about
a
load
balancer.
So
you
know,
then:
if
you
use
the
community
service
with
type
load
balancer,
then
either
cloud
provider
would
set
up
area,
load,
balancer
and
the
public
happy.
The
FG
is
for
you.
So
then
you
can
access
your
surveys
using
the
public
happy,
but
a
man
accustomed
may
need
some.
The
idea
just
basically
used
case
H
to
change
the
behavior
of
this
area
load
balancer.
So
we
supported
a
cup
of
annotation,
so
fight
them.
How
you
can
chose
your
load,
balancer
is
only
internal.
A
Maybe
you
can
use
the
public
happy.
Then
I
already
have
a
creditor
in
the
same
research
group
or
maybe
another
research
group
and
the
last
one
is
about
many
new
features.
For
example,
daughter's
Guardian,
the
virtual
machine
CEO,
says
the
availability
zone
the
cross-dressers
group
knows
so
we
have
moved
the
search
feature
such
features
from
paid
from
our
activator
actually
for
Bushra
myristic
assess
and
our
scallions.
For
them
they
have
been
G
and
the
it
is
all
supported
now
in
a
it
has
product
so
another
the
last.
A
B
B
And
finally,
a
lot
of
our
customers
are
running
out
of
ipv4
address
space
and
but
they
also
can't
completely
move
all
of
their
services
into
ipv6
and
and
so
there's
a
need
to
enable
kubernetes
to
support
both
IP
v4
and
v6.
So
what
we'll
drill
into
that?
A
little
bit
so
thankful
talk
a
little
bit
about
the
cluster
API
provider.
A
Yeah
so
for
class,
II
I
provide
a
group,
it
is
actually
said,
have
only
recently
right,
so
we
have
a
cup
of,
inter
from
Microsoft
and
from
platform
9
right,
so
they
have
to
to
set
up
with
the
drape
oh
and
make
the
initial
worker
and
then
in
case
working
for
introduced
to
the
class
API
into
area.
So
today
the
class
API
provide
a
Jew
had
had
been
introduced
in
cig,
collect
lifecycle,
so
it
has
been
the
future
project
unit
and
it
also
prints
the
class
API
related
project,
also
working
in
area.
A
So
the
the
the
repo
here
is
the
the
repo
is
in
the
community
6
August.
So
here
is
a
link,
so
you
can
have
a
try
and
can
studied
and
in
the
Judean,
then
she
set
up
a
cluster
on
area
so
originally
a
way
way
way
we
suggest
using
it
has
engine
she
set
up
with
the
clutter,
but
today
you
can
also
use
this
project,
your
the
class
API
provider
to
provision
the
clutter.
A
But
you
mean
note
until
the
the
project
is:
do
is
earlier
stager.
So
there
are
some
issues
there.
For
example,
the
virtual
machines
go
says
is:
do
not
supported,
yet
it
is
not
spotted,
not
the
body
the
not
because
we
kind
of
added
on
to
him
in
the
cloud
API
provide
Asia
it,
because
the
the
concept
from
the
class
APA
they
don't
expose,
you
know
face
for
for
the
machine,
says
the
concept
and
allow
the
different
provider
to
implement
them.
So
for
for
this
pattern,
we
have
already
proposal
on
the
github
and
published
this
week.
A
A
B
The
neck,
so
the
next
thing
is,
you
know.
The
key
thing
is
that
we
all
know
that
secrets
management
in
kubernetes
is
is
pretty
challenging
and
the
the
real
need
the
enterprises
have
and
been
coming
to
us,
but
over
and
over
again
is
that
they
don't
want
to
move
their
secrets
into
add
into
kubernetes
secrets
the
ability
to
handle
that
has
been
challenging,
and
you
know
we've
decided
to
try
to
support
this
by
enabling
a
CSI,
inline
volume
support
for
mounting.
B
Essentially,
your
secrets
from
other
providers,
and
the
initial
support
has
come
for
as
your
default
and
hashey
court
vault.
So
with
the
release
of
1.15,
which
just
came
out,
you
can
now
make
those
secrets
that
you
use
an
enterprise
service
or
your
existing
infrastructure
available
there.
So
what
we
would
like
is
to
understand
if
these
two
providers
should
have
meet
all
your
needs
or
if
there
are
additional
providers
that
our
customers
want
to
bring
into
that.
B
So
if
you
have
a
key
management
capability
that
you
would
like
to
see
there,
please
come
and
help
us
understand
the
need,
and
if
you
even
better,
if
you
can
also
implement
a
provider,
so
the
the
way
in
which
the
code
is
structured.
It's
it's
very
straightforward
to
implement
your
own
additional
provider
and
add
it
to
the
the
project
so
I'd
love
to
hear
about
that.
B
A
B
A
Yeah
I
know
the
nectar
is
about
the
Rani
equipment
committed
with
the
customers
debate.
So
Kozma
DB
is
cool
about
distributed
database
of
area
and
it
now
sports
preview
feature
it
provided
the
exit
epi.
So
so,
then
you
can
use
this
customer
DB
as
the
storage
back-end
of
your
committed
cluster.
So
if
you
set
up
your
your
Cucaracha
area,
you
can
come
come
Trager
and
Yoda
the
custom
DB,
just
like
the
cup,
the
xad
character
is
interred
on
your
local
machine.
A
So
we
can
do
this
because
the
customers
have
implemented
the
wildlife
of
product
protocol
of
the
xad.
So
then
the
every
protocol
then
required
by
communities
is
implemented
in
the
cosmos
exceed
API.
So
if
you
want
to
try
this
feature,
so
you
can
easily
follow
the
Ike
has
ancient
previous
documents
and
you
can
enable
the
customer
debase
xdd
pipe
and
join
your
community
last
year,
so
with
Kozma,
TBS
and
a
80
it
is
distributed
globally.
Then
your
cluster
could
be
easily
secured.
You,
my
name
in
many
big
deal
just
just.
B
A
Yeah,
ok,
next
one,
so
the
next
one
is
about
the
networking
we
have
been
working
into
is
part
of
the
post.
The
ipv4
and
ipv6
deals
tycoon
in
it.
So
and
you
know
then,
for
the
current
cuneus,
you
could
only
run
one
cycle
either
ipv4
or
either
ipv6,
so
we're
working
the
proposal
TG
either
the
EOTech,
who
native
and
also
we
have
a
actually
one
poor
request.
Today,
it's
still
under
review,
so
we
have
also
listed
the
protocol
here.
A
If
you
are
interested,
you
can
come
into
the
herb
and
if
you
have
any
more
ideas,
you
can
also
come
to
there.
So
for
this
feature,
we
would
like
to
we're
expecting
the
the
feature
would
be
landed
in
next
released
a
1-point
of
16.
So
then
everyone
can
tried
this
feature
and
it
gave
feedbacks
and
also
we
can
improve
it
in
the
neck
to
release
I
hope
so.
B
B
The
reason
to
do
this
is
that
IP
Zack
touches
so
many
pieces
of
kubernetes,
as
you
will
see
with
this
PR
even
to
do
this
very
limited
scope
touches
a
huge
number
of
files,
and
so
we've
had
we've
worked
very
diligently
with
cig
networking
and
all
of
the
other
related
projects
to
make
sure
that
we're
doing
this
in
a
very
careful
way.
So
we
are
not
disruptive
in
how
we
implement
this
yeah.
B
So
I
want
to
talk
a
minute
about
just
how
you
can
become
involved
right,
so
you're
here
to
get
questions
answered
or
I
understand.
You
know
why
we're
doing
what
we
are.
Hopefully,
we've
helped
you
answer
that
and
maybe
now
you're
interested.
So
there
are
several
ways
one
is
you
already
heard
that
sig
azor
is
kind
of
decomposing
into
cluster
api
and
storage
and
so
forth.
B
So
you
know
stay
tuned
for
the
way
the
user
group
is
going
to
work
and
then
get
involved
in
cluster
lifecycle
join
the
mailing
list,
because
that's
where
we'll
communicate
about
it,
but
also
join
the
slack
channel
and
ask
your
questions,
get
help
and
figure
out.
What's
going
on
there,
you
can
participate
in
the
sig
meetings
today,
those
sig
meetings
occur
at
a
time
that
is
not
at
all
convenient
in
this
time
zone
and
we're
very
aware
of
that.
B
In
the
next
couple
of
weeks,
I'm
gonna
make
a
proposal
for
when
we
do
the
sub-project
another
life
cycle.
We're
gonna
alternate
the
meeting
times
between
Europe
friendly
times
and
Asia
friendly
times,
and
that
way
we
can
get
a
broader
set
of
participants
to
get
involved
in
contributing
to
the
community,
starting
with
filing
issues
and
reviewing
PRS.
So
it's
you
know
basic
understanding
involved
in
the
engineering.
If
you
want
to
figure
out
where
you
can
contribute,
we
maintain
a
github
project
board
and
here's
the
link
to
it.
It
we
tried
it.
B
We
do
our
diligence
during
the
meetings
to
maintain
and
groom
it
and
get
new
issues.
You
know
like
first
good,
first
time,
issues
labeled,
bugs
labeled
and
so
forth
and
then
assign
them
to
people
and
track
the
progress
of
those
issues
through
the
project
board
and
I,
encourage
you
to
collaborate
any
synchronously
that
way,
and
with
that
we'd
like
to
open
it
up
for
any
questions.
C
A
A
C
A
Actually,
calico
have
made
some
changes
in
the
senior
plugin
yeah,
so
before
the
latest
release,
you
know
that
the
Calico
could
only
be
wrong
as
a
policy
only
our
area,
because
the
underlying
protocol
is
not
not
supported,
but
today,
with
the
latest
to
relive
it
is
about
the
biggest
line
at
the
overlay
network.
In
so
so,
vector
line
is
also
supported
for
area.