►
From YouTube: 2023-09-06 TAG General Meeting - Silver Surfer
Description
TAG web site: https://tag-app-delivery.cncf.io/
TAG Slack channel: https://cloud-native.slack.com/archives/CL3SL0CP5
TAG git repo: https://github.com/cncf/tag-app-delivery
TAG meeting notes: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit
A
B
B
D
A
C
D
A
B
B
C
F
E
B
E
D
E
F
A
E
E
All
right
so
we're
at
1004
we've
got
Eloise
here
too
I
think
let's
go
ahead
and
get
started,
so
the
agenda
I
pasted
the
we
are
recording
right.
Yes,
good,
we'll
learn
to
check
that
I
should
put
a
note
in
the
notes,
yeah
so
share
the
agenda
there
in
the
chat
we
like
to
start
out
if
folks,
new
folks
newcomers.
Thank
you
so
much
for
joining
us.
E
D
So
let
me
go
first,
I
think
this
is
my
first
meeting
here
at
the
census
tag
ability
so
everyone.
My
name
is
abhinav
and
I'm
working
as
devops
engineer
at
deftron
Inc.
So
it's
everything
around
kubernetes
and
everything
around
open
source
ecosystem
and
by
the
way,
I'm.
Also
CNC
fan
Belcher
AWS,
Community
Builder.
E
E
A
Maybe
already
like
two
times,
if
you
remember
correct,
I'm,
talking
about
my
tool,
a
clue,
CDL
or
clue
couple
so
I'm
developing
just
got
a
new
release
out
and
I'm
just
checking
in
to
kind
of
announce
that
next
time,
maybe
I'm
going
to
present
a
little
bit
about
the
new
release
and
new
features
and
stuff
like
that
I'm
going
to
post
the
link.
If
that's
okay,
to
see
current
release.
F
A
A
B
E
Well,
thank
you
yeah
and
I
and
I
love
that
you're
gonna
come
talk
to
us
about
it.
You
know
we're
we're
happy
to
give
people.
You
know
10
minutes
or
so
or
a
little
bit
to
talk
about
their
stories
talk
about
stuff.
It's
got
to
be
open
source
and
ideally,
we'd
love
if
it
was
on
its
way
to
cncf
but
yeah.
That
would
be
great
looking
forward
yeah
and
that
was
kind
of
what
I
was
gonna
wrap
up.
This
introduction
part
like
we
we
do.
E
A
E
F
G
E
E
Awesome,
okay,
I
guess,
yeah
on
that
I
guess:
I
need
to
check
I,
think
they
yeah
they're
meeting
on
the
18th
I.
Guess
we'll
look
and
see
what
they're
expecting
they're
expecting
I
think
they're.
They
want
us
to
have
them
finished
I,
don't
they
didn't
say
they
want
us
to
present
anything
to
them.
I!
Guess!
D
I
heard
about
it:
okay,
so
Silver
Surfer
uplifting
the
game
of
cable
discussion
upgrades.
So
what
is
Silver
Surfer
exactly
before
I
start,
who
am
I
so
I
have
already
introduced
myself
hey.
This
is
the
window
I'm
working
as
devops
engineer
at
deftron
I'm
also
CNC
and
business
cncf
New
Delhi,
chapter
Lee,
AWS
company,
Builder,
AWS,
member
and
yeah
go
to
community
guy.
D
The
existing
projects
that
we
have
in
the
entire
ecosystem
in
the
open
source
ecosystem,
a
quick
glance
of
the
architecture,
its
features
and
uses
where
it
can
be
helpful.
What
use
cases
it
can
solve
a
quick
demo,
very
small
demo,
the
state
of
silver
surface
in
the
community
as
of
today
and
the
near-term
roadmap
that
we
are
planning
as
of
today.
D
So
what
is
Silver
Surfer,
so
Silver
Surfer
is
your
good
tool
for
your
community's
cluster
upgrades.
It
checks
the
compatibility
of
your
API
verses
with
the
current
you
will
discusses
to
the
Target
can
be
discussion
where
you
want
to
upgrade
your
current
versions
and
it
gives
a
migration
path
for
all
the
objects
which
are
their
immediate
people
disclosures
okay.
Now,
let's
talk
about
the
motivation,
Bible
build
so
kubernetes.
Cluster
upgrades
are
never
been
easy
right.
D
It's
one
of
the
difficult
tasks,
one
of
the
most
difficult
tasks
that
we
have
and
communities
make
sure
they
are
constant
about
updating
those
Liberties
clusters
and
they
provide
the
entire
details
of
each
and
everything
in
a
beautiful
way
right.
But
it's
still
upgrading
is
not
an
easy
task,
and
specifically
you
are
when
you
are
upgrading
your
kubernetes
clusters.
You
born
one
any
kind
of
down
times
or
any
kind
of
duplications
or
any
kind
of
mismatch
in
the
compatibility
right.
So
there
are
several
challenges
that
we
have
in
the
security
ecosystem.
D
One
is
the
pleasure
version
compatibility
from
the
existing
processor
to
the
latest
resistor,
where
you
want
to
upgrade
thereafter.
There
might
be
the
chances
of
downtime
or,
let's
say,
service
diffusion.
If
you
are
not
following
the
right
approaches,
or
things
are
not
being
pre-planned
before
you
upgrade
your
cumulative
clusters,
it
can
be
because
of
config
management.
It
cannot
because
of
crds.
It
can
be
because
of
deprecations.
That
equipment
is
introduces
in
their
new
releases.
D
If
I
give
an
example,
for
example,
for
the
latest
version
right,
the
1.28
that
was
recently
being
released
for
a
port
security
policy.
I
guess
this
has
been
deprecated,
the
API
version
has
been
removed
and
for
HPA
the
API
version
has
been
deprecated
and
new
API
version
has
been
released
for
100
scaler.
So
if
these
things
are
planned
properly,
then
things
might
get
easier
right
when
you
upgrade
your
kubernetes
clusters
thereafter,
there
are
a
lot
of
plugin
and
there
are
a
lot
of
I.
D
Don't
compare
add-ons
compatibility
when
you
install
your
eks
cluster,
for
example,
you
directly
install
the
CSI
drivers
right.
You
have
different
add-ons
that
you
directly
install
while
creating
your
clusters,
which
it's
compatibility
with
the
latest
release
or
the
target
version
where
you
want
to
upgrade
your
kubernetes
clusters.
Thereafter,
there
is
no
tool
as
of
as
of
today,
which
does
almost
all
the
things
which
are
required,
which
are
which
is
flexible
enough
to
get
any
kind
of
inputs
and
outputs
and
in
the
osis
is
a
community.
D
If
I
say,
is
an
OSS
solution
in
this
particular
ecosystem.
There
are
barely
a
tool,
barely
some
tools
which
are
there
so
I
have
gathered
and
worked
on
these
tools.
These
are
photos
that
I
came
across
while
my
research
one
is
cubewell,
which
was
one
of
the
most
popular
tool
for
pre-cluster,
upgrade
right,
plus
a
checker,
but
now
it
is
no
longer
maintained
and
it
will
address
again.
D
The
given
conventional
files
that
you
provide,
Cube,
no
travel
or,
let's
say
Cube
Bend-
is
the
particular
bandage
which
is
used
for
the
cube,
no
travel
tool.
It
gives
all
the
information
about
the
duplicated
apis
and
the
remote
apis,
but
it,
but
it
does
not
validate
schema.
Basically,
the
community
schema
that
is
being
published
for
their
every
new
release
releases
and
also
migration
paths
are
not
being
given
in
this
particular
case,
with
the
status
of
migration.
D
It
it
defines
the
entire
info.
It
gives
you
the
info,
but
it
takes
it.
It
reads
from
the
comments
in
the
schema
table
that
you
have
and
it
does
not
provides
any
kind
of
migration
path.
For
example,
if
there
is
something
deprecated,
it
will
give
you
the
information
of
that
particular
object.
If
it
is
object
within
your
cluster,
but
it
won't
give
the
migration
path
or
let's
say
it,
won't
be
dealing
with
the
entire
schema
Edition
or
let's
say
that
open
API
step
that
we
have
for
every
new
releases.
D
And
one
thing
is:
it
does
a
validate
against
all
the
resources
that
we
have
on
it.
You
will
discussion
by
just
giving
the
docker
file,
for
example,
and
in
the
cncf
ecosystem
there
isn't
any
similar
tool
which
does
this
kind
of
activities,
and
that's
one
of
the
reason
that
we
are
proposing
Silver
Surfer
for
the
cncf
tool,
and
it
solves
all
these
different
challenges
that
we
have
with
these
existing
pooling
system
which
are
in
the
operating
Source
ecosystem,
a
high
level
idea
of
the
architecture.
D
So
let's
say:
if
you
want
to
upgrade
your
kubernetes
cluster
with
the
EPS
1.242
1.28
right,
then
there
would
be
certain
applications.
There
would
be
a
lot
of
different
things.
There
will
be
configuration
changes
right
in
your
current
ecosystem.
In
your
current
1.24
version,
you
would
be
using,
let's
say,
pod
Services
Ingress
deployment,
endpoint
slash,
so
anything
right.
Any
qubit
is
the
message
that
you
are
using,
so
the
how
the
cube,
how
silver
server
works
is
it
has
this
binary
called
Cube
DD?
D
E
D
D
E
D
D
Features
as
of
now
so
there
is
no
agent
required
for
Tubidy
to
run
so
it
can
be
installed
and
exit
from
anywhere.
Basically,
it's
just
a
simple
binary
which
can
be
used
for
all
the
relations
and
different
kind
of
configurations.
It
has
different
inputs
version
which,
which
it
supports.
Basically,
as
of
today,
it
can
directly
read
objects
from
recommendous
clusters
for
the
cube
config
file
which
you
have
given,
though
it
is
just
the
last
separate
config
annotations.
D
If
there
are
not
any
interest
applied
in
your
workloads,
then
it
will
directly
take
the
objects
from
the
manifest
from
the
existing
clusters
of
our
clothes
or
else.
If
you
want
to
validate
against
a
specific
conversion,
files
or
directors
where
it
has
all
the
manifests
and
all
the
security
resources,
then
that
can
also
be
done,
which
is
being
carried
out
in
almost
of
that
all
the
tool
that
we
have
as
of
today
in
the
end
ecosystem.
D
The
thing
is,
it
validates
against
the
open,
API
specification.
So,
whenever
kubernetes
is
a
new
version
right,
let's
say
1.28
has
been
released
so
for
1.28
they
releases
the
entire
open,
API
spec,
for
that
so
Cube
DD
uses
that
stick
for
the
validation
and
validation
and
giving
them
for
and
and
giving
the
migration
path
for
those
resources,
and
it
can
be
well,
it
can
build
it
against
any
Target.
You
will
discussor
that
you
are
giving
it
can
validate
against
the
other
different
different
apis
schema
Json.
D
The
fourth
thing
is
better
discoverability,
so
as
of
now,
it
has
different
features
which
can
help
you
scrap
the
specific
output
or
filter
out
those
output
depending
upon
your
requirements,
for
example,
if
you
want
to
weld
it
against
specific
kind
right,
let's
say
just
for
increases,
or
let's
say
if
you
want
to
ignore
certain
kinds
or
revelate
against
only
specific
group
right.
So
those
kind
of
validations
are
already
there
in
the
system
as
of
today,
as
I
mentioned
before
it
can
relate
against
any
provided,
Source
or
Target
schema
location
we
can
provide.
D
D
Let's
take
a
quick
demo
for
that,
so
I've
attached
a
screenshot
here,
so
one
of
the
major
duplication
or
the
major
challenge
when
we
discovered
and
when
when
we
started
building
this
tool,
was
the
migration
from
1.19
to
the
1.1122
version
right.
So
at
that
time,
if
we
have,
if
I
guess,
you
already
know
about
that
right,
so
there
was
a
major
deprecation
in
Ingress.
D
So
if
you
can
see,
my
screenshot
I
have
just
filtered
the
Ingress
kind
in
this
kind,
and
it
has
given
me
the
entire
details
of
the
API
version,
replicated
the
migration
status
and
also
gave
me
the
fields
that
needs
to
be
changed
into
r.
If
you
can
see
this
right
for
all
all
the
Ingress
objects
in
my
current
that
I
was
running
good.
So
if
I
quickly
show
you
a
quick
demo,
can
you
see
my
screen.
D
D
It's
okay!
Let
me
completely
to
slide
first
well,
so
it's
Community
presence
as
of
today.
So
as
of
today,
we
haven't
been
negatively
marketing
solo
server.
As
for
long
as
of
today,
we
have
four
stars
which
is
all
across
the
clock:
seven
contributors
we
have
today
for
the
syllabus
of
our
community.
The
latest
release
was
on
the
first
August,
so
I
think
so
last
two
weeks
back,
I
guess
thereafter
issues.
We
have
six
open
issues
as
of
today.
12
issues
are
already
being
addressed
and
closed.
All
the
pull
requests.
D
We
have
four
open
years,
which
is
to
be
a
validated
and
tested
and
12
PRS
have
already
been
closed
as
of
today.
So
this
is
how
the
community
is
a
bit
small
but
I
guess
this
is
one
of
the
primary
objectives
of
getting
involved
with
the
CNC
vehicle
system,
and
that
is
what
we
are
looking
forward
to
right
for
a
better
quality
collaboration
and
better
engagement
with
the
community,
so
that
we
can
shape
it
in
a
way
that
everyone
uses
it
and
everyone.
D
We
can
incorporate
everyone
feedbacks
and
use
cases
which
can
make
it
Stand
Out
basically,
and
the
near-term
roadmap
would
be.
We
have
couple
of
things
in
my
in
our
mind
that
we
would
be
working
on
further,
so
the
first
thing
would
be
as
of
now.
You
know
the
other
tools
that
we
have
talked
about
or,
let's
say,
silver
surface
itself.
It
does
not
generate
the
entire
manifest
for
you
for
the
Target
kubernetes
version,
so
this
is
one
thing
that
we
would
be
working
on.
D
So
let's
say:
if
there
are
any
deprecations,
for
example,
latest
release
sphere
right,
horizontal
pod
is
auto
scalar,
the
API
versions
have
been
deprecated,
a
new,
a
new
versions
has
been
introduced.
So
what
so?
Going
further?
With
this
feature,
you'll
be
getting
the
entire
manifest
as
well
with
the
all
the
applied
configuration
changes
which
are
required
to
be
done
for
your
Target
cubic
suppressor.
D
D
We
upgrade
check
so
whenever
you
release
a
hand
chart
right
whenever
you
upgrade
your
health
chart
to
newer
versions
so
with
the
Silver
Surfer
or
with
kubility
you'll,
be
able
to
check
the
entire
manifest
and
all
those
configurations
which
is
compatible
or
not,
with
the
target,
using
version
even
for
the
hand,
charge
directory
itself,
then
support
for
CID
check
compatibility,
which
is
there
in
Cube,
confirm
as
of
today,
but
none
of
the
rules
have
the
availability
of
a
CID
check
at
the
credit.
So
we
are
working
on
that
as
well.
D
You
will
be
releasing
this
release
wherein
three
IDs
customer
service
can
also
be
scanned,
and
if
there
are
any
things
which
can
break
down
in
the
Target
Community
structures,
then
it
should
be
a
interest
before
we'll
be
publishing
Silver
Surfer
at
different
packages
and
Homebrew
with
the
family
fund.
As
of
today
then
support
for
in
cluster
conflict.
D
So,
as
of
today,
you
need
to
provide
the
cube
config
file
for
for
the
entire
analysis
of
your
discussor
and
all
the
workloads
within
YouTube
discussion,
but
a
feature
that
helps
you
to
install
and
helps
you
installed
within
your
instruments,
clusters,
and
if
it
has
the
access
of
futile,
for
example,
or,
let's
say
the
cluster,
then
it
should
be
able
to
give
the
entire
user.
So
this
is
something
that
we
are
working
on,
which
is
not
supported
as
of
today,.
D
Support
for
that
built-in
capability
to
run
Silver
Surfer
as
a
server,
so
as
of
today,
it's
a
client-side
project,
but
we
are
working
on
to
build
it
as
a
Silver
Surfer
as
a
server
server,
because
it
will
help
you
to
integrate
with
multiple
different
ecosystems.
You
can
integrate
it
with
your
let's
say
pipeline,
so,
let's
say
other
tooling
systems
right.
It
will
open
up
the
boundaries
with
lot
more
possibilities,
which
is
which
we
have
as
a
prime
minister
today
then
upgrade
on
the
basis
of
migration
policies.
D
So
this
is
something
that
we
are
still
editing
on.
We
and
we
would
love
to
hear
your
thoughts
as
well
for
this.
So
as
of
today
right,
we
have
different
tools
in
the
ecosystem
that
from
which
we
can
create
different
policies
in
our
kubernetes
clusters,
for
example,
keyword.
No,
let's
say
the
kubernetes
itself
has
their
native
Native
mechanism,
as
of
today
with
a
Cel
right,
common
expression,
language.
D
So
as
of
today,
if
you
have
configurations
on
policies
applied
in
the
closed
clusters,
and
if
you
are
violating
those
policies,
then
it
will
break
down
your
resources
right.
It
will
break
down
your
existing
workloads.
So
what
we
are
trying
to
do
here
is
it
would
be
very
generic
approach,
wherein,
let's
say,
if
you
have
a
plan
from
Opa,
you
will
know
giveness
natively
in
which
phase
right.
D
If
there
are
policies
being
applied,
then
then
silver
server
should
be
able
to
show
you
those
policies,
and
it
will
let
you
know
that
these
policies
are
already
applied
in
your
target,
Cube
disclosure
person,
so
you
need
to
be
so.
You
need
to
work
on
those
policies.
First
make
sure
it
is
compatible
with
those
policies
and
then
upgrade.
This
can
be
a
info
kind
of
thing,
but
it
can
be
really
helpful
because
policies
will
directly
break
your
changes
if
you
are
doing
kind
of
things,
but
it
won't
break
anything.
D
B
D
Which
is
already
being
installed
in
my
system
as
of
now
so,
if
you
search
for
help
you'd
be
getting
the
entire
different
parameters
which
can
be
introduced,
and
what
does
those
parameters
right?
You
can
provide
the
ignored
flags
for
if,
let's
say,
if
you
don't
want
to
survive
the
validate
certain
things
right,
certain
kinds,
certain
name
spaces.
You
can
do
that
you
can
skip
the
tillage
verification.
If
you
want
to
you,
can
filter
on
the
basis
of
kinds
or
name
spaces.
D
You
can
select
for
specific
cumulus
version
from
which
you
want
to
Target
to
you
can
provide
the
equality
context.
If
you
have
multiple
different,
then
you
can
use
those
as
well.
So
these
all
these
things
are
natively
integrated
with
the
system
and
if
I
quickly
show
you
the
result,
how
it
looks
like
if,
today,
okay
I
already
have
the
command.
D
D
Give
me
the
entire
details
of
the
workflows
that
the
details
of
the
resources,
basically,
if
there
are
any
removed,
a
versions,
any
change
that
it
wasn't
applicable.
If
there
are
any
configuration,
then
it
will
show
the
configuration
changes
as
well,
or
else
it
will
give
the
it
will
give
you
the
migration
status
as
well.
So
what
is
the
migration
status
for
particular
version?
Basically,
as
you
can
see
here
right,
let
me
zoom
out
a
little
bit
or
visibility.
I
guess.
B
B
H
E
D
G
B
E
D
Okay,
The
Lending
is
more
about,
like
you
have
your
manifest
ready
right.
You
want
to
test
it
out
things
right,
so
those
would
be
more
towards
the
linking
I
guess,
but
in
terms
of
when
you
are
upgrading
your
activities
process
for
example,
then
I
will
have
to
think
about
it.
Maybe
linking
is
the
right
category
or
not,
but
especially
for
the
workloads.
I
think
might
go
app
delivery,
Maybe.
E
I
D
So
it
gives
me
the
magazine
status,
it
can
be
migrated
just
with
the
AP
wasn't
changed
and
if
there
are
any,
let's
say,
parameters
which
are
being
removed
or,
let's
say
or
if
there
are
any
parameters,
new
parameters
that
are
being
introduced,
then
it
will
give
me
those
statuses
as
well
here
here
in
the
status
magazine
status,
that
you
need
to
fix
those
parameters.
First,
then
it
can
be
migrated,
but
as
of
now
I,
don't
think
we
have
anything
else
to
share.
D
D
A
I
I
D
D
Let
you
know
about
those
parameters,
and
one
thing
that
we
are
also
working
on
is
to
provide
the
entire
new
manifest
for
that
with
the
right
parameters,
or,
let's
say
with
the
correct
API
version,
say
those
are
being
changed.
So
if
you
can
see
this
screen
right,
can
you
see
this
image?
Is
it
visible.
D
So
if
you
see
here
right
for
particular
in
this,
when
we
are
trying
to
migrate
from
1.19
to
1.22,
these
parameters
were
being
removed
so
and
these
parameters
were
being
addressed,
which
is
missing.
Basically
path
type
was
being
addressed,
new
new
in
the
new
in
the
newspack
of
English
right,
Service,
Port
service
member
being
removed.
So
it
will
give
you
the
entire
details
of
those
magazine
switch.
E
Yeah,
this
also
reminds
me
of
KCl
they
presented
to
us
three
weeks
ago.
It
was
a
it's
a
it
attempts
to
move
schemas
up
to
a
generic
layer
and
then
evaluate
them.
You
know
as
applied
in
yaml
Json
and
you
know
all
kinds
of
other
places:
I
just
I
I'm,
not
saying
that
there's
I'm
just
saying
that
I
guess
like
in
terms
of
where
this
would
fit
in
there's
projects
like
that
that
are
considering
coming
there's
one
called
eraser,
which
is
also
about
the
same
State
Community
wise.
E
E
G
I
mean
honestly
I
definitely
see
the
value
in
what
we're
doing
here.
I
think
it
needs
obviously
more.
You
could
always
add
like
more
of
those
rules
and
as
like,
obviously
the
API
growth.
You
would
have
to
keep
this
up
to
date,
so
there's
definitely
I
think
a
reasonable
amount
of
contributors
needed
here.
I
I've
actually
been
wondering
why
something
like
this
is
not
like
part
of
kubernetes
like
the
kubernetes
project.
As
a
sub
project,
honestly
I
can
upgrade
type
of
tool.
B
G
I
think
where
I
want
to
take
this,
do
you
want
this
like?
What
is
it
then
to
Josh's?
Point
have
other
types
of
validation
rules
you
might
want
to
put
in
there
that
go
beyond
what
you
have
in
there
right
now,
maybe
for
some
platform
engineering
efforts
where
you
want
to
forbid
like
use
certain
combinations
or
enforce
certain
constraints,
or
to
focus
purely
on
upgrades,
because
purely
on
upgrades
I
would
also
present
this
obviously
2D
to
the
sixth
of
the
kubernetes
six
as
well.
D
B
D
I
think
data
is
also
one
of
the
linking
tools
that
is
uses
to
validate
a
validate
manifest
based
upon
certain
policy
that
you
can
set
up
right,
but
not
with
the
existing
tools,
but
not
with
the
entire
images
resources
that
you
have
as
of
today
in
your
previous
clusters
versus
the
one
that
you
are
trying
to
upgrade.
Those
kind
of
capabilities,
I
think
are
very
limited
as
of
today
in
the
cncf
project,
ecosystem.
G
A
Sorry
another
side
I
just
had
is
such
a
tool
would
also
be
quite
useful
as
a
library
for
existing
tools
that
those
deployments
already
as
an
example
as
I'm
developer
of
clusteria
or
clue.
Cattle
I
could
use
that
to
kind
of
combine
that
with
dry
runs
that
I
do
before
to
actually
know
if
it's
compatible
or
not
to
do
this
CID
upgrade,
for
example,.
E
Oh
well,
thank
you
so
much
for
presenting
to
us
I,
I,
definitely
yeah.
This
seems
like
there's
around
these.
These
smaller
set
of
tools
for
kubernetes
that
are
coming
through
US
yeah,
let's,
let's
think
about
how
to
I
think
one
of
the
benefits
of
being
in
sandbox
is
supposed
to
be
cross-pollination
and
facilitation.
So,
let's
as
more
come
in
I'm,
even
thinking
KCl
is
relevant
here.
Yeah
like
let's
try
to
make
sure
you
all
are
talking
to
each
other
and.
D
D
Just
a
question
around
eraser,
so
I
was
just
looking
into
a
recommendation
which
you
shared
right.
So
it
is
more
to
us
something,
let's
say,
plus
sir,
deleting
the
overpricing
to
our
provisioning
or,
let's
say,
delete
the
unnecessary
workloads
right.
It's
something
worth
that
or
if
misunderstanding
something.
D
E
D
E
B
E
E
Yeah
the
next
thing
that
we
had
on
our
agenda
today-
I-
don't
know
if
we
have
anyone
from
this
group
Kevin.
Are
you
from
this
group
The
they're
the
group
that
had
done
the
API
enhancement
proposals
proposal
to
bring
that
kind
of
group
into
cncf
when
we
talked
to
them
a
couple
of
months
ago
we
suggested
that
they
consider
building
a
working
group
around
API
patterns
and
API
structures
and
enhancements
and
I
think
they
they
have
been.
They
have
been
working
on
that
it's
in
this
issue
here
and
so
Kevin.
B
A
E
E
E
All
right
so
going
down
the
list,
we
do
have
an
open
PR
to
set
up
translations
on
the
website.
That's
I,
think
kind
of
on
me
or
one
of
us.
Anyone
wants
to
pick
it
up
and
help
go
for
it.
I,
probably
I
will
hope
to
but
yeah
it
takes
a
little
while.
Oh
did
you
add
this,
somebody
had
a
website
in
general,
Leanne.
C
C
Yeah
so
I've
been
a
bit
busy,
but
I
will
start
working
on
the
website,
probably
starting
Sunday
I'm
going
to
be
traveling.
There's
a
lot
of
time
to
do
like
smaller
stuff,
so
I
will
create
some
issues
and,
like
specifically
around
like
platform
maturity
Matrix
to
highlight
that
on
our
website
and
the
platform
prototypes
that
we're
discussing
I
have
reached
out
to
the
getups
working
group,
but
I
think
they're
quite
busy.
They
need
something
more
specific,
I
think
before
they
can
get
started.
C
So
that's
what
I'm
gonna
do
I'm
gonna
open
the
use.
If
I
have
the
time,
I
will
even
create
a
little
bit
of
a
onboarding
guide
or
video
how
to
do
stuff
with
the
website,
but
I'm
planning
for
next
week
to
have
the
issues.
So
everyone
who
wants
to
get
involved
should
be
able
to
do
it
by
themselves
without
having
to
go
through
me.
That's
my
plan
for
next
week,
yeah.
E
E
We've
settled
on
a
set
of
levels
within
stages
within
those
aspects
that
you
can
consider
and
we're
we're
fleshing
out.
The
descriptions
of
those
now
hope
to
have
that
ready,
bye,
kubecon
the
platform
is
a
product.
That's
a
new
paper
that
another
member
of
our
group
has
just
started
sharing
with
everyone
where
he
wants
to
Aid
platform.
Engineers
seeking
to
you
know,
deliver
their
platform
as
a
product.
Take
a
look
at
that
and
contribute
and
help
out.
E
If
you
want
an
artifacts
working
group,
pretty
good
momentum
right
now,
around
kind
of
understanding,
the
current
state
around
the
many
different,
both
oci,
Registries
and
and
other
kinds
of
package
managers
figuring
out
how
to
go
next
in
in
finding
synergies
between
those
or
establishing
some
standards
yeah,
and
we
opened
the
repo
for
them
with
some
open
issues.
If
you
want
to
check
that
out,.
H
E
E
H
H
Okay,
so
yeah,
so
I
basically
put
it
in
there.
So
this
is
the
current
Charter
for
the
platform
team
right.
So
the
platform
Group
web
working
group
and
also
it's
regarding
so
there
are
several
patterns.
I
just
only
include
those
that
have
operator
in
them,
because
they're
obviously
really
to
operator
so
I
think
just
so.
If
you
look
at
I,
know
they're
at
least
on
the
artifact.io
I
know.
Most
of
the
operators
is
probably
actually
an
operator
hub.io,
but
from
the
from
the
artifact
Hub
dot.
H
H
You
know
one
I
shouldn't
even
use
the
operator
right,
so
I
guess
I
wish
to
be
able
to
create
a
survey
so
that
we
can
actually
tap
those
knowledge
about
the
new
experiences
using
operator
when
it
should
be
done
when
it
shouldn't
because
I
already
know
there
are
concerns
about
scalability
using
too
much
operator
and
all
that
good
stuff,
so
so
I.
This
is
just
one
other
examples
like
I
think
can
think
of.
Maybe
having
operator
was
an
existing
pattern.
H
H
So
I
don't
know
if
it
can
be
part
of
a
group
or
is
I
think,
but
it's
I
think
it's
interesting
to
create
some
original
survey
so
that
we
can
actually
get
really
the
knowledge
about
what's
going
on
with
operator
world,
and
should
we
even
write
operator
and
when
should
we
write
it?
Okay,
it
can
be
part
of
that.
The
platform
teams.
You
know
because
the
platform
has
a
lot
of
momentum
going
on
so
and
an
operator
could
be
part
of
that.
E
Very
cool
I
mean
I
guess
when
I
think
of
like
platforms
like,
and
we
talk
about
like
adding
capabilities
to
platforms
like
one
very
kubernetes.
That's
way
to
do,
it
is
to
add
operators
into
kubernetes,
so
I
see
a
little
bit
of
a
tie
with
platforms
from
that
perspective,
I
think
it's
okay
to
I!
Think
it's
okay
to
also
pursue
this
at
the
tag
level.
E
Parallel
to
platforms,
I
think
you've
done
a
lot
of
great
initial
work,
actually
gathering
this
all
in,
but
and
and
bringing
people
and
I
think
that's
probably
we
need
a
few
people
to
help
kind
of
review
this
survey
and
bring
It
Forward
and
review
this
work
and
yeah
I.
Guess
next
steps,
maybe
to
share
and
kind
of
gather
up
a
few
more
folks.
H
C
Think
what
I
have
right
right?
I'm
sorry
go
ahead.
No,
it's!
Let's
start
by
asking
around
select
to
for
people
to
come
and
give
feedback,
and
then
this
would
be
another
thing
that
we
could
highlight
on
the
website
also
similar
to
the
platform
maturity
model.
It's
not
a
matrix
anymore.
It's
a
model
now
right
But.
Ultimately
it
does
look
like
it.
It
makes
the
most
sense
to
do
make
it
like
a
white
paper,
because
that's
a
process
that
we
already
have
experience
with.