►
From YouTube: 2022-09-21 Delivery:System Sync and Demo
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
A
Yes,
okay,
so
I've
got
the
first
item
on
the
agenda
regarding
the
learning
how
to
build
things
inside
of
CNG,
which
contributes
to
our
current
okr
learning,
how
we
want
to
build
a
system
for
independent
deployments.
A
A
They've
had
a
lot
of
their
okrs
that
were
scheduled
for
this
particular
quarter
have
been
rescheduled
or
pushed
out
because
of
a
lot
of
interrupt
work.
That
has
come
their
way
due
to
various
compliance,
things
that
are
being
raised
to
their
team
because
of
this
I,
don't
see
them
being
able
to
readily
provide
us
the
necessary
support
that
we
need
in
order
to
make
the
necessary
contributions
to
CNG,
to
make
it
work
for
us.
A
So,
in
order
to
combat
this
I've
created
a
secondary
issue
and
kind
of
replaced.
The
initial
one.
A
The
initial
issue
was
geared
towards:
let's
figure
out
what
we
could
do
to
CNG,
to
make
our
builds
as
efficient
as
possible,
because
that
requires
us
to
work
with
distribution
and
because
they're
quite
busy
I,
don't
see
that
being
worked
on
effectively
and
being
something
we
could
successfully
do
this
quarter.
A
So
what
I've
decided
to
do
is
create
a
secondary
issue
where
we
kind
of
just
learn
how
CNG
operates
as
it
is
today
and
figure
out
what
capabilities
exist
that
enable
us
to
minimally
get
a
build
set
to
CNG
and
figure
out
how
to
get
the
data
that
we
want
out
of
it
and
then
from
there
we
could
drive
conversations
with
distribution
for
upcoming
quarters
as
to
what
we
want
to
see
and
help
guide
their
work
for
improving
CNG
as
necessary.
A
They've
already
got
a
lot
of
epics
and
issues
that
are
circling
around
making
CG
more
effective
and
efficient
in
general,
there's
even
a
rapid
Action
Group,
because
they're,
because
the
big
lab
or
gitlab
CI
project
takes
a
long
time
and
CNG
does
contribute
to
that
pipeline.
So
they've
already
got
various
issues
around
efficiency
and
driving
the
effectiveness.
A
For
that
project,
I
think
if
we
figure
out
and
learn
CNG,
we
could
help
Drive
what
we
want
to
see
out
of
it
in
the
future,
which
I
think
this
would
be
a
good
opportunity
to
take
advantage
of
so
I
just
picked
up
this
new
issue
that
I
created
so
far,
I'm
kind
of
just
learning
the
ropes
of
CG
as
it
stands.
I've
already
got
a
documentation,
update,
murder
quest
set
their
Direction
because
that
there's
some
documentation
slightly
out
of
date,
I'm
going
to
see
what
it
likes.
A
A
So
it
uses
a
lot
of
repository
storage
in
the
back
end
and
I
cannot
use
pre-proc
well,
I
guess
I
could
use
pre-prod
for
this,
but
I
don't
want
to
I,
don't
want
to
create
another
production,
clone
or
Fork
of
this
project,
so
I'm
going
to
use
I'm
going
to
use
staging
just
for
testing.
Why
not
and
I'm
going
to
go
from
there
so.
A
I,
don't
have
anything
to
demo
related
to
this,
because
this
is
something
that
I
just
started
working
started
working
on,
I'm
hoping,
maybe
the
next
time
we
have
this
meeting
I'll
have
something
more
concrete
to
either
showcase
or
at
least
indicate
you
know
what
we
could
do
with
CNG
at
that
moment
in
time.
So
unless
anybody
has
any
specific
questions,
I'm
not
really
sure
what
else
to
say
that.
B
A
I'm
gonna
try
to
create
a
lot
of
documentation
updates
inside
of
CNG,
so
what
I
might
do
is
if
I
see
something
that
is
questionable
or
maybe
there's
something
I'm
not
competent
on
obviously
I'll
send
it
to
distribution
preview,
but
maybe
I'll
send
it
to
one
of
us
here
in
systems
to
be
like
hey.
Can
you
just
review
this
documentation
and
see
if
it
makes
sense
Etc
that
way,
I'm
just
not
working
in
isolation?
A
All
this,
as
it
just
has
another
method,
to
share
the
information
that
I
get
out
of
this
as
I
learn,
so
no
I'm
not
blocked
just
a
matter
of
time
and
effort.
At
this
point
perfect
thank.
B
You
very
much
I
think,
probably
like
maybe
next
next
week,
I
think
it's
gonna
be
a
good
point
to
start
to
discuss
to
take
a
bit
put
a
bit
of
scope
within
this
POC
that
we
want
to
do
as
part
of
the
okr
related
to
this
issue
right.
B
So
we
don't
have
to
do
anything
big,
but
at
least
it's
good
to
have
some
ideas
of
what
we
can
put
together
to
showcase
the
value
that
we
built
in
this
OCR
so
far
and
try
to
to
connect
the
dots
so
I'm
gonna
put
this
one,
probably
the
discussion
Point
already
for
next
week
already
today
after
this
call,
so
if
you
have
Food
For
Thoughts
feel
free
to
add
it
already
in
a
sync
way
and
we
can
discuss
it
further
next
week.
C
Good
morning,
everyone
and
good
afternoon.
C
I
wanted
to
showcase
the
fourth
cluster
part
of
the
cluster
reconstruction
of
G.
Staging.
It's
very
brief
demo,
but
I
wanted
to
touch
point
was
something
happening
right
now,
with
the
workloads
being
getting
deployed
at
the
moment.
Let
me
share
my
screen
and
please
let
me
know
when
you
can
see
it.
C
Let
me
get
the
fourth
cluster
you're,
still
a
little
pods.
As
you
can
see,
there
is
some
workloads
on
the
fourth
cluster
I
try
to
deploy
the
monitoring,
but
we
have
an
issue
happening
there,
which
is
Nixon.
Secrets
are
not
thinking
yet.
C
Basically,
we
have
vault
as
a
centralized
secret
measurement
and
the
end
point
that
we
talk
to
is
action
and
internal
endpoint.
So
basically,
the
same
thing
cannot
really
happening
at
the
moment,
I'm
in
talk
with
Philippi
and
basically
trying
to
get
around
this.
How
we
can
basically
log
into
to
it.
He
told
me
like
they
are
working
on
getting
it
out
of
the
prvpc,
so
they
can.
C
So
we
can
talk
to
this
endpoint
and
sing
the
secrets
and
then
can
have
these
pods
here
working
because
Prometheus
is
not
working
at
the
moment,
but
this
is
just
for
the
monitoring
part
I.
Think
I
can
basically
skip
this
and
continue
deploying
the
other
charts
until
this
is
fixed
and
yeah,
like
deployment
of
workloads,
is
basically
in
process
right
now,
hopefully
Yeah
by
end
of
this
week.
We
have,
we
are
in
like
in
a
good
spot
because,
like
we
have
multiple
repositories
to
deploy,
github.com,
GitHub
and
files
and
tanker
deployments
so.
A
C
Yeah
tanka
is
not
I,
didn't
work
with
it,
yet
so
I'm
gonna
start
with
stank
at
the
Province,
and
hopefully
it's
gonna
be
easy.
Let's
see.
B
I
have
one
question:
maybe
I
I
didn't
fully
understand
before
right.
When
so
is
the
Spring
World
outside
of
BBC
peering,
just
to
be
able
to
speak
into
it?
It's
going
to
be
like
a
long-term
solution
for
us,
or
it's
going
to
be
just
to
enable
you
to
deploy
that.
C
Actually,
the
thing
is:
this:
endpoint
is
accessible
through
gitlab
Runners,
the
Ops
runner
from
the
Ops
instance.
So,
if
we
actually
and
because
we
have
VPC
pairing
with
most
of
the
clusters,
including
this
cluster,
it
should
be
working,
but
it's
not
working.
Maybe
there's
some
viral
firewall
issues.
So
thank.
C
It's
new
VPC
pairing
is
working
on
it
because
we
set
it
up
by,
but
so
I'm
not
sure.
Yet,
if
it's
VPC
peering
issue
or
firewall
issue,
I
would
need
to
investigate
this.
But
Philippine
like
pointed
out
that
this
endpoint
is
actually
internal,
it
doesn't
work
from
anywhere
except
the
Ops
instance,
so
I'm
like
we
are
basically
investigating
this
to
see.
Actually
what's
what's
the
issue
there?
Okay,.
B
Somewhere,
so
I
guess
he's
is
totally
relevant
to
what
we
are
doing
right
now
in
this
investigation
Ahmad.
So
thank
you
for
that.
A
One
I
do
have
a
you
know.
This
is
a
premature
question,
but
I
thought
I
would
ask
it
anyways,
just
because
you've
been
primarily
primarily
working
on
this.
If
you
were
to
provide
a
confidence
level
for
how
much
effort
it
will
take
to
provide
us,
a
one-click
give
us
a
cluster
that
we
could
deploy
to.
We
don't
have
workloads
work,
yet
we
could
just
deploy
a
cluster.
C
Thanks
to
you
on
other
people
like
Philippians
here,
we
actually
fix
most
of
the
issues.
So
creating
a
new
cluster
is
a
matter
of
copy
paste,
the
module
to
create
this
cluster,
and
it's
going
to
be
there.
However,
it
depends
on
the
region,
because
I
believe
we
used
to
have
only
one
region-
U.S
east
one
before
and
having
a
new
region,
for
this
is
yeah.
Sometimes
it's
It's,
Tricky
but
I
believe
it's
doable.
It's
basically
just.
B
A
B
C
The
the
issue
we
have
with
the
regions
is,
we
have
hard-coded,
Vision
or
default
into
region,
U.S
Eastward.
We
have
this
as
default
for
in
most
of
the
I
believe
it's
not
just
one
place,
but
multiple
repositories,
as
I
talked
with
Felipe,
he
appear,
are
actually
responsible
for
refactoring,
terraform
modules
and
stuff
at
the
moment.
C
So
they
are
basically
working
on
such
things
to
make
it
that
we
are
not
bound
to
Just
One
Vision
I
mean
we
are
not
bound
to
actually
own
Vision,
but
some
modules
just
have
you
know,
defaulting
to
one
region,
but
for
now,
if
we
want
to
have
a
new
cluster
with
a
different
region,
it's
easy
because
we
fix
the
issu
as
I
said.
So
it's
just
like
it
depends
on
the
modules
we
are
going
to
use.
C
No,
there
is
a
thing
is
like
I,
as
I
said,
like
it's
done,
sort
of
to
create
a
new
cluster
yeah.
If
you
want
to
create
a
new
cluster
and
kubernetes,
you
can
create
it
in
whatever
Zone
you
want.
My
point
is:
maybe
I
don't
know
like,
because
I
tried
only
one
digit.
Maybe
we
can
test
with
a
different
G
and
a
different
place
to
see.
Actually,
if
there
is
there,
if
there
will
be
any
issues
or
not.
B
Okay
I
mean
let's,
let's
keep
it
for
as
extra
scope
of
them.
Let's
see
sure
how
much
time
we
have,
because
in
any
case,
we
probably
have
to
do
also
test
our
run
book
right
at
the
end
and
see
when
it's
gonna
work,
then
maybe
there
we
could
consider
to
test
that
runbook
in
a
different
region
and
see
if
we
surface
any
problem.
This
could
be
also
something
that
we
could
use
for
a
an
acceleration
or
the
work
you're
doing
right
now.
C
A
Another
thing
that
came
to
mind
that
we
should
be
considering
like
in
the
future
like
this
is
after
we've
got
our
own
book
and
probably
after
we've
tested
that
run
book
like
maybe
next
quarter,
probably
right
now
we
reserve
a
lot
of
static,
IP
addresses
via
terraform
and
those
end
up
getting
hard-coded
into
arcade's
workloads,
repository
and
probably
others.
I
would
imagine,
especially
for
the
Prometheus
and
Thanos
endpoints,
and
then
even
more
so
those
same
IP
addresses
end
up
getting
hard-coded
inside
of
our
AJ
proxy
configurations.
A
Like
I
know,
right
now,
our
Target
is
to
create
a
cluster
as
quickly
as
possible.
That
will
let
process
you
know
consider
for
the
upcoming
okrs,
how
we
could
make
one-click
cluster
and
deploy
all
the
things
to
it
and
allow
it
to
receive
traffic,
which
would
enforce
us
to
try
to
figure
out
what
to
automate
in
terms
of
getting
those
IP
addresses
shoving
them
into
proxy
appropriately,
as
well
as
the
case
workloads
configurations
too.
B
A
I
think
if
we
could
identify
how
to
quickly
build
clusters,
you
know
we
have
the
ability
to
enable
the
reliability
team
to
rebuild
things
as
quickly
as
they
desire,
because
we
already
know
there's
changes.
We
want
to
our
clusters
as
they
stand.
You
know
like
the
networking
is
not
well
defined
for
zonal
clusters.
For
example,
we
want
to
remove
Calico
and
replace
the
data
plane
B2,
which
requires
a
cluster
rebuild
and
there's
at
least
one
other
option.
A
I
forget
what
it
is,
but
it
also
requires
a
complete
reveal
of
the
cluster
that
I've
heard
talked
about.
You
know
having.
That
would
just
make
a
lot
of
things
easier.
Luckily,
like
as
long
as
we're
rebuilding
an
existing
cluster,
we
don't
need
to
touch
IP
addresses
because
they're
all
part
of
the
same
zone
region.
The
configuration
is
also
the
same,
but
if
we
want
to
expand
to
new
regions
and
such
stuff
like
this
would
be
a
lot
more
important
to
think
about.
A
The
only
thing
I've
got
is
something
we
could
say
for
not
being
recorded.
Okay,.