►
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).
B
Yep
two
on
five
we're
talking
about
the
event
listener
or
a
web
hook
for
on
the
artelia
side
to
grab
web
hook,
events
that
are
coming
from
like
a
kubernetes
cluster
watcher
program
or
like
the
argo
cd
get
ops
operator.
B
So
those
the
the
get
ops
model
will
publish
a
notification
when
particular
things
have
happened
in
the
cluster
and
you
can
get
very
specific
to
you
can
say
I
want
to
know
when
a
pod
has
been
updated
or
you
know
in
words
a
pod's
been
scaling,
but
we're
interested
in
rollouts
and
deployments
when
those
happen,
because
what
we'll
do
is
we'll
capture
the
we'll
know
that
a
deployment
has
been
completed
by
the
get
ops
operator
and
then
from
there
once
we
get
notified
that
there's
a
command
line
program
that
takes
the
json
string
from
cube,
cuddle,
git
deployment
or
cube
cuddle,
get
rollout
and
it'll
parse
all
that
and
create
the
component
versions
inside
of
ortelius.
B
For
us,
some
of
the
little
things
that
we
need
to
dive
into
at
that
level
is
creating
that
the
web
hook
listener
where
it
could
be
either
like
a
I'm
guessing
they're
going
to
be.
Like
rest
wrestle
api
based
ones
with
either
a
post
or
a
get
with
the
payload
and
from
there
once
we
get
the
the
payload
coming
across.
B
B
B
Mainly
it's
looking
to
derive
the
images
that
have
been
that
are
running
in
the
cluster,
so
the
container
images,
so
usually
that's
gonna,
be
like
the
tag,
the
registry
name
and
then
the
service
name.
You
know
the,
maybe
I
I
think
it
I
think
it's
the
deployment
name
or
the
pod
name.
I
can't
remember
off
the
top
of
my
head
now.
B
Yeah,
I
can't
remember
the
pod
name,
gets
that
weird
generated
string
attached
to
the
end
of
it,
but
either
way.
A
It's
it's
the
part.
The
part
gets
the
the
prefix
of
like
a
good
type
thing
like
a
yeah
yeah,
it's
a
part
yeah.
Another
deployment
deployment
will
always
be
the
same
name.
B
Did
we
have
jenkins,
create
a
new
container
image
for
us
and,
if
so,
when
we
do
that,
we
record
the
registry,
the
tag
and
the
digest
so
because
that
we
can
pair
these
two
up
and
we'll
be
able
to
match
up
what's
happening
on
the
ci
side,
with
what's
what's
running
in
on
the
cluster
side,.
B
The
cli
is
a
python
program
that
does
restful
api
calls
to
the
ortelius
server.
To
do
things
like
create
a
component
update
attributes
create
an
application
version,
so
it's
separate
from
the
web
hook
microservice
that
we
needed
to
create
that's
going
to
receive
the
notifications
from
the
get
ops
operator.
A
B
Okay,
there,
the
one
that's
kind
of
out
there
is.
Let
me
put
this
in
the
chat.
B
There
is
one
called
a
cube,
watcher
or
cube.
Watch
and
cube
watch
is
just
a
generic.
Basically,
I
think
it's
a
golang
program.
B
It's
just
a
generic
golang
program
that
basically
watches
for
what's
happening
in
in
the
cluster,
and
it
supports
notifications
to
slack
hipchat
other
things
like
that.
The
one
we're
interested
in
is
the
web
hook.
Capabilities
of
of
that
and
on
the
same
note,
argo
cd
has
their
implementation.
B
Flux
has
their
own
implementation.
So
we
may
need
to
accept
notifications
that
that
that
webhook
service
should
be
able
to
accept
notifications
from
all
the
to
get
out
popular,
get
ops
operators.
B
A
B
Once
we
get
that
json
payload
in
it's
just
going
to
be
parsing,
it
we're
going
to
look
for
the
data
we
we
need
out
of
it
and
then
from
there
we'll
go
on
to
the
next
step
of
of
interacting
with
the
cia
authorities.
Cli.
A
B
It
would
so
depending
upon
the
implementation,
the
that
was,
that
watcher
would
exist
inside
of
the
cluster
in
the
arterioles
cluster
as
something
to
you
know
as
an
endpoint
that
we
can
hit
now
it
gets
a
little
tricky
because
you
can
have
the
sas
version
of
ortelius
listening
for
these
events,
it
gets
notified
and
then
it
needs
to
go
talk
to
a
a
reverse
proxy.
That's
on-prem
for
that
company.
B
A
B
A
A
Yeah,
I
can
do
both,
but
I
prefer
guy
lane
it's
okay,
it's
fun
for
me
to
write.
Does
the
api
need
or
authentication
like?
Does
it
need
to
authenticate
or
doesn't
matter.
B
I'll
have
to
think
about
how
we're
gonna,
if
we
need
to
do
that,
authentication.
A
I
think
for
now
we
don't.
We
don't
need
to
worry,
because
we
can
always
just
put
it
on
top,
but
I
think
we
would
be
trying
to
get
too
tricky
in
taking
on
too
much
work.
If
we
yeah,
I
think,
let's
just
get
something
working
and
then
we
can
maybe
discuss
it
and
see
how
it
works.
To
start
with.
B
Exactly
let's
start
simple,
and
then
we
can
build
upon
it
on
that
level.
B
So
that's
that's
kind
of
on
the
like
the
back
side
of
the
get
ops
world
now
on
the
front
side,
I
did
put
together
a
document
and
I
wasn't
sure
where
to
share
it
right
now.
It's
just
a
word.
It's
not
very
long.
B
So
I
did
put
together
a
little
bit
like
what
we
talked
about
last
time.
Ortelius.
C
B
B
Yeah,
so
it's
kind
of
because
we
do
ortillo's
deals
with
components
that
it'll
make
it
more
slated
towards
the
ortus
terminology
than
kubernetes.
A
B
So
on
this
I
know
you
were
you're
working
with
sergio
and
starting
up
a
white
paper,
and
this
is
kind
of
like
the
use
case
that
I
came
up
with
for
the
the
front
end
side
and
kind
of
how
I'm
envisioning
it
it
working
basically-
and
we
kind
of
went
over
this
last
time.
B
But
anyways
there's
like
a
stack
and
one
if
you
have
something
to
find
at
the
highest
level,
and
then
you
go
and
use
that
same
variable
that
that,
at
that
level
is
going
to
replace
the
higher
level.
So
there's
this
order
of
precedence,
but
basically,
at
the
end
of
the
day,
we
have
these
key
value
pairs
that
allow
us
to
do
some
neat
things
through
the
pipeline
process,
because
the
key
value
pairs
can
represent.
B
On
the
github
side,
it's
a
little
bit
different
because,
instead
of
us
like
interacting
with
helm
and
giving
hell
an
overrides
file,
we're
going
to
be
interacting
with
git
and
somehow
giving
this
new
data
to
the
into
this
git
repo,
and
that's
where
we
need
to
do
some
research
on
how
to
do
that,
and
you
know
I
know,
there's
like
a
this-
is
where
we
on
the
get
outside
how
people?
How
are
people
managing
you
know
two
or
three
hundred
microservices
across
you
know
three
to
four
environments.
B
You
know
dev
test
qa
production
or
dev
test
staging
and
production.
You
know
how
are
they
managing
you
know,
get
ops
at
scale
with
with
200
microservices,
for
example,
and
how
you
know,
because
that's
going
to
be,
you
know
at
least
a
minimum
400
manifest
files.
You
know
one
for
the
deployment
and
one
for
the
service,
so
there's
two
two
manifest
files
there.
If
you
add
yeah,
you
get
a
config
map
in
there
secrets
it's
just
gonna,
go
exponential.
B
So
that's
kind
of
now,
there's
there's.
I
know
people
are
using
helm
with
git
apps
and
also,
I
know,
there's
some
like
jenkins,
plug-ins
and
then
there's
also.
B
I
believe
people
are
starting
to
move
towards
customize
to
manage
updating
data
in
all
of
these
files
and
also
the
get
ops
operators
themselves
have
some
built-in
templating
or
structure
saying
if
you
can
have,
you
can
have
like
a
base
set
of
of
definitions,
and
then
you
can
add
on
these
other
files
that
are
like
overlaid
on
top
of
that
one,
and
that
type
of
thing,
so
that's
kind
of
where
I'm
kind
of
stuck
at
with
the
the
the
get
ops
world
is
just
making
sure
we
under
you
know
we
have.
B
We
know
what
the
the
key
values
are
supposed
to
look
like
for
a
particular
environment
for
this
application.
You
know:
how
do
we
get
that
information
into
the
git
ops,
world,
yeah,
okay,.
B
So
do
you,
did
you
create
a
google
shared
back
yet
yeah.
A
I
do
I
did,
let
me
get
it,
it's
just
a
template
that
I
use
for
a
security
one.
A
But
that's
a
great
problem
statement
which
I
can
add
to
the
top.
Let
me
just
grab
it
from
my
okay.
B
Put
it,
you
can
either
throw
it
in
the
chat
or
put
it
in
the.
A
A
Yeah,
I
need
to
buy
some
okay,
here's
the
link
here.
B
A
So
really
it's
just
a.
I
was
working
on
a
cncf
one
a
while
ago
and
I
like
the
sort
of
skeleton
for
it.
So
I've
just
done.
I
haven't
put
any
what
you
have.
There
will
be
good
for
the
executive
summary
and
the
problem.
Analysis,
okay
and.
B
B
A
As
well
so
maybe.
A
Because
we
catch
up
sort
of
12
hours
from
now,
that's
when
our
time's
aligned.
So
it's
about
8
pm
at
night.
B
I
will
put
all
of
our
notes
in
there,
so
that's
kind
of
like
the
problem
statement
that
I'm
just
starting
with,
and
I
think
that'll
give
us
a
good
basis
to
start
on
now.
I
didn't
the
the
part
about
the
notification
kind
of
want
to
keep
that
separate
for
now,
unless
I
don't
want
to
mix
two
different
things
at
this
point
eventually,
we'll
need
to
pull
them
together,
but
I
think
right
now
keeping
them
two
separate
tasks.
B
I
think,
will
help
keep
people
on
focused
on
what
we
need
to
look
at.
B
A
So
that
sorry,
we've
received
another
12
months
of
visual
credits:
okay,
nice.
B
Front
is
on
the
accounts
switch
over
on
the
third,
so
one
one
is
is
ending
another
one
is
starting,
so
I
have
to
go
into
the
azure
portal
and
roll
all
the
billing
manually
from
one
to
another.
It
looks
like
I
don't
think
that's
why
I
have
to
kind
of
see
what
wait
and
see
what
happens
if
it's
going.
C
B
So
once
I
know
like
on
the
fourth
or
fifth
I'll
be
able
to
should
have
that
all
sorted
out
and
then
I'll
be
able
to
get
you
guys
in
there
to
install
argo
and
and
whatever
else.
A
Yeah
we
have
all
the
scripts
ready
to
go
as
well,
so
I
actually
created
a
test
up
as
well.
That
taurus
is
using
it's
just
a
simple
react,
app
and
he's
testing
that
with
flux
and
flagger
at
the
moment,
yep.
A
B
A
B
B
You
know
it's
not
a
big
deal,
but
when
you're
looking
at
you
know
a
minimum
of
200
microservices
for
an
application
and
all
the
manifest
files
and
all
the
like,
you
said,
the
volume
mounts
security
all
that
it
just
gets
out
of
hand.
I
just
don't
just
needs-
need
some
eyes
on
how
best
to
deal
with
that
scenario.
A
A
B
And
in
our
you
know
in
our
in
our
test
cluster
we'll
just
need
to
instead
of
us
deploying
you
know,
200
microservices
I
mean
we
could,
but
I
think.
B
A
Sure
yeah,
okay
yeah,
so
I
have
the
terraform
scripts
to
spin
up
the
networking,
the
aks
etc.
Then
we
have
all
the
helm
to
push
argo.
Pretty
much.
Does
it
and
then
we
have
the
test
ups
as
well,
so
we're
looking
pretty
good
come
come
the
third
around.
Then
we
should
be
ready
to
press
some
buttons
and
then
start
seeing
these
problems
and
how
to
solve
them.
B
Perfect
because
I
think
which
one
are
you
going
to
start
with,
is
it
going
to
be
argo
or
flux,
yeah.
A
Really,
like
argo,
I
mean
there's
so
many
companies
adopting
it
now
as
well,
so
it
sort
of
makes
sense
for
us
to
do
that.
First,.
B
B
Yeah,
I
I
totally
agree.
You
know.
I've
talked
to
the
guys
that
created
over
it
into
it,
and
you
know
if
we
need
to
reach
out
to
them
on
how
to
do
things,
we
can
get
a
hold
of
them.
A
B
A
A
B
Oh,
I
believe
yeah
that
was
probably
from
neetu
yeah.
B
Yeah,
so
we're
going
to
we're
trying
to
get
some
students
through
the
google
summer
of
code
to
help
out-
and
this
is
one
of
those
interesting
issues
that
we're
looking
at
as
a
possibility
for
students
to
work
on.
But
what
ended
up
happening
is
the
the
cd
foundation
only
got
six
slots
and
they
all
five
of
them
went
to
jenkins
and
one
went
to
spinnaker.
B
So
the
other
projects
didn't
get
any
encoders
out
of
that.
A
I'm
speaking
with
the
cncf
student
groups,
probably
in
two
weeks,
I'm
doing
a
talk
for
them,
so
maybe
I
can
say
call
to
action
if
you
do
want
to
work
on
some
of
this
stuff.
Let
me
know-
and
I
can
try
and
get
some
good
talent
coming
through
there
as
well.
B
Yeah
and
what
I've
been
doing
with,
I
have
some
people
that
I've
been
you'll,
see
some
issues
out
there
like
around
bubble,
sort
and
stuff,
like
that.
One
of
the
things
that
I
do
is
we
come
across
some
students
and
also
some
people
that
are
just
looking
for
a
a
new
new
profession
and
I'll
run
into
where
they
know
some
basic
python
programming,
but
they've
never
really
created
a
a
production
application.
B
So
I
walk
them
through
building
out
a
microservice
and
we
start
with
this
bubble
sort
and
it
just
ends
up
being
a
simple
python,
flask
bubble,
sort
and
then
from
there
we
change
that
up
to
start
connecting
to
the
database,
you
know
doing
queries
getting
it
packaged
into
a
a
container
image,
having
helm,
charts
being
able
to
deploy
it.
B
So
they
learn
not
only
how
to
to
take
a
simple
flash
program
and
change
it
into
a
an
actual
microservice,
that's
connecting
to
the
database,
but
also
the
whole
get
out
the
devops
process
as
part
of
it.
So
I
got
two
people,
I'm
working
with
on
that.
So
if
you,
if
you
have
any
students
that
you
talk
to,
that,
are
that
are
at
that
level
or,
if
they're
more
advanced
on
the
programming
side,
we
got
plenty.
A
A
B
B
B
Because
I'm
not
I
because,
when
I've
talked
to
our
universities
here
in
new
mexico,
I
get
some
bizarre
things
that
they're
working
on
and
in
teaching.
So
it's
you
know:
they're
they're
still
stuck
in
some
of
these
theoretical
things
that
you
should
be
working
on
and
it.
C
A
B
So
well
I'll
write
up
the
the
notes
and
I
will
take
my
word
doc
and
insert
it
into
your
the
white
paper
piece.
Let
me
just
make
sure
I
can
edit
that.
A
A
Okay,
cool
and
then
I've
got
a
little
bit
yeah.
I've
made
somewhat
of
a
structure
but
yeah.
This
is
just
from
the
the
sig
security
one.
B
B
Alrighty,
I
will
get
our
recording
posted
and
it
should
come
across
on
the
discord
channel
once
it's
uploaded
to
youtube.
B
So
you
can
then
share
it
with
the
rest
of
your
group.
There.