►
From YouTube: Deprecating GitLab Managed App
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
Hi,
my
name
is
viktor
knight
and
I
am
the
product
manager
of
the
configure
group,
and
I
would
like
to
say
why
and
how
do
we
want
to
deprecate
gitlab
managed
apps
for
this
I'm
going
to
share
my
screen
here
where
we
have
an
epic
around
this
deprecation,
and
you
can
read
much
of
this
discussion.
One
of
the
issues
that
I
put
is
the
first
issue
now,
but
it
might
be
get
down
as
we
close
it,
etc.
A
So
why
are
we
deprecating,
gitlab
managed
apps.
First
of
all,
what
are
gitlab
managed
apps.
We
have
two
versions
of
gitlab
managed
apps,
one,
what
we
call
version,
one
or
one
click,
install
applications
that
you
can
find
under
the
operations
clusters
menu
under
specific
cluster
and
the
other
that
we
call
version
two
or
ci
cd-based
managed
apps
that
you
can
mostly
find
in
the
documentation.
It's
a
it's.
A
cloud
native
friendly
approach
to
installing
applications.
A
A
A
Why
do
we
want
to
do
that?
Because
this
is
what
our
users
want?
Actually,
so
many
of
our
users
are
experienced
kubernetes
operators,
they
know
how
to
install
these
applications.
They
know
how
to
manage
these
applications
and
we
have
to
provide
them
a
simple
way
to
just
integrate
it
with
gitlab
without
them
required
to
take
our
take
over
our
workflows
and
our
required
approaches
to
all
of
this.
So
this
is
the
direction
that
we
want
to
move
forward
and
at
the
same
time
we
have.
A
A
Is
that
anything
that
we
provide
for
our
users
should
be
production
ready?
It
should
have
come
with
directional
configurations
it
shouldn't
just
be
for
testing
environment
or
to
play
with.
The
second
principle
is
that
they
should
provide
functionality.
They
should
support
some
gitlab
functionality.
They
should
these
applications
should
integrate
with
gitlab.
A
We
are
often
approached
by
various
open
source
projects
who
would
be
happy
to
provide
their
app
as
part
of
gitlab-managed
apps,
but
actually
it
would
just
be
another
way
of
installing
the
applications
into
the
cluster,
and
there
is
no
git
lab
integration
involved
at
all.
We
don't
want
to
become
a
marketplace
in
this
sense,
so
we
are
looking
for
applications
that
provide
functionality
for
gitlab.
A
So
these
three
topics
should
be
checked.
For
something
to
come
to
be
classified
as
a
gitlab
managed
app
in
the
future
and
together
with
bringing
existing
installations
into
gitlab
and
being
able
to
use
your
own
ingress
installation
or
anything
primitives
with
gitlab,
we
decided
to
deprecate
what
we
have
today,
primarily
the
v1.
A
If
they
have
the
experience
around
that
that
that's
probably
the
best
option
you
can
provide-
and
this
is
very
important
for
us-
so
as
well
applicating-
we
know
that
we
learned
a
lot
about
using
the
band
clicking
style
about
what
our
users
need
and
they
need
exactly
this
customizability
extension
extensibility.
They
want
to
provide,
follow
their
own
workflows
and
with
the
ui
based
approach
supporting
this
is
purely
impossible.
A
With
respect
to
ci
cd-based
apps,
we
are
looking
into
that.
It's
valuable
to
keep
them,
because
that
is
an
approach
that
we
think
is
kind
of
future
proof,
so
it
provides
the
necessary
customization
customizability
that
our
users
require
there.
At
the
same
time,
it
has
a
lot
of
requirements
that
we
don't
fulfill
today,
like
in
the
case
of
security,
patches
and
upgrades.
A
A
How
can
we
support
our
users
with
these
applications
and
if
we
want
to
do
that,
we
want
to
provide
value
even
with
this
deprecation,
we
are
going
to
provide
an
api,
endpoint
and
probably
some
ui
as
well,
to
allow
users
to
register
the
applications
with
gitlab.
That
here
is
where
you
can
find
mycelium
installation.
This
is
where
my
nginx
ingress
lives
and
gitlab
features
can
use
those
afterwards.
A
Please,
if
you
have
any
questions
around
this
topic,
feel
free
to
reach
out
to
me
personally
or
even
better
on
the
s
configure
slack
channel
to
the
team.
I'm
more
than
happy
to
discuss
this
topic
with
you,
especially
if
you
depend
on
any
of
the
existing
applications,
then
I
would
love
to
hear
about
you,
so
we
can
make
sure
that
we
can
either
support
you
in
the
future
or
you
can
be
prepared
for
these
changes.