►
From YouTube: Configure stage basics part 2
Description
Intro to Configure stage and gitlab by Orchestration PM
A
Well,
so
yeah,
what
I
was
going
to
say
is
that
with
a
kubernetes
integration,
you
have
to
concern
yourself
with
writing
how
you're
going
to
build
and
deploy
your
software.
So
your
strategies,
for
example
the
environments
where
you're
going
to
deploy
to
you're
gonna,
have
Bluegreen
deployments
or
canary
or
all
that
stuff,
that's
all
manual
with
kubernetes
integration,
so
kubernetes
integration
still
making
use
of
catalepsy
I.
A
Now,
if
you
use
Auto
DevOps,
we
automate
some
of
that
for
you.
The
reality
is
that
Auto
DevOps
covers
only
a
minut
number
of
use
cases.
For
example,
if
you
have
dotnet
app,
a
lot
of
DevOps
may
not
be
an
ideal
way
for
you
to
deploy.
So
you
still
have
to
write
everything
manually,
even
if
you're
the
plaintiff
kubernetes.
You
can
use
a
lot
of
the
templates
that
we
have
inaudible
ups
and
that's
what
a
lot
of
people
do
is.
A
If
you
caught
the
chat
from
the
nasa
person,
he
said
like,
we
took
a
lot
of
inspirations
from
auto
devops
to
like
model
all
of
this
modern
DevOps
workflows.
So
that's
a
big
part
of
the
value
of
Auto
DevOps
that
it
serves
as
a
template
for
you
to
know
what
modern
DevOps
practices
looks
like
so,
but
you
still
have
to
do
a
lot
of
manual
work
now.
A
The
difference
with
serverless
big
difference
is
that
developers
don't
have
to
focus
on
on
the
infrastructure
that
they're
deploying
to
so
that
is
you
don't
have
to
concern
yourself
with
a
kubernetes
cluster.
You
don't
have
to
create
one.
You
don't
have
to
well.
I
mean
it
depends
right,
like
a
native
like
somebody's
going
to
provide
you
with
the
space
to
deploy
to
probably
an
operator
within
your
company,
but
a
lot
of
the
times
developers
don't
have
to
think
about
that
and
with
AWS
lambda
is
the
same
thing.
A
So
developers
can
only
focus
on
writing
the
code
for
their
functions
and
server
lists
will
just
make
them
work,
so
we're
doing
that
in
a
couple
of
different
ways,
but
the
main
way
they
were
doing
it
in
server
list
is
that
we
have
templates
for
both
your
collab
CIT
MO
and
your
server
with
CMO.
So
the
purrs
focus
on
writing
the
code
for
their
functions
and
the
rest
kind
of
just
happens
with
kubernetes
integration.
You
have
to
know
a
lot
about
kubernetes
to
just
make
a
simple
deployment
and
kubernetes
can
be
quite
complex.
A
A
That's
that
that
has
been
the
case
over
and
over
in
the
world
of
technologies
is
there's
this
new
wave
and
we
have
to
focus
a
lot
of
resources
on
learning
and
stuff
like
that,
and
then
tomorrow
it's
gone
and
it's
something
new
like
that
happened
with
docker
and
cloud
native
containerization.
It's
all
like
this.
It
has
a
lot
of
value,
but
yeah,
so
developers
want
to
focus
on
app
dabomb.
A
So
that's
kind
of
the
main
difference
in
my
mind,
of
course,
there's
a
lot
of
nuance
and
a
lot
of
small
details
that
have
to
do
with
a
lot
of
other
things,
but
at
a
high
level
it's
that
that
serverless
focuses
less
on
infrastructure
and
see
icd
not
know
writing
your
CI
done
ya,
know
stuff
like
that.
Okay,.
B
Have
to
discover
on
my
own
that's
what
I
want
to
say,
but
I
feel
a
bit
unclear
on
the
hierarchy
and
variations.
So
we
have
groups-
and
you
have
told
me
that
groups
do
not
have
deployments
or
Oratory
told
me.
There
are
no
repositories
within
groups,
but
groups
are
a
separate
thing.
Then
you
have
projects
and
within
projects
repositories.
B
So,
for
example,
I
was
reading
the
issue
that
we're
gonna
be
working
on
that
when
you
enable
kubernetes,
then
a
new
repository
is
created.
So
I
was
thinking.
Okay,
there
is
a
new
repository,
but
what's
in
this
repository,
where
does
your
application
code
live?
How
does
it
link
to
this
repository?
How
does
a
cluster
know
like
how
all
these
things
connected
so
I
think
I
will
need
to
start
reading
and
start
making
a
diagram
on
my
own,
because
that
particular.
A
Issue
is
little
complex,
you're,
right
and
but
I
guess
it's
worth
talking
about
it.
So
hierarchy
when
it
comes
to
anything,
is
that
you
have
a
good
lab
instance
at
the
top,
and
you
have
settings
on
that
instance
that
affect
everything
that
live
under
it.
So
like
Auto
DevOps
is
one
of
those
settings
yeah.
Maybe
if
I
show
you
you,
you
want
me
to
show
you
as
I
talk
through
this,
or
would
you
rather
just
talk.
A
So
this
is
an
instance,
and
here
all
the
instance,
level
settings
are
in
this
admin
area.
So
if
I
click
on
this
admin
area
and
I
go
into
settings
like
see
ICD
here
for
for,
for
example,
you
see
the
check
mark
for
auto
devops.
If
this
is
check,
it
affects
every
group.
Every
project
like
everything
under
the
Sun
of
this
good
lab
instance.
Alright.
So
that
is
all
of
the
settings
here
is
kind
of
there,
mainly
the
same
anything
that
you
said
at
the
instance
level
will
affect
all
of
good
life
and
a.
A
You
can
I
mean
it's
dumb
to
do
that
and
not
advised
by
us
what
a
lot
of
people
do
it.
It's
like
good
luck
is
so
easy
to
get
started
with
that.
Let's
say
if
you
work
at
a
company
that
is
using
JIRA
and
each
team
like
they
are
using
Jenkins
and
they're,
using
like
all
this
disparate
CI
tools
and
there's
a
new
person
that
comes
in
and
knows
that
good
lab
is
better
and
knows
how
to
use
it.
A
They'll
stand
up
an
instance
and
show
their
team
how
to
work
on
it
and
then
they'll
put
all
of
their
work
there.
But
there
are
other
teams
that
are
using
Jenkins
and
stuff
like
that,
and
then
the
same
thing
happens
in
a
different
department
within
the
same
company.
Now
you
have
two
instances,
and
so
that
happens
a
lot
in
the
sales
cycle
when
they
approach
us
and
they
want
to
buy
like
a
higher
license
other
than
free
and
one
of
the
problems
they
have
seen.
A
B
A
Right
you
uncheck
this
and
then
you
manually
add
CI
CD
to
each
one
of
the
projects.
So
that's
the
highest
level,
which
is
the
instance
now
then
you
have
groups
and
groups
are
nest
of
all.
So
you
can
have
within
a
group.
You
can
have
a
subgroup
and
within
that
subgroup
you
can
have
another
subgroup
and
you
can
nest
this
like
as
many
times
as
you
want.
I,
don't
know,
I've,
never
tested
how
many
levels
you
can
go
deep,
but
so
groups
can
have
subgroups
and
then
at
all
levels
you
can
have
projects.
A
So
let's
say
at
this
top
level:
I
have
group
zero.
One
I
can
attach
projects
to
group
zero,
one
or
I
can
have
a
subgroup
within
group
zero
one-
and
this
is
what
we
do
at
gate
lab
so
get
lab.
Has
so
many
things
going
that
our
group
is
called,
get
lab
org,
and
this
is
the
entire
company.
This
is
good
lab.
Oh.
A
Is
a
group
yeah
or
abroad
again
the
instance
is
good,
lab
calm
and
get
lab.
Comm
is
used
not
only
by
CAD
lab
it's
used
by
the
world,
so
we
have
a
group
within
get
lab
calm
and
our
group
is
called
cute,
lab
org
and
that's
the
organization
of
kid
lab
and
that's
every
project
that
that
you
can
think
of
is
here
so
like
our
our
most
famous
ones
are
get
lap
the
product,
but
you
can
also
see
what
groups
are
here.
Are
the
website
like
WWE
is
the
website
marketing?
A
B
A
That's
one
thing:
yeah,
that's
one
thing:
so:
teams
like
the
marketing
team
will
have
their
own
group
and
within
that
group
they'll
have
projects.
Here
you
see
the
serverless
team
has.
This
is
a
sub
group
and
within
that
sub
group
there
are
projects.
So
there
is
the
example
project
and
the
run
times
project,
but
the
server
list
is
a
sub
group.
Our.
A
Yeah
so
get
lab.
Dot-Org
has
many
projects,
most
famous
ones
are
get
lap,
so
you
that
is
the
get
lab
where
it's
good
left.
So
good
lab
is
the
product,
so
this
subgroup
called
get
lap
his
liquid
lab
product.
What
do
you
install,
and
so
this
is
the
good
lap
product
there's
another
very
popular
project
here
which
is
WWE
lab
comm?
This
is
the
website.
A
So
here
you
can
just
start
typing
and
it'll
show
you
oh
yeah
right,
oh,
so
this
website
is
not
under
the
kid
lab
or
group.
It's
on
there.
Good,
lab,
comm,
home
I
think
that
that's
all
the
assets
for
the
web
yeah.
So
this
is
the
website,
but
it's
in
there
a
different
group.
So
maybe
that
was
not
a
great
a
great
example,
but
yeah
that's
basically
as
G
as
you
can
see
that
let
me
see
what's
here,
okay,
see,
this
is
more
like
port
internal
stuff.
A
A
A
Correct,
that's
the
right
hierarchy.
So
going
back
to
my
example.
Sorry
this
one
so
I
have
a
group.
This
is
Group
one
and
within
group
one
I
can
have
a
project
or
another
sub
sub
group.
So
this
group
has
settings
and
I
can
attach
things
like
a
kubernetes
cluster
to
the
group,
and
then
every
project
under
the
group
could
make
use
of
the
cluster
and
a
lot
of
people
do
it
this
way.
A
So
let's
say
if
your
company
has
a
hundred
projects,
it's
like
a
lot
of
work
to
provision
hundred
clusters
for
people
to
use,
or
you
just
provision
one
cluster
at
the
group
level
and
it's
available
for
100
projects
to
use,
so
they
want
to
deploy
their
stuff
into
that
their
cluster
they
can,
or
you
can
also
attach
a
cluster
at
the
instance
level.
So
if
you
have
a
thousand
groups,
then
it's
basically
available
to
all
of
the
groups
and
projects
with
it
back
within
that
instance
of
good
lab.
A
Now,
there's
no
one's
there,
because
there's
some
security
settings
that
you
can
set.
So
you
know
some
people
may
not
have
access
to
it,
but
that's
the
gist.
You
said
it
at
the
instance
level
it's
available
to
every
you
know
to
everyone.
You
said
it
at
the
group
level.
Then
it's
available
for
all
the
projects
on
there
that
and
same
with
the
settings
so
just
like
I
showed
you
that
setting
for
our
DevOps
at
the
instance
level.
So
let's
say
your
administrator
turned
off
auto
dev
ops
for
the
instance,
but
you
say
hey.
A
B
A
Know
so,
groups
can
represent
many
things
more
often
than
not.
A
group
generally
represents
a
department
within
the
company,
so
let's
say
a
group
can
say
it
could
be
security
and
then
all
the
projects
that
have
to
do
with
security
are
under
that
group.
Another
group
could
be
software
development,
then
all
of
the
micro
services
that
your
company
is
working
on
are
going
to
be
a
project
within
that
group
and
so
on
and
so
forth,
but
you
can
really
structure
it.
B
A
Of
a
lot
of
companies
segment
their
products-
let's
say
if
you're,
in
retail
or
in
e-commerce,
like
all
your
website
stuff
will
be
a
group.
All
your
mobile
stuff
would
be.
Another
group,
back-end
stuff
will
be
in
our
back
office
would
be
another
group,
and
then,
within
that
group
you
have
multiple
projects
that
could
represent
the
micro
services
or
the
monolith
that
you
use
for
that
part
of
the
product.
A
Absolutely
and
I
mean
it's
it's
it's
a
pity,
because
it's
all
version
controlled
and
it's
very
powerful,
so
we
are
seeing
more
people
start
using
gitlab
as
their
issue
tracker
for
everything.
So
let's
say
there
are
certain
projects
that
don't
use
the
repo
to
hold
code,
but
they
use
a
project
like
they.
When
you
go
into
a
project
here
to
start
creating
issues
that
have
to
do
with
anything,
they
could
be
marketing,
they
could
be
sales.
That
could
be
a
lot
of
stuff,
so
we
use
it
like
that
at
good
laughs.
A
B
A
Within
that
group
they
have
a
project
called
corporate
mark
corporate
marketing
and
within
that
group
they
have
issues
to
track
all
the
marketing
activities.
Sorry,
all
the
marketing
activities
that
they
do
like
this
one
is
for
cube
con
and
here
they
have
and
then
detailed
cost
campaign
all
of
that
stuff.
So
you
know
this
could
happen
in
every
company
and
it's
a
great
way
to
keep
information
organized
and
centralized
and
just
use
one
system
yeah.
A
Yeah,
so
let's
talk
about
projects
and
repositories,
so
a
project
is,
as
I
said,
kind
of
that
collection
of
work.
Your
project
has
issues
so
like
the
website
is
a
project
that
project
has
issues
has
a
repo,
like
oldest
all,
the
files
that
go
into
the
website,
but
you
don't
have
the
necessity
to
use
a
repo
when
you
have
a
project
so
like.
If
you
look
at
this
project,
it
has
issues
that
exist
within
it,
but
the
repo
is
not
being
used,
so
there
are
no
files
in
the
repo.
A
So
if
you're
doing
software
development
you'll
probably
use
the
repo,
if
you're
not
doing
software
development,
you
probably
won't
use
it.
So,
let's
say
a
lot
of
people,
for
example,
use
the
project
for
the
wiki
and
they
use
the
wiki
as
an
information
collection
of
like
policies
like
we
use
the
handbook
on
the
website.
A
lot
of
people
have
their
handbook
on
our
wiki,
that's
only
available
internally,
so
we
see
a
lot
of
projects
that
don't
have
a
repo.
For
that
reason,
there.
B
A
Color
make
sense,
there's
no
code
yeah,
so
they
create
pages
within
wiki's
and
they
say
and
like
you
know,
they
create
a
handbook,
and
this
is
the
title
of
the
page
and
then
once
you
create
like
a
home
page,
then
you
can
link
more
pages
to
it
and
you
can
have
like
this
whole,
very
complex
structure
of
a
wiki
I.
Don't
know
if
you
use
products
like
that
before
one
very
famous
one
by
a
class
Ian,
it's
called
confluence.
B
A
B
A
A
B
B
A
You
could
have
an
issue
board
of
things.
You
want
to
read
things.
You
were
doing
absolutely
you.
You
could
do
that
now.
If
you
make
use
of
a
static
website,
you
probably
use
good
luck
pages
for
that,
so
I
don't
know
if
you're
familiar
with
it
lap
pages
or
github
pages,
but
that's
like
our
free
hosting
of
a
static
web
website
content.
A
So
there
are
these
engines
like
Jekyll,
it's
a
very
famous
one
that
allow
you
to
generate
a
full
website
just
by
editing
the
template.
So,
as
I
said,
Jekyll
is
a
very
famous
one.
I
actually
did
my
sister's.
What
website
on
good
lap
pages,
maybe
if
I
show
you
that
that's
a
cool
example
and
like
with
minimal
effort
really
all
I
did
was
fork
a
template.
A
B
B
A
A
B
A
My
could
enable
so
when
you
say
enable
kubernetes
what
I
read
by
that
is
I.
Add
a
kubernetes
cluster
to
my
project,
so
like
here,
I
have
two
clusters
but
no
repo.
This
is
a
project
that
has
two
clusters
and
does
not
have
anything
in
the
repo.
Of
course,
if
I
want
to
make
use
of
the
clusters,
I
probably
are
I'm
gonna,
write
some
code
and
have
a
deployment
script
and
things
like
that,
but
one
is
not
necessary
to
have
the
other
okay.
B
B
A
Well,
we
have
to
surface
the
contents
because
all
the
configuration
is
gonna
go
in
that
repo
and
I
guess
the
best
way
I
could
explain.
That
is.
Let's
say
you
create
a
group
level
cluster.
Then
you
want
to
host
configuration
for
that
cluster.
In
my
mind,
in
this
page
we
would
show
you
the
configuration
file,
so
you
can
click
on
it
or
you
can
upload
it
or
you
can
do
stuff,
but
we're
not
necessarily
revealing
the
repo,
although
well
yeah.
We
probably
want
to
we.
A
A
Will
be
created
automatically
by
us
on
the
appropriate
level
where
you
have
to
plus
them
and
of
course,
so
the
rough
is
reposts
can
only
live
at
the
project
level.
So
if
I
only
add
a
group
level
cluster
and
there's
no
project
under
that
group.
So
that
presents
us
with
a
challenge
so
we're
going
to
need
to
decide.
We
create
like
a
hidden
project,
only
to
hold
this.
A
B
A
A
It's
important
yeah
I'm,
just
I.
We
don't
necessarily
like
all
of
these
things
tie
into
the
configure
stage.
Knowledge
transfer
that
I
want
to
do
with
you
so
and
if
we
need
to
put
more
time
we
put
more
time,
it
doesn't
matter.
I
think
that
important
things
is
that
the
concepts
are
clear
to
you.
Yeah.
B
A
A
Maybe
they
are
mixed
know
a
great
example
of
how
confusing
that
can
be
yeah
and
good
luck
work.
So
in
good
lab
org.
There
are
many
many
things
and
the
icon
here,
I
think
represents
sub
projects
versus
pumps.
Yeah,
so
like
a
folder
is
a
sub
group
and
then
this
little
thing
I,
don't
know
what
that's
called
like
a
flag.
It's
a
project,
that's
very.
A
A
Groups
will
definitely
have
more
more
project.
Yeah
I
think
that
that's
the
reason
that
they're
created
is
like
centralize
the
work
for,
let's
say,
a
team
and
they
put
like
all
of
their
projects
in
there.
So,
like
the
database
team,
you
saw
had
multiple
projects
like
here.
This
is
a
page
where
you
see
that
they're
both
right,
so
the
folder,
oh
and
there's
a
little
drop
down
here,
where
you
can.
B
B
A
Sharing
a
project
with
a
group
of
users
share
projects
with
groups:
you
can
share
projects
with
other
groups.
This
makes
it
possible
to
add
a
group
of
users.
Okay,
go
project
with
a
single
action.
Yeah
that
makes
sense.
I
give
you
you
dope,
you
don't
want
to
add
a
thousand
users.
There
are
members
of
other
groups.
You
just
share
the
project
with
the
group.
They.
B
A
Let
me
show
you
a
project
that
has
some
that
has
both
so
here.
This
is
my
project,
and
this
is
the
repo
right.
So
when
I
click
on
repo
and
files,
if
you
see
content
there,
that
means
the
repos
probably
has
code
that
is
executed
and
then
your
pipelines,
it's
what
gets
executed
every
time
you
commit
code
or
every
time
you
initiate
a
pipeline
that
is
defined
by
the
gitlab
CI
llamo.
So
this
is
if
there,
if
this
file
is
present,
your
lab
will
run
a
pipeline
every
time,
there's
a
coach
comin.
A
A
No
so
well,
it
runs
automatically
on
to
circumstances.
If
there's
a
good
lab
see
I
got
ya
know
the
pipeline
will
run
regardless
of
if
you
have
a
kubernetes
cluster
attached
or
not,
because
there
are
many
people
that
don't
deploy
to
a
kubernetes
cluster.
There
are
many
people
that
deploy
to
a
VM
or
many
people
to
deploy
to
bare
metal
servers.
So
that's
a
regardless
of
the
kubernetes
cluster.
Your
pipelines
will
run
if
get
alive.
A
So
this
project
has
no
good
lab
CID
MO,
as
you
can
see,
so
the
only
other
possibility
is
that
it
has
auto
dev
ops,
enabled
if
our
DevOps
is
enabled,
then
it'll
run
an
audit
of
ops
pipeline
and
those
pipelines
are
clearly
marked
with
this
late
blue
label
of
auto
DevOps.
So
this
pipelines
on
my
other
project
are
not
don't
have
that
label
because
I
have
a
good
lab,
see
idml
file
that
tells
get
lab
CI
how
to
build
and
deploy
my
project
and.
A
A
So
let's
go
here
and
let's
see
that
in
action,
so
here
I'm
going
to
disable
other
auditive
ups,
and
so
you
see
that
my
last
pipeline
here
ran
a
month
ago.
So,
if
I
go
to
my
files
and
I
go
make
a
change.
That's
generally!
What
kicks
off
your
continuous
integration,
a
I'm
gonna,
make
a
change
here
and
commit
so
that
change
is
committed
and
you
see
that
no
pipelines
have
run
so.
My
last
pipelines
still
ran
one
month
ago,
but.
A
A
Yeah,
it's
true.
This
there's
no
message
telling
you
that
not
nothing
is
gonna
happen
on
CI.
They
think
that's!
Okay,
because
people
know
that
if
you
don't
have
a
CI
file,
nothing's
gonna
happen.
If
our
develops
is
disabled,
nothing's
gonna
happen,
I
think
that's!
Okay,
I
think
that
developers
are
used
to
this
workflow.
Okay,.
A
Even
yeah,
yeah
I
I
see
what
you're
saying
and
coming
from
a
like.
Coming
from
a
place.
That's
not
used
to
this
workflow
I
could
totally
see
how
that's
kind
of
a
foreign
concept
that
hey
I
was
expecting
something
to
happen
because
I
made
a
change
or
even
if
I
run
a
pipeline
here
makes
a
run
pipeline.
B
B
If
I
were
a
developer,
I
would
expect
my
pipeline
to
start
running
if
I
have
everything
configured
automatically
and
I
would
notice
that
it's
not
running.
So,
if
I'm
working
with
somebody
else
on
a
project
and
they
have
disabled
other
DevOps,
then
I
make
a
change
but
I,
don't
notice
it's
not
running
or
who
died
notice
because
you.
B
A
A
B
A
You
submitted
a
merge
request.
Yeah
if
you
see
that
your
M
R
has
a
little
red
X
or
has
nothing
at
all,
then
you
know
to
go
to
the
pipeline's
page
and
see
hey
what
happened
with
my
M
R
and
then,
when
you
go
to
pipelines,
you
can
kind
of
start
troubleshooting.
The
problem,
but
yeah
I,
know
that
you
know
developers
are
kind
of
be
used
to
this
workflow
yeah.
It's
not
necessarily
a
point
of
contention
that,
if
nothing
happens,
we
don't
show
you
anything.
I.
Think
that's
a
bit
right!.