►
From YouTube: GitLab 12.6 Kickoff - Configure:Orchestration
Description
Daniel Gruesso (PM Configure:Orchestration) walks through the planned items for GitLab release 12.6, scheduled to be shipped on Dec 22nd, 2019.
https://gitlab.com/gitlab-org/configure/general/issues/6
A
Hi,
this
is
Daniel
I'm,
the
product
manager
for
configure
orchestration
here
at
github,
and
today
I'm
bringing
you
the
gitlab,
12.6
kickoff,
a
video
and
we're
going
to
talk
about
the
exciting
things
our
group
will
be
working
on.
So
let's
get
started.
The
first
issue
that
our
team
will
focus
on
is
not
running
auto
dev
ops
when
there
is
no
docker
file
or
a
matching
belt
pack.
So,
as
you
might
have
heard
me
stating
in
the
last
video,
this
is
something
that
we
hopefully
wanted
to
get
out
the
door.
A
In
12/5
we
had
some
dependencies
in
some
CI
functionality
that
we're
implementing
that
were,
they
did
not
quite
make
it
past
the
finish
line.
So
we're
going
to
focus
on
this
as
part
of
code
lab
12
6,
and
basically
we
want
to
make
auto
dev
ops
more
efficient
about
when
it
runs
and
make
sure
that
it
runs
when
it
adds
value.
For
example,
if
we
are
using
a
certain
number
of
Heroku
build
packs
that
support
certain
languages
and
your
project
is
not
in
one
of
those
languages,
we
want
to
basically
evaluate
that.
A
That's
the
case
and
don't
run
it
if
one
is
not
supported
and,
conversely,
there's
not
a
doctor
file
in
your
project,
then
we
will
not
run
it
so
it's
kind
of
an
either
alright.
If
there's
not
a
magic
pill
pack
and
you
have
a
docker
file
and
we
want
to
make
sure
that
it
doesn't
run
so
we'll
be
working
on
this
as
part
of
12.6.
A
The
next
issue
we
will
be
focusing
on
is
the
ability
to
customize
that
covered
in
kubernetes
namespace
per
environment.
So,
as
you
know,
the
gitlab
integration
today
allows
you
to
create
a
dedicated
namespace
for
each
one
of
the
environments,
but
that
naming
takes
place
automatically
today.
So,
let's
say:
if
you
have
an
existing
practice
and
you
already
have
those
namespaces
defined.
This
is
going
to
give
you
the
ability
to
map
that
existing
namespace
to
an
environment
that
you
are
going
to
be
using
30,
laps,
yeah
hi.
So
we're
very
excited
about
this.
A
This
is
going
to
cover
a
number
of
use
cases
that
we
know
will
be
very
beneficial
and
basically,
what
we're
doing
here
is
part
of
your
CI
file.
You're
going
to
be
able
to
add
an
a
namespace
key
in
your
CI
file,
and
this
bit
in
this
I
will
allow
you
to
specify
an
existing
namespace.
So
we're
very
excited
about
that.
Some
of
the
other
things
that
we're
working
on
is
readiness
for
kubernetes
1.16.
A
As
you
know,
we
use
the
auto
deploy
app
and
we
want
to
make
sure
that
the
helmet
chart
is
updated
to
be
ready
for
kubernetes
one
one
six,
and
then
we're
also
going
to
address
a
number
of
bugs
that
we
try
to
address
on
every
release
and
in
addition,
we
are
also
going
to
go
ahead
and
create
new
templates
for
the
new
pattern
to
install
get
lab
manage
tab
onto
your
clusters.
You
were
following
closely
on
12/5.
A
We
have
released
a
way
for
you
to
specify
a
project
that
will
manage
all
of
the
installation
of
charge
for
your
cluster
and
what
we
want
to
do
now
is
basically
template
all
the
applications
that
we
support
and
make
that
template
available
to
you.
So
you
can
continue
to
do
single
command
and
install
those
charts
and
basically,
what
we
want
to
do
long
term
is
after
we
have
those
templates
in
place.
We
want
to
replace
the
current
pattern
of
single
click
installation
to
this
new
CI
back
process.
A
A
So
you
not
only
see
the
ID
there's
a
name
available,
we'll
go
ahead
and
show
it
to
you.
Another
one
is
around
pointer
focus
and
making
sure
that
that
focus
is
going
to
be
on
the
text
boxes.
When
you
click
on
each
one
of
those
areas
there,
and
then
we
also
want
to
provide
you
an
easy
way
to
switch
cloud
providers
when
you're
creating
a
cluster
within
get
labs.
Let's
say
clicked
on
gke,
but
you
want
to
go
back
and
create
an
eks
cluster.