►
From YouTube: GitOps Working Group Meeting 20210708
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
Okay,
thanks
dan
for
volunteering,
to
be
tribute
for
a
note
taker
and
also
please
anyone
else
do
pitch
in
for
taking
notes.
Welcome
everyone
to
the
july
get
ops
working
group
monthly,
meeting
july,
8th,
2021,
1800
gmt,
which
is
for
my
time
2
pm,
and
there
has
been
a
lot
of
progress
last
couple
months,
including
including
this
month.
A
So
we'll
go
ahead
and
post
the
I'll
go
ahead
and
post
the
the
link
in
the
chat
to
the
meeting
notes-
and
you
know
just
please
anyone
feel
free
to
add
topics
to
the
bottom
of
the
topics
list.
And
if
there's
something
that's
really
high
priority
that
we
might
not
get
to
just
just
speak
up.
And
let
us
know.
A
Thanks
so
I
guess
we're
going
to
start
with
looking
at
the
several
of
the
different
committees,
the
the
events
committee,
the
principals
committee
and
the
website
project
christian
you're.
First
on
the
topics
list
for
the
events
committee.
B
Yeah,
so
the
really
big
update
is
the
the
cfp
is
open
for
getupscon
here
in
l.a,
so
it's
going
to
be
again
a
day,
zero
event
with
kubecon.
B
It's
gonna
be
a
hybrid
event,
so
for
those
that
can
make
it
out
we'll
have
stuff
in
person
and
then
there
will
be
stuff
to
to
watch
remotely,
not
100
sure
how
that's
going
to
work.
The
cncf
is
going
to
take
care
of
a
lot
of
that
for
us,
but
the
the
big
thing
is:
the
cfp
is
open,
so
go
ahead
and
if
I
drop
the
link
in
the
in
the
in
the
document
of
where
to
submit
cfp's
that
is
open
through
july
25th
and
so
really
excited.
B
This
will
be
our
second
event
and
it'll,
and
it's
also
our
first
in-person
event.
So
it's
gonna
be
really
cool.
So
that's
the
biggest
update
from
the
events
committee
and
we're
right
now.
I
guess
just
working
with
the
cncf
now,
instead
of
doing
it
just
all
by
ourselves,
working
with
the
cncf
to
get
this
event.
B
A
Yay,
that's
super
exciting
and
yeah.
Please
everyone
just
check
the
link.
Excuse
me
check
the
check
the
docs
for
the
link
that
christian
put
in,
I
think
and
I'll
just
paste
it
into
the
chat
too.
A
Okay,
so
it
looks
like
my
topic
is
up
next,
it's
really
just
an
update
on
the
for
the
principals
committee.
A
You
all
heard
last
time
that
we
that
the
principal's
committee
had
released
a
a
pre-release
version
of
the
revised
github's
principles,
not
extraordinarily
different
than
what
was
already
out
there,
but
but
one,
but
one
that
went
had
a
pass
through.
Essentially
all
the
members
of
the
get
ops
working
group,
specifically
people
that
are
that
are
meeting
weekly
focused
on
the
principles
who
are
part
of
that
committee,
have
been
helping
to
make
sure
that
it
really.
A
It
really
makes
sense
to
you,
know
the
bro,
the
broadest
users,
the
broadest
audience,
and
that
it's
technically
accurate
for
for
for
what
the
intention
of
those
principles
are
so
the
pre-releases
out
there
there
has
been
some
we've
received
some
feedback
from
from
several
different
people
and
we're
still
looking
for
feedback
on
them.
But
the
feedback
that
we've
received
so
far
is
that
some
of
the
wording
might
be
a
little
bit
repetitive.
A
And
perhaps
the
initial
sentence
description
before
the
before
sort
of
the
full
paragraph
description
of
each
principle
might
maybe
a
little
could
maybe
it
could
be
a
little
more
catchy.
So
the
the
the
committee's
been
working
on
that
and
that's
really
the
update.
The
only
thing
I
wanted
to
mention
is
that
we
have
a
stated
goal
of
having
a
full
release.
We
have
not
yet
set
a
deadline
on
that.
A
We
do
have
a
milestone,
but
the
milestone
doesn't
have
a
date
attached,
so
we're
looking
forward
to
a
v
1.0.0,
but
we
just
haven't
set.
We
have
some
criteria
on
what
so
far
and
what
that
should
mean,
and
if
you
want
to
see
that
please
take
a
look
at
the
document,
the
opengetups
or
sorry
open,
dash,
getups.
A
Excuse
me:
documents
repo.
There
is
a
milestone
of
the
1.0.0
milestone
and
so
far
the
issues
that
we've
identified
are
linked
there
as
as
important
for
that
milestone,
so
anyone
that
wants
to
get
involved
in
that
please
do.
Please
join
the
principal's
committee
meeting
meetings
which
are
weekly
and
they're.
Also
in
this
committee.
Excuse
me
in
the
meetings
document.
B
Hey
scott,
can
you
post
a
link
to
the
principal
someone
asked
on
chat
absolutely.
C
A
Thank
you
donald
also,
nice,
to
see
also
nice
to
see
you
and
youtube
fancy:
hey
thanks
for
joining
great
yeah.
That's
that's
perfect,
and
and
just
to
be
clear.
There
is,
you
know
if
there
is
a
main
branch,
but
the
the
there's
also
a
pre-released
version,
so
check
out
that
version.
If
you
want
to
see
the
principles
at
that
stage
there
there
there
are
some
updates
in
progress,
so
just
just
make
sure
to
match
the
version.
A
If
you
want
to
see
you
know
what
has
been
released,
only
last
thing
is
I'll:
go
ahead
and
link
to
that
I'll.
Go
ahead
and
link
to
that
milestone.
For
for
folks-
and
here
we
go,
I
just
wanted
to
suggest
one
thing
that
we,
I
I'm
hoping
that
we
reach
a
v
1.0.0
or
basically
a
full
release
that
we
feel
comfortable
with
sooner
than
this,
but
I
think,
an
absolute
deadline.
I
would
love
to
propose
that
an
absolute
deadline
is
sometime
before
kubecon
north
america
2021.
A
I
think
that
would
be.
It
would
be
wonderful
to
make
sure
that
when
we
go
there
and
we
actually
do
get
ops
on
that,
we
aren't
still
kind
of
toiling
over
an
initial
full
version
of
these
principles.
That
would,
I
think
that
would
be
kind
of
a.
I
think,
that's
unnecessary
personally,
and
I
I
think
that
we
have
like
a
very,
very
good,
not
only
momentum
but
like
a
really
good
mutual
understanding.
It's
just
a
matter
of
getting
not
only
some
of
you
know
helping
with
some
of
the
catchiness
update.
A
It's
not
really
changing
the
underlying
content,
but
also
bringing
in
some
of
the
other
supporting
documents
that
we
have
in
earlier
drafts.
That's
it
for
my
update,
unless
anyone
else
from
the
principal's
committee
has
something
they
want
to.
I
know
there
are
a
few
of
you
on
here.
If
you
had
anything,
you
wanted
to
say
about
that.
A
D
Yeah,
I
can
speak
to
that,
so
the
website
is
nearly
complete.
The
design
was
done.
All
the
coding
is
done.
If
you
haven't
seen
it,
let
me
see
if
I
can
post,
let
me
grab
the
I'll
grab
the
the
preview
url
I
was.
D
I
was
getting
some
help
from
scott
today,
because
the
only
thing
that
was
keeping
me
from
having
this
posted
live
in
the
pr
was
actually
just
figuring
out
the
the
way
to
preserve
history
while
moving
things
between
get
repos,
which,
which
is
a
silly
problem,
but
but
scott
was
helping
me
out
with
that.
I
think
we'll
be
able
to
get
it
out
today.
Yeah.
A
And
you
basically
got
it,
I
I
was
just
gonna,
send
you
a
couple
of
fun
tricks,
but
I
actually
had
back-to-back
meetings
right
before
this.
So
sorry
about
that,
but
we
can
we'll
tag
team
after
yeah.
D
We'll
we'll
get
it
done,
I
think
today,
though
I
you
gave
me
pretty
much
everything
I
needed
and
I
just
need
to
execute
on
it.
So
this
is
the
website,
we'll
add
additional
members.
I
think
one
of
the
things
you'll
notice
with
this
I'll
share
my
screen
really
quick,
so
actually
hang
on.
D
So
one
of
the
things
you'll
notice
with
this
is
obviously
there's
a
focus
on
getting
involved
where
we're
asking
people
to
jump
into
the
subreddit.
D
So
many
of
you
may
not
already
know
that
there
is
actually
an
official
subreddit,
it's
just
our
get
ups,
and
so
now
we'll
we'll
be
promoting
stuff
there
and
it's
not
a
super
active
area.
Yet
it's
a
pretty
new
subreddit,
so
there's
only
500
people
in
there,
but
would
love
to
get
more
participation
from
people.
I
think
ongoing.
You
know
people
sharing
their
tricks
and
their
tips
and
their
ideas
and
their
concerns
and
real
stories
and
discussions,
and
things
like
that
could
be
really
really
valuable.
D
Obviously,
the
meetings
opening
an
issue
and
then
our
slack,
we
do
have
a
slack
if
you're
not
aware
of
it.
So
please
join
it.
There
is
a
sig
app
delivery,
mailing
list
with
our
own
topic
there
with
project
boards
and
then,
of
course,
we've
got
the
committees
that
are
running
so
that's
great,
and
then
we
also
have
this
section
on
member
companies.
Now
we've
had
a
little
discussion
about
what
a
member
company
is
in
this
case.
D
Each
one
of
these
companies
actually
has
essentially
like
governance,
like
a
vote
like
a
like
a
governance
vote
on
the
project,
but
we
have
a
whole
bunch
of
people
who
have
already
self-declared
that
they're
an
interested
party,
so
we're
thinking,
maybe
we'll
just
listen
to
the
city's
interested
parties.
We've
got
dozens
and
dozens
of
companies
there,
so
maybe
give
people
more
chances
to
formally
show
that
they're
engaged
with
this
process
that
they're
signing
on
to
these
principles,
etc.
D
We
have
the
current
version
of
the
principles
and
then
oh
wait.
Sorry
I
have
to
I
updated
it,
but
I
I
gotta,
I
gotta
push
my
commit
my
commit
sitting
on
my
on
my
local
machine,
still
rookie
mistake
and
then
we've
got
all
the
all
the
events
that
will
be
listed
there,
as
well
as
the
past
events
that
we'll
get
into
so
yeah.
D
That's
the
website,
we'll
I'll,
get
those
commits
in
and
get
that
pr
out,
hopefully
today
and
then
love
to
have
if
people
want
to
get
involved
and
help
improve
and
make
additions
or
open
up
pull
requests.
This
is
you
know,
going
to
be
governed
under
our
same
principles.
So
it's
all
just
a
pr
to
commit
and
we'll
get
that
automation
all
set
up
and
rocking
and
rolling.
A
I'm
pretty
excited
by
the
way
for
getting
for
seeing
that
up.
It
looks
amazing
from
my
point
of
view,
one
of
the
notes
remember
from
the
website
the
events
committee
meeting
where
we
focus
on
the
website
was:
oh
actually,
you
know
what
I
am
going
to
hold
my
comment
until
after
the
hands
that
are
raised.
A
Sorry
about
that
jesse.
A
Oh,
my
bad
christian
yeah.
B
Yeah,
my
mind's,
a
quick
because
it's
a
dumb
question.
Let's
see
because
I
know
we're
toying
around
with
the
the
official
domain
that
we're
gonna
do
we
do
we
come
up
with
official
domain.
I
know
we're
looking
for
opengetoff.dev
or
dot
io.
Well,
what's
the
just
just
so
I
know
so
like
when
it
goes
live.
I
can
start
like
blasting
that
out
to
everyone
I
know
dan.
You
want
to
take
that
one.
D
Yeah,
so
I
don't
know
that
we've
reached
consensus
on
dot,
dev
or
dot
io
between
those
we
own
both
those
domains,
so
we
can
use
either
and
then
one
of
them
just
needs
to
become
the
canonical
version,
the
arg
and
as
well
as
dot
org
good
point,
scott.
The
I
think
the
argument
for
dot
io
was
that
it's
just
very
popular
there's
a
lot
of
dot
io
projects.
D
The
argument
against
I
o
is,
of
course,
that
it
stands
for
ish
indian
ocean
territories,
which
is
not
you
know,
it's
not
a
big
deal,
but
it's
like
there
was
that
whole
issue
with
like
bitly
and
like
dot
l
y.
You
know
it's
like
well,
it's
like
a
libyan
domain.
D
Dev
is
dedicated
to
development
projects
and
it
does
require
ssl.
So
you
can't
have
a
dev
domain
without
ssl
and
then
of
course.org
sounds
more
official,
but
maybe
it
sounds
older.
Maybe
it
sounds
more
stodgy,
so
I
don't
think
we
have
a
consensus
on
it.
We
own
them,
but
I
think
at
this
point
everybody
involved
has
just
been
like.
I
don't
really
have
a
super
strong
opinion.
I
lean
a
little
bit
towards
dev.
Some
other
people
were
leaning
a
little
bit
more
towards
dot
io,
but
probably
not
a
huge
deal
lol.
D
So
yeah.
If
you
have
a,
if
you
have
a
good
opinion
about
it,
please
please
put
it
up
there
and
again,
we'll
we'll
have
all
these
domains
we'll
point
there.
We
just
need
to
have
one
be
the
canonical
for
life.
A
A
Excuse
me
common.net
by
that
that
I
don't
think
anyone
in
the
get-ups
working
group
knows
which
entity
or
who
purchased,
that
that
was
just
as
the
name
was
being
decided
on,
so
it
it.
I
will
we.
There
is
no
assumption
that
this
was
a
name
squatting
move.
It
might
have
been
purely
good
faith
that
someone
intended
to
pass
it
on
to
the
cncf,
but
so
far
there
has
been
no
move
made
for
that.
A
D
E
And
that
jesse's
old
also
saying
that
okay,
so
I
think
jesse
is
up
you're
I
that
was
my.
I
had
a
question
and
a
comment.
That
was
my
question
so
now
my
comment
is
just
in
case.
We
didn't
say
it
formally.
The
website
looks
awesome.
Good
job
really
well
done.
I
know
it
was
really
like
kind
of
solo
than
team.
Then
you
know
so
awesome
work
thanks.
D
I
saw
a
couple
tada
emotes,
yeah,
tiago
tiana
has
been
somebody
he's
been
somebody
that's
doing,
design
and
development
work
for
code
fresh
for
a
long
time
and
the
one
of
the
reasons
I
love
thiago
is
that
he
does
both
the
design
and
development,
and
so
it's
nice,
when
you
have
somebody
who's,
a
good
designer
who's,
a
good
developer.
They
can
just
get
it
done
and
he's
always
been
quick
and
responsive
and
no
problem.
I
don't
think
not
to
not
to
detract
at
all
from
his
contribution.
D
Obviously,
but
I
don't
think
he
necessarily
knows
a
ton
about
like
what
open
get
offs.
Even
is
you
know,
but
he
was
like
what
am
I
doing.
Making
this
whole
get
ups
thing:
you
got
a
logo,
you
got
colors
awesome,
I'm
on
it.
You
know
so
obviously
great
to
have
his
help
in
making
this
amazing
website
and
and
glad
to
hear
good
feedback
about
it,
and
I
will
pass
on
the
the
kudos
from
the
team
that
he's
I'm
sure
he'll
be
very
happy
to
have.
A
We
do
not
have
any
other
yeah,
hey
christian,
absolutely
we!
You
know
the
events
committee
should
definitely
be
talking
about
a
party.
That
is
one
thing
that
I
don't
think
came
up
yet
so
it
has
not
come
up
yet,
but
we
we
that's,
definitely
something.
A
I
hope
that
makes
its
way
into
the
notes.
We
don't
have
any
other
topics
right
now
on
the
list.
So
it's
just
open
at
this
point
for
us
all
to
think
about
or
say,
what's
on
our
mind
or
or
suggest,
a
topic.
A
Or
if
anyone
has
any
questions
that
might
be
a
good,
you
know
it
doesn't
have
to
be
extraordinarily
formal.
We
just
raise
hands
to
make
sure
we
don't
talk
over
each
other
and
that
we're
being
respectful.
That's
all
christian.
B
Yeah,
that's
actually
one
thing
I
I
forgot
to
mention
about
the
about
the
get
ups
con
is
that
we
are
still,
I
think,
believe
we
are
still
looking
for
sponsors
if
you
want
to.
If
you
want
your
name
there
yeah,
we
just
ping
me
and
I'll,
put
you
in
contact
and
how
to
how
to
get
a
sponsorship
package
there
right
now.
B
Red
hat
is
just
a
diamond
sponsor
right
now,
that's
showing
up
on
the
site,
but
that
doesn't
mean
that
there's
not
slots
open
for
for
further
sponsorship.
So
if
you
want,
you
know
your
name
up
there
and
are
interested
in
sponsoring
a
ping
me
and
I'll
put
you
in
contact
with
the
the
person.
If
you
want
to
you
want
to
sponsor.
Oh
there,
we
go
dan,
put
the
chat
thanks
and
that's
it.
A
Yeah,
do
you
sorry
real
quick?
Do
we
have
the
the
sponsorship
package
already
that's
shareable
to
folks.
A
Cool
dan.
D
Yeah,
I
was
just
going
to
add
on
that
that
code
fresh
has
already
put
in
our
stuff
to
sponsor.
Officially,
I
think
we
works
has
already
put
in
to
sponsor
officially,
and
the
packages
are
pretty
good.
Actually
there's
some
cool
cool
things.
You
can
do
a
gold
sponsorship's,
only
7,
500
bucks
and
there's
an
opportunity
to
generate
some
leads
off
of
that.
D
So
I
think
probably
like
90
of
the
people
in
this
call
are
probably
red
hatters,
the
people
that
I
don't
know
so
red
hat's
already
in
so
I
guess
that
one's
done
but
send
it
on
to
people
the
the
kind
of
big
vision
that
we
talked
about
in
the
events
committee
was
we
really
want
to
do,
get
ops
con.
D
Yeah
sell
your
nfts
like
you
can
we
can
make
this
a
really
big
thing
and
when
you
think
about
kubecon,
you
know
I
love
kubecon,
it's
my
favorite
event,
but
it's
funny
when
you're
at
kubecon
to
realize
that,
like
oh,
like
a
lot
of
these
people
are
focused
on
stuff
that
I'm
not
really
focused
on
like
you've
got
this
whole,
like
the
storage
folks
over
here.
Who
are
all
solving
that
you
know
problem
which
is
super
important
and
you've
got
other
people
doing
service
mesh
and
all
these
other
things,
but
get
ops
con.
D
C
C
Yeah
cheers
god.
You
just
reminded
me
that
I
I've
been
quite
rude,
so
I've
just
joined
your
group
without
introducing
myself.
So
choose
me
suggestion
there
dan.
So
my
name
is
donald
spring
hello,
everybody
I'm
from
red
hat
as
you've-
probably
guessed
so.
I
work
for
the
open
innovation
labs
in
in
red
hat,
I'm
working
there
for
a
few
years
now
and
kid
office
has
been
like
a
little
bit
of
a
magical
adventure
that
I've
been
on
with
chanson
who's,
my
partner
in
crime.
G
A
Thanks
donald
yeah,
we
had
a
good
opportunity
to
to
work
together
at
past,
get
ops
events,
so
it
was
cool
really
nice,
okay,.
C
I
have
a
question
about
the
website.
What
what's
the
website
built
in
you're
deploying
it
to
netlify?
I
presume
it's
just
built
like
with
jekyll
or
hugo
or
something
along
those
lines.
D
Yeah
it's
it's
with
gatsby.
I
think
he
said
gatsby.
Thank
you.
That's
that's
the
one
that
I
could
never
think
of.
Yeah,
it's
gatsby,
so
just
a
static
site
generator
which
actually
does
lead
to
a
little
bit
of
an
interesting
like
equation
about
doing
git
ops
for
the
website.
D
Obviously,
it's
very
easy
to
have
every
commit
generate
the
site,
but
technically
we
should
have
an
operator
actually
looking
at
the
current
version
of
the
site
and
making
sure
that
there's
no
changes
so
how
to
figure
out
like
how
we
implement
that,
because,
because
most
of
us
I
mean
scott
and
I,
for
flux,
and
for
for
argo
and
red
hat
for
argo
really
been
focused
on
the
kubernetes
side
of
the
equation.
B
A
Interestingly,
I'm
well,
I
could
say
that,
because
I
know
matt
has
his
hand
up,
but
just
tiny
parentheses
so
that
we
don't
get
lost
in
what
dan
just
said.
Interestingly,
I'm
working
on
something
like
that
right
now
as
a
way
to
help
document
the
flux
controllers
and
also
like
best
practices
for
controller
runtime.
A
So
anybody
interested
in
connecting
on
that
reach
out
to
me
yeah
all
right,
cool
dan,
okay,
thanks
matt.
H
Oh,
did
I
oh?
No
there
you
are,
how
are
you?
My
name
is
matt.
I
also
kind
of
crashed
your
party
here
for
the
first
time
and
wanted
to
just
say
hi.
My
name
is
matt.
It's
my
first
meeting.
I
was
at
red
hat
until
about
three
years
ago.
For
the
last,
almost
three
years
now
I've
been
at
a
company
called
everquote.
H
I
was
their
vp
for
cloud
engineering
and
now
I'm
just
doing
architecture
work
actually
now
that
we've
built
out
a
cloud
platform
over
the
last
two
years,
we're
running
a
largely
cncf
stack
and
from
the
get-go
for
our
infrastructure,
we've
primarily
been
using
flex
v1
and
have
adopted
get
ops
patterns
for
mostly
on
the
infrastructure
and
the
platform
side.
H
My
customers
are
engineering
teams.
My
product
is
a
cloud
platform,
that's
running
largely
on
eks
and
mostly
kubernetes.
Last
year,
her
urine
a
little
bit
ago.
We
founded
the
tag.
Observability
I've
left
a
link
in
the
in
the
google
doc
to
the
charter.
It's
a
fairly
broad
charter.
H
I
wanted
to
kind
of
reach
out
with
two
hats
on
and
so
I'll
say
for
with
the
first
head-on
as
as
chair
for
as
one
of
the
co-chairs
for
tag
observability,
I
think
that
there
is
some
gaps
and
some
opportunity
to
figure
out
how,
in
a
general
way
that
doesn't
marry
itself
or
bond
itself
to
safe
locks
or
or
whatever.
How
do
we
reason
on?
H
How
do
we
describe
observe
and
grok
what's
happening
with
gitop's
workflows,
specifically
like
how
can
we
visualize
them
and
correlate
them
with
other
activity
and
other
things
that
are
in
scope
of
the
charter?
And
I
think
that
in
particular,
the
controller
reconciler
pattern
right,
which
is
a
more
general
which
is
a
more
which
is
a
concrete
usage
of
a
more
general
system
straight.
You
know
reconciliatory
control,
loop
or
a
feedback
loop.
H
You
know,
I
think
that,
with
the
prevalence
of
folks
using
more
crds
generally
as
part
of
the
definition
of
their
workloads,
so
things
like
cross
plane
are
are
are
a
great
example
of
this,
and
as
we're
mostly
in
aws,
I've
been
looking
at
the
ack,
which
is
the
aws
controllers
for
kubernetes,
which,
when
married
with
crossplane,
puts
get
ops
not
just
in
scope
for
kubernetes,
hosted
workloads
as
it
is
for
us
today,
but
I
think
to
the
more
general
vision
of
having
all
the
things
be
done
by
the
bots.
H
So
I've
been
collaborating
with
jay
pipes
and
some
others
over
aws
on
that,
and
that's
part
of
our
future
for
our
local
development
things.
So
the
second
bit
is
more
with
my
day,
job
hat
on,
but
also
my
chair
hat
on.
So
I
think,
there's
a
huge
opportunity
to
say
like
now
that
between
iot
kubernetes
being
used
to
more
than
just
for
orchestration
of
containers
and
get
ops,
the
convergence
of
all
these
things
means
that
all
these
other
domains
are
gonna
have
the
same
general
problem
of.
H
How
do
we
like
it's
easy
to
kind
of
debug?
What
happens
with
one
operator
controller
loop,
you
know
when
you
start
zooming
out
and
how
do
you
aggregate
those,
and
how
do
you
visualize
that?
How
might
you
use
augmented
reality
or
or
or
hololens
type
stuff?
You
know
holograms,
you
know
with
these
new
modalities
of
perception.
How
do
we
both?
H
How
do
we
provide
them
the
tools
to
to
visualize
this,
so
I
think
broadly,
there's
opportunity
for
collaboration
between
tag
observability
and
what's
happening
in
the
get
off
space
and
in
this
working
group,
and
I
would
like
to
kind
of
just
open
up
some
potential
for
for
collaboration
between
the
two
in
a
way
that's
consistent
with
the
cncf's
values
and
then
our
respective
charters.
So
that's
sort
of
my
somewhat
more
verbose,
hi
and
and
yeah.
A
Thank
you,
thank
you.
So
thank
you
so
much
matt
and
definitely
welcome,
and
that
is
part
of
the
the
this
working
groups
charter
as
well,
is
to
continue
to
find
alignment
with
other
or
to
to
foster
and
welcome
alignment
with
other
well,
no
longer
cigs,
but
tags
and
and
other
groups.
So
here
it.
A
The
very
first
thing
I
would
love
to
suggest
is,
I
think,
a
pr
against
the
get
ops
working
group
charter
where
at
the
bottom
of
this
there's
some
some
alignment,
notes,
there's
cloud
native
alignment,
sig
well,
okay,
app,
delivery
tag,
alignment
and
other
related
groups,
I'm
not
exactly
sure
where
this
should,
if
it
should
be
under
other
related
groups,
or
maybe
just
maybe
just
another
section
under
the
observable
observability.
H
I
I
did
notice
that
that
part
of
the
of
the
working
group
charter-
I
I
didn't-
I
wanted
to
come
to
a
meeting
before
I
made
prs,
but
I'm
happy
to
take
an
action
for
that.
If
you
were
talking
to
me.
A
I
was
definitely
talking
to
you.
I
think
that
would
be
a
really
good,
a
really
good
way
to
do
it
and
I'm
not
really
speaking
with
any
specific
authority
for
the
group
I'm
just
moderating.
So
I
just
wanted
to
give
like
a
kind
of
a
welcoming
like
here's
another
another
good
way
to
have
that
conversation
be
available
and
accessible
to
to
to
other
people
that
aren't
in
this
call
now
so
yeah.
A
H
Put
a
short
addendum
on
what
I
my
little
monologue,
which
I
promised
wasn't
a
prepared
statement
from
before,
with
the
prevalence
of
k3s
and
like
this
convergence
of
embedded
systems
arm
and
and
all
these
new
robotics
and
drones,
and
all
these
various
scenarios
that
are
being
looked
at
from
construction
to
mining,
to
aerospace,
to
everything.
I
think
we're
we're
about
to
see
like
an
explosion
by
orders
of
magnitude.
H
You
know:
iot
alone
means
that
we're
talking
about
you
know
tens
to
hundreds
of
billions
of
clusters,
not
tens
to
hundreds
of
millions
of
clusters
in
aggregate
on
the
planet.
So
I
think
that
the
ability
in
particular
to
to
to
understand
and
characterize
like,
what's
the
you
know
as
a
get
ops
operator
as
any
operator,
goes
through
its
life
like
what
does
normal
look
like?
How
do
we
quantify
that?
How
do
we
know
what
the
outliers
are?
How
do
we
do
it?
H
I
think,
because
of
the
scale
coming
from
iot,
let
alone
these
other
domains
that
are
about
to
get
a
big
influx
of
I'm
sorry
and
then
a
big
influx
is
a
product,
whatever
a
big
addition
of
a
bunch
of
new
domains
and
scenarios.
H
A
Awesome
one
quick
note.
I
think
I
can
just
say
that
we
already
have
this
mapped
out
that
the
you
know,
since
the
the
primary.
A
If
you
look
at
the
mission
statement
in
that
charter,
that
the
primary
focus
of
the
working
group
is
to
clearly
define
the
vendor-neutral
principle-led
meaning
of
git
ops,
but
also
that
this
will
establish,
establish
a
foundation
for
interoperability
between
tools,
conformance
and
certification,
and
I
think
that's
the
level
that
you're
talking
on
and
that
all
of
those
lasting
documents,
and
that
would
relate
to
that,
whether
it's
specs
code
or
whatever
else,
to
help
with
those
things
live
in
the
open,
get
ops
project.
A
So
I
just
wanted
to
note
that
that
was
our
that's
already
been
established
by
the
group
and
thank
you
and
welcome.
A
Cool
just
want
to
look
on
the
list
to
see
if
there's
any
other
yeah,
how
do
we?
How
do
we
put
all
of
that
into
notes?
Well,
we'll
do
our
best.
D
I'm
sorry,
I
fell
down
on
figuring
out
how
to
write
that
all
down.
A
H
Verbal
assault
or
none
assault,
my
verbal,
whatever
I'll,
put
some
notes
in
the
dark
sure
that'd
be
great.
Thank
you,
yeah.
What
I
meant
by
the
embedded
stuff
by
the
way
is
you
know
now:
every
raspberry
pi
can
be
a
cluster
right,
so
kubernetes
is
just
gonna
like
spider
out
everywhere
and,
and
you
know
be
running
in
all
these
devices.
H
Thank
you
so
much.
That's
awesome,
donald!
Oh
there's
something
of
note
too.
I
don't
know
folks
saw
it,
but
the
the
kubernetes
api
server
has
just
been
instrumented
with
open
telemetry
as
of
a
week
or
two
ago,
a
pr
landed
I'll,
put
a
link
to
that
in
the
notes
as
well,
but
now,
for
the
first
time
we
actually
have
distributed
tracing.
That
starts
from
the
kubernetes
api
server
and
it's
a
pile
of
work.
That's
been
ongoing
for
a
while
that
just
landed
in
the
last
week.
A
C
A
Yeah,
it
is
well
at
the
moment,
yes
kind
of
maybe
defective
yeah
de
facto
yeah.
We
have
a
communications
team,
so
we
use
github
teams
for
some
of
these
things
and
we
have
a
community.
Basically,
so,
for
instance,
committees
are,
are
focused
groups
of
people
that
where
multiple
people
can
join
and
and
help
and
and
therefore
a
limit,
a
relatively
limited
period
of
time-
is
the
idea
that
you
have
a
committee.
A
We
do
have
some
ongoing
things
that
are
that
are
needed,
at
least
as
far
as
the
lifetime
of
the
the
working
group
and
and
probably
transition
those
into
the
open
ghettos
project
which
are
which
are
just
teams
that
we
didn't
really
call
committees,
because
we
don't
need
regular,
ongoing
like
an
ongoing
cadence
of
meetings
for
them
and
that's
the
communications
team,
and
we
also
have
a
security
team
and
excuse
me:
oh
no,
there's
one
more
yeah.
A
Right
so
I
think
those
are
those
are
really
task
oriented
things,
so
yeah
donal,
for
example,
if
there
are
areas
that
you're
interested
in
same
with
you
chansu
and
matt,
and
other
people
on
the
on
the
call
that
I
haven't
even
said
hello
to
yet,
but
but
if
you're
interested
in
getting
involved
in
any
of
those
things,
please
reach
out
to
us
and
it
is
an
open
group.
So
the
most
important
thing
is
just
that.
C
D
Yeah
yeah
we're
we're
getting
the
pr
put
up
today
like
after
this
call
we're
it's
a
it's.
A
few
commits
behind
okay
cool
that
that's
just
the
preview
site
for
people
to
get
feedback
on
yeah.
C
F
C
A
I
definitely
also
want
to
say
out
loud
what
dan
said
in
this
is
like.
Certainly,
there
are
folks
who
aren't
on
this
call
now
that
have
been
part
of
the
communications
team
like
sonia
and
chris
short,
who
have
really
helped
with
different
aspects
of
the
communication
side
and
just
who
haven't
really
foregrounded
themselves
as
being
super
visible
within
the
group,
but
who
are
officially
part
of
those
github
teams.
So
also
the
other
thing.
A
That's
that
that's
interesting,
that
what
you
all
might
want
to
know
is
that
if
you
do
want
to
join
something
it,
it
is
relative.
It's
not
formal
in
the
sense
that
there's
no
ceremony,
but
there
is,
but
we
do,
but
we
do
keep
track
of
all
of
those
things
in
github
issues
within
the
github
working
group
at
this.
A
The
github
working
group
repo
at
this
point,
so
even
folks
that
are
added
to
the
communication
team
or
the
security
team
or
whatever
else
that
that's
all
noted
there
so
we'll
make
sure
that
you
know
there's
a
proper
paper
trail
for
everyone
in
case
they
need
to.
You
know.
H
A
Show
their
boss,
or
or
even
just
or
even
just,
are
curious
who,
who
has
joined
what
for
just
for
normal
accountability
as
a
cncf
project.
A
A
H
Have
a
quick
question:
has
there
been
any
prior
art
or
work
done
by
the
working
group
or
others
around?
You
know
how
to
codify
or
or
or
describe
in
an
open
format
the
historical
execution
of
github
stuff
I
mean
I
realize
git
is
the
history,
but
when
you,
when
you
think
about
like
you
know,
a
change
is
made
to
get
and
some
number
of
agents
wake
up
and
do
things
if,
if
like
the
commit,
is
sort
of
the
the
leaf
is
the
root
of
this
whole
set
of
activities?
H
Has
there
any
any
look
about
like?
What's
the
ontology
of
data
that
should
be
collected?
Just
were
everything
to
be
collected?
I
realized
different
slices
of
it
exists
in
logs
and
time
slices,
but
like
as
a
data
model
has
that
has
that
work
been
undertaken
in
a
generic
way.
D
Yeah
so
the
way
that
we've
approached
this
has
been,
let's
be
as
agnostic
as
possible
about
all
of
those
kinds
of
things,
so
that
we
can
focus
on
the
core
elements
and
so
like,
for
example,
you
know
whatever
is
in
git
should
be
reflected
in.
You
know,
what's
in
prod
right,
but
is
that
because
you
maybe
built
an
artifact
and
that
artifact
actually
triggered
the
sink?
I
mean
I
don't.
I
don't.
I
think
it's
kind
of
neutral
on
that
topic.
D
It's
like
you
know
you
can
set
it
up
in
a
number
of
ways,
but
one
of
the
things
that
we
do
have
kind
of
on
the
roadmap
is
the
idea
of
having
a
section
of
the
website
that
we
called
patterns
or
best
practices,
which
is
a
place
where,
like
you,
would
have
a
catalog,
and
you
could
say,
like
I'm
using
aws,
I'm
using
you
know
this
resource
and
this
stack
and
whatever
what
kind
of
patterns
exist
that
I
could
follow
and
people
could
submit
patterns.
D
That
say,
like:
oh
here's,
here's
a
pattern
where,
if
you're
deploying
a
static
generated
site
and
you're
doing
x,
y
and
z,
you
can
find
this
pattern
and
this
is
conformant
with
a
standard
and
we're
not
necessarily
you
know
we're
pretty
early
in
our
thinking
about
that.
There's
not
necessarily
like.
Okay.
Do
we
have
to
like
certify
those
things
or
people
just
submit
them
and
there's
open
discussion
about
them
and
people
can
just
comment
on
them.
We
just
make
it
more
a
playground
yeah.
D
There's
nothing
in
the
principles.
This
is
anything
about
kubernetes,
there's,
nothing
that
requires
kubernetes
to
be
used,
but
that's
just
where
it's
been
easiest
applied.
Part
of
the
interest
of
like
aws
and
even
azure
is
to
look
at
like.
Can
we
use
these
principles
when
we're
even
designing
our
products
so
that
we
can
make
them
more?
Get
ops,
friendly
or
get
ops?
Approachable
more,
like
kubernetes,
is
maybe
think
about.
H
This
from
two
personas
that
roughly
need
the
same
underlying
data
just
different,
maybe
slices
one-
is
obviously
developers
right
who
increasingly
own
their
own
services
in
production,
so
it
might
be
like
hey.
I
pushed
this
commit
and
in
15
minutes
has
gone
by.
Why
is
it
taking
so
long?
Oh
because
a
cloud
sql
database
takes
you
know
12
minutes
and
they're
having
a
bad
day,
and
it's
17
minutes
today
so
stand
out
right.
So
there's
those
sorts
of
personas
about
like.
Why
isn't
the
desired
state
matching?
H
You
know
the
the
the
what's
in
get
if
it's
not
yet
fully
formed
or
if
it's
just
as
in
our
case,
it's
all
service
sort
of
platform,
but
perhaps
the
more
critical
one
for
adoption
that
I'm
seeing
in
my
own
in
my
own
day,
job
as
well
as
you
know,
from
talking
with
others
in
similar
roles,
is
when
you
go
and
need
to
get
something
certified
or
signed
up
or
blessed
by
a
cio
or
a
network
set
up.
H
That's
not
used
to
these
new
workflows.
That's
not
used
to
get
being
a
system
of
record
has
all
kinds
of
access
about
like
what's
happening.
What
artifacts
are
produced?
What's
the
some
total
artifacts
and
where
do
they
live
in
our
various
choices
right
so
like
in
general?
There's
definitely,
I
think
I
need,
because
we've
had
to
figure
it
out
as
we
go
and
it
still
can
be
an
ongoing.
H
You
know
challenges
as
it's
such
an
innovative,
rapidly
expanding
space
to
to
kind
of
sell
the
non-technical
aspects.
You
know
our
company
is
an
endurance
marketplace
and
we
deal
with
protected
data,
so
we
have
like
compliance
issues
and
auditing
and
things
like
that.
Public
companies
that
have
to
do
a
sardines
actually
once
they're,
around
three-quarters
of
a
billion
and
up
in
market
cap
like
they
have
these
additional
concerns
where
how
they
deploy
things
and
who
approves
it
and
how
that
happens
is
really
a
limiting
factor.
H
That
means
a
lot
of
tech
might
sit
on
a
shelf
for
years
before
people
get
around
to
prioritizing
it.
So
I
think
some
work
done
in
a
generic
way
to
say
like
if
you're,
using
a
get
ops
deployment
philosophy,
irrespective
of
the
tooling
here,
are
the
things
that
you
want
to
consider
when
doing
threat
modeling
when
doing
technology
selection.
H
It
are
the
last
people
to
hear
about
it
and
the
people
that
they
hear
about
it
from
typically
aren't
prepared
to
make
those
kinds
of
pitches
or
to
articulate
what
the
concerns
are,
because
many
cases
it's
a
better
position
to
be
in
it
just
takes
a
cell
that
is
targeted
at
the
decision
maker,
so
that
that's
kind
of
why
I
bring
it
up
and
I
think
that's
the
most
important
reason
why
it
might
want
to
be
done
somehow
in
in
a
vendor-neutral
way.
So
so
we
don't.
H
We
the
working
group,
the
space,
the
open
source
space
doesn't
inadvertently,
make
a
secondary
market
that
then
all
vendors
will
compete
over,
and
then
you
have
this
like
fraying
inoperable,
lock-in
everywhere,
but
happening
because
people
have
a
critical
concern
that
they
need
to
meet
their
auditor's
requirements.
So
I
don't
know
if
that's
too
scattered
or
or
makes
sense.
But
what
do
you
all
think
or
is
this
the
wrong
altitude
or
group
to
do
that
or.
A
Yeah,
I
don't
so
so
I'll
put
my
hand
down
now,
but
yeah.
I
think
I
I
will
just
give
my
own
opinion
based
on
what
we
have
already,
but
the
documents
that
we
already
have
in
place
and
the
agreements
that
we
already
have
in
place.
A
What
I
was
saying
earlier
about
you
know
just
what
dan
is
saying
exactly
and
the
principles
themselves,
that's
out
of
scope,
but
the,
but
the
mission
statement
of
the
get
ups
working
group
and
also,
ultimately
that
what
will
be
in
the
open,
getups
project
is
that
the
principal-led
meaning
of
getups
will
establish
a
foundation
for
interoperability
between
tools,
conformance
and
certification
and
and
some
of
those
things
can
be
considered.
Lasting
programs
documents
or
code,
depending
on
which
is
required
for
those
things
and
all
of
those.
A
All
of
those
things
that
are
that
are
relevant
and
and
are
accepted,
will
live
in
the
open,
getups
project.
So
to
me
it
sounds
like
that's
really
where
I
mean
this
is
where
my
opinion,
so
that
that
was
all
factual
but
like
where
my
opinion
comes
in
is
that
you
know
it
seems
that
that
is
one
of
the
places
where
you
could
very
potentially
help
matt
with
the
bridge
between
the
observability
tag.
A
You
know
we
don't
we
are
essentially,
if
I,
if
I
understand
what
you're
saying
dan
I
totally
agree
with
you
is
that
that
we
are
basically
in
the
rel
in
the
early
days,
let's
say
of
of
of
putting
together
these
best
practices
and
so
on,
and
we
are
pre
conformance
of
any
kind
at
this
point.
But
that
is
a
goal,
a
stated
goal
in
our
mission
statement.
Also,
you
know
in
as
part
of
the
the
excuse
me
the
the
principles
group.
A
What
we
are
also
doing
is
is
sifting
through
kind
of
collating,
I
wouldn't
say
prior
all
right,
but
but
drafts
in
progress
that
were
sort
of
an
older
pull
request
that
that
combined
lots
of
different
content
that
breeze
had
worked
on.
A
I
had
worked
on
a
number
of
other
people
had
pitched
in
on
and
also
contributed
to
through
the
pr
process
that
we
are
now
still
in
the
principals
committee
sifting
through
to
to
decide
to
pull
in
which,
which
of
those
relevant
pieces
into
supporting
documents
in
the
documents-
repo,
not
necessarily
the
principles
themselves,
but
other
supporting
documents,
and
one
of
those
is
relates
to
personas
or
or
user
profiles
that
work.
Some
of
that
has
been
done.
But
that
has
yet
to
be
fully
done
so
matt.
A
What
you
mentioned
about
that
persona,
that's
a
place
that
you
could
contribute
is
is
helping
to
flesh
out
just
just
starting
a
discussion
anyway
about
about
the
the
user
profile
that
you're
talking
about,
and
I
think
that
through
maybe
a
github
discussion
that
could
really
be
that
could
really
take
on
some
legs.
But
that's
just
that's
my
opinion.
H
A
We
are
fairly
open
about
it,
but
a
discussion
is
a
really
good
place
to
start
because
then
you're
it.
I
think
it
like
helps
avoid
burning
this
just
again
in
my
opinion,
but
it
helps
avoid
burnout,
because
someone
doesn't
feel
totally
frustrated
that
they
put
all
this
work
into
a
pull
request
that
then
conceptually
the
group
feels
should
have
gone
in
a
different
direction.
So,
okay
I'll
start
there,
then
I'll
start
with
the
discussion.
A
Thanks
for
the
guidance
and
in
fact
we
probably
should
add
that
to
our
our
list
of
getting
involved,
you
know
in
terms
of
contribution
process,
if
it's
not
already
there
christian.
B
Yeah,
so
dan
literally
just
posted
exactly
what
I
was
gonna
say
this
is.
This
is
exactly
something
that
you
can
bring
up
at
the
principles
committee.
However,
I
will,
plus
one
with
scott,
is
saying
that
matt,
I
love
it.
B
You're
really
really
forward
thinking,
but
you're
like
in
step
a
thousand
when
we're
in
step
two,
so
I
mean
and
that's
not
to
say
that
that
shouldn't
be
where
we
should
be
going
or
what
we
should
be
doing,
and
the
discussion
definitely
needs
to
happen,
but
just
as
a
precursor
to
joining
the
the
principles
committee.
Is
that
we're
we're
we're
a
few
steps
behind?
If,
if
yeah.
H
B
No
no,
this
this.
This
is
the
perfect
time
to
bring
it
up
because
you
know
for
for
everyone
else
to
hear
right
if
they
want
to
be
involved
in
some
of
this
documentation
that
we've
been
working
on
the
more
the
merrier
right.
We
we
definitely
need
help
in
that
regard,
especially
more
minds
make
things
better,
and
I
think
also
as
as
I
think,
scott
was
alluding
to
is
that
we
a
lot
of
times
we
work
asynchronously
a
lot
of
times.
B
People
can't
make
meetings
can't
discuss
so
a
discussion
is,
is
definitely
a
perfect
place
to
start
and
then
it'll
definitely
turn
into
a
like
a
pr
eventually
right
as
soon
as
the
discussion
is
had
so
discussion,
so
just
in
general
for
everyone
like
if
you
have
an
idea,
if
you're
thinking
of
pr
versus
discussion
discussion
is
definitely
a
place
to
start
because,
as
just
scott
is
just
alluded
to
it's
like
sometimes
you
know
you
put
a
work
in
the
pr.
It's
like.
B
Oh
we're,
never
going
to
merge
this
because
x,
y
z,
so
anyway,
so
that's
just
kind
of
adding
my
plus
one
to
what
everyone
was
saying.
A
Okay,
I'm
just
putting
my
moderator
hat
back
on.
We
still
don't
have
additional
topics,
but
we
are
two
minutes
to
the
top
of
the
hour.
So
that's
probably
a
really
good
place
to
stop.
If
you
haven't
yet,
you
know
feel
free
to
save
the
chat.
A
If,
if
anyone
hasn't
been
able
to
catch
up
to
the
chat
by
the
time
we
close
the
meeting
out,
we
also
do
save
the
chat,
we're
just
a
little
bit
behind
on
uploading
them
all
all
the
meeting
chats
we
save
them
in
the
repo,
so
you
won't
lose
it
entirely.
A
But
if
you
want
to
see
this
before
we
catch
up
to
that,
please
do
just
click,
save
chat
and
thanks
robert
for
for
the
road
map
concept
or
not
concept
suggestion
before
we
close
out,
do
we
want
to
make
any
assignments
for
the
next
meeting
in
terms
of
we've
essentially
got
two
roles:
moderator
and
notes.
Does
anyone
feel
like
volunteering
for
for
moderator
or
notes
for
the
next
monthly
meeting.
A
D
I'll
take
I'll
moderate
if
nobody
else
is,
is
jumping
up,
but
I'm
very
happy
to
seed
it
to
anyone
else
who
will
raise
their
hand
because
I've
moderated
lots
of
meetings
so.
E
A
Awesome.
Well
then,
in
that
case,
we're
unless
there's
any
other
burning
statements
or
whatever
we
are
at
the
top
of
the
hour
thanks
everyone.
This
was
an
amazing
meeting
and
we'll
and
please
do
join
the
the
weekly
meetings
for
the
different
committees,
where
you
see
that
you
can
fit
in
and
for
the
monthly
meeting
for
everyone
we'll
see
you
next
month.