►
From YouTube: GitLab 12.5 Kickoff - Configure:Orchestration
Description
Daniel Gruesso (Orchestration PM) goes over the issues the group will work on as part of GitLab 12.5 release, shipping on Nov. 22nd, 2019.
A
Hello,
my
name
is
Daniel
Caruso
I
am
the
product
manager
for
the
configure
orchestration
group
here
at
lab,
and
today
I'm
going
to
be
chatting
about
the
exciting
things
that
we
will
be
working
as
part
of
our
12.5
release
that
will
be
shipped
on
November
22nd.
So,
let's
get
right
to
it.
The
first
thing
that
we're
going
to
work
on
is
the
ability
to
create
an
AWS
eks
cluster
within
get
lab.
A
The
next
thing
that
we're
going
to
be
working
on
is
from
12.4
as
well,
and
we're
going
to
get
it
over
the
line
on
this
particular
release,
and
that
is
an
advance
setting
to
delete
all
the
kubernetes
resources
when
you
remove
a
cluster
from
gitlab.
So,
as
you
know
today,
when
you
create
a
cluster
and
you'll
remove
that
debt
cluster
from
git
lab
all
the
resources
that
were
created
specifically
for
that
project
will
remain
on
that
clusters.
A
Let's
say
it
get
left,
created,
specific
name,
space
service
account,
role,
binding
and
all
of
those
things
remain
in
your
cluster
and
they
have
to
be
manually
removed.
So
what
we
will
do
with
this
particular
feature
is
that
once
you
remove
it
from
git
lab
who
will
present
you
with
an
advanced
setting
that
will
allow
you
to
remove
all
the
integration
and
resources
and
that
will
basically
take
care
of
all
the
I'll
take
care
of
all
the
cleanup
for
you.
A
And
that
way,
let's
say
if
you
want
to
use
that
cluster
on
a
separate
project,
you
will
be
able
to
do
that
in
a
very
easy
map,
so
very
excited
to
bring
you
that,
let's
move
on
to
the
next
feature-
and
this
is
the
ability
to
customize
a
kubernetes
namespace
per
environment.
So
today
there
are
a
lot
of
software
shops
that
have
an
existing
kubernetes
primitives
and
when
they
bring
get
lab
into
the
fold,
our
integration
will
create
specific
namespaces
for
each
one
of
the
environments
that
you
have
out
there.
A
So
basically,
this
will
provide
you
the
ability
to
map
an
existing
namespace
to
an
environment
that
you
will
be
using
with
get
labs.
So,
let's
say:
if
you
create
a
staging
environment
and
a
production
environment,
and
you
already
have
namespaces
for
those
two
environments,
then
you
will
be
able
to
plug
those
in
here
and
the
get
lab
integration
will
use
those
namespaces
instead
of
the
namespaces
that
it
generally
creates.
A
So
this
will
be
very
useful
for
a
number
of
people
that
have
an
existing
products
practice,
but
they
want
to
take
advantage
of
all
the
cool
features
that
we
have
with
our
programmatic
situation.
It's
very
excited
to
bring
that
as
well.
Let's
talk
about
the
next
one.
This
is
one
that's
very
exciting
and
a
feature
that
I'm
looking
forward
to
very
much.
So
this
is
the
ability
to
version
controlled.
All
the
good
lab
managed
apps
that
we
offer
you
as
part
of
our
kubernetes
into
integration.
A
So
the
genesis
of
this
feature
is
that
we
have
a
lot
of
advanced
users
that
when
they
install
an
application
on
to
their
cluster,
they
want
to
do
some
customization
to
that
applications.
Let's
say
if
you
don't
want
to
take
the
default
values
up
the
helm
chart,
but
there's
you
know
a
couple
of
things
that
you
want
to
change
before
you
install
it
today.
That's
not
something
that's
possible.
A
So
let's
say
if
you
install
the
Gil
a
primer
and
as
that's
a
chart
in
kubernetes,
and
you
want
to
pass
it
a
tunnel
configuration
file,
there's
really
no
mechanism
to
do
that
today.
So
we
are
looking
to
bring
you
a
way
to
easily
customize
all
the
installation
of
your
katuk
managed
apps.
The
way
that
we're
going
to
do
that
is
as
follows.
When
you
provision
a
cluster,
we
will
an
advanced
setting
that
will
allow
you
to
define
a
project
that
will
hold
all
the
configuration
for
your
cluster
and
what
I
mean
with
configuration
is.
A
It
will
hold
for,
for
example,
the
charge
that
you
have
the
possibility
to
install
and
it
will
hold
any
customization
that
you
have
for
those
charts
and
so
that's
kind
of
at
a
high
level.
What
the
feature
would
be-
and
this
brings
many
benefits,
but
the
two
main
ones
that
I
want
to
talk
about
is
that
it
allows
you
to
easily
customize
the
charts
at
the
charts
before
you
install
them
onto
your
your
cluster.
A
It
allows
you
to
version
control,
basically,
all
of
all
of
the
things
all
of
the
changes
that
you
make
to
your
charts.
If
you,
for
example,
made
a
customization
that
didn't
quite
work
out,
it's
all
version
control.
You
can
see
it
right
there
and
you
can
roll
it
back
as
necessary,
and
another
very
big
benefit
is
that
the
installation
of
the
applications
now
will
be
taken
care
of
by
Kittel
FCI.
A
So,
for
example,
when
you
decide
to
install
one
of
the
charts,
what
they
will
do
in
the
background
is
that
it
will
kick
off
a
good
lab
seei
pipeline.
That
will
use
all
the
configuration
that
you
have
in
that
project.
That
holds
all
the
configuration
for
your
cluster,
and
that
makes
two
things
it
allows
you
to
see
in
real
time
all
the
steps
that
are
going
on
in
this
installation
of
this
chart
and
number
two.
A
Of
course,
we
will
have
all
the
all
the
communication
between
the
runner
and
the
cluster
and
that
will
basically
provide
all
the
feedback
right
there
on
the
pipeline
output,
and
that
is
very
useful.
So
there's
you
know
a
plethora
of
benefits
that
that
we
get
with
version
controlling
the
good
lab,
managed
apps
and
have
them
run
from
github
city.
So
we're
very
excited
about
this.
This
is
something
that
we're
getting
started
on
and
it'll
probably
will
take
us
a
couple
of
releases.
A
A
A
The
last
thing
that
we
have
planned
for
12/5
is
the
ability
to
add
cute
monkey
to
get
lab,
managed
apps,
so
cute
monkey
is
an
application
that
allows
you
to
practice.
Chaos,
engineering
with
your
kubernetes
cluster
and
the
way
that
we're
planning
to
do
this
is
with
with
the
new
method
of
installing
it
lab
managed
apps
onto
your
kubernetes
cluster.
So
if,
when
you
install
cube
monkey
onto
your
your
kubernetes
cluster,
initially
you
will
be
able
to
do
it.
A
You
know,
with
the
kid
lab
managed
apps
this
new
method
and
you'll
be
able
to
set
your
own
configuration
here
and
basically
inflict
chaos
in
the
way
that
cube
monkey
does
say,
and
the
vision
that
we
have
long
term
for
chaos.
Engineering
is
that
our
DevOps
will
allow
you
to
practice
chaos
engineering
out
of
the
box
with
basically
a
configuration
of
a
single
variable,
so
the
first
step
would
be
to
install
cube
monkey
on
to
your
cluster
and
the
second
step,
which
will
hopefully
get
you
into
op.
A
A
We
will
show
you
all
the
results
of
how
your
application
behaved
when
chaos
was
introduced,
so
this
is
kind
of
the
first
step
to
to
getting
there,
which
is
the
ability
to
install
cube
monkey
onto
your
company's
cluster,
so
very
excited
to
work
on
this
feature
as
part
of
12.5
and
as
always
feedback
is
welcome,
but
please
feel
free
to
reach
out.
Should
you
have
any
questions
or
want
to
discuss
any
of
these
issues
in
more
detail?
Thank
you.