►
From YouTube: GitLab 16.0 Kickoff - Deploy:Environments
A
I
think
hello,
my
name
is
Victoria.
I
am
the
product
manager
at
the
environments
group
here
at
gitlab,
and
this
is
our
16.0
kickoff
video,
together
with
Emily
Bowman,
who
will
presents
our
design
plans
for
the
milestone
in
the
second
part
of
the
video,
while
I'm
going
to
present
the
delivery
plans,
because
this
is
160,
we
are
primarily
focused
on
the
braking
changes.
A
A
These
are
the
more
maintenance
related
tasks
in
the
Milestone,
and
there
are
quite
a
few
that
we
are
definitely
excited
about
because
we
think
can
bring
more
value
to
our
customers.
The
top
one
in
this
list
is
currently
iteration
on
the
commands.
Dashboard
integration
environments
page
that
I
spoke
already
about
a
month
ago
as
well.
By
now,
we
managed
to
clarify
the
scope
in
the
newly
formed
team
and
I
hope
we
will
be
able
to
deliver
the
first
iteration
of
it.
Our
initial
plan
was
to
ship
it
behind
feature
flag
in
a
closed
beta.
A
Now
that
everything
is
open,
we
still
have
to
figure
out
what
might
be
the
best
approach
here,
because
it
might
has
some
performance
impact
on
gitlab
and
we
want
to
make
sure
that
cost
users
don't
suffer
because
of
this
release.
We
don't
expect
it,
but
rather
be
saved
I'm.
Sorry,
then
we
are
continuing
a
migration
from
Hamel
to
vugs
on
the
environments
pages
besides,
why?
A
The
fifth
goal
for
us
is
to
ship,
or
at
least
start
shipping
flux
integration,
but
understand
what
this
agent
guy
Agent
K
notification
might
mean.
We
should
understand
how
flux
works.
A
Basically,
a
default
install
of
flux
means
that
flux
switches
out
to
get
every
10
minutes
to
say
if
there
is
something
new
for
him
for
it
to
apply
now,
there
are
instructions
how
to
set
up
plugs
with
gitlab
with
a
web
hook
that
cause
an
Ingress
and
reaches
flux
to
trigger
a
sink,
but
for
that
users
need
to
sing,
need
an
Ingress
and
they
need
to
set
up
this
whole
infrastructure
for
it
to
work
as
Agent
K
already
knows
about
a
new
commit
in
gitlab,
we
plan
to
notify
flux
with
Agent
K
inside
the
cluster
and
save
the
maintenance
cost
of
setting
up
flux
with
gitlab,
and
the
last
item
on
our
deliveries
is
to
finish
the
deployment
management
spikes
we
run
in
the
past
months.
A
First,
we
looked
at
how
we
recommend
structuring
a
project
for
deployment
management
specifically
enough
for
application
development,
and
now
that
there
we
use
a
small
project.
It
was
like
the
hello
world
application
of
deployments
in
the
second
Spike.
We
want
to
see
our
recommend.
We
won't
come
up
with
recommendations
on
full
scale
like
three-tier
application,
how
to
do
that
with
gitlab.
B
Hey
everyone:
this
is
Emily
Bowman,
the
product
designer
on
the
environments,
team
and
I'm,
going
to
walk
through
what
the
ux
and
research
plan
is
going
to
be
for
the
16.0
Milestone.
So
a
few
things
on
the
list,
the
first
one
being
really
closing
up
the
solution:
validation
on
the
group
level
environments.
B
B
We've
been
working
on
this
for
quite
a
few
months,
and
this
will
be
Milestone
two
of
two
finishing
up
the
research,
so
this
Milestone
will
be
focused
on
conducting
the
interviews
synthesizing,
any
data
that
comes
out
of
those
interviews
and
deciding
on
what
our
next
steps
are
with
this
concept,
depending
on
how
it
users
interact
and
give
us
feedback
on
it,
so
excited
to
see
the
results
of
that
and
see
where
this
concept
goes.
B
The
next
thing
for
ux
to
focus
on
is
continued
support
of
the
kubernetes
dashboard,
with
a
main
focus
on
this
details
view
so
the
container
that
pops
over
the
dashboard
just
to
getting
the
design
of
this
finalized
the
content,
just
the
interactions
done
here
additionally
with
some
support
of
the
filtering
on
the
dashboard
and
some
other
smaller
ux
things
that
need
to
be
completed
before
engineering
can
start
working
on
this
concept.
So
continued
support
of
the
kubernetes
dashboard
will
be
another
big
thing
in
the
smilestone.
B
The
next
thing
we
want
to
focus
on
is
finishing
up
our
glossary
of
terms
for
the
deployment
section,
so
this
is
really
where
we're
defining
the
terms
we
use.
This
will
be
a
good
thing
to
have
for
the
design
Sprint
when
we
start
planning
it
too.
B
Second,
last
thing
we
want
to
do
is
finish:
planning
the
design
Sprint,
so
the
environments
design
Sprint,
is
going
to
take
place
in
16.1
and
16.0.
We
want
to
really
finalize
the
planning
of
these
activities,
get
that
glossary,
completed
figure
out
when
we're
actually
going
to
host
this
get
our
problem
organized.
So,
just
all
the
things
we
need
to
do
to
prepare
for
a
good
design.
Sprint
have
those
finished
in
the
smilestone.
B
And
then
the
final
thing
for
ux
this
Milestone
is
a
severity
2
issue
with
the
group
level
and
project
level.
Producted
environments
flow.
Currently,
when
you
protect
an
environment
and
encounter
an
error,
you
just
get
a
failed
to
protect
the
environment
and
it's
really
difficult
to
understand
what
went
wrong
here.
So
this
is
cleaning
up
the
error,
States
ensuring
that
users
are
given
the
right
amount
of
feedback
so
that
they
can
kind
of
continue
on
their
flow
without
stopping
and
those
are
the
issues
we
have
in
line
for
160
for
ux.