►
From YouTube: Discuss HAProxy downtime requirement
Description
A short discussion about alternatives that we have for site downtime for the HAProxy upgrade.
Notes (internal): https://docs.google.com/document/d/1v6kheVYq1ap4Xq6Kmnj0uKRelGTq5s-mRHZHGos7KLQ/edit#heading=h.dhp4sslmd35r
A
I
have
the
first
item,
which
is
to
just
try
to
get
a
sense
of
why
we
need
to
have
a
downtime
event
for
the
AHA
proxy
upgrade
I
read
through
a
little
bit
of
the
background
here,
and
it
seems
to
me
that
we
need
to
change
the
node
pool
for
the
new
nodes
and
doing
that
is
like
a
destructive
event.
Does
that
sound
right,
yeah.
B
Anything
I'm
missing
there,
yeah
so
in
the
in
the
Epic
upgrade,
and
the
Epic
update
that
you
linked
the
Assumption
was
that
we
just
needed
to
replace
the
node
pools.
However,
in
the
Mr
that
you
linked,
I
came
to
the
realization
that
basically,
that
rep,
that
also
forces
the
replacement
of
the
of
the
internal
lb
for.
A
B
General
Internal
lb,
which
means
that
we
cannot
guarantee
that
the
IPS
cannot
stay
the
same.
So
we're
not
talking
about
something
that
might
disrupt
might
be
disrupted
for
like
a
fraction
of
a
second
while
the
node
pool
is
switched
over,
but
something
that
potentially
carries
well
the
MS
caching
playing
into
the
whole
situation,
which
is
why
it's
probably
a
more
delicate
change
than
I.
First
anticipated.
B
A
Okay,
so
we're
not
using
a
reserved
IP
right
now,
no
I
see
that's
what
I
can
tell
so
we're
not
using
a
static,
IP,
I
wasn't
I,
wasn't
sure
and
honestly
like
this
was
Point
number
three
like
I
I,
don't
think,
there's
anything
that
depends
on
the
IP
for
the
internal
bouncer.
Are
you
aware
of
anything
yeah.
B
A
B
A
B
A
B
A
A
B
A
A
I'm,
just
wondering
like
I'm,
just
wondering
whether
There's
an
opportunity
here
to
one
is
like.
If
we
don't
set
a
static
IP
for
the
internal
IPS
we
could
we
could
do
that.
We
could
fix
the
module
or
even
like
I
I,
don't
know
how
much
Croft
is
in
that
module
that
we
use
for
the
internal
LPS,
but
maybe
there's
an
opportunity.
We
can
clean
that
up
a
bit
just
provision
new
internal
lbs
with
a
new
DNS
and
then
and
now
we
have
them
both
running
in
parallel
right.
A
Internal
lbs,
new
internal
lbs
are
pointing
to
the
new
AJ
proxy
Fleet
old
internal
LPS
are
put
into
the
old
age
of
proxy
Fleet
and
then
and
then
we
just
move
the
DNS
over
I
mean
you're
right.
We
need
to
identify
everywhere.
We
connect
to
the
internal
lbs
and
change
that
configuration,
but
I
think
it's
not
going
to
be
too
too
bad,
like
I
I.
Think
it's
only
in
three
or
four
places
for
the
CI
stuff.
There
is
the
option.
The
CI
stuff
was
only
done
to
save
money.
A
A
B
A
A
A
B
I
think
because
there's
like
when
I
when
I
looked
into
the
terraform
stuff,
there
was
a
lot
of
you
know,
policies
and
also
configuring,
the
CI
environments
and
that
kind
of
stuff.
So
that's
probably
if
we
can
just
turn
off
CI,
you
know
the
CIA
proxy
usage
while
we're
doing
the
migration
and
then
turning
it
back
back
on
again
afterwards,
that's
probably
the
easiest
way
to
deal
with
CI.
A
A
A
This
configuration
it's
pretty
opaque,
I
think
to
sres
like
how
that's
configured
I'm,
not
sure
I,
even
remember
like
all
the
details,
so
that
maybe
we
could
check
the
Run
books
and
you
know,
get
that
stuff,
updated
and,
and
that
was
kind
of
serious
half
serious,
at
least
about
like.
If
this
internal
lb
terraform
module
is
really
bad,
we
could
maybe
fix
it
in
a
way
that
it's
nicer,
I,
don't
know.