►
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
Hi,
my
name
is
victor
and
I'm
the
product
manager
of
the
configure
group
here
at
gitlab
and
in
this
video
I
would
like
to
demo
you,
the
group
level
ci
tunnel
with
the
gitlab
kubernetes
agent.
What
is
the
gitlab
commands
agent?
First
of
all,
the
gitlab
commands
agent
is
the
foundations
of
all
gitlab
kubernetes
integrations.
A
In
this
release,
we
added
support
for
push-based
deployments
at
the
group
level
too,
which
means
that
an
agent
can
be
set
up
to
support
all
the
projects
within
the
group
or
even
selectively
specific
projects.
Only
now,
let's
see
how
this
setup
works,
assuming
that
we
already
have
at
least
the
basic
knowledge
of
the
agent.
If
you
don't
know
what
the
agent
is,
you
can
reach
out
to
this
page,
where
we
describe
how
to
set
up
the
agent
and
how
to
use
it
in
general.
A
In
this
setup
I
will
have
two
projects,
one
that
contains
actually
the
agent
definitions
and
the
agent
configuration
you
can
see,
but
see
that
here
I
will
use
this
temporary
agent
and
its
configuration
is
described
in
this
file.
It
has
one
pool
based
deployment
specified,
which
grabs
all
the
ammo
files
under
the
kubernetes
directory
from
within
its
own
directory.
This
is
a
feature
that
we
shipped
a
year
ago
and
many
users
use
it
already.
A
A
A
If
you
look
very
closely
now,
you
can
see
an
error
that
I
have
to
specify
the
same
project
name.
This
is
by
error.
You
have
to
specify
the
project
name
of
your
agent
configuration
project,
not
the
project
that
you
are
using,
and
then
we
see
if
we
can
actually
reach
the
cluster
from
ci
specified
at
the
group
level
using
an
agent
from
another
project.
A
A
A
Okay,
so
our
job
finished
and
we
can
see
the
results
here
is
the
get
context
score,
which
shows
a
context
that
was
preset
for
us
using
the
gitlab
kubenz
agent
and
gitlab.
As
I
told
you,
this
project
has
nothing
configured
except
what
I
showed
you
in
the
gitlab.cml
file.
So
there's
nothing
about
the
agent.
All
of
this
was
preparated
prep
populated
by
in
gitlab,
using
the
setup
connection
in
the
configuration
repo.
Then
we
switch
to
the
right
context
and
we
could
get
the
pods
from
the
namespace
that
we
are
interested
in.