►
From YouTube: Move the GitLab Kubernetes Agent to Core #300464
A
Hello,
my
name
is
viktor
knight,
and
I
am
the
configure
group
product
manager,
we
own
the
gitlab
events
agent
and
we
decided
to
move
one
feature
of
the
agent
to
core
together.
With
this
feature,
we
are
going
to
move
the
basic
underlying
agent
registration
to
core
as
well
and
in
this
video.
I
would
like
to
give
you
a
quick
explanation:
what
is
actually
going
to
be
moved
to
core
and
what
stays
in
premium
today,
all
the
features
that
the
agent
supports
are
in
premium,
that
is,
network
security
policy,
integrations
pool
based
deployment.
A
At
the
same
time,
we
are
working
for
some
time
on
something
we
call
the
ci
tunnel
that
connects
gitlab
runner
jobs
with
a
kubernetes
cluster
using
the
kubernetes
agent.
This
enables
a
secure
setup
for
anyone
already
using
gitlab
ci
to
connect
to
the
cluster
and
run
deployment,
jobs
or
any
comments
targeting
the
cluster
itself.
A
One
can
do
this
in
several
ways.
One
is
to
reuse
the
same
service
account
that
the
agent
the
cluster
set
component
of
the
agent
uses
today
and
actually
what
we
are
moving
to
core
is
exactly
this
setup.
So
so,
there's
a
service
account
that
the
cluster
set
component
uses
to
operate
in
the
cluster
and
ci
108
reusing
this
service
account
will
be
moved
to
core.
A
What
will
not
be
moved
to
core
are
our
future
plans,
that
is,
to
provide
a
user
based
service
account,
for
example,
that
is
the
git
lab
run
user
who
initiates
ci
run.
We
receive
the
impersonated
account
and
that
will
remain
in
premium.
Similarly,
we
have
plans
to
have
job-based
impersonation,
that
is
the
user
can
say
that
this
job
has
these
rights
in
their
cluster,
and
this
is
not
to
be
moved
to
core,
neither
together
with
moving
these
very
basic
ci
tenant
setup
to
core.