►
From YouTube: Jan 6, 2022 - Ortelius Architecture Meeting AUS TZ
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
Okay
cool,
so
this
is
the
arterius
architecture.
Australian
time
zone
for
january,
6th
and
ben
was
just
talking
about
the
work
he's
been
doing
with
artifact
hub
and
making
it
all
look
pretty.
B
So
what
we
had
the
issue
that
we
had
with
our
what
we
had
uploaded
to
artifact
hub
was,
it
didn't,
have
any
readme,
so
it
didn't
have
much
information
and
well.
I
had
been
doing
some
digging
around
seeing
how
other
repos
have
been
doing
their
work
and
it
turns
out
to
be
quite
simple:
it's
actually
having
a
readme
alongside
your
charts.yaml
and
whatever
you
put
in
there
that
will
get
copied
exactly
into
artifact
hub
and
you'll,
have
the
whole
nice
and
pretty
documentation.
B
A
And
does
that
end
up
on
the
the
github
pages
branch?
Hey
brad,
happy
new
year,
my
usual.
A
D
C
So
let
me
just
share
this
charts.
B
B
B
So
this
just
gets
brought
over
alongside.
So
if
we
just
look
at
our
tedious
thing,
it
will
say
that
package
does
not
include
a
readme
file,
and
I
guess
that
was
the
hint
like.
If
you
had
to
read
me
adjacent
to
it,
it
will
come
up
with
it'll
just
bring
this
across,
which
you
see.
Is
it's
the
exact
same
thing
here
directive.
That's
the
exact
same
thing
that
gets
brought
over
yeah
and
yeah.
B
It's
in
terms
of
the
icon,
it
just
that
wasn't
what
I
expected,
but
you
literally
just
pop
it
in
there
nice
and
yeah.
If
you
didn't
have
the
thing
in
there,
if
you
didn't
have
an
icon,
let's
see
as
an
example,
that
is
the
default
helm
package
icon,
which
is
what's
applied
for
all
the
ortiz
ones.
B
A
Right
right,
let
me
see
if
I
know
where
the.
B
Where
do
we
use
the
the
green
alien
or
whichever
other
logo.
E
D
A
Yeah
yeah
I'll
make
sure
those
readmes
get
updated.
A
Let's
see
oops
wrong
directory,
I
think
we
can
steal
it
from
the
website
repo,
but
I'm
just
looking
into.
A
B
B
A
All
right,
let
me
get
the
the
logo
out
there
for
all
those
repos
on
the
github
pages
branch.
B
A
A
Let's
double
check
to
make
sure
this
is
the
one,
and
what
else
do
you
have
you
found
this
part
of
part
of
the?
What
you've
been
up
to.
B
B
A
A
Okay,
that'll
be
easy
to
do
to
go
cruise
through
the
charts
and
add
those
in
all
right.
B
I
think
we've
put
all
of
these
in
the
issue
under
others
itself,
so
that
perfect
should
be
fairly
well
documented.
Now.
A
Cool,
and
did
you
figure
out
with
your
program
how
to
do
the
merge,
the
charts
and
preserve
the
you
know,
so
we
have
like
a
version.
B
Of
the
release
version
yeah
yeah-
that
was
the
one
that
I
did
not
managed
to
get
well.
I
haven't
mentioned
found
the
answer
to
the
other
thing
that
I
was
looking
into
was
getting
like
micro
service
a
when
that
gets
an
update,
send
and
send
a
notification
to
right
helm,
charts
to
trigger
a
re-release
yeah.
That
was
when
that
it
was
those
two
things
that
we
were
supposed
to
be
looking
at.
One
was
trigger
the
re-release
and
the
keeping
versions
right,
keeping
versions.
I
wasn't
able
to
get
the
answer
to
that.
A
Basically,
it
looks
like
you
pass
along.
The
github
token
to
the
curl
command
is
part
of
the
off
bearer,
and
then
you
just
hit
the
api
on
the
other.
Repo
is
going
to
be
the
end
point
that
you
end
up
hitting
and
you
basically
one
of
the
parameters
is
which
figure
yeah,
which
trigger
to
run
the
other
way
is
through
the
gh
command
line,
so
we
can
in
the
actions
themselves.
I
believe
the
gh
command
is
available.
A
A
Yeah,
let's
see.
A
A
And
I
haven't
played
around
with
that
particular
event,
but
I
think
that
that
one
does
look
promising.
C
B
Yeah,
that
makes
sense,
but
that
was
one
of
the
things
that
I
was
looking
into.
This
workflow
dispatch
thing,
whether
you
trigger
the
workflow
dispatch
event
via
the
github
cli
or
to
irs
endpoint,
either
way.
That's
why
we
would
need
to
update
onto
that
the
charts
repo
itself
to
accept
this
dispatch
event
and
on
all
the
separate
microservices.
They
would
need
to
add
the
the
trigger.
I
guess
at
the
dispatch,
whereas
the
other
ones
they're
receiving.
A
B
B
A
A
Let
me
let
me
if
I
find
it
I'll
pass
along
what
I
found,
but
I
I
think
the
ghcli
from
meyer
member
had
a
way
to
to
say
you
know:
do
this
exact
workflow
over
on
this
other,
this
other
branch
or
other
repo.
B
A
A
Cool
all
right,
so
I
will
put
on
to
my
to-do
list.
Actually
I
just
cloned
this
repo
and
it
goes,
the
icon
goes
into
the
gh
pages.
A
B
B
Whatever
you
do
in
the
ortiz
charts
that
gets
updated
every
hour,
got
it,
but
in
terms
of
just
re-indexing
that's
12
hours
or
we
could
always.
I
think
you
could
I'm
not
sure
if
we
could
just
make
it
run
on
click.
I
I
don't
know.
If
I
had
that
set
as
an
option,
you
should
be
able
to
just
run
it
when
you
want
it
to.
C
E
But
you
should
you:
shouldn't
have
to
run
that
at
all.
We
should
just
if
there's
a
change
made
to
chart,
then
it
triggers
the
build.
C
A
No,
and
if
we
can
get
it
to
react
to,
you
know
changes
that
would
be
great
yep.
E
Even
if
in
the
action
you
could
even
there's
a
hundred
ways
to
do
it,
but
you
could
even
do
in
each
individual
repo.
If
the
charts
and
if
the
charts
folder
has
changed,
then
you
could
even
commit.
B
E
I've
changed
and
that
will
re-run
the
helm
indexer
as
well.
A
The
way
so
I
put
so
this
is
the
artist
church
repo
and
I'm
on
the
gh
pages.
B
A
I
put
the
logo
png
there
do
I
have
to
do
anything
else.
Are
we.
B
D
Benjamin
or
steve
is
anyone?
Is
there
a
plan
to
document
any
of
this
stuff
for.
A
Yeah
so
as
part
of
the
installation
documentation
once
we
get
the
process
sorted
out
and
we're
past
the
debugging
we're
gonna
document
all
this
in
how
to
install
ortilius
and
as
part
of
that
we'll
go
ahead,
and
you
know
kind
of
lay
out
how
things
work.
So
I
think
what
we
probably
should
do
is
once
we
get
all
the
plumbing
in
place
is
kind
of
do
like
a
quick
little
diagram
kind
of
showing
you
know
when
you
check
in
here.
This
is
what
happens.
A
You
know
you
do
the
check
in
and
we
go
through
and
do
the
the
update,
the
yamas,
and
then
we
do
the
the
workflow
trigger
to
the
other
repo
that
stuff,
I
think,
will
once
we
get
it
that
plumbing
sorted
out,
then
we
should
be
good
to
get
the
documentation
firmed
up.
D
Okay,
so
right
now
the
any
update
we
are
pushing
the
helm,
charts
to
artifact
hub
right.
A
Yes,
we
are,
it
is
all
like
ben
and
brad
were
saying
it's
done
on
timers
right
now
and
that's
where
we
need
to
get
the
last
couple.
Little
steps
in
place
with
the
arriba
repo
trigger
okay,.
A
So
ben
it
looks
like
I
pushed
the
logo
out
there,
so
yeah.
B
A
A
All
right
cool,
let
me
all
right.
I
will
go
through
and
add
that
line
to
all
the
other
charge,
ammos
yeah
exactly
I
have
all
the
repos
local.
So
it's
not
a
big
deal
for
me
to.
A
Oh
yeah.
A
A
And
what
was
the?
It
was
just
icon
right.
B
C
A
Give
me
one
second:
just
gonna
push
it
over
and
we'll
do
one
to
make
sure
it
looks
good.
F
A
So
what
I
do
and
the
back
end
side
is,
I
have
deploy
hub,
actually
is
going
back
and
after
it
deploys
it
to
the
cluster,
it
goes
and
updates
the
charts
values
file.
So
everything
is
kept
in
sync,
so
it's
kind
of
like
the
the
loop
process
that
we.
F
A
So
I
just
pushed
the
so
there's
a
microservice
called
comp
item
that
one
I
just
updated
the
chart.yaml
with
the
icon
link
in
it.
So
it'll
take
a
little
bit,
but
it
should
hopefully
by
tomorrow
we
can
take
a
peek
and
see
if
everything
kind
of
caught
itself
back
up
and
it
is
working
as
we
expect.
B
Sounds
good,
let's
see,
chart
yaml
has,
is
it
on
main
or
in
deploy.
B
Yep,
I
think
that
should
trigger
release
charts
got
angry.
I'm
not
sure
why
it's
run.
Chart
releaser
successfully
error,
creating
validation
failed.
B
B
B
Yet
it's
complaining
that
there
already
is
a
release
with
that
particular
version.
Probably.
C
A
Okay,
I
just
kicked
off
another
one.
I
bumped
it
to
40.
A
Yeah
and
we
we
use
the
the
job
number,
basically,
the
build
number
to
increment
the
release.
So
when
I
did
all
this
manually
it
just,
I
think
I
messed
it
up
a
little
bit,
but
I
think
we'll
should
be
back
on
track.
B
A
B
B
All
right
and,
on
my
end
I'll
continue
looking
into
the
the
github
dispatch
thing
to
get
repo
a
to
get
chart
released
to
rerun,
rather
than
on
a
12
hour
shift.
A
Right,
perfect,
and
let
me
know
if
you,
if
you
are
having
a
hard
time
finding
or
getting
it
to
work,
and
I
will
hunt
down
what
I
saw
at
one
point.
E
Yeah
I've
been
doing
a
lot
to
argo
city.
Actually
I
changed
the
installation
of
it
from
home
to
customize,
because
it
it
allows
me
to
be,
you
know,
have
way
more
customizations.
A
E
It's
actually
a
really
highly
configurable
tool,
which
is
quite
awesome,
doing
lots
around
secret
management.
At
the
moment
I
was
studying
over
the
new
year
hashicorp
vault,
so
I've
got
hashtag
vault
running
in
kubernetes
as
well
nice.
So
getting
that
working
with
a
argo
cd
plugin
they,
it
was
built
by
ibm,
called
fault
secrets
or
something
like
that
yeah
and
then
just
been
testing
out
external
secrets,
sealed
secrets
and
hashicorp
vault
and
seeing
what
fits
best.
E
E
A
When
we
get
close
to
doing
switching
over
to
argo
well,
we
could
actually
do
it
in
parallel.
We
could
have
the
playhub
deploy
to
one
namespace
and
then,
at
the
same
time
we
can
have
argo
deployed
to
another
namespace,
and
we
can
kind
of
you
know,
compare
what's
happening
on
that
front.
E
E
Oh
I'll
pick
out
the
good
ones,
the
sometimes
it's
hard
work,
having
people
that
don't
really
know
much,
but
when
I
pick
out
the
good
ones
I'll
get
someone
kept
in
and
then
we
can
finish
this
project.
A
Yep
yep
yeah,
I
think
we're
getting
really
close
yeah
or
you
know,
and
I
think
even
I
can't
remember
on
the
cluster
side,
we
may
actually
have
the
two
different
clusters
where
deploy
hub's
deploying
to
one
cluster
and
argos
is
deploying
to
the
other
one.
So
that
way
we
can.
We
can
actually
you
know,
compare
things
that
way
as
well.
Instead
of
separate
name
spaces,
so
it'll
be
it'll,
be
interesting.
E
Yeah
because
we
still
have
a
devops
cluster
that
we
can
use
as
the
management
cluster
and
then
we
can
deploy
use
that
to
deploy
the
charts
to
the
other
cluster.
E
A
Yeah
yeah,
just
just
let
me
know
if
you
think
most
of
the
people
are
gonna,
be
from
your
side.
You
know
which
time
zone,
so
we
can
figure
out
the
best
yeah
kind
of
to
make
sure
that
we
get
the
right
people
in
in
the
room.
E
Yeah
it'll
it'll
it'll
be
more
like
india
apac
time.
A
lot
of
this
will
be
from
india,
so
it
won't
be
this
time
anyway.
It'll
be.
E
A
Yeah,
I'm
working
with
on
my
to-do
list
is
to
work
with
sergio
to
help
clean
up
some
of
the
tickets
and
get
them
kind
of
re-categorized
and
give
some
more
details
to
them.
So
we
can
kind
of
start
make
it
easier
to
dull
tickets
out
to
people
to
work
on
so.
B
A
That's
kind
of
on
the
to-do
list
is
to
get
that
cleaned
up,
so
we
can
bring
more
people
on
to
help
contribute,
especially
at
the
coding
level.
F
E
A
Okay,
yeah,
I'm
gonna,
have
some
travel
in
february,
but
january
looks
pretty
open.
Okay,.
E
E
That
that's
pretty
much
it
for
me.
Make
good
progress
on
other
and
do
are
we
going
to
use
sdo
going
forward
as
well?
You've
got
it
in
the
other
cluster.
A
We
can
go
either
way
on
that.
We
can
stand
up
the
nginx
route,
do
the
routing
through
the
engine
x
as
a
reverse
proxy,
or
we
can
use
istio
both
of
them
work.
It's
just
how
you
plumb,
together
the
incoming
traffic
yeah,
what
you?
What
you
stick
in
the
cloud
cluster
for
the
proxy
routing.
A
Okay,
yeah
and
that
and
that's
already
configured
to
use
engine
x.
So
it's
it's
not
a
lot
of
changes
on
that
front
for
us
to
implement
that.
E
E
E
Yeah
I
can.
I
can
do
an
example
of
that
this
week
as
well,
and
I
just
did
something
recently
with
directive
about
it.
So
yeah.
A
Right
all
right,
yeah,
oh
sasha,
is
working
on
the
I
talked
to
him
this
morning
and
he's
picking
up
working
on
the
the
main
and
sub
charts.
So
we'll
have
a
main
chart
that
we
can
do
a
a
single.
How
like
helm,
install
or
tell
this,
and
then
that
one.
C
A
Include
the
sub
charts
as
part
of
it:
okay.
E
A
So
he's
pulling
that
together
and
I'm
gonna
bug
him
to
see
if
he
can
get
it
done
by
like
monday
or
tuesday.
E
Yeah,
if
he
needs
help,
I'm
more
than
happy
to
help
him,
because
I've
done
home
for
a
long
time
so
happy
to
help
him
if
he
needs
it.
D
No,
I
just
started
getting
back
into
the
calls,
so
I
have
to
just
get
you
know
catch
up
at
least
a
week
or
two.
I
think
yeah.
C
A
Ari
well
excellent
progress,
everybody.
This
is
very
exciting.
We're
we're
getting
to
that
home
stretch.
Just
gotta
pull
it
over
the
finish
line
here.
Yep.
E
Oh
I'll,
we'll
catch
up
with
the
captain
team
soon
as
well
I'll
sit
up
meeting
up
with
them
as
well
they're
in
austria,
time.
A
E
A
Oh
perfect,
yeah
excellent,
all
right
cool
that
that
that
works
for
me.