►
From YouTube: Kubernetes WG IoT Edge 20220126
Description
January 26 meeting of the Kubernetes IoT Edge Working Group. Short discussion of plans for upcoming conferences.
A
A
A
So
just
take
that
as
tentative
but
cfps
for
that
are
open.
Now
I
would
expect
that
would
be
similar
to
these
kubernetes
on
the
edge
days
that
have
occurred
at
kubecon
europe
last
year
and
yeah
kubecon
north
america
this
year,
with
the
exception
being
that
it's
been
a
while,
since
we
had
a
physical
version
of
that
so
and
sponsorships
are
still
open
by
the
way
as
well,
or
at
least
they
were
earlier
in
the
week.
A
When
I
heard
from
the
linux
foundation,
organizers,
then
kubecon
itself
is
that
whole
week
of
may
the
16th.
Originally.
I
think
I
understood
that
was
going
to
be
a
physical
only
event,
but
I've
noticed
now
that
the
website
says
that
at
least
for
purposes
of
attending
it
appears
to
be
hybrid,
because
there's
a
virtual
attendance
option.
A
Cfps
for
that
main
conference
are
closed
at
this
point,
but
I
don't
believe
they
haven't
announced
the
speakers
yet.
So
that's
pretty
easy
to
find
with
a
google
search,
but
I'll
update
the
notes
later
on
details
of
that
as
usual,
the
organ
the
cncf
has
invited
this
working
group
to
submit
a
proposal
for
a
maintainer
track
talk,
and
that
is
due
in
a
week
or
two.
I
believe.
A
A
It
it
might
be
a
good
idea
for
per,
I
think,
we're
open
to
all
suggestions
from
members
on
what
might
go
in
there.
It
probably
shouldn't,
in
my
experience,
attempt
to
cover
the
whole
universe,
but
be
something
a
little
more
focused
on
one
topic,
with
an
open
and
close.
That
just
explains
what
this
group
is
and
how
you
can
get
involved,
but
I,
I
think,
attempting
to
cover
the
whole
universe
of
kubernetes
edge
and
iot
stretches
it
so
thin
that
in
the
early
days
it
might
have
been
a
value.
A
A
The
other
topic
I
put
on
the
agenda
is
that
there's
the
kubernetes
project
runs
with
a
mechanism
for
cigs
working
groups
and
user
groups
to
periodically
report
up
to
the
community
steering
organization
and
were
due
to
give
a
report
on
this
group.
We've
done
it
in
the
past,
so
I
think
dion
has
usually
headed
up
that
effort.
I'm
hoping
he
can
do
it
again,
but
it
is
something
that
everyone
should
participate
in
both
chairs
leads
and
members.
A
Should
they
choose
to
do
it
to
put
in
their
own
comment
in
that
document
that,
as
far
as
I'm
concerned,
I'm
willing
to
take
them
completely
unedited,
because
you
know
I
don't
want
to
pressure
or
put
words
in
anybody's
mouth,
with
the
caveat
that
any
comment
should
abide
by
the
code
of
conduct.
You
know
there's
there
there
might
be
some
limits
to
what
is
appropriate
for
such
a
comment,
but
you
know
be
open,
honest
and
say
what
you
think
and
will
accept
it.
A
I
think
we're
trying
to
operate
that
group
on
that
policy
anyway,
for
accepting
feedback,
not
just
when
these
reports
come
due,
but
you
know
for
the
continuum
of
the
operation
of
this
group,
but
just
throwing
that
out.
There
is
both
an
opportunity
and
maybe
an
obligation
and
something
we
can
discuss
more
at
this
meeting.
A
Does
anybody?
Oh
let
me
let
me
mention
since
frederick
is
here
I'll
mention
this
a
sidebar
thing
so
before
the
meeting
started,
I
just
told
dion
that
I'm
an
organizer
of
this
scale
open
source
conference
and
they
just
announced
in
the
last
couple
days
that
that
was
slated
for
march
and
it's
been
postponed
to
july
because
of
the
prevalence
of
omicron.
Here,
in
los
angeles,
there
were
just
too
many
people
nervous
about
attending
with
the
news
of
rapidly
growing
positive
test
results.
A
Living
here
in
la
my
observation
is
that
this
is
spreading
rapidly,
but
you
know
the
people
who
get
it
don't
seem
to
be
reporting
very
severe
symptoms,
but
it
does
cause
people
to
be
nervous
about
signing
up
for
travel
speaking
and
attending
the
conference.
That's
just
you
know
a
month
and
a
half
out.
So
the
organization
decided
to
slide
it
into
july
and
frederick.
I
think
the
reason
I
think
it's
important
to
you.
You
should
have
gotten
the
notice
that
your
talk
got
accepted.
I
think
yeah.
B
A
A
A
A
A
A
B
B
A
A
C
A
A
B
B
A
A
Yeah,
well,
it
doesn't
necessarily
have
to
be
problems.
I
I
don't
think
I
personally
need
pats
on
the
back,
and
one
of
the
big
issues
is
that
if
we
troubled
anybody,
they're
unlikely
to
show
up
for
this
meeting,
you
know
to
be
aware:
there's
an
opportunity
to
engage
in
self-improvement
because
maybe
unfortunately
they
just
drop.
But
you
know
the
whole
point
of
doing
it
is
to
have
a
continual
process
for
getting
better.
A
So
hopefully
we
can
pull
that
off.
I
mean,
to
be
honest,
I
don't
know
if
it's
coveted
or
whatever,
but
I
think
my
gut
feel
without
tabulating.
The
actual
metrics
is
that
attendance
has
dropped
a
bit
over
the
past
year
or
so
could
be
zoom
burnout
or
whatever,
but
it
it
we
kind
of
peaked
a
while
ago
and
it
it's
dropped
off,
not
sure.
A
But
any
ideas
for
you
know
making
this
something
that
people
get
value
out
of
I
mean
that's
the
key
to
driving
attendance
and
a
lot
of
it
is,
I
think,
if
you,
if
you
get
the
same
people
over
and
over
there's
a
risk,
it
just
becomes
an
echo
chamber
rather
than
you
know
something,
vibrant
and
growing.
Frankly,
I
think
kubernetes
in
general
is
like
that,
and
hopefully
it
isn't
one
of
these
things
like
you
know
what
what
is
that
thing?
A
A
We
probably
you
know
I
I
haven't
heard,
but
we
have
a
co-chair
in
this
group.
Cindy,
who
was
it
was
great,
but
I
I
haven't
heard
from
her
for
about
a
year
and
don't
you
know
it
could
be
with
kovid
she's
got
issues,
but
maybe
we
could,
you
know,
entertain
some
changes
in
who
is
listed
in
this
group
as
the
group
of
chairs
and
leads,
you
know
to
to
get
more
active
and
more
diverse
leadership
of
the
group.
A
It's
something
that
that
it
that
isn't
in
the
report
and
the
steering
will
expect
us
to
cover
that.
They
also
have
an
expectation
that
these
working
groups
are
operated
underneath
the
supervisory
governance
of
sigs
and
that
when
this
charter
system
was
initially
developed,
I
think
somebody
had
the
expectation
that
these
groups
were
in
charge
of
maintaining
code
associated
with
the
kubernetes
project
and
we're
really
not
doing
that
in
this
group.
At
this
time,.
A
Yeah,
so
it
doesn't
really
align
with
some
of
the
things
asked
for
in
our
report.
We
have
to
be
honest
and
say
that,
but
you
know,
maybe
it's
appropriate
for
us
to
change
those
expectations
that
every
working
group
does
code
or
maybe
it's
time
to
suggest
that
we
belong
in
a
different
category
there.
There
is
a
category
called
user
groups,
and
you
know
it's
meant
to
serve
people
who
are
using
kubernetes
as
opposed
to
you
know,
working
on
code.
A
So
one
thing
to
entertain
is
that
maybe
this
group
operates
more
closely
like
a
user
group
than
it
does
what
they
consider
a
working
group.
Now
this
code
expectation,
I
think,
dion
you've
been
in
this
group
longer
than
I
have,
but
I
think,
maybe
that
this
group
started
before
they
put
that
rule
in
place.
A
So
we
got
grandfathered
in
under
an
older
expectation
where
that
wasn't
part
of
it,
and
one
thing
we
could
do
is
simply
call
that
to
their
attention
that
hey
look,
you
went
and
changed
the
description
without
actually
going
out
there
and
serving
how
these
things
were
working
in
the
first
place
and
the
problem
is
that
description?
Not
you
know
the
operation.
A
A
That
isn't,
you
know,
is
isn't
authorized
under
the
charter
or
something
I
suppose
you
know
it
could
be
anything
from
find
another
position
you
fit
into
to
change
the
rules
or
just
drop
the
group.
So
it's
hard
to
say
it
should
be
a
discussion
and
I'm
not
expecting
that
we
got
get
taken
out
behind
the
barn
and
and
carved
up,
but
you
know
it'll
be
what
it'll
be
and
we'll
see,
but
anyway,
just
throwing
it
out
there.
A
I
think
for
now,
I'm
going
to
if
he'll
accept
it
drop
this
on
dion's
shoulders
to
compose
a
draft
document
and
share
it
because
he's
done
it
a
few
times
before
and
then
we'll
just
take
it
from
there.
I
think
we've
been
given
an
expected
deadline,
but
I
don't
recall
what
it
is
and
with
that
said,
let's
move
on
to
take
a
look.
D
A
A
A
At
the
event,
however,
my
experience
has
been
with
these
user
panels
that,
unlike
vendors,
they
have
a
more
difficult
time
getting
budget
for
travel
and
particularly
under
covid,
where
a
lot
of
companies
have
additional
impediments
out
of
safety
concerns
that
go
beyond
just
the
budgetary
issue
and
that
this
is
in
europe.
So
it
probably
means
that
you
know,
in
terms
of
people
will
being
willing
to
attend.
A
Those
users
would
be
more
than
likely
europe-based
already
for
travel
cost
reasons,
and
you
know
that
it
kind
of
makes
recruiting
a
whole
panel
of
people
like
this
a
little
bit
difficult,
especially
for
me
not
being
based
in
europe.
I
don't
have
that
many
contacts
over
there
myself
to
engage
in
recruiting,
but
just
throwing
that
out
there
that's
one
possible
thing
that
we
could
cover
in
the
maintainer
track.
A
I'd
also
maybe
like
to
avoid
things
that
we
covered
recently,
just
let's
keep
it
fresh,
so
the
last
one,
if
you'll
recall,
was
on
web
assembly.
I
think
that
was
a
great
presentation
yeah.
I
thought
that
went
well.
Let's
not
do
it
again
this
quickly,
you
know,
maybe
a
year
later
but
and
I
think
we've
had
topics
on
integrating
in
devices
too
small
to
run
kubernetes
themselves
using
you
know,
alternate
communications
and
eventing
technology
and
if
I'm
not
mistaken,
that
was
one
we've
done
in
the
past
year.
A
A
That's
one
of
the
reasons
why
trying
to
be
the
jack
of
all
trades
cover
the
whole
universe
is
not
ever
going
to
get
very
deep,
and
at
least
if
we
pick
some
topic,
I
think
we
can
manage
to
get
at
least
moderately
deep
on
it.
As
long
as
we
focus
so
I'll
give
up
the
mic
if
and
ask
maybe
I'll
put
every
one
of
you
on
the
spot
to
throw
out
one
idea,
even
good
or
bad,
just
whatever
pops
up
the
top
of
your
head.
D
D
That
will
use
the
whole
stack,
so
so
the
the
firmware
written
in
rust
and
billy
mesh
then
some
gateway
that
will
push
that
to
the
cloud
and
then
what
we
have
in
the
cloud
with
the
drug,
iot
and
detail
and
everything.
So
it's
it.
It's
a
whole
architecture,
basically
presenting
the
the
one
particular
use
case
and
there's
the
kubernetes
on
the
cloud
there
might
be
on
on
the
on
on
the
gateway
on
the
edge,
I'm
not
sure
yet,
but
that's
something
I
can
I
can.
I
can
help
with
that.
B
That
that
sounds
good
one
thing
personally,
that
will
be
would
be.
Unfortunately,
I
don't
have
the
time
to
invest
on
this,
but
one
thing
I
would
be
curious
about
is
how
how
easy
to
work
with
various
iot
protocols
in
a
in
a
kubernetes
context,
in
the
sense
that
you
have
you
have
co-op
and
qtg
lightweight
m2m
dds
zeno,
whatever
right,
so
there
are
maybe
pitfalls
to
some
of
those
in
the
kubernetes
context,
or
maybe
they
are
all
equal
and
and
and
they
could
be
worthwhile
to
discover
for
kubernetes
audience
but
yeah.
B
A
C
C
Also
of
of
microservices
and
so
on,
to
the
edge
via
with
with
kubernetes
stuff,
where
we're
still
keeping
intact
secrets,
because
yeah
that
that
is,
that
is
a
subject
on
people's
mind,
is
yes
the
secret?
The
secret
infrastructure
might
be
fine,
but
once
the
container
is
running,
has
that
not
been
embedded
as
an
environment
variable
and
if
you
can
get
in
the
vice
site?
So
just
opening
that
topic
for
discussion,
yeah.
A
I
think
that's
a
good
ad
and
probably
even
essential,
because
one
of
the
keys
for
this
being
under
the
auspices
of
this
group
is
it
has
to
be
kubernetes
related
and
this
subject
of
device,
provisioning
and
providence
by
and
large,
much
of
what
goes
on.
There
occurs
as
a
foundation
that
is
below
the
kubernetes
abstraction
layer
right,
so
it's
not
really
kubernetes
related
per
se
there,
the
venn
diagram
of
people
who
are
interested
in
it.
Probably
you
know
anybody
trying
to
use
kubernetes.
A
A
A
I
just
threw
out
another
one
that
popped
in
my
head,
as
I'm
thinking
of
it
too,
like
I
started
thinking.
How
does
kubernetes
get
involved
with
this
provisioning
and
things-
and
I
I
know
from
prior
discussions
of
people
trying
to
do
this-
that
a
big
element
becomes
operation
when
you're
severed
from
internet
connectivity
either
permanently
periodically
whatever,
and
you
know
it
entails
things
like
hosting
container
images
and
other
binaries
so
that
you
can
recover
from
power.
A
Outages,
do
updates
and
things
and
that
could
be
related
to
the
device
provisioning
in
providence
in
some
way
and
it
can
tend
to
bring
in
kubernetes,
because
sometimes
people
host
the
gateways
and
binary
and
image
registry
components
on
kubernetes
itself,
either
at
a
gateway,
low,
mezzanine
location
or
an
edge.
But
maybe
air-gapped,
kubernetes
operation
is
a
third
potential
topic.
You
know
it
isn't.
B
C
A
A
D
A
Yeah,
okay,
let's
so,
we've
covered
the
report,
we've
covered
kubecon,
maintainer
track
and
the
edge
day.
I
think
that's
about
it
that
I
put
on
the
agenda
unless
somebody's
else
has
anything
more.
Another
thing
I
guess
I'd
like
to
bring
up
is
trying
to
get
some
fresh
presentations
into
this
group.
You
know
because
I
think
part
of
that
is.
We
haven't
been
that
successful
at
getting
people
to
present
on
topics
and
that
tends
to
draw
attendance.
So
one
of
the
things
I
suggested
just
because
I
came
across
it
an
article.
A
So
maybe
we
can
get
somebody
to
talk
about
that
at
an
upcoming
meeting
and
if
anybody
else
has
any
other
ideas
of
some,
you
know
some
open
source
project
where
we
could
recruit
a
speaker
if,
if
either
of
you
missed
it,
that
presentation
on
portainer
that
occurred
back
a
while
ago,
I
thought
was
just
fantastic.
It
was
that
that
was
really
an
interesting
presentation
by
neil
creswell.