►
From YouTube: 20210615 SIG Arch Conformance
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
Hi,
I'm
kirsten-
I
am
a
software
engineer
at
red
hat
and
I'm
involved
in
shake
architecture
and
also
the
release
team.
So
I
just
wanted
to
get
a
little
bit
of
more
understanding
of
what
was
happening
in
these
meetings
and
kind
of
just
listen.
A
And
let's
start
with
the
first
agenda
point,
which
is
the
extended
api,
e2e
testing,
endpoints
stephen,
you
want
to
take
that.
D
Yeah
sorry.
D
As
discussed
with
clayton,
historically
there's
a
bug
and
the
way
that
some
stuff
is
happening
was
the
patching
with
api
service,
as
I'm
trying
to
do
a
conformance
test
for
some
endpoints
and
if
we
scroll
further
down,
there's
been
some
feedback
to
suggest
looking
at
dispatching
it
sorry
adding
the
label
before
the
test
is.
D
I
think
it's
actually
a
little
bit
further
down
brian
yeah
here
it
is
looking
at
actually
just
creating
the
appropriate
label
earlier
when
the
api
service
is
created
to
start
with,
and
then
everything
should
work
as
required,
though
just
at
the
stage
looking
to
use
that
as
a
way
to
get
the
test
to
work.
For
now,
and
hopefully
we
can
make
a
a
an
appropriate
comment
somewhere
so
that
this
issue
isn't
actually
completely
forgotten
about
just
want
to
mail
to
get
the
endpoints
tested
and
and
for
this
release.
E
I
I
guess
I
didn't
understand
why
we
couldn't
just
change
the
the
test
to
put
it
where.
Maybe
I,
like
I'm
misunderstanding,
the
question,
but
at
least
would
we
just
fix
the
issue?
I
I
can't
tell
like
I
thought
this
originally.
I
thought
this
was
like.
There
was
a
serious
bug
in
api
service
and
I
just
saw
the
comment
was:
is
this
about?
You?
Don't
want
to
refactor
the
test.
D
No,
it
was
more
around
the
the
fact
of
I
thought
by
have
having
this
potential
bug.
Was
it
not?
The
bug
should
be
sorted
out,
but
if
I
can
just
add
it
at
the
start,
then
that's
what
the
plan
my
current
thought
is
just
do
it
that
way.
B
What
I
hear
you
saying
stephen
is
that
there
is
a
exposed
bug
that
we
were
hitting
and
rather
than
trying
to
avoid
hitting
it,
we
were
wondering
if
we
should
ensure
that
the
bug
is
fixed
before
we
merge
this
test,
or
should
we
write
another
test
later
to
ensure
that
the
bug
is
fixed.
D
Is
that
right,
yeah
it
might?
The
easiest
solution
at
the
moment
for
me
is
just
change
the
way
that
the
api
service
is
created
at
the
very
start,
and
so
it
has
the
appropriate
label,
and
then
we
won't
run
into
this
issue.
E
D
Based
on
my
logs
and
the
way
we
talked
about
it,
I
put
the
link
in
the
conformance
slack
channel
about
the
point
where
we
discussed
it
a
few
months
back
and
basically
it
it's
like.
The
api
service
is
getting
completely
ripped
out
and
put
back
in
because
of
the
change
and
it's
just
not
available
so
that
I
can
delete
the
appropriate
some
components
at
the
end
of
the
test.
D
A
Stephen,
do
I
understand
so
the
option
is
either
we
have
to
wait
for
somebody
to
fix
the
bugs
before
we
can
do
conformance
or
you
create
a
label
first
and
we
walk
around
the
bug.
Yeah,
it's
still
getting
the
end
point
tested,
so
you
want
the
choice
of.
Should
we
walk
around
the
boat
or
should
we.
F
E
D
Back
in
the
conformance
slack
channel,
a
second
I'll,
just
scroll
back
to.
D
F
F
D
I'll
just
put
it
in
chat,
clayton.
A
Thanks
steven,
you
can
just
paste
it
in
the
conformance
agenda
as
well.
B
And
I
think
I'd
like
to
recommend
as
clayton
did,
that
we
should
be
putting
these
things
inside
of
the
issue,
because
both
slack
and
the
agenda
are
a
bit
transient.
C
C
E
I'm
looking
at
the
link
you
have,
and
I
don't
I
see
the
both
of
those
links.
Don't
take
me
to
things
that
look
like
actual
bugs.
They
look
like
test
changes,
so
I'm
just
I
don't.
I
don't
remember
what
this
discussion
was.
If
there
isn't,
if
you're
saying
that,
like
I
don't
want
to
read
between
the
lines
here
so
it'd
be,
what's
the
actual
bug,
I'm
not
just
not
seeing
b.
D
It
and
the
logs
there
that
I've
put
in
basically
after
I've
done
the
appropriate
patching
and
I've
checked
everything's.
Okay,
then,
once
we're
looking
at
doing
going
back
to
the
current
test
to
look
at
doing
the
delete
at
the
very
bottom,
but
then
that's
when
it
gets
a
unexpected
error
and
it's
saying
that
they
it's
a
503
error
and
the
service
basically
unavailable.
E
D
E
B
Co,
so
action
items
here
are
create
an
issue
documenting
the
bug
and
reproducibility
and
in
parallel,
go
ahead
and
work
around
it
in
this
issue,
but
note
the
change
that
was
required
so
that
we
can
create
an
additional
performance
test
later,
hitting
the
same
endpoint.
That
specifically
ensures
this
bug
is
fixed.
G
A
Okay,
the
next
one
is
also
your
stephen
debugging
redirects.
Oh.
D
D
If
we
scroll
a
bit
further
down
rihanna
it's
where
we
start
to
get
into
the
logs
of
actually
using
so
I've
getting
a
part
product,
that's
using
the
agnostic
host
image
so
that
I
can
do
a
confirm
the
method
going
through
to
the
pod
by
my
test,
I'm
just
using
a
curl
to
start
with
and
the
logs
I'm
tweaking
so
that
I
can
confirm
what
the
request
is
coming
back,
but
they
I'd
say:
yeah,
sorry,
happy.
B
D
Yeah,
so
I've
added
in
some
extra
blogging.
D
So
I
get
some
extra
detail
about
how
the
property
part
is
working
and
also
having
it
so
that
I'm
only
if
you
scroll
just
a
fraction
further
only
having
it
where
we
only
redirect
only
for
http
get
and
for
head,
but
for
all
other
methods,
we're
just
selecting
it
straight
through
as
normal,
so
going
back
to
the
other
set
of
dogs.
D
If
we
carry
on
further
down
rayon
yeah.
So
here
it's
it's
going
through
pretty
much
how
I
expect
it
to.
D
D
What
I'm
finding
is
that
the
actual
endpoints
only
hurt
we
should
be
getting
because
we're
looking
at
the
route
we
should
be
getting
pod
is
turning
up
on
the
actual
hit
logs
here,
but
it
seems,
though,
everyone's
getting
redirected
through
to
proxy
with
pass.
D
So
it's
skipping
about
10
endpoints
at
this
stage,
so
I'm
a
little
frustrated
partly
lost
on
where
or
why
the
actual
path
that
I'm
trying
to
hit,
which,
if
we
scroll
just
a
fraction
further
back
up
ryan.
D
I've
got
well
just
at
this
point
here,
there's
both
the
proxy
endpoints
that
the
sets
that
I
should
be
looking
at
getting
responses
from,
which
should
be
just
for
the
road.
D
B
Want
to
make
about
this
one
stephen
one
thing
I'd
like
to
make
sure
is,
if
you're
doing
curl
or
any
other
thing
look
at
the
the
actual
anything
hitting
from
that
user
agent
to
ensure
there's,
not
some
logging.
Like
error
in
how
we're
mapping,
I
tried
to
get
the
actual
endpoint
names
recorded
in
the
audit
logs,
but
I
got
pushed
back
from
the
api.
B
B
But
that's
done,
you
know
and
not,
and
it's
an
automated,
but
it
is,
it
is
programmatically
done
and
there
may
be
some
errors
there,
because
if
you
go
down
to
the
bottom,
where
you
have
your
list
at
the
very
very
bottom,
curl
is
hitting
proxy
with
path
and
we're
not
expecting
with
path
and
it.
If
you
can
look
at
where
you
say,
here's
curl
and
here's
the
urls
and
show
that
the
actual
url
hitting
api
server
and
getting
recorded
because
that's
all
we
have
is
the
url.
B
D
Yeah,
I
I
believe,
there's
another
table.
I
need
to
go
back
to
to
be
able
to
confirm
the
confirm
exactly:
what's
actually
getting
hurt
and
the
raw
logs
that
we're
getting
on
the
audit
events,
yeah
cool.
A
No
no
problem,
thank
you.
That
brings.
A
E
I
approved
the
two
of
them
that
were
no
comment
and
then
there's
just
the
two
comments
from
john
on
the
others
about
the
the
text.
So
once
that
gets
fixed,
I'll
approve
those.
So
it's
just
the
the
two
that
were
not
tagged.
Just
need
john
asked
for
a
slight
tweak
to
the
description
text.
I
agree.
It
wasn't
quite
clear
what
the
conformance
test
was
asking
was
validating
in
its
description.
D
Yeah
I
saw
that
just
before
the
meeting
and
I'll
look
at
that
straight
after
the
meeting.
B
Pepe,
no,
I
just
said:
let's:
let's
do
that
right
after
the
meeting
so
that
we
don't
lose
the
velocity
on
these.
A
Absolutely
clinton,
we
will
continue
the
moment,
we're
done
with
that
things,
and
then
we
have
three
more
e2e
tests
that
is
ready
to
go
on
the
test
grid
that
all
has
been
have
been
approved
by
oh
lgtm.
By
switch
apps
reviewed,
we
went
through
and
they're
all
following
the
existing
pattern
of
other
tests.
That's
already
conformed
and
merged,
so
they're
all
ready
for
review
or
just
just
approval,
if
you're
happy
with
them,
they're
all
sick
apps,
and
this
will
help
us
take
the
the
app's
endpoints.
D
B
These
are
the
actual
test
submissions
for
these
top
three.
Do
we
want
to
go
through
those
real,
quick,
just
particularly
also
for
other
people,
on
the
call
to
see
what
it
looks
like
to
write
a
conformance
test.
B
Sure
we
submit
through
a
pr
that
says
what
missing
pieces
are
there
and
we
can
show
you
api
snoop
later,
but
this
is
the
actual
ticket
and
the
ticket
itself
comes
from
an
org
file,
which
is
an
emacs
file.
B
We
use
to
see
what
missing
things
are
there
and
put
some
snippets
together
of
code
in
order
to
make
sure
that
inside
of
a
living
cluster
that
we
can,
these
snippets
actually
do
hit
the
end,
so
they're
selecting
to
see
the
pieces
of
software
that
that
hit
that
and
there's
our
ede
test
with
the
new
the
new
test
there
and
if
we
go
back
that
gets
exported
as
the
the
ticket.
B
B
As
an
issue
on
these
calls
to
say,
are
we
going
to
do
this
right
and
then,
when
it's
actually
a
pr
to
kkk
is
when
it
has
to
go
through
the
normal
kubernetes
community
approval
for
merging
into
the
the
test
frame
tests
themselves
and
after
waiting
two
weeks,
we
do
approvals
for
a
promotion
to
include
those
in
the
suite
have
tests
that
everybody
runs
globally
and
so
four
of
the
tests
you
saw
today
are
things
that
clayton
as
part
of
the
api
stewards
and
and
stick
architecture
get
to
formally
approve,
and
so
we're
glad
that
those
four
will
get
approved
in
these
next
three
we're
trying
to
get
through
quick
enough
so
that
we
have
the
two-week
window
to
get
inside
of
the
120
22
release
window.
B
The
tests
themselves,
our
basic,
we
have
some
framework
we've
extended
to
write
those
tests
in
that
we
use,
and
it's
part
of
the
standard
golang
test
framework
it
exports
into
yaml
files,
which
is
where
we
need
to
touch
those
the
the
people
that
are
in
the
owners
for
conformance
test
data
have
to
approve
so
where
to
go.
Update
the
metadata
for
this
test
that
john's
asking
for
clarity
on
just
after
this
call.
B
A
That's
correct:
if
we
can
get
some
eyes
on
those
and
we
will
fix
that
issue
quickly
and
can
reach
out
to
clinton
when
we're
done.
I
A
B
For
the
other
people
on
the
call,
if
you're
interested,
we
can
spend
a
little
bit
of
time
going
through
what
the
conformance
project
is
and
where
those
connection
points
are.
But
if
you
just
wanted
to
see
what
we
normally
do
on
a
on
a
head
down
call.
This
is
what
we
normally
do,
but
we
have
allocated
another
30
minutes.
If
that
would
be
helpful.
B
This
is
so
we
are
funded
from
the
cncf
to
provide
this
conformance
program
in
order
to
ensure
where
the
definition
of
kubernetes
and
definition.
Therefore,
the
definition
of
what
the
cloud
is
is
clear
and
we're
always
looking
for
more
people
to
participate
in
that
red
hat
agree
on
while
you're
driving
can
you
go
to
github.com,
cncf,
kate's
conformance
and
look
at
the
recent
prs
and
limit
to
red
hat.
So
we
can
show,
I
believe,
kirsten
said
she's
from
red
hat.
B
So,
at
the
end
of
the
tool
chain,
the
main
thing
here
is
getting
the
shiny
badge
that
says
my
company
has
fancy
software,
that
is
the
cloud
and,
if
you'll
scroll
down
to
one
121
there
right
the
one
b121
up
a
little
bit
four
days
ago,
china
mobile
was
the
last
one
to
submit
their
bits,
but
I
bet
something
that
looks
like
red
hat
will
be
in
this
list,
just
scroll
down
and
look
look
at
the
so
not
yet,
but
that's
okay.
B
C
B
H
B
Right
and
so
it's
shockingly
right
and
and
there's
directions
on
how
to
bring
up
one
cluster
of
kubernetes
using
the
the
ci
job
that
was
generated
by
this
commit
and
and
to
run
the
test
and
in
the
end,
the
test
generates
some
log
files,
the
e
to
e
log
and
the
j
unit
xml
log-
and
we
make
sure
this
is
stuff
that
that
our
friend
rian
and
then
and
his
brother
burno,
worked
on
and
product
yamo
or
yeah
go
and
go
to
the
pr.
B
That's
a
great
great
way
to
do
it
is
we
verify
in
this
this
list?
We
have
a
cncfci
automation,
bot
and
the
first
time
around
it
looks
like
the
product.
Yaml
was
not
there,
so
there
must
have
been
it's
not
verifiable
and
clayton
said
oops.
I'm
gonna
force
push,
so
he
pushed
again
and
then
the
bot
said.
B
Yeah
you've
got
your
document
in
there
and
it
has
the
appropriate
fields,
and
then
it
checks
to
make
sure
that
the
title
is
there
in
the
logs
and
the
and
and
the
title
has
v21
in
the
name
of
it,
and
that
it's
the
right
version
in
the
logs
and
that
there
aren't
any
missing
tests
and
clayton
was
sad.
He's
like
hey.
These
should
be
there
what's
the
problem,
and
so
people
were
looking
at
it
this.
This
is
actually
more
verbose
than
we
most
time
have
mostly
just
automated.
B
It
done,
and
we
looked
at
there's
some
strict
ways
that
the
tests
are
verified,
and
so
he
re-pushed
it
in
the
way
that
everybody
else
does
it.
I
think
the
the
the
underlying
thing
is
that
we
usually
only
accept
things
run
by
sonoboy
and
in
a
particular
format,
and
we
also
burno
updated
the
verify
conformance
test
to
parse
it
better,
there's
a
ticket
for
that
for
later,
but
we
may
not
get
to
that,
because
this
was
kind
of
a
one-off
thing
to
fix.
Clayton's
submission
gotcha.
B
C
B
C
B
And
that's
going
to
be
a
cncf
employee
who
has
permission
to
do
this?
Our
team
just
provides
the
infrastructure
for
connecting
this
projects,
the
cncf
sponsors
to
the
infrastructure
provided
by
our
donors,
the
website
that
that
our
friend
rion
is
pulling
up
now.
Is
it
115
something's
weird
go
to
go
to
yeah
there
we
are
so.
B
This
is
122
test
coverage
and
the
little
gray
dots
for
the
gray
areas
are
like
color
in
the
blanks
with
your
favorite
pencil,
preferably
via
the
category
there,
and
if
you
zoom
into
stuff
that's
part
of
stable,
you
can
see
that
there's
actually
68
percent
coverage,
although
we
removed
some
of
those
because
they're
in
eligible
conformance
we're
at
73..
Ideally,
all
of
the
ga
endpoints
have
a
clear
definition
and
are
run
globally,
and
you
know
that
your
workloads
will
run
anywhere
as
long
as
you're
focused
on
the
generally
available
kubernetes
endpoints.
C
I
A
B
A
Ahead,
if
you
look
at
the
signature
you'll
see
at
the
moment,
sick
apps
have
63
ga
endpoints
and
of
those
40
is
conformance
tested.
So
what
we
just
did
in
the
meeting
we
discussed
all
the
prs
that
we
created,
so
the
ii
team
is
focusing
on
getting
all
these
endpoints
conformance
tested.
So
stephen
and
myself
go
and
find
the
endpoints
that's
untested.
We
create
e
to
e
test.
You
see
this
one
is
showing.
H
A
B
So
the
short
version
is
the
org
files
that
we
start
with
in
emacs
query
a
database
of
what's
left
and
then
we
focus
on
those
and
go
read
the
documentation
and
get
with
that
community
and
write
just
a
small
snippet
of
golan
code
and
run
it
and
then
check
our
logs
to
see
if
we
hit
it
and
that's
before
we
actually
write
anything
formal
so
that
org
file
becomes
a
markdown
that
we
create
an
issue
for
and
ask
the
right
people
we
notice
these
are
not
tested
at
all.
Yet
we
read
the
docs.
B
Are
these
the
right
docs
we
talk
to
these
people?
Are
they
the
right
people
and
here's
a
little
log,
noting
what
this
code
did?
If
we
were
to
write
a
test?
Is
this
the
right
way,
because
previously
way
back
in
the
day,
there
was
no
progress
like
for
years
like
you
could
see
a
year
and
a
half
it
was
before
our
team
took
over
to
start
writing
tests.
So
all
of
the
extra
red
stuff
is
the
technical
debt
that
the
ii
team
pays
off
by
writing.
These
endpoints.
C
This
is
super
cool
like
this
is.
It
looks
like
such
an
improvement,
and
I
know
that
the
conformance
test,
like
criteria
got
incorporated
into
also
the
cat's
template,
so
it
feels
like
this
is
on,
like
a
really
good,
like
a
really
good
trajectory
like
with
a
lot
of
impact.
So
it's
pretty.
B
C
B
H
B
So
my
commitment
to
to
the
cncf
is
the
this
team
is
to
get
that
below
75
before
end
of
year,
and
that
means
very
likely
in
2022,
we'll
be
100
defined.
What
the
cloud
is
by
working
with
the
community
to
understand
it
and
and
enforcing
all
of
the
world
that
wants
to
have
the
shiny
badge
to
have
passed
them.
H
B
B
So
these
meetings
are
not
well
intended.
They're,
usually
people
like
clayton
or
or
people
that
have
the
executive
permission
to
approve
these
things,
but
I
do
find
them
super
interesting
and
then
I
particularly
the
way
that
we
work
is
is
quite
fun.
Stephen.
Are
you
yeah
you're
here?
Can
you
yeah?
Can
you
drop?
Can
you
drop
your
pear
link?
B
B
Yeah
stephen,
why
don't
you
share
the
web
browser
and
or
share
a
screen
on
your
side,
show
kirsten
the
pair.sharing.iou
first
and
then
jump
into
your
pair
session
and
go
through
your
current
org
file
that
creates
the
markdown
and
then
maybe
your
test,
because
we've
still
got
yeah.
We
got
24
minutes,
there's
plenty
of
time.
B
How
do
I
make
you
a
host?
I
just
noticed
we
have
another
another
human
here.
You
don't
have
to
introduce
yourself,
but
we
would
invite
you
to
hi.
My
name
is
jyoti.
H
I
was
just
introduced
to
the
compliments
test
area.
A
few
weeks
back.
I
got
interested
I'm
here
to
see
what's
happening
in
the
meeting,
so
I
work
for
aws,
I'm
the
eks
team
and
I
released
one
twenty
120
for
eks
and
I
had
to
run
this
conference
test
and.
H
I
found
a
few
things
interesting.
I
would
probably
share
since
you're
asking
one
thing
was
you
mentioned
just
now
that
sauna
boy
is
the
preferred
way
of
running
customers.
H
Do
some
digging
to
find
out
what
my
previous
teammates
did
and.
B
Foreign,
it's
not
a
hard
requirement
to
be
honest,
it's
that
it
shouldn't
be
and
where
we
have
issues
where
they're
not
submitted,
we
need
to
capture
those
as
part
of
the
automation.
I
think
it's
somewhat
in
the
way
that
the
j
unit
files
are
slightly
different
and
we
don't.
H
Yeah
so-
and
I
read
in
the
readme
that
the
gingo
test
framework
is
what
is
advised
right,
so
probably
sonoma
runs
the
same
framework
internally,
maybe
totally.
B
And
and
that's
a
open
source
like
it's,
not
curated
by
the
cncf,
which
is
a
different,
I
think
I
think
sonoboy
may
be,
but
it's
it's
run
by
vmware,
slash,
google
vmware
or
no.
It
was.
H
Yeah,
it's
vmware,
so
the
next
thing
I
had
to
like
this
was
which
version
of
sony
should
I
use.
There
are
image
versions
and
I
just
picked
something
got
lucky
yeah.
B
It
doesn't
yeah
it's,
it
depends
on
how
far
you
need
to
go
back
and
we
only
go
back
three
releases,
and
so
the
current
release
of
sono
boy
should
be
able
to
run
against
all
versions
of
what
we
are
allowing
conformance
for,
and
if
it
doesn't
it's
about,
I
see
the
latest
is
the
is
the
criteria
guideline
yeah.
H
B
F
B
So
give
me
a
moment
behind
the
scenes
to
to
launch
the
browser
and
figure
out
how
to
how
to
share
the
bits
by
the
way.
I
just
want
to
say
the
stuff
you're
about
to
see
it's
super
cool,
and
I
don't
think
many
people
in
the
world
understand
how
useful
it
is.
But
I
know
that
I
all
the
host
disabled
participants
screen
sharing
and
three
on
your
host
eh.
A
B
We
are
it's
always
tomorrow
and
I
won't
be
able
to
stick
around
very
much.
I
forgot
I
have
an
appointment
at
10.,
but
what
can
I
share
now?
B
Yeah,
all
right
here
we
go
so
I'm
going
to
share.
So
that's
fine,
so
this
is
pair
dot.
Sharing
that
I
owe
and
I'm
going
to
drop
that
in
here.
If
you
are
a
member,
don't
go
wild
and
tell
everybody
yet
because
it's
still,
it
is
open
to
the
entire
kubernetes
community,
but
it's
still
incubating
and
I
I
don't
want
to
get
inundated
with
with
with
stuff
yet.
H
B
If
I
go
to
here
and
I
log
in
with
github,
I
can
log
in
with
a
read
only
or
read
write
token,
and
if
I
log
in
with
a
read,
write
token,
it
went
through
to
github
and
got
permission
to
be
here,
so
we
now
have
the
ability,
within
this
box
to
check
out
code
and
whatnot,
and
if
I
click
on
new,
I
can
fill
in
repositories
like
seen
like
kubernetes,
kubernetes
and
I'll
invite
you
to
be
a
part
of
this
as
well.
So
can
you
give
me
your
github
usernames.
B
And
then
carson,
if
you've
got
yours
I'll
grab
that
one
as
well-
and
this
is
just
as
it's
a
white
space
separated
list
of
people
to
to
pair
with
oh
beautiful,
that's
a
fun
one.
I
I
used
to
watch
that
and
you
can
put
environment
variables
like
here
and
we'll
say,
helping
equals
good
and
we're
gonna
call
the
box.
It
will
default
to
your
username
and
but
I'm
gonna
call
this
one
conformance
because
that's
the
name
of
our
box.
B
So
if
I
hit
launch
on
here-
and
you
could
do
it
as
well-
with
different
repos
and
different
guests
and
different
environment
variables
and
different
name,
I
believe
it
is
launching
now
and
it
is-
and
this
becomes
this
url.
If
you
log
in
to
pair.sharing.io,
and
do
you
don't
have
to
do
read
write
if
you
don't
want
to
if
you
don't
trust
us,
whatever
it's
fine
but
you'll,
be
able
to
see
your
list.
So
if
I
go
to
all
on
this
little
blue
icon
I'll
see
all
the
other
people
that
I'm
pairing
with
somewhere.
B
Our
poor
little,
not
not
well-designed
interface,
I
mean
not
like
heavy
loaded
right.
This
has
been
internal
primarily,
so
I
see
created
by
me.
I've
got
the
conformance
one
hh
and
other
people,
so
while
we're
waiting
for
it
to
come
up,
I'm
going
to
go
click
on
hey
stays,
which
is
stephen
haywood.
Who
is
on
the
call-
and
I
have
this
permission
to
take
a
look.
That's
all
right.
B
He's
got
www
and
grafana
sites
up
inside
of
this
living
cluster
and
he's
got
this
cool
config
bit
to
get
in
there
and
there's
this
join
pair
session.
B
So
without
any
software,
I
can
either
click
on
this
link
here
and
put
it
in
my
terminal
or
I
can
click
on
join
pair
to
make
it
super
simple,
I'm
just
going
to
click
on
join
pair
and
it
will
bring
up
a
terminal
inside
of
my
browser
to
interact
with
is
the
code
now
this
window
that
you
see
here
is
inside
a
kubernetes
cluster
running
on
packet
and
he
has
opened
a
apps
v1
statefulstatuslifecycletest.org,
which
is
an
emacs
like
fancy,
markdown
file
and
and
now
I'm
going
to
walk
away,
because
I
have
to
go
to
another
meeting
but
you're
in
good
hands
with,
and
if
you
have
any
questions,
if
you
want
to
spin
up
one
of
these
on
your
own
feel
free
to
do
so
and
reach
out
to
the
team.
B
B
C
Oh
and
just
I
I
posted
in
the
slack
channel,
but
big
architecture
was
wondering
if,
if
someone
from
conformance
could
give
like
a
brief
update
and
thursday's
meeting
so
if
anyone
wants
to
give
like
a
five
five
ten
minute
update-
just,
I
guess
add
yourself
to
the
agenda.
That
would
be
great.