►
From YouTube: August 19, 2021 AUS TZ - Ortelius Architecture Meeting
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
Like
to
play
around
with
let's
customize
a
little
bit
as
well,
but
yeah
we've
got
two:
we've
actually
done
it
as
well.
So
we
have
a
polyamory
and
a
monochrome
to
to
show
you
if
you're
on
yeah
last
time.
B
Last
time
you
two
weeks
ago,
you
showed
me
the
matrix
piece
with
the
polyrepo,
and
I
posed
the
question
of
how
do
we
handle
the
monorepo?
I
mean
the.
B
And
not
a
monorepo
and
ahmet
was
going
to
look
into
that.
How
to
handle
that,
because
there's
a
question
of
in
the
matrix.
If
you
could
put
multiple
git
repos
in
sources
for
the
at
the
matrix
level
or
if
you.
A
Yeah,
I
think
we
can
try
that
right
now
I'll
share
my
screen.
I
think
just
I'll
get
another
project
because
I
don't
want
to
expose
ips
and
stuff
on
the
menu,
but
I
have
a
personal
one
that
I
it's
my
little
sandbox
that
I
play
around
with
yeah.
It
works.
Let
me.
A
A
So
this
is
just
a
really
simple,
essentially
what
it
does
is
it
deploys
my
external
dns
cert
manager.
B
Yeah,
I
I
I
kind
of
remember
how
it
was
working
so,
okay,
so
yeah,
I
remember
the
matrix
piece
from
last
time
would
go
through
and
scan
the
different
directories,
like
your
db,
dns
and
observability,
pass
for
to
kind
of
apply
values
to
those
different
paths
based
on
your
template
from
what
I
remember
is
that
correct.
A
Yeah,
correct
yeah,
so
if
I
had
nested
folders
as
well,
you
simply
go
like
that
as
well,
and
that
will
go
and
search
through
it.
We
actually
did
one
at
the
github
organization
level,
so
it
can
actually
go
even
further
and
scan
all
of
your
repositories
in
the
and
they
get.
A
A
This
one
here
is
using
the
different
provider
so
on
the
other
one
we're
using
list
and
list
and
get
this
one
is
the
scm
provider.
This
will
go
to
organization.
Obviously,
cloud
similar
to
orterius
gets
the
the
secret
name
and
then
filters
any
anything
any
repository
we
have
in
the
organization
yeah
that
will
look
for
any
chart
and
then
do
it
as
well.
So.
B
So
that
that's
awesome,
that
that
will
definitely
now-
let's
say
you
have
you
just
want
to
do
five
out
of
the
ten
repos
in
the
organization
is
there
is,
is
a
filter?
Also,
can
you
filter
on
the
repo
name.
A
B
D
A
I
don't
I
can't
I
can't
answer
that
question
today,
but
I
will.
C
E
E
A
Yeah
but
I'm
sure
there's
more
filters
as
well.
This
is
and.
B
A
But
in
short,
yes,
you
can,
and
if
we
do
need
other
filter
capabilities,
we
can
simply
make
a
ticket
or
just
build
it
into
either
ourself.
C
B
A
B
Somebody
posted
it.
Okay,
let
me
drop
it
in
the
chat.
B
Yeah
I
have
some
family
in
town.
B
So
they're
out,
tracy
and
my
niece
are
out
riding
horses
right
now.
So
oh
wow,
that's
amazing!
Yeah!
We
have
where
we,
if
it's
real
rural
so
literally
just
go
out
the
front
door
and
go
in
any
direction
and
you
don't
run
into
anything
for
miles.
B
So
that's
why
what
covid
for
us
is,
you
know
we're
so
remote,
it's
it's
only
when
we
need
to
go
to
the
grocery
store
or
something
like
that.
We
have
to
take
our
precautions.
B
It
looks
like
it
was
applied,
because
if
that
issue
I
dropped
in
the
chat
looks
like
it
was.
B
It's
very
pretty
recent.
A
A
B
So
I
don't
know
if
the
it's
definitely
looks
like
it's
applied
to
the
like
the
cli
level,
but
I
don't
know
if
it
was
how
it
was
applied
to
the
yaml.
B
A
We,
when
we
used
app
of
apps,
we
would
use
cli
as
a
workaround
for
projects
and
stuff,
because
we
use
a
git
ops
model
to
actually
provision
argo
itself
right
and
then,
for
example,
we
use
helm
file
to
sync,
you
know
to
bootstrap
cluster,
and
then
we
have
we
need.
Argo
needs
external
dns,
cert
manager
and
then,
after
argo
is
implemented,
it
takes
over
those
apps
that
will
bootstrap
to
start
off
with.
If
that
makes
sense,.
A
A
A
Sorry
just
go.
B
So
right
there
right
where
your
cursor
is
right
below
the
text.
B
It
could
be
repo
url
so
that
that's
kind
of
looks
like
how
they
kind
of
implemented
it.
Okay,.
B
To
know
that
there
that
it's,
it
may
not
be
right
out
of
the
box
today,
but
being
able
to
support
a
poly
repo
and
do
it
that
way
will
definitely
make
things
organization
a
lot
easier
instead
of
having
to
duplicate,
helm,
charts
and
multiple
repos.
So
your
app
of
app
repo
plus
your
micro
service,
repo.
B
A
Yeah,
no,
I
think
we
always
want
to
stay
as
close
to
the
dev
branch,
as
we
can
so.
D
A
Okay,
so
it
looks
like
we're
getting
to
a
point
where
these
capabilities
will
solve.
Well,
we
can
use
aggro
to
solve
the
problems
that
we
want
to.
B
Exactly
so,
the
next
step
is
to
think
about.
Have
you
have
you
played
with
the
the
argo
cli
at
all
or
just
for
the
install
of
argo
itself,
yeah.
A
So
so
we
have
it:
we've
got
in
the
bottom
of
our
our
pipeline.
This
is
just
a
azure
devops
pipeline.
We
have
it,
we
use
github
actions,
but
this
is
just
a
aks
one.
A
Here
we're
downloading
the
cli
and
then
I'm
just
I'm
simply
adding
the
cluster
to
logo
and
then
applying
the
applications
there.
B
And
so
that
that
apply
is
applying
argo
itself
to
the
cluster.
A
Yeah,
that's
we
do
that
before.
Actually,
so,
let's
look
at
that.
Actually,
where
is
that,
let's
look
here?
Are
there.
A
It
let
me
find
it
it
might
be
in
another
repository.
A
This
is
the
app
project.
Let
me
open
the
other.
Actually
it
might
be
just
give
me
a
second
define
it.
A
Now
shouldn't
be
in
there,
I
think
it's
that
we've
got
to
see
us.
Let
me
just
find
that
on
the
other,
I'm
just
being
careful
here
just
I
don't
want
to
expose
too
much
on
the
recorded.
B
If
it's
too
hard
to
show,
don't
worry
about
it,
we
know
it's
out
there
and
we
know
that
we
can
what
we
need
to
do
to
get
there,
get
it
in
place.
A
That's
right,
so
this
is,
do
you
mind
if
it
has
no
color
or
would
you
no.
B
A
Yeah,
so
we
what
what
we
do
is
like
like
I
was
actually
hoping.
We
can
do
this
to
the
orterius
azure,
because
what
I
can
do
is
we
have
a
in
the
okay
github
organization,
I'd
like
to
just
start
putting
this
code
into
that
actual
regrow,
and
then
we
could
start
bootstrapping
the
cluster
with
that
home
file
as
well.
So.
B
We
could
put
take
this
put
into
the
azure
cluster,
then
we
can,
because
we,
we
have
the
monolith
and
I
think,
five
or
six
microservices-
that
we
need
to
work
with
right
now
that
are
coming
out
of
the
service
catalog
and
I
think
that
would
be
a
perfect
fit
and
those
are
all
in
all
the
microservices.
So
we'll
have
like
six
or
seven
repos
that
we
need
to
look
across
to
deploy
over
into
the
azure
cluster.
B
A
Yep,
you
can
do
that
yeah.
So
what
you
use
what's
the
ingress
is
the.
A
Yeah,
okay,
we
have
all
the
code.
I
have
the
code
for
that
as
well.
I
actually
have
terraform
code
for
the
whole
infrastructure
provisioning
as
well,
and
then,
if
we
want
to
do
play
around
with
multi-region
clusters,
I
have
there's
your
front
door
connectors.
The
global
load
balancer.
If
we
want
to
start
going
crazy,
that'll,
obviously
be
done
alone,
but
yeah.
B
A
We're
doing
when
I
even
I
run
my
stuff
and
I
think
us
west
yeah,
because
it's.
A
Yeah,
that's
way
down
the
line
anyway,
the
multiverse
and
stuff,
but
yeah
okay.
So
we
can,
we
can
start
to
build.
It
will
be
cool
even
to
have
a
couple
of
use
cases
like
even
the
autelius
docks
or
something
or
we
can
pick
a
small.
A
We
can
do
a
bit
of
a
proof
of
concept
with
it
and
start
collaborating
on
the
code
together,
yeah
full
requests,
yeah.
B
Exactly
so,
the
what
we'll
need
to
do
is
document
how,
since
we're
working
so
close
to
the
dev
branch
for
argo
document,
what
how
basically,
how
to
install
argo
and
apply
all
the
the
the
updates
that
we
need,
like
the
application
set
crd,
it
looked
like
ahmed
had
another
thing
around.
I
can't
remember
any
notes
something
else
that
he
ran
into
that
he
had
a.
He
had
a
find
a
workaround
for.
A
A
Yeah,
because
we
we
can,
we
can
document
it
and
then
also
like
our
setup
is
fully
automated.
So
I
could
destroy
this
today
and
then
I
could
even
delete
the
cluster
and
press
a
button.
That's
back
up
again.
B
Yeah
and
if
you,
if
you
have
it
fully
automated,
and
if
you
want
to
share
that
automation,
we
can
get
that,
like
you
said,
do
a
couple
prs
and
push
it
into
the
one
of
our
repos.
And
then
we
can
do
the
automation
against
the
artillious
kubernetes
azure
cluster.
B
A
Yeah
or
if
I
yeah,
that
would
be
our
first
milestone
yeah
and
I
don't
see
a
problem
with
that.
That
would
be
we
can
make
a
video
out
of
it,
and
a
lot
of
people
would
be
interested
in
that.
I
think.
B
Yeah
and
then
then
kind
of
kind
of
in
parallel.
Well,
it
could
be
in
parallel.
It
just
depends
on.
You
know
how
how
crazy
you
want
to
stay
up
all
night
is
to
start
looking
at
the
the
user
interface
from
ortelius
into
argo.
B
So,
let's
say
out
of
out
of
the
build
process.
We
get
two
new
microservices
that
we
need
to
update
what
ends
up
happening
in
the
pipeline
process.
We
get
a
new
application
version
in
the
artillia
side,
but
it's
it's.
It
represents
the
a
new
version
of
the
application
with
those
two
new
versions
of
the
microservices
plus
all
the
old
ones
and
then
from
there
it
hasn't
deployed.
B
Yet
we
can
then
have
ortillius
do
the
deployment
and
in
which
it
would
actually
go
ahead
and
create
a
pr
with
the
app
of
app
repo
saying
this
is
these
are
the
new
image
tags?
I
want
you
to
apply
to
the
cluster
and
then
once
we
do
that
commit
and
the
pr
gets
merged
then
or
argo
takes
off
and
does
all
the
work
for
us
yeah.
That's
kind
of
what
I'm.
A
No,
it
does
like
you,
almost
can
cut
I'll
go
out
and
just
have
autism
interact
with
the
git
repo
and
argo's
constantly
polling
anyway,
in
the
configuration
exactly.
B
Exactly
yeah,
so
that's
what
I
mean
ortelius
doesn't
talk
directly
to
argo,
but
it
talks
to
argo
through
the
git
repo.
A
Yeah
through
the
yeah,
and
it's
better
that
way,
because
we
don't
have
another
load
of
obstruction
for
no
reason
and
we're
following
if
tomorrow
we
want
to
go
away
from
over
we're
still
using
get
ups
paradigm.
Where,
therefore
other
get
ups
tools
we'll
have
to
confine
to
you
know
somewhat
close
to
that.
B
The
only
thing
that
the
weird
thing
for
me
around
get
ops
is
the
pr
process.
I
know
it's
there
as
a
gatekeeper,
but
it
sure
seems
to
slow
everything
down.
E
A
B
Nice,
because,
right
now
I
see
the
the
the
pr
as
the
bottleneck
for
a
continuous
deployment
process
where
you're
literally
checking
in
code.
It's
being
tracked
all
the
way
through
the
git
repo
and
everything
like
that.
But
then
it's
it.
You
know
moves
out
to
production,
basically
on
it
without
any
human
interaction.
You
know
once
once
the
developer
says
it's
good
to
go.
B
B
Well,
let's
put
is
maybe
it
would
not
necessarily
go
to
production
but
go
to
the
qa
cluster
automatically
or
the
qa
environment
automatically
at
that
level,
and
then
you
get
you
run
through
your
test
cases,
your
automated
test
cases
and
then
after
that's
happy,
then
you,
I
don't
know
that's
where
the
wheels
kind
of
fall
off.
The
cart
for
me
on
the
process
is
on
the
github
side.
Do
you
then
move
that
to
a
different
branch
or
re-tag
it?
You
know,
you
know
how's
the
life
cycle
represented
in
the
gitaps
world.
C
A
It's
that's
why
we
need
to
get
this.
This
pocket
or
yeah.
B
Yeah,
so
I
think
the
like
you
said
milestone,
one
would
be,
let's
get
argo
installed
into
the
ortilius
azure
cluster
and
then
we'll
also
get
the
the
five
micro
services
plus
the
monolith,
deploying
through
argo
into
azure.
A
Okay,
that
sounds
good
I'll
talk
to
sergio
because
he
he
may
nearly
instill.
I
go
I'll.
Just
ask
him,
you
know:
do
you
have
any
work
and
now
that
you
need
to
persist
or
whatever
and
then,
if
it's
okay
with
then
I'll
just
blow
that
out
and
then
I'll
we'll
do
the
automated
pipeline
to
to
put
it
in.
B
B
What
you
guys
have
found
for
through
the
research
is
amazing,
because
I
know
a
lot
of
the
questions
that
I've
been
posing
there's
hard
to
find
any
answers
to
out
there.
You
have
to
go.
A
A
B
E
B
It's
an
interesting
space
and
it's
you
know
I
can
see
that
I
totally
see
the
benefits,
but
also
I
see
some
of
the
bottlenecks
and
I
think
or
artilleous
and
like
I
think
like,
like
I
said
ortelius,
maybe,
like
you
said
kept
in
with
some
of
the
automated
gatekeeping
and
some
of
that
stuff
is
gonna,
looks
like
it's
gonna,
be
a
combination
of
things
that
are
going
to
make
it
actually
work.
You
know
pretty
seamless
from
end
to
end.
A
A
B
Yeah,
because
what
we've
seen
for
on
the
microservices
side,
most
people
are
managing
them.
Basically,
they
got
a
google
spreadsheet
up
to
like
20
or
30
micro
services
and
then.
B
They
can't
keep
track
anymore,
and
it's
just
not
possible.
That's
like
what
sasha's
running
into
in
his
world
is
is
just
keeping
track
of.
What's
where
and.
B
A
I
think
emmett
just
messaged
me
then
he
must
have
forgot.
He'll
come
in
we're
probably
running
out
of
time.
So
I
don't
know.
A
Yeah
I've
got
a
clear
vision
of
what
we
need
to
do
I'll
need
to
get
the
list
of
which
should
we
perhaps
make
a
ticket
or
issue
in
our
project,
and
then
we
can
get
some
acceptance
criteria
around
it
and
then.
B
Yeah,
let's
go
ahead
and
make
a
issue
and
associated
to
the
get
ops
project
and
yeah
just
make.
A
A
B
Yeah
the
reason
why
I
put
everything
in
a
single
repo
it
makes
it
easier.
A
B
Add
add
argo
cte
to
azure
cluster.
B
And
just
put
in
there
now
just
talk
to
sergio
about
blowing
away
old
version.
A
I'll
just
quickly
write
his
what's
his
handle.
It's
like
four.
A
Did
you
create
talk
to
cj
about.
B
And
then
just
add
in
just
to
add
in
going
planning
to
install
from
automated.
B
B
That
an
issue
then
we'll
create
a
second
issue
for
installing
ortilius
with
argo.
B
Yeah,
I
think
you
guys
have
a
really
good
handle
up.
You
know
on
what
we
need
to
you
know,
move
things
along
and.
A
B
Yeah,
I
think
part
of
it
is
we're
just
running
into
a
time
zone
issue
with
india.
A
Yeah
you
yeah,
I
mean
you
mean
we
want
to
have
people
from
india
contributing,
but
they
can't
make
this
time.
A
Yeah
because
because
I
can
move
like,
I
can
just
report
back
to
you
if
we
want
to,
I
can
run
them
at
night
time
here
and
then
that's
indian
time,
and
then
I
can
just
report
back
to
you
on
on
the
outcomes
and
actions.
Yeah.
B
If
you
want
to
well
well,
let's
get
this
milestone
out
there
I'll
reach
out
to
some
of
the
and
we're
wrapping
up
the
service.
Catalog
piece
we're
going
into
testing
hopefully
next
week
and
documentation
is
the
plan
to
hit
that
next
week.
So
that's
gonna
be
wrapping
up.
A
C
B
Yeah
we
have
home
files,
we'll
just
need
to
make
sure
just
put
in
our
review
helm
files
for
argo
implementation.
A
Yeah
I'll
give
you
like
a
two-minute
update
of
what
we
talked
about.
So
we
reviewed
application
sets
as
well
of
what
what
we've
done.
We're
now
talking
about
removing
sergio's
argo
from
the
aks
cluster
on
the
ortillius
subscription
and
then
we're
going
to
do
an
automated
way
of
getting
argo
city
into
orterius
at
the
cluster
and
then
we're
going
to
actually
install
all
the
autonomous
application
using
argo.
So
we're
just
making
a
few
tickets
for
that
as
well.
B
Yeah
so
the
the
new
version,
the
service
catalog
version
of
ortillius,
we're
going
to
have
the
monolith
plus,
I
think,
five
or
six
microservices
and
probably
like
a
nginx
ingress.
As
part
of
that
that
we'll
want
to
install
using
argo
and
that's
a
poly
repo
type
of
setup.
A
Yeah
we
have
the
code
as
well
to
so
we'll
have
in
nginx,
but
then
we'll
have
the
separate
load.
Balancer
entry
point
for
argo,
because
I
did
that
research
regarding
you
don't
want
to
go
through
ingress
because
then,
if
your
ingress
fails,
you
don't
have
a
weight.
Well,
you
can't.
B
A
Yeah,
I
mean
I
mean
technically,
you
could
for
the
service
to
your
local
whatever,
but
I
mean
it's
not
ideal.
D
A
Yeah
so
nginx
ingress.
D
D
Yeah,
so
we
have
completed
poly
repo
as
well,
for
application
set
up,
there's
just
a
specific
format
for
it,
which
I've
shown
brad
yeah.
We
were.
B
D
B
Earlier
and
I
I
posed
the
the
question
to
brad
about
filtering
repos
at
the
github
organization
level,
and
we
found
a
an
issue
on
the
argo
side
that
addresses
it,
but
it
looked
like
it
was
at
the
cli
level,
but
it
must
be.
I
didn't
go
into
the
the
go
lane
code
yet
to
look
at
how
it
was
being
picked
up
from
the
yaml
file,
but
I'm
sure
that
it's
going
to
be
the
same
implementation
on
the
back
end.
D
D
There
is
a
certain
there
is
one
type
of
filter
for
poly
reapers.
As
long
as
you
have
different
folder
structures,
rather
than
changing
the
entire
repository
name
and
filtering
by
repository
names,
you
can
have
a
separate
folder
structure
and
only
read
those
repos
which
have
that
folder
structure.
So,
for
example,
in
50
of
your
repos,
you
can
call
the
folder
chart
and
configure
that
into
your
poly
repo
setup
of
our
go
and.
A
D
Read
those
setups,
so
that
is
one
solution
before
they
come
up
with
the
fix
for
this.
B
B
And-
and
I
don't
know
if
you
caught
it
when,
if
you
jumped
on
yet
but
the
tentative
proposal
that
our
design
that
we're
kind
of
kicking
around
is
so
out
of
the
cicd
process,
let's
say
you
get
two
new
containers,
new
images
that
were
created
on
the
ortilla
side.
B
That's
a
new
version
of
the
application
and
ortilius
then
would
interact
with
the
git
repo
to
update
like,
for
example,
the
image
tag
in
the
app
of
app
repo
saying
this
is
the
new
values
I
want
you
to
apply
for
to
the
cluster
and
then
ortilius
would
be
interacting
with
github
or
git,
probably
creating
a
pr
or
doing
something
like
that,
and
then
once
the
pr
has
been
merged,
argo
would
take
over
and
do
all
the
heavy
lifting
from
there.
B
Argo
argo
events
come
on
the
back
end,
so
the
argo
events
come
into
play.
When
argo
completes
the
deployment,
then
we
know
that
we
can
record
it
on
the
artelia
side
saying
this
is
the
deployment
the
deployment
of
this
version
of
the
application
finally
happened.
D
B
So
one's
the
front
end
piece,
so
the
front
end
piece
is
saying:
I
have
a
new
version
of
the
application.
I
want
you
to
deploy
to
the
qa
cluster,
for
example
in
that,
in
that
new
version
that
we're
that
we're
sending
out
there's
two
new
microservices
and
there's
ten
old
ones.
B
So
I'm
going
to
go
ahead
from
the
artelia
side
and
update
the
the
manifest
files
with
the
new
image
tag
and
I'm
going
to
go
ahead
and
do
my
push
and
my
pr
with
the
new
values
file
right
so
from
there.
That's
stasis,
ortelius,
interacting
with
with
git
and
github,
to
do
the
the
pr
process
once.
A
B
Once
somebody
comes
in
and
merges
that
pr,
then
argo
takes
over
and
and
rolls
that
out
to
the
qa
environment.
For
me,.
D
Correct
one
other
question
I'll
have
is
ideally
shouldn't
this
pr
be
conducted
on
a
dev
environment
rather
than
a
qa,
like
general
flow
of
practice,
would
be
on
dev,
you
create
your
prs,
etc.
You
merge
it
into
dev.
So
now,
whatever
you
have
in
master,
gets
deployed
on
all
following
environments,
which
is
staging
qa,
pro
preprog,
etc.
B
Yes,
yes,
you
could
yeah.
I
just
is
using
that
example
yeah.
We
could
you,
you
merge
merged
to
master
and
then
from
there
you
would
pick
up
from
there.
B
That
was
one
thing
that
I
wasn't
quite
sure
on
how
an
outstanding
ish
understanding
for
me
is
how
the
pipeline
is
handled
in
argo,
but
that's
down
the
roads.
You
know
how.
How
is
our
it's
more
of
an
argo,
get
ops
thing
than
than
anything.
You
know,
how
do
you
handle
dev
test,
uat
and
production
at
the
repo
level?
Do
you
do
separate
branches?
Do
you
do
separate
folders?
B
B
It
would
be
nice
to
understand,
but
kind
of
beyond
the
scope
of
what
ortilius
needs
to
know
about.
D
Correct
so
in
my
head,
what
I
was
thinking
is
for
so,
if
you
notice,
we
mentioned
the
type
of
branch
which
is
head
or
master
etc
within
the
respective
application
set
yeah.
So
I
was
thinking
that
for
dev.
Ideally,
you
would
want
star
feature
branches
or
all
the
feature
branches
to
get
deployed
on
your
dev
environment
only
so
that
would
mean
that
dev
branch
needs
a
separate
application
set
right,
and
apart
from
that,
all
the
other
environments
should
be
committing
only
master.
D
So
all
the
other
branches
will
have
master.
So
you
don't
need
to
specify
for
all
the
other
branches,
but
it's
only
for
dev.
You
would
have
to
create
a
separate
application
set
within
the
cluster
and
for
all
the
other
branches.
You
just
include
them
within
your
matrix,
where
you
mention
head
and
the
cluster
would
have
all
the
different
cluster
names.
B
Got
it
yeah
yeah
that
makes
sense
and
then,
where
the
events,
the
argo
events
come
into
play
is
on
the
back
end.
So
after
argo
has
been
completed,
the
deployment
to
the
dev
cluster,
for
example,
we
would
use
that
events
hook
to
let
ortilius
know
that
this
application
version
has
made
it
to
the
dev
cluster
and
we
can
record
because
one
of
the
things
we
keep
track
of
on
the
artillery
side
is
which
environments
have
which
versions
of
the
application.
B
D
No,
I
already
started
playing
around
with
artwork
events
and
deployed
it
internally
cool
the
thing
with
that
is,
I
think,
argo
events
is
the
more
I
read
about
it.
The
more
I
feel
algo
events
is
tightly
coupled
with
argo
workflows.
So
without
the
workflows
you
can't
trigger
the
events,
because
I
created
whatever
is
required
by
the
events,
but
there's
no
way
to
trigger
them
without
the
workflow
in
place
yeah.
D
D
Yeah,
so
there
is
something
called
a
source,
a
source
and
event
box
and
a
sensor,
so
the
if
the
source
is
the
weapon
where
the
source
basically
would
get
triggered,
and
you
mentioned
what
is
the
end
point
of
the
webhook,
etc.
C
D
Eventbus
is
the
one
which
will
take
care
of
the
overall
deployment
and
finally,
it's
the
sensor,
which
does
the
end
deployment
or
displays
the
final
result
or
pushes
that
thing
into
your
code,
etc.
So,
that's
the
last
bit,
but
wherever
I'm
looking
into
the
examples,
they
all
refer
to
workflows
as
a
resource.
D
B
Right
right
now,
I
remember
when
I
was
looking
at
events
that
they
had
a
slack
example
to
throws.
Basically
after
the
deployment
was
finished,
that
it
would
send
out
a
slack
message.
So
you
may
look
into
that,
because
that
was
one
of
the
events
I
saw
or
one
of
the
examples
I
saw
on
catching
a
deployment
completion.
D
C
B
I
honestly
don't
remember
as
a
while
ago,
so
I
don't
recall
off
the
top
of
my
head.
E
A
So,
for
the
five
to
six
microservices,
can
we
assign
someone
to
give
us
more
information.
B
You
could
put
me
as
the
contact
for
now
and
I'll.
I
will.
A
A
Okay,
that's
three:
four:
five.
D
All
right
yeah
do
we
have
any
specific
use
case
for
the
argo
events
where
we
could
actually
test
it
with
ortelius,
because
right
now
I
don't
have
okay.
Maybe
I
could
just
do
the
slack
integration
for
myself
and
see.
B
My
question
no
to
answer
your
question:
no,
we
don't.
We
don't
have
the
web
hook
created
yet.
B
B
Yeah,
that's
what
basically
we
were.
I
was
gonna
write
as
basically
a
flask
just
because
I'm
more
familiar
with
python
then
go
either
way.
It
doesn't
really
matter.
D
I
totally
agree
brad.
I
was
thinking
that
we
could
probably
write
a
quick
thing
where
which
basically
shows
every
time
we
push
into
the
kubernetes
repository.
It
pushes
out
onto
slack
saying
that
you
know
we
pushed
into
the
repository
type
of
thing.
Yeah
yeah.
A
B
D
A
B
A
For
me,
a
little,
I
think,
keeping
it
inside
the
cluster
is
a
good
option
and
we
can,
because
if
we
want
to
write
to
the
postgres
sql
as
well
the
payload
or
we
want
to
get
certain
metadata
to
update,
we
can
sort
of
kill
two
birds,
one
stone,
so
we
almost
make
like
a
little
interface
in
between
it,
and
then
we
have
different
events
going
to
different
tasks
that
we
required.
Does
that
make
sense.
B
B
A
That's
just
a
yeah
apr
basic
api.
B
B
B
Yeah
now,
like
you
like
you're
saying
ahmet,
I
don't
know
if
how
if
a
workflow
is
needed,
or
you
know
what
is
needed
to
make,
this
thing
actually
happen
other
than
just
just
deploying
the
the
sensor
into
the
cluster
you
know
or
that
that's
still
a
mystery.
D
I
will
update
you
all
well
I'll,
update
you
on
the
next
cycle,
but
I
will
dig
into
this
over
the
weekend.
Okay
and.
B
A
A
We
could
almost,
if
maybe
we
can
get
invaded
to
do
this.
I
actually.
A
So
steve
we're
mentoring.
We
take
like
a
couple
of
interns
just
to
mentor
them,
so
we
can
give
them
like.
You
know,
teach
some
tasks
like
this,
which
is
pretty
easy
and
then
yeah.
Okay,.
A
A
Yeah-
and
this
is
quite
cool
like
little
garland-
it's
fun.
A
Okay,
I
I
think
that's
almost
the
ticket
itself,
then.
A
Let's
make
it
a
ticket,
so
are
we
calling
it
implement
sensor
of
arvo
sensor,
object
or
whatever.
B
A
We
can
we
can
go
over.
Whoever
wants
the
pictures
that
you're
up,
we
can
sort
of
mentor
them
and
go
over
or
yeah
and.
B
Then
brad
before
under
projects
they're
on
the
right.
A
B
Yeah
yeah,
no
right
there.
On
that
page,
I
made
a.
B
Oh
yeah,
either
way
whichever
easier,
okay
but
that's
out
there.
So
we
can
start
since
we're
gonna
have
more
coding
around
this
and
we
need
to
keep
track
of
stuff
yeah
and
you
need
a
little
checkbox,
but
click
on
the
little
icon.
Next,
to
the
get
ops.
B
A
B
A
B
If
you
wanna,
if
your
intern
does
a
pr
against
the
arterius
readme,
we
can
add
them
to
the
dev
group
and
then
they
can
be
assigned
that
issue.
A
B
A
Yeah,
it's
it's
going
to
be
really
awesome,
especially
to
implement
this
like
when,
when
they
release
the
argo
release,
we're
already
like
because
we're
using
dev
branch,
it's
so
cool
that
as
soon
as
they
release
we've
already
like
full
using
application
sets
and
yeah.
It's
quite
impressive.