►
From YouTube: How to make your app cloud native
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
70
of
us
is
an
is,
are
an
engineer
we
tender
mostly
to
startups
and
scale
ups,
and
we've
been
in
web
hosting
for
about
20
years.
A
We
we
do
public,
private
clouds
and
azure,
and
also
hybrid
environments,
and
we've
been
doing
azure
and
kubernetes
since
2017.,
and
we've
gone
in
the
last
20
years
from
a
traditional
operations
company
to
a
devops
company
and
where
mavericks
is
hard,
then
of
course
you'll
immediately.
Think
of
top
gun,
we're
not
that
kind
of
maverick
we're
not
flying
any
any
f-16s
or
jets.
But
we
are
the
type
of
maverick
that
always
questions
your
direction.
A
My
name
is
marijan,
my
I'm
a
solutions
architect
at
true.
My
background
is
in
systems
engineering
and
I've
been
around
in
managed
hosting
since
2013..
B
Well,
thank
you
marine,
it's
very
nice
to
have
a
colleague
that
has
almost
the
same
name
and
it
has
a
lot
of
challenges
with
within
the
company,
but
I'm
with
diane
for
calgary,
I'm
working
at
true
since
april
this
year
and
within
my
role
as
solution
architect,
I'm
mainly
focusing
on
cloud
and
kubernetes
and
to
get
people
onboarding
on
that
platform.
So
today
I
want
to
give
you
some
insights
in
what
we're
doing
where
we're
talking
about
and
how
you
can
take
advantages
of
this
topic,
the
cloud
native
environment
and
services.
B
Let
me
get
the
quick,
the
clicker,
the
topics
today,
I
will
be
talking
about
our
definition
of
cloud
native.
We
have
to
set
a
definition
to
make
sure
everyone
has
is
talking
about
the
same
thing,
we're
going
to
tell
you
a
little
bit
of
what
that's
going
to
how
cloud
native
and
the
cloud
is
going
to
impact
your
application
and
the
advantages
it
can
bring
to
your
organization
and
your
application
as
well.
B
Last
but
not
least,
we
have
some.
We
will
tell
a
lot
of
kubernetes
and
we
will
mention
it
a
lot,
but
we're
going
to
tell
you
what
a
container
is
and
how
you
can
take
advantage
of
it.
And
if
you
need
to
go
to
kubernetes
or
not
we're
going
to
end
up
with
a
demonstration
in
which
we
will
show
you
some
workarounds,
how
you
can
work
with
containers
and
how
you
can
set
up
pipelining
for
them
to
get
some
really
nice
benefits
from
that.
B
B
Definitely
thank
you
cloud
native
and
it's
a
very
booming
topic
right
now
and
we
need
to
define
what
it
is
and
before
we
can
use
it
and
fill
it
in.
So
to
do
so.
I
want
to
start
with
the
definition
of
the
cloud
and
the
cloud
for
us
means
some
computational
units
you
usually
can
consume
as
a
service.
B
You
can
consume
those
by
api,
and
so
they
are
scalable
they're
more
than
two
servers
within
your
rack
within
your
data
center
and
if
you're
doing
it
right,
sometimes
you
don't
have
to
manage
the
hardware.
Sometimes
you
don't
have
to
manage
the
middleware
and
we'll
have
a
look
at
that
as
well
and
that
all
you
will
you
will
able
and
that
all
is
available
in
a
pay-as-you-go
model.
So
you
only
pay
for
the
usage
you're
doing
there.
B
So
I
talked
a
little
bit
about
services
and
the
cloud
products
and
you
can
consume
those
via
an
api
and
you
need
to
think
about
infrastructure
as
a
code.
You
can
also
think
about
platform
as
a
code
where
we
will
come
to
in
the
next
slide,
but
if
you're
going
to
consume
your
platform
via
infrastructure
as
a
code,
you
need
to
make
sure
that
you
are
aware
of
all
the
things
you
have
to
manage
your
own
virtual
machines.
You
have
to
patch
them,
you
have
to
update
them,
so
you
still
need
to
manage
a
lot.
B
B
The
next
stage
is
platform
as
a
service
which
you
can
consume,
and
the
platform
as
a
service
is
an
interesting
one,
because
it
has
a
very
wide
variety
of
services
you
can
consume
and
you
can
consume
kubernetes
as
a
service
or
you
can
consume
storage
as
a
service
and
both
come
in
different
versions,
but
you
have
complete
different
separations
of
concern
and
what
you
need
to
manage
and
what
they
are
managing
for.
B
You
so
make
sure
that
when
you
start
using
platform
as
a
service
within
your
organization
or
within
the
cloud
that
you
understand,
what
kind
where
you
are
responsible
for
the
fun
part
here
about
kubernetes
is
when
you're
using
kubernetes
as
a
platform
as
a
service,
you're
still
responsible
for
that
runtime
and
the
middleware,
because
you
need
to
store
them
to
build
them
within
your
container.
Without
that
and
if
you're
doing
that
in
a
nut
or
not
correct,
you
don't
get
the
benefits
of
that
platform
and
it
will
work
against
you.
B
B
Well,
service
products
are
created
around
it
and
where
we
saw
a
few
years
ago
that
you
will
only
you're
only
available
or
capable
of
storing
some
single
file
script
files
to
execute
them
to
do
some
input
and
you
get
some
output
from
it.
They're
evolving,
and
currently
you
see
that
they're
also
able
to
have
a
container
runtime.
So
they
support
your
own
container
and
that's
gonna,
and
that
has
create
enormous
services
around
it,
which
are
very
nice.
But
you
still
need
to
build
your
own
container
if
you
want
to
do
it
that
way.
B
B
B
Decoupling
all
the
services
within
your
application,
your
application
needs
to
be
as
stateless
as
possible
and
if
you
want
to
have
that
functionality
within
your
application,
you
want
to
extract
that
to
a
different
service.
So
you
see
that
all
the
components
within
your
application
you're
going
to
make
services
around
to
provide
to
that
application.
B
You
want
that
components
to
be
as
immutable
as
possible.
So
if
one
dies
or
crashes
it
can
spins
up
a
new
one.
Your
orchestrator
can
spin
up
new
ones,
and
that
really
is
one
of
the
benefits
of
the
cloud
where,
if
you're
doing
it
right,
your
container
might
be
killed
because
it
crashed
and
a
new
one
is
already
running
for
you.
You
haven't
even
noticed
the
downtime
there
and
to
achieve
that,
you
need
to
design
your
application
and
everything
around
that
for
automation
and
to
make
sure
that
it's
able
to
run
within
that
environment.
B
So
the
question
is
then,
where
to
start
and
probably
when
you're
starting,
there
will
be
some
kind
of
questions
and
you're
gonna
start
searching
for
the
right
tooling,
and
there
is
a
lot
of
tooling
currently
available
within
the
landscape
of
cncf
and
what
cncf
has
done.
They
have
created
the
landscape
of
all
the
available
toolings
right
now,
which
you
can
use
to
take
advantages
of
that
cloud
to
integrate
with
the
cloud
and
you
can
use
them
for
scaling
for
orchestrating,
etc.
B
Well,
we
usually
see
that
this
landscape
is
a
bit
overwhelming.
So
before
you
start
using
this
or
before
you,
when
you
look
at
this
for
the
first
time,
you
might
think.
Where
do
I
need
to
begin
and
that's
why
and
that's
why
the
cncf
also
created
the
trail
map.
The
trail
map
is
really
nice
when
you
want
to
say
make
a
first
step
within
the
cloud
native
landscape
and
it
starts
with
containerization.
B
You
shoot
containers
containerize
your
application,
and
I
will
come
back
to
that
in
the
next
two
slides.
When
you've
done
your
containerization,
you
need
to
set
up
proper
ci
ncd
for
that
application
to
make
sure
that
whatever
you
do,
whatever
new
commits
you
do
to
your
application.
Whatever
changes
you
do,
it
will
be
delivered
in
the
environment.
B
That's
your
confidence
to
go
to
such
environments
when
you're
done
with
that
you're,
probably
gonna,
look
at
an
orchestration
platform
so
how
you're
gonna
run
that
container
or
your
code
that
you've
built
with
it
and
from
there
if
you're
running
it,
you
want
to
observe
it
and
from
there
you're
going
to
go
to
step
5,
and
you
probably
want
to
have
a
service
proxy
or
a
service
mesh
to
manage
more
than
just
your
application
from
there
on
you're,
going
probably
to
networking
and
policies
like
kubernetes
itself
is
very
open
and
a
lot
of
cloud
providers
are
open
by
default.
B
So
you
need
to
set
some
rules
about
who's
going
to
talk
to
who
and
who's
allowed
to
consume
those
services,
you've
created
and
deployed.
So
you
want
to
create
some
policies
about
it
to
make
sure
that
it's
correct
and
updated
when
you
need
it
and
when
you've
done
that,
I
think
the
next
step
should
be
security,
but
that's
the
only
thing
I'm
missing
on
this
trail
map,
because
security
when
you're
going
to
the
cloud
or
you're
going
to
anywhere
with
your
software,
is
something
you
need
to
think
of
the
rest
of
these
steps.
B
So
7,
8,
9
and
10
are
a
bit
out
of
scope.
I
think
for
this
presentation-
and
I
don't
want
to
touch
them,
and
I
want
to
continue
with
the
advantage
of
containers.
We've
already
mentioned
it
a
lot,
but
packing
your
building.
Your
application,
packing
your
application
into
a
container,
really
gives
you
the
advantages
of
portability
where
you
can
build
one
container
and
run
it
anywhere.
B
So,
on
my
laptop
in
the
cloud
in
kubernetes,
two
internet
of
things,
devices
on
the
edge
or
even
functions
functions
as
I
mentioned,
so
you
have
a
consistent
operations
of
all
those
environments.
You
will
create
and
want
to
deploy
to
buy.
So
there's
you
can
benefit
of
scalability.
B
B
So
it's
quite
easy
to
take
those
advantages.
Last
but
not
least,
is
isolation
and
it's
possible
to
achieve
that.
As
you
see,
there
is
a
star
behind
it
and
that's
because
you
need
to
do
it
very
good.
You
need
to
think
of
how
you
can
isolate,
isolate
your
container,
because
by
default
your
container
will
be
running.
Probably
as
root
can
do
anything
can
connect
to
everything.
So
you
need
to
make
sure
that
your
container
is
isolated.
A
All
right
so
now
that
you've
talked
a
bit
about
the
advantages
of
using
containers.
Are
there
any
moments
that
you
would
advise
against
using
containers
or
maybe
even
advise
against
using
kubernetes.
B
C
B
Is
not
aware
of
the
underlying
infrastructure,
so
it
would
just
schedule
your
container
everywhere
on
that
platform.
So
if
you
have
a
hard
dependency
on
networking
or
maybe
storage,
you
might
think
twice
to
go
to
containers
or
to
go
to
kubernetes.
A
B
Definitely
you
can
move,
I
think,
almost
any
application
to
kubernetes.
I
think
that's
where
the
challenge
currently
is.
We
see
a
lot
of
people
adopting
it,
but
we
also
always
ask
questions
to
a
customer.
Do
you
really
need
to
run
on
kubernetes?
We
see
a
lot
of
function.
Providers
app
services
in
the
cloud
where
you
can
deploy
a
single
container
for
your
single
application
and
for
your
probably
a
single
wordpress
installation.
B
C
B
We'd
love
to
hear
from
you
and
to
get
some
interaction,
let's
see
if
we
can
switch
screens,
I
think
that
would
be
nice.
B
Cool,
so
in
this
demo
I'm
gonna
demonstrate
the
advantages.
Containers
can
bring
you
and
the
advantages
your
pipelining
when
you've
created
them,
can
give
you
as
well,
and
what
we're
going
to
focus
on
is
the
application
so
we're
going
to
make
an
application
we're
going
to
create
an
application
we're
going
to
build
it,
we're
going
to
push
it
first
to
a
registry
and
from
there
on
we're
gonna
use
it
to
create
an
environment
for
to
run
it
on.
B
So
what
we're
gonna
do
I've
prepared
a
few
things,
and
I
think
I'm
going
to
do
my
last
slide
first,
because,
when
we're
going
to
deliver
this
application,
what
we're
going
to
do
is
we're
going
to
use
the
registry
and
where
we've
pushed
the
charge
and
the
application.
B
And
we're
going
to
use
normally,
you
would
use
if
you're
moving
to
kubernetes.
You
would
start
with
some
github
methodology,
and
what
that
means
is
that
you
have
your
registry
of
your
application,
the
definition
of
your
application
living
within
the
git
repository
or
within
a
helm
registry
from
there
on
your
github
stooling,
and
in
this
case
that's
argo
cd
for
us
it
will
pull
continuously
for
changes
within
that
registry
or
that
repository.
B
So
on
the
other
side,
it
will
look
in
kubernetes
to
see
what
the
state
of
that
application
is,
what
you've
defined
in
git,
and
it
will
compare
those
contently
constantly.
So
when
that
application
is
out
of
sync,
so
I've
updated
my
applications
back
and
I
want
to
go
to
a
new
version.
Argo
cd
will
notice
that
will
prepare
a
deployment
and
if
I
want
it,
I
can
sync
that
automatically
to
my
environment.
B
The
advantages
of
of
this
and
of
all
those
tooling
is
that
you
can
integrate
them
with
your
own
workflow,
and
I
really
want
to
take
advantage
of
using
argo
and
today,
I'm
going
to
not
I'm
not
going
to
work
from
a
github's
perspective.
I
do,
however,
have
a
helm
repository
prepared
for
this
demo,
but
I'm
going
to
use
argo
to
dynamic,
generate
all
the
environments.
I
need
for
this
in
this
example.
B
B
B
C
B
B
Then
the
first
step
I've
showed
so
here.
Then
it's
mirroring
again
right.
B
Interesting
how
this
works
when
I've
pushed
it,
we've
completed
the
containerization
of
our
application
and
then
it's
living
inside
the
registry
from
there
on.
I
can
probably
trigger
argo
cd
to
update
my
application
or
to
create
the
environment
for
that
application
and
use
it
and
test
it.
If
that's
what
we
want.
B
B
Yeah
for
demo
purposes,
I'm
sharing
my
screen
way
too
often
yeah.
You
should
see
this.
So
what
I
have
is
the
automation
repository
here
and
I
have
a
very
small
script:
that
script
is
going
to
create
a
new
repository
and
populate
it
with
a
ci
cd
file,
which
only
includes
the
templates
I've
created
here.
B
Let's
see
if
that's
still
working,
create
a
project
name
and
I've
already
populated
this
one
with
we
are
going
to
the
cloud
because
that's
where
we
want
to
end
up
today,
I've
registered
a
domain
name
for
it.
I
want
to
use
it
and
the
helm
chart
I've
created
for
this
one
as
well,
and
the
version
of
my
home
chart.
B
B
Tools,
appearance
and
the
presentation
mode
there
we
are
so,
as
I
said,
the
script
I'm
running
what
it
does.
It
creates
the
gitlab
ci
yaml
and
the
pipelines
I
want
to
use
and
it
includes
the
projects
I've.
It
includes
the
scripts
I've
set
up
so
the
build.
I
want
to
build
that
docker
image
and
I
want
to
run
it
as
well.
B
B
B
Is
I've
set
up
a
default
branching
deployment
strategy
and
what
I'm
using
there?
What
I'm
doing
there
is
that
all
comments
that
are
pushed
to
the
main
branch,
so
in
this
case
it
should
be
master,
will
be
deployed
to
the
staging
environment.
We're
going
to
use
argo
cd
first
to
check
if
such
environment
already
exists.
So
if
the
application
is
configured
and
when
it's
not,
we
will
create
the
environment,
and
after
that
we
will
update
the
image
tag
to
make
sure
it
has
the
latest
version
of
what
we've
built.
B
B
Well,
that's
nice!
But
let's
see
if
it's
worked
and
if
I
go
to
argo
cd,
you
see
a
new
app
is
appearing
on
the
right
and
that's
that
we
are
going
to
the
cloud
staging
environment
and
there
you
can
see
that
the
helm
chart.
I've
specified
argo
cd,
well
kind
of
enlightens
you
what
the
resources
are
you're
going
to
deploy,
or
it
has
deployed
on
kubernetes
I've
automated
this
step.
So
everything
I'm
giving
argo
cd
will
be
deployed
directly
to
the
staging
environment.
B
B
So
what
we've
done
is
we
have
created
a
repository
and
from
there
on
your
pipelining
is
direct
in
place.
You
have
a
docker
file
which
you
can
extend
to
other
well
needings
for
applications
and
from
there
on
your
pipelining
is
in
place
to
not
only
deliver
it,
but
eventually
we
can
extend
it
to
testing
as
well,
because
when
we've
built
a
container,
you
definitely
want
to
test
it.
On
recent
vulnerabilities.
A
B
That's
nice:
we
have
this
application
and
I
think,
from
here
on,
we
do
want
to
have
well
something
more
than
just
this
landings
page
and
what
you
normally
would
do
in
in
a
company.
If
you
have
this
environment
and
you
want
to
iterate
for
a
new
version,
you
probably
will
check
out
the
new
branch
based
on
this
current
version
and
from
there
on
start
changing
your
code
of
that
application.
B
The
challenge
you
most
of
the
time
have
is
that
you
want
to
create
a
temporary
environment
to
check
out
the
changes
you're
having
and
you've
done.
So
what
we're
going
to
do
is
I've
set
up
a
different
piece
of
pipelining
of
templating,
which
allows
me
to
create
environments
based
on
feature
well
name
spacing.
B
So
each
branch
that
I
commit
to
a
feature
branch
will
be
delivered
in
a
new
environment.
New
environments
will
be
created.
So
what
we're
going
to
do?
I
have
a
demo
application,
or
at
least
a
demo
landing
landing
space,
which
is
a
little
bit
better
than
this
one,
and
what
I'm
gonna
do
is
I'm
gonna,
deploy
it
in
four
different
feature
branches,
and
then
you
can
vote
on
which
of
those
feature
branches.
We
will
eventually
push
first
to
the
acceptance
environment
when
we
merge
it
and
after
that
we
will
take
it
for
production.
B
B
So
we
have
the:
where
do
we
are
going
to
the
cloud
repository
over
here?
I
have
to
admit
I
did
some
work
before
so
what
I'm
going
to
do
is
I'm
going
to
copy
my
it's
dot
damp
and
from
here
I
have
the
red
to
hd.
B
Index.Html,
so
if
I
now
performing
a
git
div,
you
can
see
there
is
a
lot
of
stuff
changed.
I'm
going
to
check
out
a
feature
branch,
let's
see
which
color
I
had.
I
had
the
red
one.
So
I'm
going
to
hit
checkout.
C
B
For
the
yellow
one,
so
what
I'm
gonna
do
here?
I
currently
get
status,
don't
have
any
changes,
because
I've
already
commit
everything.
I'm
gonna
use
the
same
copy
command.
B
So
what
we've
done
we
have
within
the
we
are
going
to
the
cloud
repository.
We
have
created
branches,
so
two
branches
and
you
see
that
automatically
the
pipelines
are
running
for
that
for
those
branches.
So
you
see
here,
I
have
two
new
pipelines,
two
feature
pipelines,
one
is
already
finished,
the
red
one
and
the
other
one.
The
yellow
is
currently
still
running.
B
If
I
go
back
to
argo
cd,
you
see
there
is
a
new
environment
created
new
application
created
which
is
based
on
that
branching
model.
So,
if
I'm
going
to,
if
I'm
clicking
on
that
and
when
you
see
the
application,
apparently
it's
still
waiting
for
the
ssl
certificates,
but
it's
not
there.
It
is.
We
have
a
red
version
of
our
landings
page.
I
would
say
it's
a
great
success
from
here,
but
we're
not
there,
because
we've
also
deployed
the
yellow
one
and
that
one
should
be
ready
in
a
few
seconds
as
well.
C
A
It's
almost
working
on
my
end,
I'm
I'm
still
getting
a
a
certificate
warning,
so
I
think
you
might
have.
B
B
You
mean
the
the
domains
to
to
visit
the
website,
so
I've
prefixed
the
branching
name
within
the
domain
name.
So
if
you
go,
if
you
have
the
main
domain
name
and
we
are
going
to
the
cloud
if
you
prefix
that
domain
name
with
the
subdomain
as
feature
red,
you
should
be
able
to
visit
that
one
so
feature
mine
is
red.
Let's
I
can
only
zoom
in
my.
B
I
cannot
zoom
in
my
in
your.
B
B
B
A
Thankfully,
the
branch
names
speak
for
themselves,
yep.
B
I
hope
so
so
these
pipelines
are
being
created
and
you
can
already
have
a
look
and
what
we
want
to
have
is
to
have
your
vote.
Marijuana
is
gonna
open
the
poll
to
see
which
color
the
red
one,
the
blue
one,
the
yellow
one
or
the
purple
one.
We
are
going
to
merge
into
the
main
range,
so
the
main
branch.
A
I
have
opened
the
poll,
there
should
be
a
poll
and
you
should
be
able
to
choose
which
color
you
like
most
and
that's
what
we're
gonna
deploy
eventually
to
production,
for
we
are
going
to
the
cloud
and
while
we
wait
for
that,
so
you've
been
showing
how
you've
basically
created
feature
branches
based
on
on
on
copy-pasted
html
files.
C
B
Yeah,
you
can
do
this
with
anything,
and
this
is
now
a
basic
static,
html
file,
but
I
can
also
change
this
container
to
a
php
container
and
run
my
php
application.
So
my
laravel
back
and
or
a
symphony
back
end
or
maybe
even
a
wordpress
backend.
I
can
use
this
same.
Pipelining
methods
would
have
created
for
all
those
applications.
A
B
B
I
do
kind
of
use
the
feature
as
well,
but
switch
oh
switch
to
php
and,
let's
see
if
we
can
create
a
php
container
in
which
we're
going
to
do
from
php
and
what's
currently
the
latest
version
8.01,
I
think
so,
and
what
we're
going
to
do
here
is
a
gonna
do
a
little
bit
of
magic
here,
and
I
advise
you
to
not
do
this
in
your
production
environment
as
well,
but
for
the
sake
of
this
demo,
let's
use
this
expose
port
80
and
I'm
gonna
use
as
command
php.
B
B
Going
to
find
out
for
sure
yes,
that's
what
I
expected
I'm
going
to
commit
my
changes
into
my
feature:
branch
and
switch
to
a
php
backend,
and
if
I'm
pushing
this
change,
I
first
need
to
make
sure
I
insert
my
password
and
then
within
here
gitlab.
You
should
see
a
new
pipeline
for
that
feature:
branch.
We're
going
to
wait
on
that.
A
I'm
not
actually
sure
I'm
seeing
that
the
poll
is
running,
I'm
not
quite
sure
if
someone
behind
the
screens
can
see
whether
we
have
results
in
already.
B
A
Results
so
I
think
we
we're
eager
for
the
answer,
so
I'm
going
to
end
the
poll
and
I'm
hoping
hoping
that
it
will
then
do
something.
But
of
course
this
is
live
and
I
don't
get
to
click
anywhere.
B
I
don't
have
to
export
thee,
but
I
need
to
expose
this
one
for
sure
hit
commit
and
I'm
gonna
change
that
one
in
fix.
A
A
While
I
end
the
poll,
we
see
that
25
went
for
blue
and
this
is
wonderful
because
I
ended
the
poll
and
now
it
disappeared.
But
I
think
everybody
overwhelmingly
chose
red.
A
There
was
an
overwhelming
there's,
a
50
red
there's,
25,
blue
and
25
purple.
Somehow
nobody
went
for
yellow.
B
So
that's
cool,
so
I
think
we
should
merge
the
red
branch
into
the
main
branch,
the
main
branch
cool.
Let's
do
that
I
don't
have
any
merge
requests
yet
so
I'm
gonna
create
a
new
merge
request
and
I
want
to
merge
I'm
in
the
correct
branch.
No,
I
want
to
change
branches
and
I
want
to
merge
the
feature
red
into
master
to
compare
it,
and
I
should
see
the
changes
here
that
have
been
done.
B
A
I
had
some
questions:
yeah
I'll
start,
the
at
the
top.
We
had
tim
ask
us
hi
guys.
Can
you
tell
me
what
the
difference
is
between
app
cloudification
and
app
modernization.
B
That's
a
very
good
question:
I'm
not
very
familiar
with
the
app
modernization
and
app
cloudification
terms.
Do
you
have
any
context
about
that.
A
I
think
that
if
you
you
modernize,
your
application
is
usually
a
play.
Where
you
take
your
application
and
you
change.
You
really
change
it
to
work
in
a
cloud
native
or
in
a
modern
ecosystem,
whereas
I
think
that
cloud
app
cloudification
would
refer
more
to
taking
your
application
and
is
basically
running
it
in
the
cloud.
So.
A
A
B
I
think
it
really
depends
on
your
application
and
what
we
tend
to
see
sometimes
is
like
the
legacy
applications
that
people
are
not
sure.
What's
inside,
that
you
can
try
to
containerize
it
and
to
make
or
to
see
if
you
can
run
it
on
that
machine
within
that
container
as
well.
But
you
need
to
make
sure
that
stuff
is
configurable,
so
if
you're
going
to
lift
it
to
another
platform
that
you
can
configure
the
endpoints
etc.
B
A
Yeah,
so
there's
the
I
think,
another
thing:
when
should
you
not
do
it?
I
think
you
need
to
realize
that
you
have
to
go
into
it
for
the
right
reasons.
So,
if
your
reason
to
go
to
the
cloud
is
because
somebody
once
heard
that
it's
the
next
thing-
that's
not
gonna,
that's
not
maybe
gonna
bring
you
the
results,
maybe
think
about
what
you
want
from
your
app
modernization,
what
the
desired
outcomes
are
and
work
from
there
and
another
one
that
you
need
to
realize.
A
That
is
this,
depending
on
your
application,
size,
of
course,
for
a
simple
html
landing
page.
It's
it's
a
relatively
small
project,
but.
A
Anything
that's
of
any
size
running
in
production.
I
think
really
think
about
how
much
time
this
is
going
to
take
you
yeah.
B
B
We're
back.
I
think
at
the
staging
environment,
we've
merged
the
red
branch
into
the
staging
environment
and
you've
probably
already
updated
your
application,
but
let's
see
or
your
your
application,
yeah
your
environment.
But
let's
see
what
happens
when
I
refresh
my
page
and
there
it
is
well,
that's
pretty
easy,
I
would
say
so.
The
rest
one
is
on
staging,
and
now
we
have
to
do
one
thing
and
I've
chosen
for
this
one
before
I
go
to
production,
to
only
do
that
with
tagged
comments.
B
B
There
is
one
catch
after
the
refactor.
I
did
not
test
it,
so
we
will
see
if
it's
still
working
I'm
going
to
the
comments.
B
This
is
my
last
commit
immerse
the
branch
and
I'm
going
to
attack
this
one
and,
let's
start
with
version
2
print
zero,
because
I
like
that
and
from
there
on,
we
should
see
some
new
pipelines
being
created
and
before
that's
running,
let's
see
that
we
are
going
to
the
cloud
doesn't
have
a
back
end
yet
so
it's
all
live.
Every
nothing
has
been
configured
in
advance.
B
Ooh,
that's
a
very
specific
question.
Don't
you
think
super
specific,
I'm
very
curious
about
the
context
as
well,
but
we
what
we
see
is
when
people
are
moving
to
the
clouds
my
pipeline
is
failing.
I
will
dive
into
that
one
after
this
question,
but
when
people
lift
and
shift
their
stuff
to
the
cloud,
the
cloud
environment
is
tend
to
be
different
than
well
your
local
environment.
So
where
your
server
is
standing,
probably
close
to
the
database
in
a
cloud
environment
yeah
we
we
cannot
guarantee
that
it's
so
close
to
each
other
and
those
delays.
A
I
I
completely
agree,
and
I
think
to
add
to
it.
What
you
see
often
is:
if
you
have
a
single
instance
running
both
your
application
and
your
database
you're
introducing
a
network
so
you're
introducing
latency
between
the
two.
A
So
maybe
the
network
is
just
slow
for
a
little
bit
or
there
might
be
a
little
congestion
somewhere
on
a
switch,
and
you
should
really
make
sure
that
your
database
connection,
your
application,
is
ready
to
really
deal
with
that
sort
of
transient
error
and
also
detect
whether
this
is
something
that
you
maybe
need
to
retry
once
or
twice
but
never
forever,
or
that
you
should
just
give
up,
because
things
are
really
really
down,
and
I
think
the
better
that
you
do
this,
the
better
that
you're
going
to
be
able
to
leverage
a
cloud
environment.
B
B
Is
the
error
message?
I
expect
it's
still
the
same
error,
so
I'm
not
sure
if
it's
it
will
retrieve
the
new,
updated
version
of
this
template.
So
that's
a
challenge.
I'm
gonna
re-tag
it
to
at
least
make
sure
that
I'm
starting
a
new
pipeline
and
that
I
will
retrieve
the
new
version
of
the
templates.
I've
created
all
right
and
I
have
to
go
to
commits.
B
A
B
B
We
have
it
hey,
and
this
is
very
nice,
it's
out
of
sync
and
it's
not
deployed,
and
how
does
that
come
because
I've
disabled
automatic
deployment
to
production
I
want
to
have
that
manual
trigger,
and
that
really
is
one
of
the
advantages
of
using
argo
cd
in
this
use
case.
So,
if
I'm
going
to
roll
this
to
production,
I
first
can
check
the
version.
That's
there
and
from
there
I'm
gonna
synchronize
it
to
the
environment.
B
B
A
B
I
haven't
helped
yet
it's
a
very
easy
one.
I
do
not
want
to
go
in
detail
about
that
one,
but
it
exists
of
a
deployment
which
is
a
very
small
definition
about
container,
and
I
want
to
run
on
this
environment.
It
has
a
surface
because
I
want
to
expose
that
container
and
a
piece
of
ingress
in
which
I
have
set
up
some
tls
for
that,
so
it
will
obtain
an
automatically
generated
certificate
for
that
environment.
B
We
do
had
one
more
environment
running
and
let's
see
if
I
can
open
it,
because
we
have
created
the
php
branch.
Do
you
remember,
let's
see
what
happens
when
I
open
it,
ta-da
that's
nice,
so
we
did
a
php
version.
Well,
more
of
a
dump
of
all
the
configuration
and
there
you
can
see
that
we've
successfully
deployed
this
yeah.
Well,
this
php
container.
A
All
right,
so
it's
super
cool
that
this
works,
and
this
also
shows
you
the
flexibility
right
of
this
whole
process.
So
you
could
just
take
your
own
application.
I
mean,
if
you,
if
it
takes
this
little
time
to
even
change
coding.
Language
well,
is
html
really
a
language.
A
Takes
you
this
little
time
to
to
really
remodel
your
app
in
such
a
way
and
just
see
it
running
in
a
place
where
you
can
see
it
where
maybe
your
clients
can
see
it
and
approve
of
it?
Yeah.
A
Like
a
really
powerful
way
of
developing
to
me
at
least,
I
have
one
more
follow-up
question
from
paco
and
his
question
is
so
if
you
were
to
to
move
this
legacy
application
to
the
cloud
with
millions
of
records
being
dealt
with
from
both
database
and
flat
files
in
the
cloud,
what
would
be
the
best
practices
and
his
question
specifically
is?
Would
you
remodel
the
process,
so
it
does
not
deal
with
more
than
a
million
records.
A
The
question
so
the
the
question
is
really,
if
you're
moving
your
application
to
the
cloud
and
you're
dealing
with
millions
of
of
records
being
dealt
with.
A
B
A
Have
been
there
for
questions
about
this
by
the
way
paco
feel
free
to
contact
us
yeah.
Definitely
because
I
think
we
need
a
little
bit
more
context
for
for
this
sort
of
a
situation,
but
I
think
there's
some
general
stuff.
You
can
say
about
this.
B
Yeah,
can
you
is
it
allowed
to
have
downtime
for
your
application?
Can
we
just
pick
it
up,
shut
it
down
and
transfer
it
to
the
cloud,
or
is
that
not
possible?
That
are
basically
the
first
question
to
ask
and
if
it's
not,
then
we
need
to
probably
design
something
around
it
that
maybe
you
can.
B
You
can
distribute
specific
resources
to
specific
endpoints,
so
you
start
using
the
cloud
and
you
slowly
kind
of
fill
that
one
up
with
your
new
resources.
So
you
have
a
very
smooth
transition.
If
that's
not
possible,
we
should
probably
think
of
some
other.
A
Methods
exactly
yeah
and
I
think
another
one
I
mean
you're
talking
about
a
batch
process.
So
the
biggest
question
is:
what
is
your
application
doing
here
and
is
this
maybe
an
etl
process
that
you're
running
there
are
strategies
to
deal
with
this
one
could
be
using
a
message:
queue
to
split
up
this
work
into
different
applications,
or
so
this
is
super
application
specific.
A
But
if
you
want
to
get
started
on
looking
at
how
you
might
use
this
strategy,
other
than
contacting
us
obviously
or
a
party
like
us-
is
that
you
could
go
and
have
a
look
at
12factor.net
and
they
will
have
some
guidelines
on
how
to
deal
with
with
with
these
kinds
of
operations,
and
it
might
give
you
some
inspiration
to
to
rework
your
application
to
to
live
in
a
cloud
context
really.
C
B
So
I'm
not
sure
if
you
were
able
to
see
my
screen
while
I
was
doing
some
magic
stuff
for
most
of
the
people
that
well
watching
I've
created
the
new
repository
in
the
same
way,
I've
set
it
up
the
first
one
and
I've
give
that
the
name
of
myself
so
martin
van
gaal
and
I've
configured
that
with
the
domain
name
of
martial
calgar
printer,
now
it's
pointing
to
the
same
server
and
it
will
make
sure
that
over
a
few
minutes
a
future
environment
or
at
least
a
staging
environment
will
be
populated
with
a
coming
soon
welcome
message.
B
So
if
you
want
to
have
a
look
at
that
check
it
out,
and
I
think
for
now
we're
well,
it
should
be
deployed.
I
see,
but
that's
for
someone
else
and
later
on,
yeah
cool.
I
think
we're
currently
at
the
end
of
our.