►
From YouTube: Kubernetes WG IoT Edge 20190703
Description
July 3 2019 meeting of the Kubernetes IoT Edge Working Group - formative discussion of the Edge Security White Paper
A
Okay,
ready,
okay,
yeah,
so
we're
ready
with
the
security
edge
security
challenges.
White
paper
I
think,
ready
to
publish.
We
did
a
final
integration
over
the
last
couple
of
weeks.
Everyone
who
had
been
contributing
kind
of
got
in
last
comments,
never
going
to
be
perfect,
so
we
had
some
stuff
that
was
kind
of
final
decisions.
Just
earlier
today,
I
closed
out
some
comments
that
were
from
long
ago
that
seemed
to
have
been
resolved.
A
We
had
some
last
stuff
that
was
edited
by
jono
and
who
said
he
may
or
may
not
make
the
meeting
tonight,
and
then
I
added
some
final
section
in
so
I
think
we're
good
and
now
the
question
is,
you
know
like:
what's
the
the
right
way
to
publish?
Well,
we
had
done
some
research
on
that
as
a
group
and
had
found
that
there
is
great
support
from
the
cncf
to
push
this.
B
A
And
we
just
have
to
make
it
officially
announced
that
this
paper
is
ready
and
coming
out
of
this
working
group.
So
basically
dan
tell
us
what
it
is
that
we
should
do
next
and
I
think
we're
we're
ready
to
put
this
out.
A
Okay,
let
me
let
me
review
and
then
and
moritz
if
you
want
to
jump
in
to
feel
free,
because
I
I
think
I'm
reviewing
our
group
chat
and
I
think,
let's
see
here,
I
think
it
was
bernhard-
had
reached
out
yeah
to
ask
about
the
process.
A
I'm
taking
a
look
here
looks
like
we've
got
some
comments.
Let's
see
here,
okay,
there
was,
there
was
one
individual
who
kind
of
jumped
in
but
the
same
thing
she
was
a
consultant.
So,
let's
see,
we've
got
we're
supposed
to
write
an
email
to
pr
so
obviously
public
relations
at
cncf.io,
and
that
sounds
like
the
first
place
to
go
with.
A
Dot,
io,
okay,
yep
and
I
think
that's
our
next
path,
because
everything
else
yeah,
so
it
was,
let's
see
dan
cohn
at
the
cncf
said.
If
you
email
pr,
cncf.io
we'd
be
happy
to
help.
You
feature
it
on
the
kubernetes
and
or
cncf
blog.
I
think.
B
A
Since
it's
an
email,
I
think
all
of
the
all
of
the
leaders
of
this
working
group
should
be
included,
and
then
I
think,
all
of
the
authors-
and
I
think
we
should
just
write
that
email,
I'm
happy
to
write
the
mail
and
and
say
here
we
go
and
I
have
a
look
and
then
basically,
everyone
who's
in
who's,
leading
the
working
group
or
who's
involved
in
the
paper
would
be
apprised
of
the
details
of
what's
planned
and
where
it
goes.
A
That's
obviously
the
start
of
promotion
for
it,
because
it's
a
living
document
that
stays
in
the
working
group
and
all
over,
hopefully
all
over
the
kubernetes
community
will
not
only
look
at
it,
but
we'll
want
to
also
contribute
to
enhance
it
so
yeah.
I
can
share
my
screen
and
actually
show
what
I
did
at
the
top
here
and
based
on
some
verbal
contributions.
A
couple
of
side
conversations
I
had
with
with
steve
wong
I
decided
it'd
probably
be
best
to
attack
him
on
the
end
of
the
author's
list
too.
A
So,
okay.
So
what
we
have
here
is
this
follows
the
standard,
cncf
format,
and
then
I
put
here
the
I
I
can't
remember
if
this
was
the
day
that
we
actually
kind
of
like
looped
back
and
did
stuff,
but
it's
not
really
that
important.
What's
important
is
this
first
public
version
1-0
and
I
think
solid,
we're
ready
now
and
then
I'm
not
sure
the
last
time
I
did
this,
but
I
think
I'm
supposed
to
go
and
do
refresh
there.
A
We
go
okay
table
of
contents
refreshed
and
then,
as
you
can
see,
on
the
right
hand,
side,
we
do
not
have
a
whole
bunch
of
comments
anymore.
It's
all
been
temporarily.
The
comments
are
quelled
and
and
then
we'll
we
can.
B
Okay,
well
I'll
yeah,
let's
think
about
it
today,
offline
with
other
guys
as
well
and
and
send
it
I'm
I'm
out
of
the
office
tomorrow
and
and
and
friday,
but
I'll
be.
You
know
in
the
access
of
the
email
and-
and
I
can
follow
up
on
on
this,
so
so
it
wouldn't
be
a
big
problem.
I
think
maybe
maybe
it's
the
best,
I'm
just
thinking
out
loud.
A
Sure
sounds
good.
In
fact,
why
don't
I?
Why
don't
I
plan
to
do
that
and
include
all
the
authors,
the
paper
and
then
and
then
will
this
one?
We
feel
like
it's
good,
maybe
send
it
next
week
when
people
are
back
because
we've
got
a
bunch
of
a
lot
of
holidays.
You
know
it
was
yeah
yeah
and
then
it's
fourth
of
july
in
the
u.s.
So
next
week's
probably
a
better
week
to
kick
it
off
so
we'll
use
this
week
to
refine.
B
A
B
Are
are
you
planning
to
go
to
the
the
san
diego
event.
A
Yes,
yeah,
I
think
I
I
submitted
that's
the
which
one's
that
that's
the
embedded
embedded
linux,
oh
you're,
doing
like.
A
Oh,
absolutely
absolutely
yeah
and
we'll
we'll
be
there.
Edgeworks
will
be
their
full
presence
eclipse
foundation,
be
their
full
presence
and
yeah
yeah.
Okay,
there's
also
a
san
diego
event
in
august,
which
is
linux,
foundation,
event
embedded
linux,
world
or
whatever,
and
I
submitted
a
talk
and
I
didn't
make
it
so
so
I
don't,
I
don't
think
I'll
go
down
if
I.
B
B
B
B
A
A
B
A
B
A
B
Sounds
good
yeah,
so,
let's,
let's
keep
on
that
as
well
on
the
agenda
for
for
the
next
week
where
everybody
is
is
back
from
vacations
and
and
try
to
put
proposals
for
that.
I'm
I'm
trying
to
organize
with
a
couple
of
my
colleagues
as
well
to
to
do
some
other
sessions
as
well.
So
I
hope
I'll
go
there
as
well
and
yeah,
as
you
said,
if
if
we
can
get
a
session
and
maybe
see
if
anybody
is
interested
to
sponsoring
a
meeting
or
meet
up
or
something
and
you
know
have
have
some,
you
know
off-site.
B
A
That's
nice
yeah,
it's
nice
to
to
have
the
the
one
topic
be
a
success
topic.
I
I
did
want
to
comment
a
little
on
the
last
meetings,
harbor
presentation
and
just
the
the
large
volume
of
challenges
around
you
know:
image,
guarding
images
and
just
cloud
and
data
center
and
the
fact
that
at
the
edge
those
problems
are
exacerbated,
but
I
really
enjoyed
the
presentation.
I
thought
there
was
a
lot
of
interesting
stuff
there.
B
A
B
A
link
here
what
we
did
also
give
me
just
a
second
to
find
it
so.
B
I
started
also
so
if
people
don't
want
to
to
follow
all
the
recordings.
B
Yeah,
so
I
I
got
a
youtube
channel
where,
where
I'm
planning
to
put
only
the
presentations
there,
just
for
people
that
want
to
follow,
don't
want
to
follow
all
the
all
the
discussions
and
all
the
recordings
cool.
So
we
we
have
the
last
two
there
and
you
know
everything
that
that
comes
along
in
in
the
next
sessions.
We
will
put
it
there
as
a
material
for
people
to
to
you
know,
follow
all
the
all
the
presentations
excellent
and
also
while
we're
talking
so
another.
Congratulations
on
your.
B
A
Yes,
yes,
in
fact,
I
think
the
the
the
steve
maybe
had
asked
it,
or
maybe
several
people
had
asked
when
it's
ready
to
do
a
demonstration
in
this
working
group
of
so
we
did
the
announcement
and
we're
still
getting
kind
of
the
official
code.
You
know
the
the
official
eclipse
you
know
foundation
release
of
the
code
base
right,
which
you
got
to
go
through
a
license,
review,
process
and
stuff
of
various
things.
A
B
A
You
know
allows
you
to
attach
to
your
edge
and
whatever,
but
the
most
important
stuff
to
discuss
in
this
working
group
is
how
we've
linked
the
io
fog.
You
know
control
plane,
which
is
like
this.
The
you
know
where
the
control
plane
sits
is
anywhere
cloud
data
center
or
at
the
edge,
but
it's
from
there
down
is
your
edge,
and
at
that
point
we've
implemented
a
fork
of
microsoft's
virtual
cubelet.
A
That
represents
a
large
number
of
edge
nodes
on
the
blood
makes
native
to
kubernetes
custom
operator,
custom
resource
definition
and
custom
scheduler
and
yeah
makes
makes
the
what
we're
trying
to
put
out
there
in
the
industry.
Is
this
concept
of
making
kubernetes
edge
aware
so
leveraging
attributes
that
are
edge
only
gps,
location
latency
to
the
next
hop
the
price
of
bandwidth?
A
These
are
all
things
that
kubernetes
should
be
able
to
use
to
schedule,
but
it's
not
going
to
do
it
in
the
default
scheduler,
it's
not
enough
to
like
tuck
stuff
into
affinities
and
and
pack
labels
with
data
like
you
really
want
to
be
having
a
custom
scheduler
with
logic
that
you
know
that
takes
care
of
these
things
and
that's
the
architectural
approach
that
we've
put
our
money
down
on
and
we
feel
like
it
might
take
a
while
to
get
there.
But
that
to
me
says
you
know,
native
kubernetes
and
edge
extension
is
sustainable.
A
A
Dive
and
we'll
you
know
we'll
try
to
do
diagrams
and
all
this
stuff
and,
of
course,
we'll
show
it
in
action,
but
yeah,
but
but
yep
that
release
that
release
came
out
and
we
got
a
lot
of
a
lot
of
lookers
from
that,
which
is
how
it
should
be,
and
we
also
got
a
lot
of
people
talking
to
us
about
just
how
relevant
it
is
now
to
to
both
be
using
kubernetes
and
edge
environments
simultaneously.
A
This
working
group
is
well
attended,
usually
and
for
good
reason,
so
right
place
right
time,
right
architecture,
I
don't
know
we're
gonna
find
out
later.
B
A
B
B
B
So
you
know,
step
up
and
and
and
then
yeah
make
it
a
good
apac
iot
edge
community.
That's
that's
my
my
message
right
I
mean
we
always
can
add
more
meetings
for
the
for
the
u.s
u.s
fund.
If
you
need
it,
I
I
think
now
it's
you
know
the
summer
period
is
coming,
so
I
think
a
lot
of
people
will
be
on
vacations.
It
will
be
more
quiet
everywhere.
So
maybe
we
can.
You
know
revisit
that
in
september
october,
when
you
know
everybody
is,
is
back
back
full.
A
B
B
Yeah
the
other
hard
lesson:
we
learned
that
every
time
we
changed
the
the
time
of
the
meeting
it
drove
people
off
so,
for
you
know
it
takes
a
lot
for
everybody
to
to
to
catch
up
on
the
new
times
and
every
and
everything.
So
I'm
really
also.
You
know
from
that
point
of
view,
hesitant
to
to
do
it
often
because
it's
it's
it's
already
confusing.