►
From YouTube: Intro: SIG Apps - Janet Kuo, Google
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: SIG Apps - Janet Kuo, Google
In this Kubernetes SIG Apps Intro session, you will learn about the areas of our focus, what we are working on currently, and how you can get involved. Veteran SIG Apps members will be on hand to help answer questions.
To learn more click here: https://sched.co/FuLH
A
C
D
B
These
are
our
leads.
They
can't
be
here,
I'm,
sorry
about
that
and
I
was
become
behalf
of
them
and
if
you
want
to
maybe
chat
with
them
a
little
bit,
you
could
find
their
contact.
Information
here
have
their
IDs
here
and
before
we
officially
start
I
would
like
to
ask
if
there's
anyone
here
knows
anything
about
Singapore
has
ever
attended
our
meeting.
Please
raise
up
your
hand
only
one,
okay
good,
so
you
are
exactly
my
target
audience
today.
So,
first
of
all,
what's
see
gaps
well,
it
means
a
special
interest
group.
C
C
B
C
B
C
B
B
And
other
tools
helping
you
develop
and
manage
your
applications,
for
example,
compose
which
could
help
you
shift
a
darker
profile
to
a
Cuban,
ite
amo
profile
and
we
care
about
all
the
application
developers
and
operators
experienced.
So
if
you
have
any
problem
in
using
them
or
you
think
you
want
to
add
some
new
features,
we'll
welcome
you
coming
to
us
and.
C
B
C
B
A.M.
yeah,
so
maybe
not
that
convenient
for
the
Chinese
participants,
but
it
doesn't
matter.
We
were
to
put
the
video
recordings
on
youtuber
and,
of
course
you
could
contact
us
through
slack
channel.
You
know,
Supernanny
has
a
slight
channel
and
at
each
meeting
we,
the
the
chair,
would
make
some
self
introductions
first
of
all
and.
C
B
Members
will
offer
you
the
most
in
time
feedbacks
and,
of
course,
we
will
have
some
scheduled
discussion
topics,
for
example,
on
how
will
we
continue
this
API
and
what
changes
were
going
to
make
and,
of
course,
you
could
register
on
the
discussion.
Topics
included
into
the
topics
and
the
rest
of
the
time
will
be
for
open
and
free
discussion.
C
B
B
Apparently,
it
enables
you
to
run
your
work
clothes.
Well,
what
is
work-life?
It
is
essentially
your
applications
in
different
times.
You
have
stateless
or
stateful
workloads,
for
example,
in
the
database
in
the
apps,
are
the
stateful
once
and
for
web
servers.
For
example,
they
don't
store
any
data,
those
are
stateless
or
some
batch
workload.
You
know
they
are
processed
in
batches,
so
they
need
to
be
done
with
batch
workloads
and.
C
C
C
C
B
B
Then
it
has
a
corresponding
replica
set
to
take
care
of
it,
and
if
your
deployment
is
updated
to
a
new
version,
it
will
create
a
new
replica
set
and
a
new
replica
set
well
start
new
part,
and
then
the
deployment
will
gradually
go
down
the
old
replica
set,
and
this
is
the
back
to
replica
set
and
about
a
replication
controller.
It
is
very
similar
to
replica
set
it's
just
in
case
a
kind
of
old
API.
C
B
Know
it
has
replaced
by
replicas
that,
and
if
you
don't
know
about
replication
controller,
you
don't
need
to
know
about
repeater
set
actually
and
then
it's
stateful
set.
What
does
that
mean?
It
is
like
your
data
base,
your
distributed
database.
If
you
want
to
store
data
in
the
backstage,
for
example,
Cassandra
or
zookeeper,
it
has
three
parts
and
maybe
between
each
parts
they
want
to
know
IDs
of
each
other.
B
C
B
D
B
B
C
B
Set
is
to
run
a
part
on
each
node,
for
example,
when
you
want
to
do
matrix
or
collect
metrics,
or
you
want
to
save
some
logs
and
on
each
log,
you
could
install
a
daemon
set
part
to
help
you
capture
the
log
and
save
somewhere
so
applications
similar
to
this.
If
you
want
to
install
something
on
to
the
node,
you
can
use
daemons
net
and
what
about
the
future
of
workloads?
Api
we've
mentioned
some
api's.
D
B
A
B
C
B
You
do
machine
learning,
you
may
create
a
large
number
of
jobs
at
one
time
and
later,
who
will
delete
well
now
in
the
system,
there
is
no
mechanism
to
delete
them.
You
need
to
delete
them
manually
and
that's
a
big
trouble
so
for
also
1.12
I,
designed
a
garbage
collection
feature
which
can
help
me
delete,
for
example,
other
jobs
when
they
finished
running
within
one
hour
after
they
finish
running.
D
B
C
C
C
E
D
C
C
E
C
C
C
E
C
C
C
C
C
C
D
C
C
C
C
C
C
C
C
C
E
C
C
E
C
C
C
D
C
C
E
C
A
D
C
C
C
E
C
E
C
E
C
C
E
C
C
D
E
C
E
C
E
C
C
C
C
C
C
E
C
C
C
C
C
C
C
E
C
C
D
C
C
C
E
C
C
C
E
C
C
C
C
C
C
C
C
C
C
D
C
C
C
C
C
E
C
E
D
B
B
C
B
C
B
Current
guiding
role
is:
if
we
are
going
to
add
some
more
new
features,
we
would
not
add
them
to
kubernetes
call
like
the
application
CRD.
We
plan
that
you
added
to
kubernetes
call,
but
the
results.
After
the
discussion
with
the
community,
we
decided
to
make
it
external
extension
first
and
then,
if
it
is
popular
enough,
we
will
add
it
to
that
to
the
latest
call
as
a
feature
and
in
the
future
for
other
API.
They
will
not
be
the
same
first
of
make
them
stable
and
if
we
are
going
to
add
them.
C
C
B
C
C
C
B
D
B
This
respect,
what
for
our
for
us
for
see
gaps,
although
we
host
some
other
ecosystem
project,
but
our
principle
is
like
we
would
loft
back
up
any
other
solution,
even
though
it
is
a
Google
solution,
it's
not
that
everybody
should
adopt
it.
We
hope
all
the
community
members
could
make
use
of
versatile
tools
and
then
tell
us
which
one
is
the
best
which
one
they
like
the
most.