►
From YouTube: TAG General Meeting - 2022-08-17
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
C
D
Yeah
I'm
good,
it's
it's
just
a
little
late
night
for
me,
like
I'm
in
the
midnight
now.
C
I'm
looking
over
the
agenda,
I
didn't
really
have
much
on
the
agenda
today.
C
C
C
Glasses,
are
you
you're?
Are
you
what's
your
name?
Are
you
the
one
who's
been
contributing,
A,
Potato,
Head
yeah.
B
Yeah
we
met
briefly
over
at
the
open
source
Summit,
so
yeah
I
meant
to
I
meant
to
get
around
to
trying
to
join.
One
of
these
not
sure
I
figured
I'd
just
be
more
of
a
lurker
for
the
first
call,
because
I've
never
been
on
one.
So
I
don't
want
to
mess
up
the
flow,
but.
C
I
don't
know
yeah
I've
been
there's,
there's
some
there's
some
stuff
to
do
in
pod.
Potato
Head
is
a
few
open,
PR's
and
issues
there.
So
I'm
hoping
to
take
a
look
there
soon.
Famous
last
words.
I
know:
I've
got
a
couple
open,
PR's
of
mail,
but
if
you
wanna,
you
wanna
take
a
look
at
any
of
those
it's
great
to
have
some
some
help.
There.
B
Yeah
I
actually
opened
up
PR
yesterday
or
two
days
ago.
It's
a
real
nuanced
thing.
My
GitHub
username
has
uppercase
letters
in
it
and
that
breaks
stuff.
So
when
trying
to
contribute
locally,
I've,
always
well.
I've
only
contributed
a
few
times
previously,
but
I've
done
some
stuff
to
make
it
work
and
I
thought
well.
I
should
probably
actually
contribute
that
back.
E
E
Group
updates
have
not
happened
for
quite
a
while.
Apologies
on
that
I
think
some
of
us
driving
the
the
work
group
Charter
were
caught
up
in
a
few
Arc
changes,
but
the
good
news
is
that
we
are
resuming
the
work
group
activities.
The
white
paper,
the
next
sections
of
the
white
paper
that
we
wanted
to
fill
out
are
being
finalized
at
this
point,
and
we
also
have
a
few
new
user
interviews
coming
up
for
from
KS
practitioners
in
the
community,
which
includes
iFood
and
FIS.
E
So
some
of
those
user
stories
will
go
into
our
work
group
repo
and
we
will
make
it
into
the
white
paper
as
well.
So
at
this
point,
as
as
we
speak,
we're
just
working
with
the
broader
team,
which
also
comprises
folks
from
the
other
chaos
projects
on
how
our
next
few
sections
should
be
covered
in
the
white
paper.
What
we
have
now
is
something
like
a
basic
refresher,
but
we
want
to
basically
refresher
or
introduction
to
chaos,
but
we
want
to
add
some
more
material
in
there.
So
I
think
this
Friday.
E
C
C
E
E
E
E
Not
specifically,
there
are
a
few
updates
to
the
the
litmus
chaos
projects
which
might
be
of
interest
to
the
amp
delivery.
Community,
which
I'll
probably
add
into
the
agenda,
has
a
very
quick
update
session
on
what
we're
doing
in
the
project,
but
otherwise
I
just
wanted
to
sort
of
pop
in
and
say
that
we're
sort
of
resuming
the
work
group
and
what's
coming
up
next
I'll,
share
that
in
the
selection
here
as
well.
C
I
guess,
on
the
on
the
topic
of
the
working
groups,
I'll
give
a
quick
update
on
the
other,
the
couple
things
that
are
coming
out
of
Cooperative
delivery.
So
right,
multi-tenant,
paper,
I
mentioned
I,
don't
think
we've
really
I
actually
had
covered
last
week.
So.
E
C
I,
don't
think
we've
made
so
much
progress
in
the
past
couple
weeks,
but
I
know
that
Alex
Jones
and
I
had
made
some
contributions
there
in
Late
July,
so
we'll
continue
iterating
there.
It's
definitely
I've
seen
a
couple
articles
out
of
red
hat
the
past
couple
weeks.
There's
definitely
a
lot
of
interest,
so
you
know
we'll
see
if
we
can
keep
working
on
that.
Another
thing
that
I
was
just
going
to
mention.
I
know
that
I've
said
that
I'll
write
up
the
Cooperative
delivery.
C
You
know
where
we're
going
with
that.
Why
we
have
it
and
try
to
build
some
momentum.
I
just
wanted
to
mention
I've
been
thinking
a
lot
like
platform
as
product
all
that
kind
of
stuff
that's
been
floating
around
the
past
year
or
so,
and
I
feel
like
that
when
we
form
the
Cooperative
delivery
group,
it
was
kind
of
with
that
kind
of
thing
in
mind
how
to
coordinate
platform
capabilities
with
the
applications
that
are
being
delivered
so
that
you
know
they're
all
in
sync.
C
At
least
that
was
out
of
my
thought
so
that
as
I
I
just
wanted
to
throw
that
as
I'm
thinking
about
how
we
might
write
an
article
about
Cooperative
delivery,
I've
been
thinking,
maybe
we
wrap
it
and
couch
it
as
as
defining
and
helping
our
users
understand
what
a
platform
is
and
how
you
know
you
can
integrate
a
platform
with
with
apps
this
one.
That's
just
something:
I
was
thinking
about.
E
C
C
I
think
the
only
other
thing
that
I
was
going
to
mention
in
this
call.
If
there's
no,
it's
not
on
the
agenda,
is
that
there's
been
some
discussion
recently
in
the
in
the
talk
and
I
want
to
mention
this
because
I,
because
you
all
are
here,
you
know
just
to
let
people
know
that
want
to
participate,
we're
trying.
C
You
know
the
Talk
reviews
all
of
the
projects
coming
in
and
we've
been
discussing
how
the
tags
can
better
support
the
top
in
that
primary
job
of
theirs,
and
one
of
I
mean
one
of
the
ways
is
to
help
them.
When
there
are
projects
coming
in
to
understand
whether
they
fit
and
and
how
we
can
support
them.
C
You
know
if
they
don't
so
I
I
mean
I'm,
taking
a
little
inspiration
from
that
to
to
get
a
little
deeper
into
the
sandbox
projects
that
we
have
to
understand
them,
and
you
know
understand
how
we
can
support
the
talk.
C
The
technical
oversight
committee,
by
the
way,
that's
what
I'm
the
group
that
leads
the
technical
side
of
the
ncf,
so
I
guess
yeah
I
just
wanted
to
share
like
if
you
all
you
know,
wanna
are
looking
for
ways
to
contribute
like
that,
might
be
a
place
to
start
or
people
looking
for
ways
is,
is
to
review
the
the
sandbox
projects
and
have
opinions
on
how
they
fit
in
the
cncf
and
how
they
support
our
users.
I
guess
that's
our
mission.
C
C
Don't
have
any
projects
scheduled
to
talk
today.
You
know
there
was
a
follow-up
from
the
cloud
native
PG
group
last
time
and
I
think
Thomas
took
that
offline,
so
I
haven't
heard
anything
back
so
I'm,
assuming
that's
okay
and
the
same
thing
with
SRE,
Works,
actually
hongcha
I,
think
that
might
be
with
you
also
Thomas
said
he
would
take
care
of
that.
Are
you?
Okay,
with
that
yeah.
D
D
Like
yeah,
I,
I
I
know
this.
Those
people
personally
like
from
Alibaba
yeah
I,
will
take
care
of
them.
B
I
have
like
a
real
random,
quick
question:
do
you
do
you
all
maintain
that
GitHub
repo,
it's
minor
thing,
but
the
time
on
that
doesn't
seem
to
match
the
time
of
this
meeting?
I
only
noticed
because
I
was
like
oh
shoot,
I
have
a
conflict,
I
won't
be
able
to
join
and
I
happen
to
click
through
and
I
was
like.
Oh
actually,
it's
an
hour
earlier
than
what
what
that
link
said.
D
I
think
yeah,
due
to
the
daylight
saving
time
like
this.
The
time
is
like
changing,
sometimes
not
consistent,
yeah.
D
Felt
like
we're
trying
to
fix
that,
like
like
the
8
8
AM
Pacific
time
is
the
it's
the
normal
one,
yeah.
C
There's
a
way
to
this
to
to
subscribe
to
a
notification,
let's
see
if
I
can
I'm
trying
to
find
it.
It's
like
the
cncf
community
I
get
a
notification
every
like
Friday
that
this
meeting
is
coming
up.
B
And
I
guess,
while
you're
looking
for
that
be
curious,
if
I
was
understanding
what
you're
talking
about
Josh
correctly
and
that
as
things
change
in
the
platform
and
there's
dependent
applications
that
you
don't
need
that
platform
to
change,
is
that
kind
of
what
you're
talking
about
like
if
I
upgrade
to
kubernetes
122
and
they
remove
certain
apis
that
the
application
team
has
to
have
kind
of
their
changes
staged
or
whatever
to
deploy?
You
know
their
updated
version
of
their
Ingress.
Let's
say
that
that
is
using
an
old
API.
C
I
would
say:
that's
included,
I
what
let
me
paste
in
the
charter.
What
you
know
what
we
were
originally
kind
of
going
for
is
even
at
the
initial
deployment
like
when
you
deploy
your
app.
You
also
have
a
lot
of
dependencies.
You
know
Service
dependencies,
identity,
databases,
observability
I
mean
forget
about
computed,
Network
and
stuff,
and
how
do
you
coordinate
that
so
that
you
know
it's
a
seamless
process?
It's
not
like
one
guy
deploys
a
platform,
one
person
deploys
an
app
and
then
somebody
else
has
to
configure
the
bindings
and
things.
C
But
what
you're
saying
is
is
relevant
too,
like
how
do
I.
You
know
continuously
deploy
an
app
and
continuously
deploy
the
platform
and
keep
them
coordinated.
So
yeah.
B
Yeah,
that's
something
that
we're
we
always
we're.
Still
relatively
new
to
production,
workloads
and
kubernetes,
like
about
less
than
a
year,
I
would
say,
but
as
we
ex
as
we
see
more
people
on
board
at
our
company,
that's
definitely
like
how
do
we
ensure
that
we,
you
know,
find
things
ahead
of
time
and
communicate
that
in
advance?
Hey
we're
going
to
this
version
of
kubernetes
and
it's
going
to
deprecate
these
apis,
and
we
see
that
you're
running
something
that's
using
that
API.
B
C
I
feel
like
I
need
to
note
that
down
yeah,
that's
like
that's
like
you're,
giving
us
a
use
case,
you're
giving
us
you
know
some
good
user
feedback
there,
like
one
of
the
issues,
is
how
do
I
update
the
platform
and
keep
the
apps
you
know
running
alongside
it.
B
Our
our
sulfur
now
has
been
a
little
bit
messy,
but
we
used
Cube
dump
to
dump
everything.
That's
in
the
cluster
out
to
yaml
files
on
you
know,
you're
on
someone's
machine,
and
then
we
use
Pluto
to
scan
all
those
files
and
see
hey.
Does
anything?
Look
like
it's
going
to
be
broken
in
the
next
kubernetes
version,
so
I
it
feels
like
it.
Could
those
two
projects
could
work
together
a
little
bit,
so
it's
easier
but
or
somebody
could
come
up
with
a
third
project
that
kind
of
uses
both
or
something.
C
That's
pretty
interesting,
I
mean
that's,
come
up
with
openshift.
Recently,
that's
what
I'm
spending
most
of
my
time.
These
days,
where
like
before
we
do
an
upgrade,
we
will
say
we
won't
do
it
automatically,
because
124
deprecated
these
apis
and
we
give
some
advice
like
here's,
how
to
discover
like
those
like
Cube
cuddle,
get
API
requests
or
something
I
can't
remember,
and
you
can
get
you
can
find
out
who's
been
using
certain
apis
or
which
ones
are
used.
A
B
C
B
We
we
haven't
gotten
to
a
point
where
we're
like
replacing
clusters
we're
doing
In-Place
upgrades,
so
yeah
I
mean
everything
we
do
is
terraform
for
IAC
for
provisioning
and
then
that
bootstrap
bootstraps
flux
and
then
flux
does
all
the
configuration
for
us
and
then
right
now
we
have
GitHub
actions
is
our
primary
way
for
people
who
are
writing
like
engineered
solutions
to
deploy
to
the
Clusters.
C
B
So
exactly
we,
we
would
but
there's
nothing
that
stitches
together
today
the
engineered
Solutions,
which
is
something
that
we're
looking
at
like
doing
at
some
point
of
like
hey.
If
I
do
destroy
this
cluster
and
I
rebuild
it
can
I
also
have
it
redeploy,
you
know
all
the
workloads
which
there's
a
couple
different
ways
that
we're
looking
at
that
might
be
an
option,
but
today
it's
been
hey.
Don't
don't
spend
time
on
that?
Just
do
your
In-Place
upgrades
and
call
it
a
day.
B
We've
had
to
do
that.
I
think
we've
had
to
blow
away
a
cluster
once
because
something
went
real
funky
in
Azure
with
it,
but
I
mean
we
Blow
Away
Acro
a
Sandbox
cluster
periodically
to
confirm
that
everything's
stole
our
IAC
and
our
our
flux.
Configurationist
code
still
works,
but
we're
not
doing
that
to
our
all
of
our
other
clusters
with
regularity.
C
B
And
actually
I
should
say
that
that's
where
we
came
across
Pate
ahead
is
we
wanted
some
type
of
an
app
at
the
end
of
that?
If
we
did
a
destroy
or
we
do
some
upgrade
or
something,
how
do
we
ensure
like
something?
You
know
we
can
test
something,
that's
not
engineered
by
somebody
else.
It's
something
that
we
kind
of.
Have
you
know
control
over
and
understanding
of.
So
that's,
basically,
at
the
end
of
the
cluster
upgrade
hit.
Potato
Head,
like
oh
he's,
he's
there
he's
smiling
so
we're
good.
E
I
just
want
to
mention
here
we
are
doing
that
as
well.
I
think
Potato
Head
is
one
of
the
popular
apps
here.
One
of
the
first
thing
that
goes
into
any
newly
confident
clusters.
C
C
All
right,
hey,
Amy,
how's
it
going.
A
C
A
C
C
A
What
I
see
down
here
is
basically
like
at
the
bottom.
It
says
like
the
1600
UTC,
which
might
have
been
correct,
Maybe.
B
I
only
pointed
it
out
Amy
because
I
wanted
to
join
this
meeting
and
I
I
saw
that
link
and
I
thought.
Oh
shoot.
I
have
a
conflict
that
at
that
time
in
my
time
zone,
but
then
I
went
ahead
and
still
clicked
through
and
found.
Oh,
it's
actually
an
hour
earlier
than
what
the
the
GitHub
link
said.
So
it's
like
I
can't
join
great,
but
I
was
like.
Oh
I
probably
should
mention
that
yeah.
A
That's
actually
quite
compelling
and
here's
a
better
link
for
like
where
this
is
listed
on
the
calendar.
C
A
C
But
I
also
have
this
thing
that
I
have
been
using
recently.
It's
actually
Thomas
set
this
up
and
it's
actually
been
kind
of
working
for
me.
It's
you
sign
up
for
that
group
and
it
sends
you
a
notice
like
on
Monday
or
Friday,
or
something
before
the
next
meeting.
A
No
good,
okay,
all
right,
I'm
glad
I
dropped
in
then
small
small
little
Joys
excellent,
okay,
perfect!
Oh
yeah,
the
community
cncfio,
that
is
a
Meetup
page
kind
of
I.
C
A
Been
I
mean
so
we
created
those
groups
to
be
able
to
see
if
people
wanted
to
be
able
to
use
them.
That
was
kind
of
in
a
time
when,
like
we
were
having
like
tons
of
Zoom
bobbing
problems,
just
like
all
over
and
so
like,
this
is
basically
your
backup.
A
Like
you
did
fine
like,
as
far
as
like
the
keeping
keeping
the
Community
page
like
like
super
handy
and
all
of
that,
but
for
the
moment
like
people
are
mostly
like
GitHub
and
zoom.
But
should
we
come
back
into
a
space
where,
like
there's
plenty
of
Zoom
bombing?
This
is
how
to
be
able
to
resolve
that.
C
Okay,
so
I
think
we're
good
here
today.
Anyone
want
to
talk
about
anything
else.