►
From YouTube: Meshery Build & Release Meeting (April 28th, 2022)
Description
End-to-end testing using GitHub workflows and actions in the Meshery project.
Cypress tests
Shared updates for progress on Issue #5211 [Docs] Meshery UI: Add contributing instructions for end-to-end testing using Cypress.
Will send PR for this branch.
How to get started with automating Meshery Integration tests?
Integration test coverage review. See spreadsheet (link).
Test automation assignments. Who is doing what?
D
C
D
D
Totally
no
problem,
actually,
you
know
the
the
exercise
that
we
have
around
itemizing
kind
of
documenting
and
understanding
the
coverage
that
we
have
between
all
the
workflows
when
they're
kicking
off
and
kind
of
what
they're
testing
that
actually
like
as
a
gus.
This
familiarizes
with
github,
workflows
and
github
actions.
D
C
Yeah
in
the
the
meeting
notes,
if
you'll
go
on
to
the
third
task-
and
there
is
a
link
to
the
machine
test
plan
there-
we
have
all
of
the
workflows
there
and
if
you'll
go
at
the
last
row,
you'll
find
that
core
workflow
and
there
we
have
columns
on
you
know
when
the
workflow
runs
and
what
the
area
under
tests
are,
etc,
etc.
So
you
can
go
and
have
a
look
there
to
see
when
that
particular
workflow
that
I
was
talking
about
kicks
in
other
than
that.
D
C
B
C
That
yeah
different
tests,
so
different
tests
have
different
purpose
here
and
they
all
are
testing
different
components.
For
example,
the
initial
few
rows
you'll
see
these
are
mystery
related
tests,
but
the
last
one
actually
runs
inside
of
the
adapter
and
that
that's
where
we
have
covered
the
area
under
you'll
see
their
area
under
test,
so
mesh
three
adapters
on
the
only
row
which
has
machine
adapters.
This
one
runs
inside
of
the
adapter,
the
other
ones
run
inside
of
meshi.
C
So
this
core
workflow
that
I
was
talking
about
last
time,
gets
triggered
on
commit
when
you
create
a
commit
on
a
pr
when
and
also
when
the
pr
is
merged
with
the
master.
So
when
the
pr
is
merged,
it
actually
updates
the
dock.
So
if
you
go
on
you,
you
might
have
seen
the
compatibility
matrix.
That
is
what
we
are
updating,
yeah.
D
D
It
like
this
actually
because
this
might
help,
which
is
I'm
pleased
that
augustus
keeps
showing
up
and
since
he
does
it,
there
is
well
there's
there's
punishment
for
that
or
there's
a
reward
for
that
which
is
like
hey.
We
should
we
should
get
him
really
comfortable
on
an
area
of
interest
and,
if
it
so
happens,
to
be
like
on
a
workflow
or
understanding
what
the
heck
these
workflows
are
doing.
That's
like
a
that's,
a
perfect
opportunity
for
him
to
help
fill
in
the
spreadsheet
and
so
like.
D
Actually,
I
don't
think
augustus
has
a
question
per
se
as
much
as
his
question
is
just
like
what
the
heck
is
going
on
here.
Where
can
I
help
or
like
what-
and
you
know
like
orient
orient
me
to
what's
going
on
it's
like
perfect
timing,
because
that
spreadsheet
it's
only
lists
out
a
few
of
the
workflows
that
occur
across
all
the
repos,
so
within
the
measuring
org,
there's
like
30
repos
and
in
each
repo
there's
between
six
to
15
workflows.
D
So
with
the
column
b
here,
this
is
only
documenting
the
measuring
repo,
the
measuring
measure,
repo,
which
is
the
biggest
one.
It
has.
The
most
workflows,
it's
the
most
complex
and
what
we're
trying
to
do
is
just
like
understand
our
complexity.
Okay,
how
many
workflows
we
have
when
do
they
trigger?
What
are
they
testing?
D
D
D
Nice,
so
this
is
actually
a
good
one
to
take
a
look
at
briefly,
because,
because
many
of
the
adapters,
the
adapter
should
really
be
almost
the
same,
and
this
one,
this
multi-platform
workflow,
is
available
in
every
re-adapter
repo
so
to
to
just
read
it
really
quickly
at
just
a
high
level.
It's
like
this
triggers
when
one
of
one
of
three
things
happens.
A
D
A
B
B
A
C
So
yeah,
so
one
of
the
bottlenecks
that
I've
seen
people
facing
is
that
they
don't
have
a
patent
file,
so,
for
example,
this
is
one
of
those
workflows
that
I
was
talking
about
last
time.
So,
as
I
went
over
last
time,
there
are
three
three
particular
things
that
I
want
you
to
focus
on.
The
first
thing
is
the
setting
of
patent
file
which
will
be
used.
The
second
thing
is
the:
this
is
the
call
that
we
make
inside
of
the
machine
venture
workflow,
instead
of
instead
of
the
test
plan.
C
This
is
what
I'm
referring
to
this
is
github
allows
us
to,
you,
know,
call
other
workflows.
So
this
is
where
we
do
the
actual
heavy
heavy
load,
heavy
work
basically,
and
the
logic
is
inside
of
mesh
chemistry.
So
you
can
look
at
the
exact
logic.
How
and
the
logic
is
pretty
simple,
you
know
it
just
starts
your
kubernetes
cluster.
It.
It
takes
the
pattern
file
that
you
gave
it
here
and
then
it
deploys
that
pattern
file
and
makes
a
bunch
of
port
assertions.
C
So
in
a
simple
patent
file,
where
you'll
have
in
a
simple
pattern,
file
which
deploys
linkerd
you'll
have
three
parts
come
up
in
the
linkery
system.
Namespaces,
and
these
are
the
port
assertions
that
I
was
talking
about
and
in
this
particular
task.
It's
like
deploy
apps
right.
So
what
I
mean
by
deploy
apps
is
that
there
are
a
lot
of
apps
that
different
service
membership,
their
demo
app.
C
So,
for
example,
linkedin
has
an
emoji
moto
app,
and
if
you,
if
I'll
go
over
to
the
emoji
moto
linker
d,
then
you'll
see
let
me
yeah.
So
they
have
divided
them
into
separate
folders.
Where
they'll
have
you
know,
services
and
okay?
I
think
my
internet
connection
is
a
little
slow.
That's
why
so
yeah,
basically
coming
back
to
here
coming
back
here.
C
So
what
I
was
saying
is
that,
instead
of
writing
your
own
pattern
file
by
yourself,
if
you
go
over
inside
a
configuration
if
you'll
go
inside
designs,
if
I
should
reload
this
just
to
go
through
it
step
by
step,
you'll
be
landed
in
this
page,
and
this
is
a
pretty
good
page
for
you
to
be
landed
in.
If
you
want
to
start
writing
your
patent
file
and
as
we
call
it
here,
it's
a
design,
so
you
click
on
create
design
and
this
an
empty
template
for
you,
pops
up.
C
C
C
Yeah
so,
for
example,
this
is
an
emoji.
This
has
a
bunch
of
things
like
name
space
and
service
account
and
right
now
we
are
only
doing
pod
assertions.
We're
not
doing
these
extra
things,
and
this
is
actually
one
thing
that
we
are
going
to
do
in
future-
that
we
will
make
a
change
inside
of
the
core
workflow
and
inside
of
the
core.
C
Workflow
we'll
have
another
field
which
would
be
the
kind
field,
and
then
we
can
give
things
like
you
know,
service
account
and
namespace,
so
that
right
now
it's
hardcoded
to
pod,
and
I
I
can
go
over
how
you
can
do
that,
but
you
just
to
come
back
here.
You
have
a
bunch
of
services
and
you
have
a
bunch
of
deployments
for
emoji
water
right.
So,
for
example,
let's
say
that
I
have
this
particular
deployment
and
I
want
to
create
this
deployment
inside
of
the
inside,
measuring
instead
mentally
patent
file.
C
So
instead
of
having
deployment
and
service
separately,
because
this
is
a
very
common
pattern
for
people
to
build-
you
know
our
deployment
and
their
corresponding
service.
So
we
have
a
machine
core
component
which
we
call
application.
So
let's
say
that
I
clicked
on
application
and
it
popped
it
automatically
generated
this
this
template
for
me.
So
let's
say
I
name
it
here
something
and
then
I
can
fill
the
fields
here.
So
I
can
say,
like
replica
is
one
and
for
example,
here
let's
say
it
says
inside
of
the
particular
service.
C
Let's
say
it
says:
the
name
is
web
service
and
the
name
space
is
emoji.
Actually
the
name
and
namespace
fields
are
yet
to
be
put
here,
so
you
can
edit
them
manually
here.
Other
than
that
you
can
fill
up
things
like
container
name
of
the
container.
You
can
go
and
you
can
fill
labels
and
annotations
from.
C
C
The
name
yeah
enhancements
to
be
made,
for
example,
the
name
spaces
here
default
and
right
now
in
the
in
the
ui
you're,
not
getting
any
option
to
change
it
to
something
else,
and
that's
actually
that's
an
open
issue,
so
that
should
be
an
open
issue,
so
you
can
you
for
the
for
that
reason.
For
now
you
can
just
you
know,
manually
change
the
name
from
default
to
like
here
it
has
web
service.
C
So
with
with
this
thing,
you
can
have
a
patent
file
and
after
you
have
that
patent
file,
all
you
need
to
do
is
you
need
to
store
that
patent
file
inside
of
your
install
directory
in
dot
github
folder?
This
is
a
common
pattern
across
all
of
the
adapters.
So
all
of
the
adapters
have
this
dot.
Github,
slash
install
here
you,
this
dot
yaml,
is
actually
a
patent
file.
So
this
is
a
patent
file
and
you
put
it
here,
you
know
by
convention,
and
then
you
come
when
I.
C
If
I
come
back
to
my
workflows
and
my
my
e2e
tests
here
is
inside
of
set
pattern
file,
I
mean
the
there
is
some
extra
things
that
I'm
doing
here,
for
example,
for
that
particular
pattern
file.
I
had
left
the
version
field
empty
because
we
that
particular
pattern
file
that
I
showed
you
just
now
I'll
have
to
go
back.
So
let
me
take
my
word
for
it:
it
deploys
link
id
adapter,
linker
d
service
mesh,
and
we
also
always
need
to
test
with
the
latest
linkedin
service
mesh.
C
Yeah
yeah
just
yeah,
we
just
take
the
latest
version,
and
then
we
manually
go
and
update
that
particular
field
inside
of
services
instead
of
linkedin
server.
Basically,
we
go
inside
of
that
camel
and
replace
that
version
field
with
the
latest
version.
So
we
have
our
and
then
we're
using
this
upload
action.
We
upload
the
artifact
inside
of
dot
github,
slash,
install
slash,
deploy.
You
know
we
from
where
we
had
taken
it,
so
we
just
update
it
inside
of
the
running
workflow.
C
We
update
it
now
after
updating
it,
this
is
the
actual
workflow
that
runs,
and
here
we
give
it
the
patent
file,
and
here
we
actually,
you
know,
give
our
assertions
like
these
are
the
parts
that
we
expect.
Instead
of
these
namespaces-
and
here
we
are
give
it
the
url
of
your
your
deployment
and
service,
because
here
what's
going
to
happen,
is
that
the
workflow
will
build
your
adapter,
because
we
are
going
to
test
the
adapters
on
your
particular
commit.
C
So
on
that
particular
commit,
the
adapter
will
be
built
and
a
custom
image
with
the
name
test,
something
I
guess,
and
this
url
will
be
taken
out
from
the
mystery
repo
and
that
particular
for
yaml
would
be
actually
repopulated
with
the
image
that
was
dynamically
built
inside
of
that
workflow,
and
that
image
represents
your
version
of
the
adapter.
The
changes
that
happened
when
you
made
a
commit
and
yeah
mario,
you
have
a
question.
A
B
A
Excellent
yeah,
I'm
yeah.
It's
glad,
I'm
glad
that
that
that's
the
answer.
I
was
just
wondering
if,
for
all
that
information,
should
we
include
that
in
in
the
measuring
docks,
because
I
do
see
it
ran-
mentions
like
how
to
invoke
the
reusable
workflow,
but
probably
most
of
that
information
is
not
present
there,
and
I
understand
that
these
steps
are
just
to
generate
the
pattern
file
right.
E
C
C
You
yeah
or
you,
and
when
we
make
a
release,
then
also
we
update
the
dock
and
that's
what
you
see
here,
you
know
in
the
edge
and
the
edge
channel
is
basically
your.
These
are
on
the
merge
and
the
stable
one.
These
are
on
the
release,
so
these
are
what
is
here
and
for
a
reference
you
can
go
to
one
of
these
workflows.
For
example,
one
of
these
runs
and
see
what
happened
in
each
of
these,
and
I
deliberately
you
know
in
a
lot
of
these
steps.
C
A
A
C
A
C
C
E
C
A
yeah
this
is
a
valid
application
file
and
we
have
actually
we
support
two
valid
application
files,
but
I
should
mention
this
because
we
recently
added
support.
So
if
you
have
a
docker
compose,
so
we
actually
convert
that
docker
compose
into
the
kubernetes
manifest
for
you
on
the
fly.
If
you
pass
a
docker
compose
instead
of
passing
your
kubernetes
manifest
and
if
you
pass
the
communities
manifest
inside
of
you
know,
applications
so
so,
as
you
can
see,
you
see.
A
C
Yeah
so,
for
example,
the
current
end-to-end
test
is
based
on
patents
and
not
application.
We
can
make
changes
in
the
core
workflow
to
have
application.
So
when
I
refer
to
application
right
now,
I'm
referring
to
either
docker
compose
files
or
your
or
your
communities
manifest
you,
and
here
you
won't
see
any
docker
compose
files,
because
you
know
that's.
C
C
Yeah,
it's
a
compose
with
the
k
and
the
reason
in
the
ins,
the
reason
inside
of
the
core
workflow
we
did
not
use
measuring
ctl
application
apply
and
right
now
we're
doing
messages.
It
will
pattern
apply
inside
of
the
core
workflow.
The
pattern
that
you
create
inside
of
the
dot
meshi
slash,
install
directory
that
that
pattern
is
actually
deployed
using
message.
Ctl
pattern
deploy
and
if
we
had
an
application
we
would
use
message
little
application
device.
C
So
the
reason
we're
not
doing
that
is
because
our
at
first
reason
is
at
that
point.
Application
was
not
really
that
stable,
so
we
couldn't
use
it.
The
second
reason
is:
even
if
it
was
stable,
it
was
limited
to
unity's
manifest,
and
you
know
I
want.
We
wanted
that
core
workflow
to
be
a
little
more
extensible,
so
that
you
know
we
can
test
more
things.
We
won't
be
relying
on
only
communities
manifest
and
also
but
yeah
yeah.
It's
kind.
A
D
E
D
C
C
No
actually
files,
no
actually
these
older
batch
tests
are.
These
are
the
ones
responsible
for
all
these
other
workflows.
Failing
as
well
so
secretary,
you
can
ignore
those
particular
tests
for
now,
because
those
are
going
away
or
we
would
be
replaced
in
the
future.
So
if
that's
the
only
test,
that's
failing
and
that's
stopping
you.
I
think
you
can
ignore
them
for
now.
A
E
A
C
Yeah
we
were
using
these
earlier,
but
there
is
some
issue
with
these
failing
tests,
which
I
didn't
look
over,
because
the
reason
I
didn't
see
because
they
were
going
to
get
replaced
by
our
end
to
end
test
anyways.
So
of
course,
yeah
so
secretary
suggested
all
the
suggestions
that
were
made
or
did
you.
E
C
Are
those
the
only
tests
that
they're
failing
I
mean
these
tests
are
failing
as
well?
I
guess
the
invalid
workflow
yeah,
I
think
some
job
names
were.
There
was
some
conflict
in
the
job
names
and
that
that's
something
I
I
had
pointed
out
as
well,
instead
of
the
pr
so
so,
for
example,
it
exp
job.
This
depends
on
an
unknown
job,
so
this
job
doesn't
exist,
but
you
have
referred
so
I
think
you
should
for
you
to
change
the
names.
I
think
I
had.
C
A
C
C
Yeah
after
you
commit
after
you
actually
commit
that
this
particular
workflow.
This
will
not
run
inside
of
mesh
here,
because
you
know
it's
not
merged
yet,
but
inside
of
your
fork,
it
will
run
and
if
it
runs
successfully,
we
would
know
that
everything
is
going
fine
and
then
we
can
go
ahead
and
merge
it
here
as
well.
E
C
E
C
E
C
Don't
you
use
a
message
message,
ctl
for:
are
you
able
to
use
messy
ctl?
So
if
you
go
and
update
when
you
get
the
url,
you
you'll
go
so,
for
example,
just
just
to
show
you
here:
have
you
looked
at
your
messaging
config
yaml,
yet
so,
for
example,
yeah
here
this
endpoint,
you
have
to
update
it
with
the
with
that
particular
url
that
you
are
using
to
access
your
cluster
and
then
your
messy
ctl
will
be
able
to
talk
to
your
messy
server
and
I
think
okay,
so
your
concern
is
that
is
the.
C
Is
there
a
endpoint
that
can
take
your
kubernetes
manifest
and
convert
it?
So,
as
I
said,
if
you
can
access
the
ui,
because
if
you
have
the
url
you
can
that
you
get
from
any
cube
tunnel
now
you
can.
Why?
Don't
you
use
that
url
to
access
the
ui?
You
can
access
the
ui
with
that
and
then
you
can,
you
know,
do
import
application
and
and
get
your.
E
E
C
For
example,
this
is
a
communities
manifest
as
you
can
see,
and
if
I'll,
if
I'll
hit
deploy.
Of
course,
this
might
fail
because
of
some
reasons,
because
maybe
I
have
it
consists
of
some
particular
components
that
I
don't
have.
For
example,
it
may
have
some
okay.
For
any
reason,
the
idea
is
to
not
actually
deploy
it
but
to
see
the
results
here.
If
I'll
look
at
the
response
here,
the
first
request
actually
generates
a
pattern
file
from
the
communities
manifest.
C
So
if
I'll
take
this
thing-
and
actually
this
is
pretty-
you
know
hard
to
see,
but
if
you'll
copy
it
into
vs
code
and
do
control
shift,
I
and
you
it
will
be
into
a
more
readable
format,
and
this
is
actually
a
patent
file
in
the
response.
So
the
first
request,
the
first
request
that
happens
at
slash
api,
slash
pattern
is
a
post
request
and
there
in
the
response,
you'll
have
this
patent
file
inside
of
the
patent
file
field.
C
I
had
it
here
so
the
point.
The
point
is
that
you'll
be
able
to.
This
is
a
valid
pattern
file,
so
I
think
you
should
be
able
to
see
it
from
mystery.
Ui
I
mean,
if
you
have
to
do
all
that,
you
know,
go,
find
the
end
point
and
do
all
those
things.
There
is
no
point
in
having
a
ui
which
can
do
it
for
you
or
a
command
line
utility
which
actually
does
it
for
you.
C
C
If
you
can
just
access
the
ui
and
if
you're
having
problems
with
accessing
the
ui,
then
then
that
you
can
either
we
can
help
if,
after
all
the
topics
here,
I
can
help
you
with
that
or
maybe
you
can
post
it
on
the
channel,
the
particular
errors
that
you're
getting
accessing
the
ui,
because
I
think
you
should
be
able
to
access
the
ui
you'd
be
missing
out
on
a
lot
of
things.
You
should,
if
you
cannot
access
the
ui,
then
I
think
that's
a
problem
so.
E
A
A
That's
one
and
a
I
decided
to
add
this
contributing
cyprus.
Oh
and
this
is
all
for,
like
I,
don't
have
the
issue
at
hand,
but
it's
for
this
issue
and
discuss
topic
about
you
know
just
helping
contributors
get
like
no
certain
considerations
when
they're
contributing
to
the
measure
ui.
So
part
of
that
is
like
this
existing
change
in
the
like
this,
this
contributing
to
the
ui.
So
it
already
exists.
I
just
added
some
changes
to
make
it
more
like
user.
A
E
A
A
You
know
they
would
like
to
know
more
details
so
just
to
simplify
like
where
to
go
next.
If,
if
there's
some
issues
with
running
the
the
server,
they
could
reference,
the
this
other
section
just
to
get
more
details
before
just
racing
like
simple
issues
that
for
or
troubleshooting
you
know
like
that-
and
this
is
the
relevant
part.
So
basically
it's
just
an
explanation
of
this
new
make
command.
A
This
describes
what
it
does
so
installs
dependencies
invokes
specific
npm
script,
and
then
this
also
references
the
this
would
reference
the
master
version
of
the
package.json
so
that
this
brings
awareness
of
that
command
and
that's
basically
yeah
that'll
help
the
yeah.
The
contributor
know
the
specifics
of
that
command.
E
A
A
Well,
we
could
merge
it
as
it
is,
but
the
I
would
like
to
get
some
feedback
on
the
status
on
this
other
new
contributing
cyprus.
So
I
added
this
reference
over
there
so
for
contribution
and
just
benefiting
from
that
those
existing
tests-
and
that
is
over
here.
Let
me
just
I
collapse
it
on
purpose,
because
this
reference,
the
other
one,
so
it's
over
here.
A
I
think
I
would
be
able
to
merge
it
this
week.
I
just
need
to
update
maybe
some
remove
someone
needed
parts,
but
this
basically
explains
what
tool
we're
using
a
what
is
its
purpose
and
just
some
links
to
the
features
it
provides,
just
linking
the
relevant
documentation
and
guides
for
cyprus
itself
and
the
support
test
types
like
the
reasoning
of
why
anyone
would
pick
the
tool
and
then
again
here
is
like
the
most
relevant
thing.
A
I
think
just
this
part
about
what
each
folder
contains,
what
it's
supposed
to
be
used
for,
like
the
helpers,
a
water
fixtures
like
how
is
that
used
and
even
provided
a
link
to
the
master
version
of
some
samples,
which
would
be,
I
mean
it's
not
too
readable.
Sorry
for
that,
but
basically
it's
explaining
the
difference
between
when
it's
used
by
an
integration
test
which
is
to
stop
the
backend
responses.
So
that
is
some.
A
That
is
what
contributors
would
be
running
in
their
local
for
now
and
maybe
instead
of
like
this
needs
to
go
away.
This
other
part,
but
I'll,
be
adding
just
more
some
more
details
about
maybe
some
troubleshooting
on
running
the
the
integration
tests
and
also
a
the
end-to-end
test,
and
maybe
some
prerequisites
because
at
least
links
to
those
prerequisites
as
to
like
having
a
cluster
running
and
there
needs
to
be
a
server
like
the
backend
running
as
well
and
probably
like
a
like
the
context
being
defined
for
the
cluster.
A
A
It
was
on
this
other
channel
on
the
on
the
ci
channel,
so
our
channel,
he
was
asking
about
how
to
test
cyprus,
and
I
don't
know-
maybe
some
of
this
could
be
integrated
to
the
contribution
documentation
for
cyprus,
as
it's
like,
I
think,
for
an
end-to-end
test.
There's
a
lot
of
more
more
of
prerequisites
as
to
what
the
contributor
needs
to
know
to
contribute
to
that,
and
generally,
I
think
it's
a
good
good
set
of
information
to
you
know
bring
awareness
of
all
contributors.
E
C
A
Well,
one
thing
to
mention
is
that
I
did
add
this
cyprus
label,
so
that'll
help
us
just
talk
about
that.
I'm
hoping
and-
and
I
I
linked-
I
added
that
tag
to
some
of
these.
So
right
now,
there's
no
pr
open
for
these,
but
I
do
plan
on
starting
working
on
this
there's
some
commented
out
test
data
for
a
test
I
added
before
so
part
of
on
commenting
it
out
would
be
just
finding
like
if
there's
a
workflow
github
workflow
changes
needed.
C
C
C
C
C
Actually
yeah,
actually
you
can
you
I
mean
you
can
do
that
without
starting
working
on
them
and
inside
of
the
write-up,
you
can
actually
tell
people
okay,
I'm
going
to
start
working
on
these
by
this
day.
So
if
someone
else
comes
up
and
says
hey,
I
want
to
pick
it
up,
so
you
can
hand
it
over
to
them.
So
it
would
be
easy
if
you
set
a
deadline.
C
C
A
C
While
I
am
on
action
items,
I
think
augustus,
you
had
a
pretty
good
idea
about
the
whole
test
inside
of
the
adapter.
So
can
I
expect
something
from
you
some,
you
know
some
action
item
from
you
or
would
you
be
like?
Would
you
be
comfortable
with
committing
to,
let's
say,
let's
say
in
linkedin
sample
apps?
So
are
you
comfortable
now
with
information
or
is
there
something
missing
right
now
or
you
know,
do
you
have
enough
to
go.
C
Whichever
you
wish,
I
mean
it's
a
democracy
among
adapters,
but
we
already
have
inside
of
istio.
So
you
can
pick.
Let's
say:
linker
d,
you
can
pick
linker
d
or
you
can
pick
any
other,
and
if
you
have
any
problem
you
can
tell
your
exact.
You
can
ping
me
and
I
would
be
available
and
yeah.
So
I
I
think
I
can
expect.
I
can
expect
some
progress
from
you
inside
of
linkedin
right.
Yes,.
B
A
A
C
Yeah,
so
inside
of
messy
ci
channel,
if
you
can
just
drop
links
a
bunch
of
links
and
a
bunch
of
that,
that
was
the
whole
point
of
it,
so
that
would
be
nice
segrently.
Do
you
want
to
take
something
up
or
after
your
console
pr
get
get
smart?
Because
I
don't
think
that
that
pr
has,
after
those
issues,
get
resolved
that
you
know
what
we
can
hold
on
to
that?
Let's
get
your
pr
mers!
First,
I
think.
That's!
We
shouldn't
hog
you
down
with
a
bunch
of
other
sample
apps
and
everything.
E
C
I'll
I'll
have
a
look
look
into
that
because
even
I
didn't
look
into
psyllium
adapter.
I
didn't
get
time
to
look
into
psyllium
adapter
as
well
as
cilium
service,
which
so
smashed
that
much,
but
I
think
they
might
have
something
in
samples.
If
I
get
something
I'll
post
it
on
the
ci
channel
and
I'll
definitely
tag
you,
oh
and
user
as
well.
C
Yeah
might
have
something
as
well
are
absent
because
they
had
some
things
with
school
and
all
so
rita.
Raj
is
actually
doing
some
good
progress
and
he
was
the
one
who
done
who
the
first
did
sample
apps
inside
of
his
two
adapter.
So
he
was
the
one
who
first
created
that
pr.
So
he
might
have
some
idea
about
psyllium
as
well.
Maybe
you
can
ask
on
the
ci
channel
to
other
people
as
well
and
I'll
find
one
for
myself.
E
Okay
and
the
other
thing
is
console,
they
are
sample
app.
There
are
some
two
containers.
No,
there
is
a
pod
that
comes
out
of
place,
so
here
in
the
test
should
should
I
only
test
for
it
once
because
it's
it's
the
same
code
but
the
I
I
think
it's
characterized
should
I
test
for
it
once
or
like
where,
where
you
expect
some
pods
in
some
name
spaces.
E
B
C
E
E
E
C
C
Yeah
so
yeah
yeah
yeah,
so
you
can
do
for
because
right
now,
inside
of
our
assertions,
we
don't
specify
one
part
or
two
part
or
three
part.
We
just
you
know
specify
pod
so
yeah.
Even
if
two
come
up
you
can
you
have
to
only
do
it
once,
because
that
will
not
change
anything.
If
you,
you
know,
if
you
append
that
list
with
10
times
the
same
name
and
the
same
name
space,
it
won't
make
any
change.
C
E
C
Yeah
does
anyone.
I
think
I
answered
all
the
augustus
questions.
I
think
augustus
has
an
action
item
here
and
mario
also
has
an
action
item
and
he
has
he
had
some
things
that
he
can
share
in
the
see
he
will
share
in
the
cia
channel
and
sakuranda.
Has
this
pr
up,
which
is
going
to
get
merged
and
has
this
answer
answers
answered?
C
So
I
think
and
we're
almost
up
in
time,
so
I
think
it's
the
time
to
say
goodbye.
I
guess
so
good
night
good
evening
and
good
morning
to
each
of
you
depending
upon
what
time
zones
you
live
in
and
see
you
in
the
next
meeting,
and
I
hope
by
that
time
we
have
progressed
a
little
bit
much
more
in
this
in
these
tests.
So
everyone.