►
From YouTube: GitLab 12.8 Kickoff - Configure:Orchestration
Description
Orchestration PM (Daniel Gruesso) walks through the items scheduled for 12.8 GitLab release, shipping Feb. 22nd, 2020.
A
Hi,
this
is
Daniel
I'm,
a
product
manager
in
the
orchestration
group
here
at
the
good
lab
part
of
the
configure
stage,
and
today
I
like
to
talk
about
the
kickoff
for
the
release,
12.8
that
we'll
be
shipping
in
February
22nd.
So
let's
get
started
the
first
thing
and
some
of
the
things
that
you
will
see
here
get
started
as
part
of
twelve
seven
and
because
we
had
the
holidays,
he
was
kind
of
a
short
release
for
us
and
we're
going
to
work
to
get
some
of
those
items
in
across
the
finish
line.
A
That's
the
first
thing
that
we're
going
to
do
is
show
you
the
name
space
for
your
deployment
on
the
deployments
page.
So,
basically,
right
now
on
the
jobs
page,
we
show
you
the
environment
and
the
cluster
that
your
job
was
deployed
to,
but
we
don't
show
you
the
name
space
and,
for
example,
if
you're
using
a
cluster
that
is
not
being
managed
by
kit
lab.
So
it's
not
creating
kind
of
those
namespaces
with
the
conventions
that
we
follow,
figuring
out,
which
namespace
and
the
your
job
was
deployed
to
it's
kind
of
a
chore.
A
You
have
to
go
to
the
command
line
and
figure
out
where
that
was
deployed
to
so
we're
going
to
make
it
easy
for
you
right
there
on
jobs,
page
we're
going
to
show
you,
the
environment,
the
cluster
and
the
namespace
that
your
job
was
deployed
to
so
a
minimal
feature.
That
brings
a
ton
of
value
all
right.
A
Let's
move
along
the
second
item
that
we're
going
to
work
in
is
going
to
be
readiness
for
kubernetes
1.16
and,
as
you
may
know,
some
of
the
endpoints
on
the
API
are
being
removed
after
being
deprecated
for
some
time.
So
it's
gonna
be
kind
of
a
two-fold
approach
here.
The
first
one
is
migrating
ingress
and
the
second
one
is
migrating
deployments.
So
we
want
to
make
sure
that
all
aboard
features
like
our
DevOps
continue
to
work
with
1-6
without
interruption,
all
right,
the
next
thing.
A
A
So,
as
you
know,
we
kind
of
moving
into
a
place
where
a
kid
web
CI
will
do
all
the
management
for
insulation
upgrading
and
removing
your
it
lab,
managed
apps
right
now,
it's
kind
of
hard
coded
by
derails
back-end
and
we're
moving
to
a
place
where
CI
will
do
it.
So
we
have
a
couple
of
templates
out
there
that
you
can
get
started
with
today,
namely
ingress
and
sentry
are
out
there.
A
But
we
want
to
work
to
make
sure
that
all
the
apps
that
we
offer
today
have
a
matching
template
that
you
can
use
for
CI.
So
you
can
simply
kind
of
flip
a
switch
on
your
config
that
ya
know.
File
and
the
pipeline
that
will
trigger
that
will
trigger,
will
go
ahead
and
install
that
app
on
your
cluster.
So
we're
going
to
work
to
make
sure
that
the
templates
that
you
see
here
are
going
to
be
available
in
CI.
Alright,
the
next
one
is
kind
of
a
quick
ux
win
here.
A
As
you
know,
when
you
create
a
cluster
currently
in
one
of
the
clouds
that
we
have
integrations
with
like
AWS
or
google,
once
you
select
your
provider,
let's
say
it's
like
AWS.
There's
really
no
way
to
switch
provider,
see
if
I
wanted
to
select
Google
instead,
I
have
I
kind
of
have
to
start
over
the
whole
process,
so
we're
gonna
kind
of
do
a
minimal
change
here
and
we're
going
to
leave
the
provider
selection
on
that
page.
As
you
fill
out
that
form
so
in
case
you
want
to
switch
and
just
go
ahead
and
switch.
A
So
that
is,
and
the
next
thing
and
let's
see,
moving
right
on
we're
going
to
keep
working
on,
allowing
the
selection
of
networks
and
sub
networks
when
you
create
a
GK
cluster
in
get
lab.
So,
as
you
know,
when
you
create
that
cluster
in
gke,
you
have
this
field
here
in
networking
where
you
can
select
the
network
and
the
subnet
that
your
cluster
will
belong
to
and
that's
kind
of,
if
you
want
to
use
resources
in
an
optimal
way
and
have
them
communicate
in
that
subnet.
A
So
what
will
happen
is
when
you
create
your
cluster.
We
will
create
that
project
automatically
for
you
and
provision
it
with
all
the
necessary
templates.
So
you
can
kind
of
get
up
and
running
quickly
if
you
want
to
manage
your
apps
from
that
project.
Alright.
So
the
next
thing
that
we're
going
to
do
is
also
adding
another
managed
app,
and
this
is
going
to
be
in
this
new
CI
paradigm,
where
we
add
the
CI
template
and
the
CI
job
will
install
it,
and
that
is
for
Kaos
engineering.
A
So
we're
going
to
use
an
open-source
product
called
litmus
chaos
and
it's
a
very
cool
product
and
it
works
in
a
very
kubernetes
native
way.
So
talking
to
the
kubernetes
api
and
using
kubernetes
primitives,
you
have
a
set
of
experiments
that
you
can
run
for
chaos,
engineering,
that
kind
of
work
out
of
the
box.
You
have
to
configure
a
couple
of
configuration
points
you
can
get
started,
it's
quite
easy
and
very
cool.
A
However,
Auto
DevOps
relies
on
a
lot
of
external
dependencies
to
get
lap
and
what
we
want
to
do
for
our
selfish
customers,
for
example,
who
are
running
a
highly
secured
environment.
That's
air-gapped
to
have
that
same
ability
to
maybe
specify
where
those
dependencies
will
lie,
and
then
we
will
look
for
those
there
instead
of
going
out
to
the
Internet.
So
we're
gonna
start
the
process,
it's
part
of
12/8
and
then
finally,
you
see
that
we
have
included
all
the
design
work
items
that
we're
going
to
tackle
in
the
next
release
as
part
of
this.
A
So,
to
that
end,
we're
gonna
have
you
know,
basically
a
redesigned
and
we're
gonna
split
the
cluster
management
page
into
sections,
and
that
will
hopefully
provide
a
better
experience
and
not
only
that,
but
it
will
scale
further
and
it
will
kind
of
take
us
into
the
future
managing
those
apps
in
cluster.
So
that's
it
for
12-8,
we're
very
excited
to
get
old
stuff.
That's
currently
in
flight
across
the
finish
line
and
then
tackle
some
of
the
new
challenges,
as
always
we'd
love
to
hear
from
you.