►
From YouTube: GitLab 15.0 Kickoff - Configure:Configure
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
my
name
is
viktor
naj
and
I
am
the
product
manager
of
the
configure
group,
and
this
is
our
15.0
kickoff
video.
What
do
you
plan
to
work
on
and
to
achieve
in
the
next
milestone?
First
of
all,
this
is
the
last
milestone
before
15.0,
so
we
are
primarily
focusing
on
deprecations
and
removals
work,
including
some
migrations.
A
You
will
see
in
a
minute.
Besides
this,
we
are
pretty
confident
about
having
support
for
quantus
121.
So
we
want
to
update
the
list
of
supported
clusters
and
we
want
to
try
to
provide
support
for
122
as
well
during
this
milestone,
that's
a
stretch,
but
we
will
try.
Another
important
work
that
we
are
working
on
are
one
specific
bug
fix
that
I
will
speak
a
bit
later
and
several
performance
improvements
around
the
agent.
A
A
A
That
is
to
simply
better
understand
the
deployment
management
tools
not
only
from
product
perspective
but
as
well
from
an
engineering
perspective,
so
tiger
is
working
on
it
and
he's
going
to
share
us
share
summaries
of
his
insights
there
and
after
that,
you
want
to
move
on,
if
necessary,
with
the
designs
paint
or
simply
by
picking
some
of
these
tools
or
coming
of
your
design
around
around
them.
A
We
believe
that
this
is
a
relatively
good
experience
for
us
as
well
to
see
some
user
clusters
and
see
how
the
immigration
goes.
So
we
want
to
improve
our
documentation
around
the
migrations
and
you
might
come
up
with
a
few
new
issues
as
well
along
the
way,
as
it
already
happened
in
the
past
month
when
the
migrations
started.
A
Besides
that,
we
have
a
few
other
removal
related
15.0,
specific
work,
and
here
you
can
see
the
kubernetes
121
version
and,
in
the
stretch
the
matrix
122
version
upgrade,
and
the
issue
that
I
would
like
to
speak
about
is
this
support.
A
Cube
ctl
exec
attach
cp
command
with
the
cicd
workflow
on
the
agent,
you
can
run
cube,
ctr
commands
or
ham
commands,
or
any
commands
that
require
kubernetes
contacts
to
to
connect
to
the
cluster,
and
here
it
turned
out
that
some
of
these
commands
actually
does
not
work
because
of
how,
because
they
are
rooted
differently
using
different
protocols
than
the
basic
commands
are.
Such
commands
are
cube,
ctrl,
exact,
attach
and
copy.
For
example,
last
week,
mikhail
came
up
with
a
new
idea
that
doesn't
require
us
to
fix
the
upstream
issue.