►
From YouTube: SIG App Delivery Operator Working Group 2021-03-24
Description
SIG App Delivery Operator Working Group 2021-03-24
B
A
B
A
A
B
B
B
C
B
C
D
Well,
the
clocks
change
in
the
uk
only
I
think
next
week,
so
they
I
realized.
The
cncf
calendar
is
kind
of
following
some
u.s
time
zones
like
and
then
they
changed
to
summertime
before
europe.
I
think
so,
I'm
it
is
a
number
at
five
right
and
I
and
I
didn't
have
I
don't
have
it
on
my
calendar.
I
don't
know
why,
like
it's
gone,
but
I
know
it
is
at
five,
so
I
was
yeah
well.
D
C
D
Next,
you.
A
D
B
Yes,
you're.
Fine
thanks.
B
Today,
I
I
thought,
we'd
talk
about
some
comments
in
the
white
paper
from
the
reviews
and
try
to
solve
them
if
possible,
or
to
to
add
additional
comments
to
solve
the
meeting
and
yes
currently,
I
think
we
have
a
pretty
much
a
pretty
good
amount
of
revenues,
so
I
think
three
or
four
people
at
least
waited
until
now,
and
we
had
a
lot
of
very
nice
comments
until
now.
B
So
let's
say
this
way,
it
wasn't
fundamentally
wrong
what
we
wrote.
At
least
it
seems
so
so,
let's,
let's
try
to
get
this
out.
Another
thing
because
I
think
I've
wrote
it
on
this
lecture
on
this
lecture
last
week.
B
To
make
this
white
paper
a
bit
prettier
afterwards,
have
you
got
an
idea
or
do
you
know
where
we
could
reach
out.
D
Wait,
what
is
the
phase?
Are
you
talking
about
just
to
check
I'll
open
this
schedule?
Here?
I
don't
have
it's
just
I
guess
it's
the
one
that
reviews
of
like
I
basically
like
editor,
like
of,
is
that
what
people
had
in
the
in
the
other
white
papers
like
what
what
did
they
do
so
it
is
the
one
that
and
stats
narrative
voices
that
the
one
you're
talking
about.
D
D
Who
did
that
for
like
the
security,
for
example,
the
security
white
paper?
Was
it
somebody
like
who
should
do
it?
What
will
the
profile
of
the
person.
D
B
I
think
at
some
point
it
would
be
nice
if
it's
if
someone
would
write
you
know
whose
native
languages.
This
is
because
I
think
in
all
three
cases
and
english
is
not
our
native
language.
Isn't
it
and
therefore
this
would
be
would
be
pretty
cool
yes
and
furthermore,
but
I
will
also
talk
about
our
talk
with
emily
about
this.
B
B
D
C
D
B
That's
all
I'll
try
to
try
to
find
out
how
they
deal
with
this
and
yes,
I
will
keep
you
in
touch.
B
C
B
B
D
D
At
the
things
that
you
approved
and
and
are
merged,
or
are
we
gonna
look
at
the
stuff?
That's
still
pending.
B
No,
we,
we
should
look
up
over
the
things
which
are
currently
here
so.
B
So
it's
I
think
they
are
so
I
I
don't
want
to
talk
about
such
things.
They,
I
think
we
should.
We
should
simply
change
them.
This
is
also
already
resolved,
but
there
is
a
lot
of
things
out.
There
is
a
large
discussion
and,
I
think
talked:
do
you
have
a
plan?
What
we
should
change
here.
A
I
think
we
need
to
capture
michael
ideas,
especially
his
second
comment,
which
explain
a
little
bit
more
a
declarative
idea,
and
then
I
think
we
should
change
the
word
domain.
Specific
knowledge
to
state.
B
To
be
honest,
an
operator
deals
with
domain
specific
knowledge,
and
this
domain-specific
knowledge
should
be,
in
my
opinion,
specified
in
the
declarative
way.
I'm
not,
and
I'm
not
really
sure
if
this
is
only
a
problem.
A
In
the
content,
so
the
domain
specific
knowledge
according
to
michael
is
explaining,
and
I
think
it's
reasonable
is
the
domain.
Specific
knowledge
is
captured
in
the
code
of
the
operation,
the
api
that
exposes
declarative,
but
that's
not
the
domain.
Specific
knowledge
that
domain
specific
knowledge
of
how
to
run
commands
against
resources
are
is
actually
the
code
in
the
controller.
B
Okay,
I
think
I
get
your
point,
so
you
thought
about
the
content
of
the
custom
resource
when
you,
when
we
we
thought
about
the
content
of
the
custom
resource
when
we,
when
we
all
wrote
such
things
as
domains,
are
declarative
domain,
specific
knowledge
and
the
domain.
Specific
knowledge
itself
is
written
in
the
operator
code,
which
is
absolutely
correct.
A
B
B
Yes
and
last
thing
with
this,
with
the
thing
we've
specified
as
domain,
specific
knowledge
might
be
the
desired
state
of
the.
So
we
should.
We
should
say
that
this
is
the
desired
state
of
this
of
the
application
or
whatever
the
operator
is
responsible
for
yeah.
B
B
D
B
So
the
domain
specific
knowledge
should
be
the
operator
code
itself
and
the
desires
it's
the
thing
we
made
before.
B
So
let's
see
kind
of
configuration.
B
C
B
A
B
Okay,
so
I
think
this
is
also
a
thing
we
could
handle
in
this
task,
because
this
all
this
also
has
to
do
something
with
domain
specific
knowledge
and
so
on.
D
A
B
D
I
guess
the
bit
that
is
here
is
just
like
the
domain.
Specific
knowledge
is
part
of
the
operator,
but
the
domain
specific
knowledge
is
not
what
describes
the
state
of
the
application.
A
D
The
controller
also
manages
the
state
they
state.
Isn't
that
trying
to
reconcile
this
state
and
ensure
it
is.
D
But
the
controller
yeah,
but
you
can
have
a
like,
is
I
don't
know
if
it's
like
the
type
that
is
attract?
Basically,
I
don't
know
if
I
can
call
tractor
by
the
controller
that
ensures
that
it
has
a
state
like
yeah.
So
when
we
say
state,
I
think
that's
what
we're
talking
about
right.
The
thing
that
is
tracked
by
the
controller,
because
it's
being
reconciled
and
watched.
A
B
So
let's
say
we
have,
we
have
a
configuration.
This
is
the
thing
we
have
in
the
custom
resource.
We
have
a
controller
which
is
the
domain
specific
knowledge
and
we
have
managed
objects.
B
Well,
I
I
afraid
about
how
how
someone
could
name
this.
B
As
we
as
we
discussed
earlier,
this
is
the
only
difference
is
the
is
the
type
of
work
of
operates.
Let's
say
this
way,
so
it's
only
about
operator
things
which
an
operator
would
typically
do.
I
would
typically
have
done
about
10
to
15
years
ago,
so
this
is
the
this
is
the
theme
how
I
how
I
can
remember
what
an
operator.
B
B
I
think
the
main
point
in
this
in
this
comment
was
that
we
also
used
that
we,
then
we
mixed
up
the
domain,
specific
knowledge
and
the
decorative,
and
I
think
we
should
we
should
change
this.
D
Yeah
maybe
like
try
to
write
it
again,
maybe
without
looking
and
then
looking.
I
don't
know
some
that
theory
thing
that
if
you
want,
I
can
try
to
write
these
three
components
and
suggest
or
something
if
you
want
to
tag
me
there
to
like
suggest
yeah
just
maybe
because
then
it's
a
new
like
fresh
pair
of
eyes
in
that,
but
maybe
yeah.
B
A
B
D
B
It
I
think
we
could.
We
could
remove
the
thing
which
are
defined
by
custom
resource
definitions.
D
A
I
think
we
need
to
change
that.
The
word
domain
specific
the
knowledge
there,
but
let
can
we
take
that
question
back
to
sig
docs,
that's
really
how
to
write
top
question.
A
C
B
B
As
I
wrote,
this
was
that
you
are
dealing
with
custom
resources
and
they
are
defined
by
custom
resource
definitions,
so
these
are
two
different
things
in
this
way,
but
for
me
it
would
be
perfectly
fine
if
we
as
it's
pretty
obvious,
if
we
did,
if
we
remove
this
this
one.
This
is
this
part,
because
then
it
would
be
more
or
less
clearer.
Previous.
D
D
But
I
am
happy
with
either
I'm
not
if
you
prefer
to
remove.
I
don't
think
it's
actually.
I
don't
think
it's
so
obvious.
That's
what
I
mean
like,
because
people
who
are
new
to
this
will
not
necessarily
know
that
you
will
declare
with
custom
resource
definitions,
but
if
you
mention
that,
maybe
I
would
have
to
read
the
doc
if
it's
already
been
mentioned
several
times.
Maybe
you
already
know,
but
if
not
it's
it's
not
a
problem.
D
B
B
B
A
B
B
So
we
would
add,
in
addition
to
the
default
custom
resources
and
used
to.
B
C
B
C
D
D
D
D
D
D
It's
okay,
don't
worry
it's
it's!
It's
in
lowercase!
Forget
everything
I
said
anytime,
I'm
reading
here
on
the
documentation.
When
you
specify
the
resource
level
lights,
I
know
yeah.
I
think
it's
it's
with
the
lower
case.
So
don't.
B
Maybe
okay,
then
the
next
one
I'll
simply
do.
C
B
Yes,
we
could.
We
could
write
that
we
found
that
this
could
be
applied
with
keeps
cue
cuddle
apply.
But,
yes,
I
don't
think
it's
necessary
at
this
point.
B
Okay
and
he
wants
to
yes,
so
he
wants
to
represent.
B
That's
also
true,
because
there's
also
statuses
inside-
and
this
would
also
would
also
would
be
the
complete
custom.
A
D
So
if
we
think
that
I
I
haven't
finished
reading
but
like
we
could
put
the
comments
there
as
well,
so
then
at
least
to
like
why
and
then
we
can.
You
know
if
there's
a
more
kind
of
like
a
concern,
not
consensus,
but
like
democratic
things
would
be
like
okay,
the
reason
it
was
no,
it
was
nothing
no
word.
It
was
just
that
thought
about
it
and
I
think
that
and
then,
like.
B
To
be
honest
in
a
in
a
perfect
world,
it
would
be
obvious
to
that
that
the
baker
that
makeup
you
make
is
also
restorable,
but
in
the
last
20
years
I
had
cases
where
this
was
not
not
the
case
and
therefore
it
should
be
mentioned.
Is.
D
Who
do
we
put
perhaps
like
so
this
backup
should
be
implemented
in
a
way?
Maybe
so
then,
like
I
don't
know
if
it
would
help
so
like
this
backup
should
be
done
in
a
way.
It
feels
like.
D
Know
like
does
the
backup
needed
to
do
anything
to
do
with
it
can
be
restored
and
restored
like
what
is
what
is
in
the
implementation
of
a
backup
that
thinks
about
risk?
Well,
although
okay,
if
you
encrypted
the
backup
file
and
that
it
cannot
be
decrypted
or
something
like
that,
maybe
but
then
it's
like
well,
you
know
what
I
mean.
D
D
B
So,
as
I
said
before,
it's
pretty
obv
the
sentence
is
pretty
obvious
but,
as
I
said
it's
a
bit
it's
a
bit
important
to
to
to
define
to
not
to
defend
this
to
state
it.
But
if
you
think
it's
more
obvious
than
I
think,
then
we
could
also
simply
drop
it.
D
Well,
I
just
I,
I
think
it's
okay
to
to
have
it
to
have
it
there
if
we
think
this
way
like
what
we
want
to
con.
That's
the
thing
what
they
this
person
thought
was
that
there
was
nothing
useful
about
this
like,
but
you
think
to
me
that
there
is
something
useful
that
is
that
the
implementation
of
the
operator,
backup
functionality
should
be
considering
the
next
thing
because
of
the
domain
knowledge
that
is
there.
D
So
I
think
it's
worth
perhaps
changing
this
sentence
to
ensure
that
that's
understood
that
the
implementation
of
one
thing
that
that
the
the
knowledge
there
is
important
so
that
you
can
guarantee
some
next
thing.
That
needs
to
be
done
to
I'm
not
sure
very
clear,
but
basically
like
we
can
put
that
in
the
sentence.
I
think
you
want
me
to
try
to
to
suggest
something.
Then
I
can.
I
can
get
something.
B
Okay,
yes,
there's
a
there's
one,
one
handwritten
diagram
of
of
chong
there.
I
think
we
should
change
this
and
I
will.
C
D
Yeah,
you
did
right,
I
think,
just
like.
If
you
think
this
would
be
great,
he
could
ask
me.
B
So
roland
wrote
that
the
steps
to
the
first
step,
when
you
try
to
give
the
right
operator
is
that
you
should
not
assume
that
you
know
what's
needed
and
whatever
he
meant
there
at
some
point,
sometimes
he's
a
bit
too
low.
So
he
lost
it
so
quickly.
C
D
D
C
D
Okay,
cool
yeah,
because
we
don't
know
anyone
I
mean
I
don't
know
these
people
in
the
community,
so
I
prefer
to
be
always
very
cordial
like
and
and
like
don't
dismiss
their.
I
don't
think
yours
was
but
like
I
was
just
thinking
to
maybe
make
it
even
more.
I
prefer
to
make
sometimes
extra
cordial
just
to
in
this
statement.
D
So
we
can
right,
so
I
guess
the
next
thing
this
is
the
same
thing
is
already.
We
already
saw
this
one
right
this
one
I
saw
I'm
going
directly
on
the
on
the
thing
will
be
handled.
B
D
B
D
D
D
Sorry,
maybe
I'm
looking
at
the
wrong
screen,
because
I
I
normally
go
through
the
main
pull
request
comments
here.
Did
we
do
this
change
here?
The
wrong.