►
From YouTube: CNCF SIG App Delivery 2021-01-20
Description
CNCF SIG App Delivery 2021-01-20
A
A
B
C
Thank
you
harry
so
yeah.
My
name
is
james
labocky,
I'm
a
I
work
in
product
management
at
red
hat,
but
the
we've
been
focused
on
kubernetes
and
obviously
openshift
on
the
red
hat
side.
But
I
guess
one
of
the
things
I
I
put
on
the
on
the
proposed
agenda
items.
I
just
wanted
to
kind
of
introduce
myself,
but
also
one
of
the
communities
that
we
started
called
conveyor.
C
So
I
think
I
put
a
link
to
it:
it's
www,
dot,
conveyor,
k-o-n-v-e-y-o-r,
dot,
io
and
the
whole
idea
behind
this
community.
Is
we
we've?
We've
recognized
the
need
for
practitioners,
developers,
sysadmins
sres,
wanting
more
tooling
to
help
them
analyze
their
applications
and
help
with
re-hosting,
refactoring
and
re-platforming,
and
so
we're
beginning.
We
have
a
number
of
open
source
tools
that
are
there
this
the
source
code's
all
open.
A
lot
of
the
builds
and
development
are
not
really
done
in
an
open
fashion
yet
and
we're
moving
towards
that.
C
So
directionally
we're
trying
to
kind
of
build
a
community
of
tools
that
help
people
get
their
applications
onto
kubernetes
and
kind
of
align
with
the
cncf
projects
and
architectures.
So
I
just
wanted
to
bring
that
up.
Let
everybody
know
about
it
and
see
if
there
are
any
opportunities
to
collaborate
or
if
there's
any
advice,
the
group
would
have
for
kind
of
a
community.
C
That's
just
starting
to
ensure
josh
burkus
from
red
hat,
who,
I
think
some
of
you
may
know,
is
really
helping
us
to
make
sure
that
we,
you
know,
put
the
right
governance
structures
in
place
and
licensing
to
allow
for
more
contribution
from
outside.
The
community
is
outside
of
red
hat,
as
well
as
we
kind
of
try
and
build
that
community.
But
I
just
wanted
to
bring
that
up
and
see
if
there's
opportunities
to
collaborate
and
if
not
completely
fair,
if
there,
if
there
are
I'm
more
than
happy
to
work
with
folks.
B
C
Yeah,
I
could
certainly,
if
you
want,
I
didn't.
I
didn't
want
to
assume
that
I
would
have
the
time
to
do
it
today,
but
I
could
certainly
you
know,
I
think,
if
you
wanna,
we
could
set
up
a
follow-up
where
I
can
walk
you
through
some
slides,
explaining
kind
of
the
different
tools
that
we've
open
sourced
and
put
in
there
and
some
of
the
direction
that
we're
thinking
about
going
with,
with
with
further
investment
in
engineering
and
development.
And
then
you
know,
we've.
C
We
also
have
some
meetups
that
we
run
where
we're
trying
to
have
people
talk
about
the
problems
they're
facing
when
trying
to
refactor
or
re-host
or
re-platform
and
and
so
yeah.
But
I
think
maybe
next
time
I
could.
If
there's
a
slot
on
the
next
meeting
for
15
minutes,
I
could
walk
everybody
through
some
slides.
B
Okay
and
on
the
other
hand,
if
you
eat
any
help
from
the
sick
and
well
sensitive,
please
let
me
know
you
can
ping
me
offline
on
slack
as
well.
Okay,
thank
you
sure.
So
this
is
a
first
item
in
today's
agenda:
a
introducing
of
a
new
project
which
is
focused
on
application
migration.
I
think
on
kubernetes,
and
we
are
looking
forward
to
see
its
presentation
next
meeting.
B
Okay,
the
next
agenda
in
today's
meeting
is
for
some
update
from
the
operator
working
group.
I
also
noticed
there
are
several
progresses
on
this
working
group,
not
sure
if
anyone
from
the
operator
working
group
to
give
the
update
also
I'm
curious
about
what's
the
current
status
of
the
chairs
and
we
need
to
also
there
are
some
nominations
in
the
seeker
delivery
mailing
list.
B
D
D
A
D
B
Yeah
cool
got
it
yeah.
I
also
said
that
all
lawyers
had
already
put
your
names
on
them
seek
aptly
many
lists.
So
if
anyone
has
any
concerns
or
objections,
just
let
us
know
by
sending
emails
to
the
email
list
and
also
you
could
show
your
sponsor
and
support
on
your
support
for
these
three
folks
for
the
co-chair
of
the
operating
working
group.
So
please
check
the
email
in
the
mailing
list
and
we
can
move
forward
with
the
open
working
group.
B
And
the
next
item
is
for
the
githubs
working
group
and
we
definitely
had
another
meeting
several
days
ago
and
we
saw
there
are
a
lot
of
progress
over
there,
as
well
as
discussions
on
the
expected
delivery
for
the
github's
working
group.
So
I'm
not
sure
if
anyone
from
from
the
github
working
group
want
to
give
a
quick
update
on
that.
E
So,
as
you
said,
we
had
an
our
second
community
meeting
was
last
week
on
thursday,
we're
aiming
for
about
a
roughly
a
a
monthly
cadence
on
those
we're
going
to
do
a
lot
of
work
asynchronously,
and
so
I
have
on
my
to-do
list
to
connect
with
you,
harry
and
or
eloise
to
help
me
with
some
of
the
administrative
administration
getting
meetings
on
the
cncf
calendar.
We
want
to
establish
a
google
group.
You
know
that
kind
of
stuff,
so
I'll
reach
out
to
you
offline
on
getting
some
help
with
some
of
that
stuff.
E
In
terms
of
just
the
highlights
of
the
last
meeting,
I
will
we
need
to
get
the
worker
notes
up
online
and
linkedin
all
the
right
places,
but
there
are
notes,
and
so,
if
anybody's
interested
until
we
get
those
organized
and
online
just
send
me
a
note
and
I'll
I'll
send
you
the
link.
A
couple
of
things
of
note
is
that
we
have
officially
moved
our
github
repository
over
into
a
new
organization
called
the
get
ops
working
group.
The
expectation
there
is
that
we'll
have
kind
of
a
root
repo.
E
That
is
the
centralized
thing
for
the
gitaps
working
group,
and
then
we
expect
to
be
building
other
repositories
that
might
be
sample
applications
or
those
types
of
things.
So
that's
why
we
have
an
organization,
so
we've
moved
everything
over
there,
including
the
governance
model
that
is
in
place.
We,
of
course,
will,
as
a
part
of
the
the
working
of
the
working
group,
take
any
discussion
or
prs
or
those
types
of
things
around
the
governance,
but
we
have
kind
of
the
the
scaffolding
in
place.
E
If
you
will,
we
also
have
decided
that
our
first
deliverable
will
be
a
get
ops
definition,
slash
manifesto
slash.
There
was
another
name
that
came
up
commitment,
and
so
that
is
something
we
have
a
you
know,
a
draft
that
we
are
able
to
collaborate
on
some
of
the
other
things.
There's
two
other
things
that
we
discussed
during
that
meeting,
that
there
was
a
general
appetite
for,
which
is.
We
would
like
to
create
a
website
that
will
host,
for
example,
the
manifesto
and
something
along
the
lines
of
12factor.net.
E
You
know
something
that
can
give
folks
kind
of
a
high-level
overview
of
what
the
principles
of
get-ops
are
and
kind
of
be
very
inspirational
from
that
perspective.
So
we
definitely
want
to
do
some
kind
of
a
website
and
then
finally,
the
other
thing
that
came
up,
which
is
really
a
catalog
of
use
cases
and
or
case
studies.
B
B
E
E
And
you'll
notice,
for
example,
that
it
on
the
cover
it
says
forward
by
alexis
richardson,
and
so
we
have
done
a
review
of
some
of
the
material
there,
and
these
are
folks
that
we
definitely
would
like
to
pull
into
the
community.
So
that's
a
great
point.
I
think
it's
more
focused
around
kind
of
they
are
planning
on
selling
their
book,
so
this
is
more
of
a
website
for
their
book
than
it
is.
C
B
E
Know
it's
interesting,
as
you
can
imagine.
You
know,
at
weaveworks,
being
kind
of
the
pointers
of
the
term.
We
get.
We
get
in
contact
a
lot
with
people
who
and
there's
a
fair
bit
of
chatter
out
there,
there's
folks
who
are
putting
together
training
courses
on
git,
ops
and
those
types
of
things,
and
so
that's
something
that
we
definitely
aim
to
do
with
the
with
the
working
group
is
to
really
kind
of
form
a
collective
community.
E
E
B
A
B
B
B
We
are
very
happy
to
involve
you
as
the
end
user
interview
for
this
incubation
review
process
and
another
update
regarding
to
flux
is
because
recently
there
is
a
small
change
happening
in
flux
community,
because
that
is
flagger
was
merged
to
the
phlox
organization
as
part
of
the
flux
family
project,
so
we
will
also
involve
fl
flagger
as
part
of
the
this
review.
So
this
is
a
little
bit
different
from
the
original
proposal,
which
is
only
which
was
only
flux
project
alone.
So
now
we
basically
have
a
flux
family
to
review.
B
This
is
this.
This
little
change
will
also
have
will
also
be
reflected
on
the
due
diligence
dark
and
we
will
also
add
the
contents
regarding
to
the
flagger
part
of
the
review
as
well
so
yeah.
This
is
update
from
my
site.
Anyone
have
any
questions
on
the
flux,
incubation
review
process
or
has
any
idea
on
that.
B
Know,
okay,
so
seems
that
everybody
is
good
with
the
current
process
and
then
we
will
move
to
the
next
discussion
which
which
was
actually
raised
by
toc
from
a
recent
the
meeting
and
these
questions
about
basically
about
what
is
the
next
big
thing
for
cncf
in
in
the
in
errors.
We
have,
for
example,
what
is
the
next
thing
we
want
to
put
I
own?
B
We
all
want
to
on
board
in
the
app
delivery,
in-app
delivery
ecosystem-
and
I
I
personally
also
want
to
have
this
discussion
with
everybody
here,
because
right
now
we
have
kubernetes.
We
have
argo,
we
have
vlogs,
we
have
a
lot
of,
I
will
say
very
promising
project
in
the
family
of
the
c
gap
delivery,
but
also,
but
the
tlc
also
raised
this
question.
B
B
We
know
that
people
that
they
are
actually
trying
to
deliver
applications
by
using
web
assembly
sandboxes,
and
I'm
also
trying
to
have
a
discussion
discussion
with
you
folks.
So
what
will
be
the
next
thing?
We
think
we
try
to
invest
in
the
same
safe
as
well
as
in
captivity.
Anyone
has
an
idea
on
that.
F
B
That
is
really
good
idea,
so
I
think
the
attraction
for
applications
is
really
important
for
developer
experience.
Developer
experience
is
actually
one
of
the
most
important
items
also
brought
up
with
the
poc,
I
think,
at
the
sense
of
organization.
We
should
definitely
invest
on
this
field
to
help
people
to
to
help
people
understand
better
on
how
to
use
the
clone
native
technology.
So
today
we
are
basically
very
focused
on
the
we'll
say,
the
infrastructure
layer.
We
are
talking
about
networking
storage
containers,
things
like
that,
but
yeah.
B
F
E
F
Or
so
we
are
following
a
similar
pattern
to
deploy
those
cloud
resources,
sometimes
they're
associated
with
application
deployment.
Sometimes
they
are
deployed
independently
and
although
they
are
declarative,
people
are
using
terraform
or
cfn,
or
something
like
that
now
they
want
to
also
follow
githubs.
For
that.
B
F
F
B
B
F
So
we
already
see
like
users
in
github's
work
in
github
slack
channels
deploying
lambda,
using
sometimes
argo,
even
like
we
internally.
When
we
set
up
our
aws
accounts
to
deploy
the
clusters,
we
create
the
accounts
or
set
up
the
security
groups
and
the
vpcs
using
our
internal
githubs
tools,
which
we
haven't
yet
open
source.
But
this
is
one
area
where
not
just
us.
I
see
people
talking
about
it.
Even
in
the
cncf
github
slack
channel,
kubernetes,
github,
slack
channels,
yeah.
B
F
So,
for
example,
internally,
when
we
develop
those
are
not
crds.
Those
are
regular
services
and
we
are
using,
for
example,
cdk.
We
are
not
using
a
cd
suppose
internally.
Today
we
support
aws,
cdk
and
terraform,
but
when
we
open
source,
obviously
we
have
to
see
like
whether
it
should
be
a
controller
and
crd
yeah.
B
Got
it
I'm
very
personally,
very
interested
in
this
topic,
because
I
saw
a
lot
of
needs
for
for
managing
cloud
resources,
alongside
with
your
applications
following
the
same
pattern,
yeah,
I'm
looking
forward
to
see
anything
open
source
coming
coming
next
and
definitely
stick
up
delivery,
one
to
put
them
into
the
scope
of
the
next
big
thing
for
slight
upgrade.
Thank
you,
okay
right.
This
is
the
this
is
the
main
discussion.
I
want
to
bring
up
this
sick
today.
B
B
But
we
are
definitely
discussing
discussing
something
like
a
mentor
program
to
help
with
the
project,
to
incubate
to
move
into
the
incubation
stage
yeah.
This
is
basically
the
idea
where
the
best
where
the
idea
coming
from-
and
we
want
to
find
some
early
stage,
projects
which
are
more
like
the
future
investment
and
we'll
have
a
mentor
program
or
something
like
that
to
help
those
projects
grow
step
by
step,
and
they
may
fail
that's
okay,
but
as
long
as
some
of
them
grow
into
a
promising
project,
they
basically
are
doing
very
good
things
for
the
community.