►
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
Victor
Naj
I
am
one
of
the
product
managers
at
gitlab
and
me
and
my
team.
We
are
responsible
for
git
Labs,
kubants,
Integrations
and
infrastructures
code
functionality
in
this
series
of
videos
likely
in
three
videos.
I
would
like
to
demo
you
how
gitlab
can
help
you
if
you
are
an
infrastructure
engineer,
an
SRE
or
if
you
are
a
platform,
engineer
who's
setting
up
automations
for
your
teams
or
if
you
have
a
good
platform
engineer
and
want
to
benefit
from
their
work.
A
What
we
want
to
do
in
the
end
is
to
allow
our
customers,
our
software
developers,
to
easily
deploy
their
workloads
to
staging
or
Dev
environment
and
to
production,
and
in
this
case
they
will
actually
deploy
this
Potato
Head
project.
But
that's
not
really
our
responsibility
that
will
be
around
the
platform
engines,
but
we
have
to
provide
that
environment
for
them
that
infrastructure
and
what
we
are
going
to
do.
A
A
First,
we
provide
you
a
template
and
that
you
can
build
upon
and
in
this
case
as
well,
what
we
provide
you
is
support
for
open
ID
tokens
and
with
gcp
instead
of
storing
a
Long
Live
token
somewhere
in
the
variable
in
gitlab,
that's
insecure,
and
then
you
have
to
take
care
of
what
you're
going
to
use.
Is
this
oidc
token
and
we
are
going
to
authenticate
with
gcp
using
this
token,
for
that
we
need
to
set
up
a
few
things
for
the
gcp
authentication
and
specifically
this
file,
the
Google
application
credentials.
A
A
Besides,
providing
you
the
template
to
run
terraform,
another
nice
thing
that
gitlab
provides
is
a
terraform
HTTP
backend
that
you
can
use
without
any
configuration
from
gitlab,
Pipelines
and,
of
course,
to
run,
or
this
Machinery
I
need
to
configure
several
telephone
variables.
As
you
can
see
here,
some
of
these
are
predefined,
the
ones
that
start
with
CI
underscore
While
others
are
actually
defined
as
cicd
variables
in
this
project.
Under
the
CI
CD
settings.
A
All
in
all,
once
I
have
the
oigc
set
up
and
I.
Have
this
very
simple:
transform
configuration
I
can
just
run
this
cell
phone
project
and
the
cluster
will
be
created
together
with
the
Caster.
What
we
want
typically,
is
a
standard
cluster.
You
could
create
a
separator
from
Project
to
to
install
flags
and
agent
okay,
in
this
case
I
added
to
the
same
telephone
project
for
Simplicity.
A
But
basically,
here
we
deploy
flux.
Flux
has
an
amazing
CLI,
but
if
you
prefer
to
manage
connections
through
the
futile
form
and
through
code,
then
this
might
be
your
approach
as
well.
We
will
use
a
gitlab
deploy
token
to
bootstrap
flux
and,
in
the
end,
flux
will
ride
back
to
to
this
gitlab
project.
It's
manifest
in
order
to
write
back.
We
actually
don't
need
only
a
deploy
token,
because
deploy
token
will
be
used
by
flux
in
the
cluster
to
retrieve
its
own
definition
from
gitlab.
A
A
This
almost
concludes
the
demo.
A
very
minor
addition
to
generic
environment
management
is
the
environment's
functionality
in
gitlab,
where
we
show
you
the
latest
Pipeline
and
its
status
and
in
case
of
kubernetes,
and
if
you
have
the
agent
configured,
you
can
actually
set
up
this
view
to
show
you
either
the
raw
cluster
or
subset
of
your
cluster.
In
this
case,
this
is
my
whole
classic
thread
to
be
smaller,
as
you
can
see
just
for
this
demo,
and
you
quickly
have
a
quick
overview
of
the
cluster
state.
A
The
sync
status
is
unavailable
because
I
didn't
Define
a
flux
resource
to
watch,
but,
for
example,
I
could
adhere
the
core
flux
controller
to
see
if
flux
works
or
not
or
doesn't-
and
this
concludes
demo
in
the
next
one
I'm
going
to
speak
about
how
platform
Engineers
can
benefit
from
using
gitlab
and
how
they
that
gitlab
can
help
them.