►
From YouTube: GitLab 15.1 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
A
So
what
do
we
plan
to
work
on
in
the
next
milestone?
First
of
all
we
would
like
to
we
are.
We
are
going
to
focus
mostly
on
maintenance,
related
maintenance
type
of
work.
We
are
way
behind.
Our
commander's
version
supports
the
official
release
of
kubernetes.
124
happened
two
or
three
weeks
ago.
We
are
just
giving
support
for
kubernetes
122..
We
don't
even
support,
coincidentally
three
and
at
the
same
time
we
want.
We
came
up
with
a
new
support
model
around
kubernetes
versions.
A
A
The
next
goal
is
to
look
into
how
flux
does
helm
and
customize
support.
We
are
looking
into
this
because
the
agent-based
github's
approach
today
only
super
supports
pure
comments,
manifest
files
and
the
most
often
requested
feature-
is
to
have
ham
and
customized
reports
out
of
the
box,
and
a
very
typical
workflow
is
when
you
want
to
chain
ham
and
customize
for
deployment.
So
we
want
to
support
these
use
cases
and
want
to
learn
how
flux
does
it.
A
Almost
all,
but
let's
see
a
little
bit
more
detail
around.
What
do
we
mean
in
151?
We
have
a
few
items
that
are
kind
of
must-haves.
They
come
from
from
the
engineering
organization,
like
this
first
item
around
providing
database
dictionaries
for
the
team.
A
The
next
item
that
I
want
to
speak
about
is
what
I
already
mentioned
around
flux.
We
want
to
learn
how
they
do
it.
Flux
aims
to
be
aims
to
follow
the
unix
philosophy
of
doing
small
things
that
you
can
pipe
one
after
the
other,
and
you
can
just
pick
some
of
those.
A
Actually,
we
don't
think
that
they
do
a
really
good
job
in
in
being
replaceable,
so
we
can't,
we
very
likely
won't
be
able
to
use
the
flux
controller,
a
ham
controller,
customized
controller,
but
if
we
do,
we
will
go
that
direction
as
it's
better
to
work
together
with
the
community
and
build
our
own
stuff.
But
although
what
we
want
to
provide
here
is
a
technical
learning
around
how
others
do
han
and
customer
support
in
a
github's
workflow.
A
The
next
items
I
want
to
speak
with
more
is
a
warning,
a
pretty
small
development,
but
a
very
important
one.
For
us.
We
want
to
get
rid
of
all
the
certificate
based
cluster
connections
on
github.com
and
in
order
to
continuously
notify
the
users
we
want
to
show.
We
are
going
to
show
a
warning
message
on
every
project
that
has
a
certificate
based
cluster
attached.
This
warning
will
be
shown
only
to
maintainer
rows
and
up
so
developers
won't
see
this
warning,
but
maintainers
will
and
the
warning
is
not
dismissible.
A
It
will
be
there
as
long
as
there
is
a
certificate-based
cluster
available
in
that
project.
Even
if
the
cluster
comes
from
a
group
level
cluster,
if
the
project
inherits
it,
we
will
show
the
warning.
We
hope
that,
thanks
to
this
warning,
more
and
more
users
will
still
continue
the
immigration
to
the
agent
and
we
will
be
able
to
finally
turn
it
off
around
15.6
on
github.com.
A
A
The
kubernetes
api
does
not
support
a
website
protocol
for
this,
and
that's
what
we
are
improving
and
adding
support
for
it.
We
hope
that
this
will
land
in
kubernetes
125,
that's
expected
to
be
released
around
august
and
after
that,
as
we
add
support
for
it
and
as
our
users
upgrade,
they
will
be
able
to
start
using
this
feature.
A
A
Until
now,
we
said
that
we
are
going
to
take
on
most
of
the
burden
of
immigration
as
it
meant
to
be
very
fast,
not
just
we
had
to
act
quickly
now,
as
there
is
a
half
year
to
finish
these
migrations
we
want
to.
Instead
of
us
doing
all
the
migrations,
we
want
the
owners
to
do
the
migrations
and
provide
us
feedback.
A
Of
course,
in
the
same
time,
we
will
support
these
migrations,
which
means
that
there,
all
our
engineers,
will
do
at
least
one
migration,
but
above
that
we
are
looking
for
the
owners
and
I'm
going
to
poke
the
owners
to
move
on
with
the
migrations
with
our
support.
A
A
That
means
auto
devops
security
scanners
and
vulnerability
scanners
and
so
on.
We
are
very
close
to
ship,
the
122
version
and
actually
that's
a
deliverable.
123
is
way
more
valuable
for
us,
because
that's
more
recent
and
more
in
use
these
days
and
that's
still
only
a
stretch,
goal
for
the
milestone.