►
From YouTube: CNCF Network Service Mesh Meeting2020-02-04
Description
CNCF Network Service Mesh Meeting 2020-02-04
C
C
B
You
see
my
screen:
yes,
I
do
okay
last
week
and
now
I'm
working
on
updates
forward
matrix,
so
the
general
idea
is
to
move
from
cross-connect
matrix
we
have
and
from
a
cross-connect
api
to
have
a
just
a
pure
connection,
monitor
and
humans,
working
just
with
our
unified
request,
calls
and
mental
connections
with
the
Dollar
Tree.
So
the
idea
is
to
add,
show
in
a
brutal
booth
right
now.
In
a
connection,
we
have
a
bias
of.
B
Of
segments,
so
every
segment
has
tokens
and
so
on,
so
general
idea
is
to
have
same
way
metrics
and
the
metric
segment.
So
for
a
connection
object,
we
will
have
all
possible
matrix
to
be
available
in
periodic
update
or
by
request,
update
and
to
just
one
problem
with
it.
It
could
be
a
lot
of
metrics
home
endpoints
and
to
solve
this
additional
context.
Matrix
context
should
be
introduced
it
to
password
interval
parameter,
do
not
send
updates
too
often
to
the
client.
B
So
if
we
can't
do
a
request,
it
will
receive
all
the
metrics
combined
it
from
all
the
endpoints.
But
if
we
just
a
form
earlier,
we
don't
send
periodic
metrics
update.
It
will
send
just
not
so
often
so
if
someone
would
like
to
comment
just
welcomed
with
API
changes
and
two
people
requests
in
his
DK
I
think
also
to
pull
request
to
is
decayed
to
just
fix
the
current
metrics
chain
and
to
introduce
the
fixed
mentoring
training
to
fix
a
metrics
chain.
B
C
A
Currently
I'm
working
on
the
pr2
is
decade,
I,
don't
know
the
screen
or
it's
okay,
there's
PR,
that
covers
healing
element
chain
element
with
tests
unit
tests,
and
there
are
also
discussions
with
ads
about
the
way
how
we
should
test
that
element,
so
at
first
I
made
kind
of
white
box
testing,
so
I
using
a
lot
of
chicken
private
maps,
but
we
decided
that
it's
better
to
do.
Tests
in
another
package,
I
mean
in
test
package,
so
I
change
it,
and
now
we
have
discussions
with
edge
how
to
properly
dispose
resources.
A
They
were
finalizer,
but
it
doesn't
work
well
in
test
environment
I
mean
you
see.
The
ugly
output
I
mean
the
wine
pass
and
after
the
line
pass,
the
there
are
some
still
some
output
because
finalizer
works
later.
So
it's
not
really
good
and
I
proposed
a
couple
ideas.
I
think
we
will
discuss
that
ideas
in
terms
of
that
PR
and
I
also
have
some
work
done
for
spire
Federation.
They
work
quite
good.
C
A
D
D
D
B
D
B
D
Dragon
about
phenomena
dragon
we
have
disks
at
is
at
about
moving
out
dragon
into
ordinary
Apple
to
get
rid
of
custom
image
in
Assam
Cardenas
and
today,
I
have
provided
PR
and
I
have
created
an
issue
into
ordinary
PO.
It
has
mark
Wiebe
and
I'll
work
on
this
I
just
provided
some
dogs
and
specification.
D
D
D
B
B
E
F
G
D
C
A
Major
task
is
here
to
be
able
to
switch
to
him
version
3
which,
where,
where
each
team
is
more
robust
and
if
and
it
uses
less
infrastructure
like
there
is
no
additional
tiller
code
that
manages
installations
hand
is
basically
at
the
debugger
stage.
There
is
only
couple
of
tests
that
that
fails
on
CI
and
I
will
I
hope.
A
I
will
finish
the
task
who,
once
I
finish
the
recently
emerged
task
that,
with
him
version
two
where
it
turns
out
that
we
in
Docs,
we
should
use
bare
hand
comments
to
install
charts
rather
than
you
can
make
targets
so
currently
I
made.
If
you
are
to
fix
those
problems
and
after
the
these
PR
will
be
nourished.
I
will
finish
the
helm
transition
to
Humphrey.
That's
basically.
C
Cool,
if
there's
no
questions
at
this
particular
point
as
always,
you
can
find
us
on
the
NSM
dev
channels
and
ask
questions
there
and
you
can
always
ping
me
and
add
Nikolai,
we're
always
happy
to
help
and
with
that
it
will
yield
back
four
minutes
of
time
and
we'll
see
most
of
you
in
the
next
meeting
and
around
10
minutes
or
now.
Thank
you,
yep
yep.
B
C
C
C
C
C
Well,
let's
get
let's
get
started
so
welcome
to
the
to
today's
network
service,
my
lady
and
we
have
this
particular
meeting
which
occurs
every
Tuesday
at
8
a.m.
Pacific
time.
We
have
an
issues
and
PR
group
which
occurs
every
7:30
a.m.
Pacific
time
on
Tuesdays.
We
are
also
involved
in
the
CN
CF
Telecom
user
group,
which
is
every
first
Monday
at
8
a.m.
Pacific
and
every
third
Monday
at
3
a.m.
Pacific,
the
next
the
night.
The
next
Tiger
meeting
will
be
13
days
from
now
at
3
a.m.
C
C
C
C
We,
we
also
are
going
to
participate
in
cuke
on
the
schedules
have
been
announced
and
there's
a
diverse
set
of
talks
that
have
been
accepted
that
are
related
to
medicine
and
we'll
see
about
getting
the
agenda
listed
with
them.
I
think
I
counted
around
five
or
six
of
them,
so
it
was
quite
a
quite
a
healthy
number.
C
We
have
o
ne
s.
That's
up
and
I
had
a
brief
talk
with
with
our
pitch
Julie,
Hall
and
and
Heather
about
their
closing
time,
because
their
website
closed
the
O's
omes
earlier
than
it
should
have
been
most
so
they've
extended
the
time
to
submit
for
someone
specified
period
of
time.
So
if
you
were
including
to
submit
and
for
that
or
were
unable
to
plea
and
the
brave
now
is
your
time
to
do
so.
C
The
schedule
will
be
announced
on
March
5th
in
July.
There's
gonna
be
cute
con
and
cognitive
con
China,
the
CF
Peace
closed
in
February
21st.
So
few
weeks
from
now,
though,
the
cases
will
go
out
in
May
and
the
end
of
September
will
be.
Oh,
oh
na
s,
Europe,
which
will
be
held
in
Antwerp
again
CFPs
closed
in
June
7th.
They
are
currently
open
and,
finally,
we
have
Q
Khan
Crowley
to
come
Boston.
The
CFP
is
open
in
a
couple
months
on
April
22nd
and
they
closed
in
June
12th.
C
We
also
have
the
NSM
column,
and
that
is
co-located
in
Amsterdam
that
should
occur,
I
believe
on
March
30th,
and
so
we
have
a
larger
room
this
time
twice
the
size.
The
event
pages
on
the
agenda
schedules
for
those
will
be
posted
on
February
21st
and
there
are
sponsorship
slots
available.
So
please
consider
and
juniper
in
sponsorship
and
I'll,
showing
your
support
for
and
ascend.
If
you
are
in
such
a
position
so
and
with
that,
are
there
any
other
events
that
people
would
like
to
announce.
C
Okay,
so
we'll
make
the
announcement
again.
We
have
the
new
and
ascent
project
page,
so
this
project
page
crosses
now
that
we
have
spanned
across
multiple
repos
and
coupled
with
a
new
addition
to
github.
We
can
set
projects
on
organizations,
so
this
is
an
organized
organizational
level
project,
page
that
spans
multiple
projects
that
helps
link
to
issues
and
PRS.
C
H
C
So
here's
an
example
of
what
it
looks
like,
so
you
can
see
that
it's
to
do
a
variety
of
in
progress
things
and
if
you
see
there's,
we've
even
tagged
things
with
a
good
first
issue.
So
if
you're
looking
to
join
them,
you
can
you
can
sort
of
based
on
tags
and
and
we
track
things
as
a
as
a
move
across.
C
F
Thank
you,
hi
everyone.
My
name
is
Ashley
and
I'll
be
providing
the
social
media,
community
team
updates,
and
so
this
last
week
has
brought
us
again
some
pretty
consistent
engagement
and
followings.
Compared
to
the
last
few
weeks
that
we
have
been
monitoring
this.
As
far
as
Twitter
goes,
we
have
gained
an
additional
13
followers.
We
followed
an
additional
six
accounts
and
we
have
tweeted
and
retweeted
27
posts.
F
Some
of
those
include
cube
con
announcements,
so
all
of
the
NSM
talks
that
were
accepted
just
the
other
team,
we've
tweeted
about
registering
for
cube
con
as
well
as
in
SM
con,
adding
that
on.
While
everyone
is
registering
for
Q
concatenative
con
again
getting
some
information
out
there
about
the
prospectus
and
trying
to
get
some
support
through
sponsorship
and
again
just
reminding
people
to
submit
their
CFPs
there's
also
been
some
general
cool
reminders
that
have
been
promoted.
F
Some
CN
CF
news
about
the
toc
election
guides
about
Cuba
Nettie's,
surpassing
100,000
registrations
and
promoting
cnc
FCI
working
group
calls
as
well
as
their
weekly
webinars.
So
I
think,
with
these
general
tweets
getting
out
there,
it
is
allowing
us
to
gain
some
additional
followers
and
get
some
extra
eyes
on
the
NSM
account
and
then
just
getting
some
other
events
out
there.
She
appears
for,
if
a
networking
edge
summit
coming
up
as
well
as
the
go
SF
meet
up
building
cloud
native,
zero
trust
solutions.
F
In
addition
to
that,
some
general
tweets
and
blog
posts
from
VMware
CNF,
test
beds,
cisco
and
dr.
dai
and
as
far
as
linkedin
goes
again
an
additional
ten
followers.
So
that
has
been
very
consistent,
so
good
to
see
that
that's
all
growing
and
as
far
as
what
we
posted
on
in
pretty
much
the
same
as
the
original
tweets
that
we
have
been
getting
out
on
Twitter
and
the
plan
moving
forward
is
to
continue
promoting
NSM
Khan.
F
As
far
as
CFPs
sponsorship
signing
up
registering
you
name
it
and
getting
some
retweets
and
contributor
podcasts
up
there
as
those
are
starting
to
come
out.
Any
other
events
that
are
coming
up
that
are
in
SM
related
will
just
continue
to
push
those
to
get
us
as
many
eyes
on
network
service
mesh
as
possible.
So
if
there's
anything
else
that
comes
up
any
further
announcements,
then
please
do.
Let
me
know
and
I'll
get
those
promoted.
C
Well,
a
couple
other
minor
announcements,
I
forgot
to
add
in
weather
one
so
I
I
spoke
with
with
Dan
cone
yesterday
he
asked
me
to
talk
and
the
Linux
Foundation
event
Mobile
World
Congress,
so
they're
hosting,
and
so
it's
it's
not
gonna,
be
in
the
SEM
specific
of
a
Buddha
tinge
of
some
stuff
that
we're
doing
kind
of
sound
research
context.
So
if
you're
going
to
be
in
that
area,
I
definitely
definitely
get
a
hold
of
me
and
find
and
find
me
and
with
that
is
a
so.
C
E
Have
a
couple
she
find
me:
we
have
time
for
for
Iran.
So
first
I
I
just
noted
like
like
why
I
was
browsing
here,
that
we
effectively
are
covering
each
and
every
day
with
the
NSM
so
start
with
NSM
calm
the
whole
day,
then,
okay,
it's
not
the
whole
day,
but
it's
good
enough
coverage
like
for
talks
on
the
first
day
actually
of
the
of
the
conference.
This
is
Capcom,
of
course,
and
then
we
have
tomorrow.
E
E
E
E
It's
more
or
less
something
that
I
think
that
we
as
a
community
need
to
to
try
to
figure
out.
So
the
final
target
of
the
repo
pipelining
that
is
called
ongoing
now
is
to
get
into
situation.
Something
like
this.
Similarly,
the
problem
that
I
see-
and
we
kind
of
discussed
with
Andrey
quickly,
was
that
we
we
see
that
there
a
lot
of
PR
sin
issues
which
has
to
filed
and
especially
kind
of
huge
big
new
functionalities
being
filed
against
the
main
monolithic
repo
is
record.
E
You
know
it
was
not
his
measure
on
and
you
want
to
get
into
something
that
is
going
to
evolve
from
from
these
experiments
here.
So
I
think
is
that
maybe
we
should
kind
of
I
don't
know.
What's
the
right
wording
here,
what
exactly
techniques
we
should
use
but
kind
of
stimulate
the
peep,
stimulate
like
the
contributors
and
new
committees
to
actually
go
directly
to
the
new
structure
and
try
to
propose
their
new
functionalities
there
and
keep
this
one
in
kind
of
semi
maintenance
mode
for
for
now.
D
G
E
To
go
into
extremes
like
we
don't
get
any
PLC
network
service
measurement
II,
don't
think
that
that's
possible
and
meaningful
now,
but
not
maybe
we
can
decide
on
some
steps
like
today
we
are
going
for
simple
API,
plus
several
SDKs
split.
So
exactly
this
one,
and
until
we
get
done
here,
anything
that
touches
SDK
or
API
here
is
not
getting
much
so
that
we
can
make
a
clean.
You
know
implementation
here
and
merge
everything
cause
functionality
from
here
to
here
and
then
once
we
make
network
service
mesh
actually
use
these
SDKs
refer
to
them.
E
E
C
I
would
prefer
to
have
most
of
the
effort
into
the
first
few
until
and
in
a
good
sake,
but
I
think
they're,
starting
to
approach
that,
like
the
next
big
step
that
needs
to
get
out
there
is,
is
the
commands.
Weibo
was
a
structure
out
sometime
this
week
so
that
we
can
finally
complete
that,
particularly
but
yeah
I
I,
don't
know
an
easy
way
to
solve
that
other
than
like
trying
to
friend
load
as
much
of
the
work
as
possible.
A
C
E
Just
going
to
say
that,
for
the
time
being,
examples
are
like
CIA,
for
example,
is
broken
because
of
some
kind
of
misunderstandings
with
how
we
use
charts,
but
that's
going
to
be
fixed
and
I
was
thinking.
Maybe
maybe
we
can
create
a
PR
where
I'm
my
creation
to
use
this
new
SDK
can
be
used
there.
I
mean
there
are
no
nightly,
builds
there.
So
well,
if
we,
if
we
start
migrating
at
least
some
of
the
examples
of
the
new
SDK.
B
B
So,
based
on
the
current
state,
subparts,
like
n
points,
could
be
already
started
to
be
implemented
using
Queen
new
is
decay,
I
think,
but
NSM
manager
itself
could
not
yet
be
replace
it
with
the
components
from
the
new
SDK,
since
not
all
chamber
remains
required,
I
already
implemented.
So
a
major
change
for
new
is
decay.
It's
to
move
from
for
murder
as
a
separate
component
of
a
system
for
murder
as
an
endpoint,
and
this
part
of
work
is
not
yet
finish
it.
It's
it's
major
change.
It's.
E
E
E
G
E
That
actually
was
done
back
at
the
time
when
the
SDK
was
critical,
that
we
had
this.
You
know
huge
okay,
huge
compared
to
other
parts
of
the
of
the
code
explanations
of
what
actually
the
NSM
is
about.
You
know,
with
all
the
components
that
we
have
here:
I
guess
that
this
is
also
plan
to
be
migrated
and
to
kind
of
reflect
the
reality
of
the
new
I
guess
like
changing
at
least
these
bits
here,
so
that
people
can
just
use
it
kind
of
safely.
E
E
E
E
B
E
C
H
This
is
Alex
from
breadhead
I've
been
talking
with,
with
Eden
and
Frederick
on,
like
about
the
NSM
operator,
so
I'm
about
it's
working
right
now.
If
you
try
to
install
it's
pretty
rough,
but
there
is
enough
instruction
there
on
the
repo
to
try
installing
NSM
using
the
operator,
but
only
on
a
vanilla
kubernetes.
For
the
moment,
okay,.
E
H
I'm,
almost
in
the
point
where
I
would
be
able
to
deploy
in
openshift
qu
and
using
what
we
call
operator,
lifecycle
manager,
which
is
a
tool
that
integrates
multiple
operators
and
calculates
dependencies,
and
all
of
that
and
I
feel
that
at
some
point
in
time,
we'll
need
to
have
a
discussion
around
to
two
topics
on
the
operator,
which
are
the
specs
and
the
status
fields
on
the
CR.
So
what
would
you
guys?
H
What?
What
would
you
want
to
see
on
the
configuration
of
this
virtual
object
called
MSM
inside
kubernetes?
And
what
would
you
like
to
see
in
the
status
field?
So
these
two
would
be
topics
for
probably
III
think
it
would
be.
It
would
take
some
time.
It
won't
be
like
something
decided
F
once,
but
probably
need
some
engineering
on
that
and,
of
course,
you
know
way
more
about
the
inner
things.
G
H
C
G
H
H
H
D
H
Dependencies
for
NSM
to
be
installed
right,
so,
if
I
put
those
guys
before
and
then
I
put
aspire
as
a
helm
chart
before
we
recover
to
install
the
operator
right
so
after
after
doing
that,
I'm
just
cloning,
the
project
to
get
the
deployments
for
the
CRD
and
the
operator
resources.
So
this
here
D
must
be
there
before
the
operator.
H
All
right
and
after
deploying
the
operator
I
can
deploy
a
CR
and
I
will
explain
that
looking
at
here,
so
the
operator,
basically
is
a
deployment
that
takes
care
of
your
installation,
can
take
scare
on
of
the
health
of
everything
that
we're
trying
to
run
on
top
of
your
kubernetes
cluster.
So
for
that
I
mean
every
single
component
in
the
NSM
charge
that
we
assume
the
helm
charge
can
be
deployed
by
the
operator
and
taken
care
by
an
operator
right,
so
you're,
pretty
resources
is
a
yellow
file.
That
is
right
here.
H
If
you
see
everything
that
is
needed
to
deploy
the
operator
is
here,
so
it
counts
roles
and
everything.
So
it's
just
to
speed
up
the
process.
Instead
of
deleting
Admetus
apply
this
guy.
So
if
I
apply,
it
will
create
a
container
here
that
is
at
the
deployment
actually
will
create
a
container
here.
That
is
the
operator
the
operator
holds
within
it,
some
controllers
that
will
be
watching
the
behavior
for
each
and
every
component
on
the
NSM.
H
Let's
say
application
as
a
whole
as
a
system
right,
so
it
will
be
watching
the
admission
webhook
deployment
it.
We
are
watching
the
daemon
sets
for
the
forwarder
and
also
for
the
network
service
manager
right
since
I.
Don't
have
anything
any
CRS
here,
I'm
doing
underneath
here,
a
cube,
CTL
get
and
SMB
cuz
I
created
that
CRD
to
represent
the
system
right,
but
I
don't
have
anything
here.
H
I
have
a
CR,
though
that
is
actually
representing
an
SM
here
with
the
same
options
that
you
guys
put
on
on
the
ham
charts,
so
here
I'm
basically
give
it
or
take
copying
the
same
thing.
That
is
there
right.
So,
if
I
deploy
this
CR,
let
me
find
it
on
my
history
here.
Yes,
so
if
I
deploy
the
CR,
it's
gonna
create
everything
you
should
create
it.
H
H
It
creates
the
deployments
and
the
daemon
sets
as
well
and
you
if
you,
if
you
look
before
deploying
an
SM
operator
matrix,
was
already
there
because
it's
it's
been
developed
with
the
operator
SDK
and
it
comes
with
any
matrix,
endpoints
embedded,
which
kind
of
facilitates
the
process
of
publishing
metrics.
So
this
is
the
work
of
the
operator
is
to
take
care
of
it,
so
it
can
be
extremely
flexible
because
everything
is
going.
H
We
just
have
a
boilerplate
from
your
barrier
SDK
to
build
everything
at
least
the
skeleton
project,
and
we
can
concentrate
on
the
controller's
on
the
logic
inside
of
the
controllers.
So
this
is
the
point
where
I
say
that
here
many
decisions
have
have
to
to
be
to
be
made,
because
if
you
want
a
complex
system,
if
you
want
to
change
configurations,
you
can
do
anything.
You
can
you
disrespect
view
the
way
you
want
like
we
can
even
have
nested
objects
and,
whatever,
whatever
is
needed,
it's
possible
to
be
done
right.
H
If
you
guys,
if
you,
if
we
have
somebody
that
actually
knows
the
roadmap
for
the
project.
So
what
what
do
you
guys
envision
in
the
future
for
NSM
and
what
we
can
do
from
from
a
coding
perspective
to
make
that
happen
from
a
central
point,
such
as
an
operator?
And
the
good
thing
on
the
operator?
Is
that
if
you,
if
you
install,
if
you
have
a
cluster
with
the
operator
lifecycle
manager,
then
I
can
actually
build.
H
A
small
helm
operator,
for
example,
for
inspire
jäger
tracing
actually
has
already
an
operator,
so
I
can't
just
point
out
those
dependencies
and
then
the
operator
lifecycle
manager
will
bring
those
operators
in
in
order
to
comply
with
the
requirements
to
install
the
NSM
operator.
So
it
seems
to
be
interesting
and
it
can
go
way
further
than
helm,
charts
because
he'll
charge
on
how
much
arms
you
can
version.
You
can
group
everything
together.
H
To
keep
some
information
and
and
make
sure
that
database
is
back
it
up,
for
example,
or
if
you
want
to
do
I,
don't
know
billing
on
a
cloud
provider,
and
you
want
a
part
of
this
operator
to
actually
build
reports
for
you,
based
on
the
cloud
provider
API.
So
the
possibilities
are
really
really
wild.
Like
you
can
you
can
bring
in
the
metrics,
but
also
process
the
metrics
outside
with
the
help
of
the
operator
and
have
deep
insights?
You
can
go
further
and
do
outer
pilot.
H
If
you
have
some
sort
of
behavior
that
you
you
can
see
on
on
clients
using
NSM
and
something
is
happening.
Okay,
we
need
to
check
that
and
to
fix
that
we
need
to
change
some
configuration
or
to
tune
out
to
tune
something
on
on
the
application
or
even
restart
a
poet
or
something
like
that.
It
is
possible
using
the
operator
because
it's
always
alive
watching
the
resources
and
it
can
have
many
conditions
inside
to
say:
oh
okay,
if
this
component
is
going
to
that
stage,
I
can
change
like
that.
To
that
state.
H
H
E
E
H
Yes,
one
one
of
our
goals
is
to
have
the
operator
doing
seamless,
upgrades
and
downgrades
as
well.
So
if
you
there
are
direct,
so
there
are
a
few
ways
to
do
that
you
can.
You
can
tie
the
operator
to
a
particular
image.
So
let's
say
that
you
have
a
tag
on
the
operator
and
that
tag
represents
certain
images
on
on
your
CR.
So
then
the
operator
will
deploy
just
one
version
of
an
SM
and
then
to
the
next
version.
H
You
create
a
new
tag
on
the
operator
and
you
tie
the
whole
an
SM
version
to
that
new
operator
and
when
you
say,
hey
I
want
to
upgrade
my
operator.
The
operator
itself
will
upgrade
the
whole
application.
So
this
is
one
way
of
doing
that.
We
actually
prefer
not
to
put
the
image
itself,
as
as
we
are
doing
here
on
on,
like
registry
Oregon
tag.
H
Instead
of
doing
that,
we
could
tie
everything
to
a
particular
version
of
the
operator
and
not
open
this
on
the
configuration
side
and
then
when
it,
when
you
update
the
operator,
you
update
the
whole
application
and
if
some
something
goes
wrong,
you
can
do
the
opposite.
You
can
downgrade
it
and
make
it
do,
make
it
down
grade
everything
gracefully
as
well.
So.
H
H
That's
it
so
from
here.
We
need
to
think
okay.
What
do
we
want
to
see
happening
on
the
pier
I
can't
hide
this
easily
I
can
hide
this
and
say:
okay,
I
have
a
particular
version
for
that
operator.
The
thing
is
that
is
that
I
don't
have
yet
a
release
on
your
career.
That's
that's
what
I'm
working
on
right
now,
because
I
need
to
build
a
file
I
actually
already
built
I
I'm,
just
testing
and
at
the
end
of
testing,
which
is
called
closer
service
version.
That
file
is
important
because
that
file
is.
H
We
have
all
the
metadata
that
describes
the
operator.
What
what
it
can
do,
feuds
that
it
can
show
on
on,
for
example,
openshift,
UI
and
everything
else,
and
with
with
that
file,
I
can
version
the
operator
so
once
I
have
that
file,
ready,
I
can
put
a
release
out
and
then
I
may,
for
example,
hide
this
and
tie
the
operator
to
a
particular
and
assembler.
C
Cool
so
I
guess
a
little
bit
of
feedback
in
this
direction
is
so
we're.
Gonna
have
to
find
a
good
balance
in
this
area,
because
one
of
the
things
within
a
sound
is
it's
designed
to
to
work
not
only
with
kubernetes
but
things
outside
of
kubernetes
as
well.
So
that
means
some
of
the
ceiling
and
and
so
on.
C
If
you
would
tend
to
drive
to
an
operator,
we're
gonna
have
to
make
sure
that
those
work
in
when
you're
trying
to
drive
like
a
hardware
switch,
we're
Papa,
Drac,
switch
or
OpenStack,
or
so
on
that
that
being
said,
I
think
that
there
might
there.
There
may
be
a
good
opportunity
for
for
this
particular
project
to
keep
track
of
certain
types
of
metrics
or
keep
track
of
certain
types
of
things
that
have
been
exposed
to
try
to
work
out
like
if
there's
an
air
condition
that
we
can
detect.
C
Or
we
see
that
the
service
is
stock,
responding
or
or
so
on,
that
that
gets
mediated
properly
or
to
help
us
with
with
an
upgrade
path
where
we
want
to
perform
an
upgrade.
And
yes,
we
technically
could
just
do
a
big
bang.
Helm
style
go
abrade
everything,
but
this
would
it
also
give
us
the
opportunity
to
do
something.
That's
a
little
bit
more,
a
little
bit
more
controlled
a
little
bit
less
invasive
I!
Guess
you
could
say
I'm!
Sorry,
I!
C
H
H
C
H
Yeah
yeah,
actually,
no,
it
doesn't
work
right
away
because
openshift
works
with
what
we
call
security
context,
constraints
and
those
that
we
call
SCC's.
They
have
very
very
specific
rules
on
security
technologies
under
the
hood,
meaning
apparmor,
as
he
Linux
a
bunch
of
things
underneath-
and
this
is
one
in
particular,
which
is
the
user
ID
that
openshift
changes
by
default.
You
try
to
run
on
openshift.
So
if
I,
if
I
configure
the
user
ID
to
be
any
user,
ID
I
can
run.
H
I
can
run
ok
with
no
problem
so
now
I'm
trying
to
integrate
into
OpenShift
and
put
it
straight
into
the
into
the
embedded
operator
hub
and
then
once
it
is
there.
Okay,
it's
working,
then
I
can
try
to
push
the
CSV
file
that
when
I
mentioned
to
the
community
upstream
operators
and
the
apps
and
the
community
operators
are
two
repos
to
be
able
to
find
operator,
habeo
and
also
pinches.
But
yes,
it
is
installable,
but
not
by
default.
We
need
to
change
a
few
things.
H
C
So
this
is
a
security
context
and
the
other
thing
that
that
we
need
to
work
out.
We
have
not
tested
it
with
Clio,
and
so
it
will
also
be
good
to
to
get
some
feedback
on
whether
you
have
any
trouble
with
how
big
racks
with
Rio
but
yeah
I
think
outside
of
those
outside
of
those
couple
areas
yeah.
If
one
of
the
things
that
I
think
would
be
a
good
idea
to
Edwards
would
be
the
eventual
inclusion
of
some
of
the
OpenShift
stuff
into
our
into
our
CIS,
and
so
when,
when
that's
much
further
along.
C
H
C
H
Yeah
I
do
we
are
seven
off.
There
is
one
more
coming
to
the
team
tomorrow,
so
we
work
exclusively
with
operators,
doing
a
lot
of
stuff
presentations,
consulting
development
and
on
the
NSM
operator
itself.
It's
only
me
for
now,
but
yeah
I
think
they
are
more
than
than
inclined
to
help
help
and
if
I
can
put
you
guys
on
open
it
up
and
OpenShift
hub
and
push
the
operator
to
another
level,
because
we
are
classifying
operators
into
levels.
If
I
can
bring
the
operator
to
level
four
I
can
actually
I.
H
Think
I
can
I
can
have
a
special
channel.
Encore
OS
is
like
just
for
the
operator,
and
then
you
have
access
to
the
whole
team
to
talk
with
them
and
everything
else.
That's
that's
that's
the
way
we
we
were
working
with
with
partners
and
clients.
We
have
almost
every
one
of
you
on
another
project
on
other
projects,
not
just
an
assemble
other
projects.
H
We
have
Cisco,
we
have
VMware,
you
have
f5,
we
have
a
lot
of
Juniper,
so
everyone
has
a
channel
with
us
because
we
work
directly
with
the
partners
and
so
on
and
so
forth
and
and
operators
level
level.
Four
and
five
are
the
most
important
to
us.
So
we
have
a
lot
of
work
to
do
yet
on
that
to
be
there
but
yeah.
C
C
So,
there's
something
that
I
would
like
to
start
building
and
I'm
looking
for
someone
to
help
with
taking
up
a
substantial
portion,
and
so
yes,
we
in
order
to
help
with
the
CNF
efforts,
the
economy,
the
network
functions
that
are
being
built.
Eventually
we're
going
to
need
some
form
of
a
test
harness
to
help
with
the
certification
path
that
they
all
want
to
Edwards.
So
I
want
to
build
this
very
simple
component.
It's
basically
a
test
harness
with
a
generating
temperature
and
a
monitor
conceptually.
It's
very
simple.
C
The
last
bounce
I
wanted
to
pass
out
and
then
short
it
just
be
starting
to
create
a
network
service
that
it
exposes
itself
connects
to
itself
with
a
CNF
or
group
of
CNF
in
the
in
the
chain,
and
it
monitors
everything
in
the
chain
and
looks
for
things
that
look
suspicious
and
suppose
that
CNF
was
the
firewall
on
the
capture
side.
You
can
check
the
dis,
ting,
properly
block
things
that
I
asked
it
to,
or
or
so
on,
so
just
a
short
something
of
what
something
useful
to
build.
That
I
would
appreciate
some
help
with.