►
A
A
B
A
A
C
A
D
C
A
C
A
I'm
open
of
doing
that.
The
thing
is,
if
it's
not
needed
urgently,
it
puts
probably
another
another
one
hour
or
two
hours
of
installing
it
and
updating
it
and
maintaining
it.
So
could
totally
do
it.
On
the
other
side,
I
was
thinking
of
another
thing:
we've
do
at
gitlab,
for
example,
for
like
mono
wrappers,
where
you
have
different
use.
Cases
to
fulfill
have
some
sort
of
detection
in
your
pipeline,
whether
you're
deploying,
for
example,
only
the
block
on
the
website
or
to
a
full
deployment
or
just.
B
B
So
I'm
using
a
similar
setup
for
my
personal
kubernetes
cluster
and
there
I
also
use
ansible
and
one
thing
with
ansible-
is
that
it's
a
python
tool
and
you
need
to
install
all
the
python
dependencies
to
run
it,
which
takes
a
little
bit
of
time.
So,
for
example,
in
our
ansible
directory,
we
have
this
requirements
yeah
the
requirements
txt,
where
we
tell
which
ansible
version
we
want
to
use
and.
B
Know
100
dependencies
or
something
that
are
all
installed
each
time
or
if
we
run.
If
we
run
this
in
a
gitlab
runner,
we
will
install
those
dependencies
every
time
which
is
not
nice.
Looking
at
the
runtime
of
the
ci
drop,
and
it's
also
not
so
nice
for
the
package
registry
pi
pi
of
python,
because
we
pull
those
packages
all
the
time
again
and
again,
which
is
a
little
bit
inefficient.
B
B
B
B
B
B
A
B
A
B
So
in
our
before
script,
we
have
to
do
a
little
bit
of
a
work
around
because
the
back
here,
the
ssh
key,
is
used
as
a
file
and
ssh
doesn't
like
it.
If
your
private
key
is
public,
readable,
and
so
it
will
not
use
this,
then
so,
let's
just
take
all
away
all
the
permissions
for
the
group
and
other
accounts
from
this
file.
So
we
can
actually
use
this
key
and
also,
let's
switch
into
the
subdirectory
ansible,
because
it's
the
directory
we
have
or
our
stuff
in
front.
B
B
So
I'm
curious:
if
this
will
even
work
with
the
shared
runners.
I
guess
we
have
to
look
it
up
a
little
bit.
What
we
can
do
if
we
can
use
some
text
to
use
a
shared
runner
that
allows
us
to
to
use
docker
and
docker.
We
will
see-
because
I
usually
run
this
in
those
headset
autoscaling
runners
we
do
a
while
ago
and
those
just
work
with
docker,
and
I
suspect
that
this
will
not
work
out
of
the
box
with
gitlab
runners.
If
anyone
knows
how
to
use
docker
in
shared
gitlab.
A
Is
there
are
pr
pre-built
templates
available?
If
you
want
to
use
docker
and
docker?
Let
me
see,
because
I've
been
creating
a
pull
request
around
this
as
well
for
updating
it
for
the
main
branch,
and
I
might
have
an
example
in
a
test
playground
repository
which
you
can
just
copy
paste
or
somehow
copy
paste.
A
A
A
B
D
D
A
B
A
A
B
B
And
then
we
just
want
to
want
to
run
pip,
which
is
already
available
in
the
python
image,
because
we
don't
have
any
cache
available
in
our
runner.
We
can
also
just
disable
it
for
pip
and
install
everything
from
here
like
ansible
and
the
h
cloud
package,
and
if
you
remember
what
we
did,
I
don't
know,
maybe
months
ago
was
also
use
ensemble
galaxy
to
install
those
dependencies.
B
B
I
think
we
can
add
here
right
changes,
because
we
only
want
to
do
this
for
some
specific
files,
because
we
do
it
each
time,
then
the
joke
is
on
us,
because
then
we
don't
reduce
our
amounts
of
yeah
installing
python
dependencies,
but
if
we
do
it
only
if
there's
stuff
changed
in
yeah,
we
can
also
remove
this
one,
because
we
don't
have
this,
but
only
if
we
change
the
docker
file,
the
requirements
txt
or
the
requirements
amplify
only
then
we
want
to
build
this
new
image.
Otherwise
we
just
want
to
use
the
existing
one.
D
D
D
B
B
Trigger
the
ci
run
over
the
web
interface,
then
I
think
the
changes
will
not
be
evaluated.
It
will
just
trigger
all
the
time
if
I
remember
correctly,
there's
something
in
the
docs
about
this-
that
it's
yeah,
that
this
only
works.
If
you
have
a
merge
request
or
yeah
only
if
you
refer
to
a
commit
like
if
it's
a
push
event
or
match
request
event,
I
think.
B
D
A
If
it
still
works
with
rules,
it's
more
like
a
programming
language
approach,
I
would
say,
but
I
think
there
are
some
patterns
you
cannot
really
catch,
which
you
can
with
only
and
accept.
So,
for
now
both
will
stay.
It's
not,
I
would
say
the
best
way,
because
it's
two
two
ways
to
do
it
right,
but
still
over
time
we
will
find
a
way.
A
The
current
approach
for
making
main
the
default
git
branch
is
to
use
only
except
with
variables,
which
is
also
a
possible
thing,
so
you
can
do
easy
comparisons
with
ci
variables
in
in
only
and
accept
see.
I
need
to
find
the
merch
request
for
my
docker
build
template
which
references
to
epic,
where
this
is
being.
A
A
A
B
A
Me
it's
like
I'm
on
I'm
on
fire,
which
means
I'm
super
busy,
and
I
don't
know
when,
when
when
work
stops
yeah
I
know
when
I
moved
to
the
couch
and
continue
watching
westworld,
which
I
kind
of
missed
in
the
past
five
years.
But
yeah
I've
been
I've
been
quite
busy
and
I'm
toying
you
can't
you
can
set
the
emoji
as
a
busy
state
or
as
a
state
in
your
profile,
so
yeah,
basically
modified
by
state
yeah
on
on
the
upper
right
hand,
corner.
A
A
A
B
B
B
Apparently
I
tested
something
for
this
two
weeks
ago.
Already,
that's
interesting,
no
memory
of
that
okay.
Anyway,
we
have
this
image
here
now,
which
means
we
can
use
it
and
I'm
pretty
sure
that
this
job
will
trigger
each
time
we
hit
the
run
pipeline
button
now,
so
I
propose
that
for
now
we
just
disable
it
because
it
will
cost
us
five
and
a
half
minutes
each
time
we
click
on
run
and
then
in
a
later
stage,
when
we
change
our
pipeline
a
little
bit
to
run
for
each
push.
B
A
B
A
Means
it's
a
template
import
me.
I
would
yeah
in
my
world.
I
would
rename
extends
to
import
but
different
story
kind
of
used
to
what
we've
designed
with
our
singer,
2
in
the
dsl
so
yeah.
If,
if
the,
if
the
configuration
doesn't
tell
you
by
the
keyword,
what
it
does,
I
tend
to
name
objects
and
shop
names
in
a
way
that
I
can
immediately
see
what
it
does.
B
Yeah,
that
makes
sense,
so
we
want
to
run
our
ansible
playbook
and
we
want
to
use
our
existing
ssh
key,
because
we
know
that
this
key
has
access
to
all
our
machines,
because
this
is
the
same
key
we
deploy
with
terraform
and,
I
think
yeah.
It's
called
main
yammer,
it's
our
playbook
and
yeah
in
the
diff.
We
can
completely
skip
the
cube
conflict
jumps
and
we
run
it
in
check
mode.
B
And
I
think
it's
also
like
this-
I
don't
think
we
need
the
div,
because
if
I
remember
correctly,
we
added
this
in
our
answer-
configuration
but
yeah
over
here
we
already
said
always
display
a
div,
that's
nice,
and
why
we
skipped
the
cubeconfig
tag
is
because
in
this
row
we
pull
the
cubeconfig
to
our
localhost,
fix
the
hostnames
in
it,
and
this
way
have
a
working
cubecontract
to
talk
to
our
deployed
cluster.
But
in
this
stage
we
don't.
We
neither
need
this
cube
config
yet,
nor
do
we
have
it
because
there
is
no
cluster
deployed.
B
B
B
B
B
B
B
B
Interesting,
we
need
to
decide
where
we
store
this
cube
config,
because
what
we
want
to
do
is
to
store
this
cube
contract
as
an
artifact.
So,
as
a
user,
we
can
download
it
from
our
gitlab
interface
and
connect
to
this
created
cluster,
but
I'm
not
entirely
sure
how
I
thought
we
would
do
that
anyway.
What
we
need
is
an
additional
in
additional
variable
where
we
overwrite.
B
B
C
B
A
C
B
B
So
we
can't
just
like
download
this
cube
config
file
in
the
home
directory
of
the
current
user
or
something.
Instead,
we
have
to
put
it
somewhere
where
it's
in
the
scope
of
our
repository
and
only
then
we
can
use
it
as
an
artifact
and
we
can
use
the
same
variable.
We
used
a
few
times
before
ci
project
directory,
because
that's
already
like
the
directory
of
our
current
git
repository,
so
everything
in
there
is
available
if
we
want
to
as
an
artifact,
and
so
we
just
want
to
put
our
q
config
file
in
there.
B
Let's
call
it
dot,
cube
config
and
what
happens
down
here
in
our
keep
conflict
drop,
which
I
probably
like
confu,
which
is
a
little
bit
confusing,
because
I
was
thinking
about
it
while
talking
so
that
might
not
have
been
obvious.
But
what
we
tell
ansible
here
is
to
override
this
variable
with
the
contact
content
of
this
variable.
B
A
A
B
B
A
B
C
A
B
B
A
A
B
B
A
A
We
can
talk
it
over.
The
reason
I
was
late
today
is
I'm
running
a
blog
post
around
using
check
you
and
jason,
and
I've
also
found
a
way
to
use
this
d8
api
endpoint
for
ci,
linking
or
for
linting
a
gamma
configuration
from
the
cli,
and
I
wrote
a
github
for
it
on
monday
and
the
blog
post
is
about
to
be
published.
Then
I
need
to
do
a
recording
for
the
gitpod
community
day
next
week,
then
I
have
a
dockercon
talk.
I
have
an
slo
conf
talk.
A
B
A
B
Yeah,
I
use
it
a
little
bit
to
create
the
namespaces
and
network
policies
in
my
kubernetes
cluster,
but
I
wouldn't
say
I
have
the
qualification
to
like
give
an
introduction
to
it.
I
mean
we
can
figure
it
out
together,
but
it's
not
I'm
just
tried
it
out
a
while
ago
and
since
then
I'm
using
it-
and
I
don't
really
know
if
what
I'm
doing
is
the
way
you
are
supposed
to
use
it
and
everything.
A
Yeah,
maybe
if
we
cannot
find
someone,
we
could
do
it
the
other
way
around,
like
we
kept
learning
rust
together,
not
the
two-hour
edition,
but
like
reading
the
tutorial
and
trying
things
out
and
then
and
then
like
see
how
things
are
going,
because
I
I
would
love
to
encourage
everyone
to
like
contribute
to
the
session
and
not
just
staring
at
the
screen.
Saying
press
this
button,
but
maybe
changing
roles
and
saying
hey
one.
One
does
decoding
and
four
others
look.
A
Okay,
that's
a
it's
an
austrian
building
place,
but
a
construction
place
construction.
Yet
whatever
it's
super
hard
to
translate
in
english,
but
yeah,
maybe
like
try
something
else
out
of
the
sudden
and
you
have
little
experience
and
if
we
have
a
success
together
it
it
weighs
more
than
it
weighs
it
weighs
a
lot,
not
comparison,
not
comparing
anything.
A
A
A
B
D
A
Team
calendar
yeah,
we
kind
of
populated
that-
and
I
think
the
reminder-
oh
yeah,
and
on
friday
there's
a
session
around
gitlab
commit.
So
if
you
want,
if
you
want
to
provide
your
story,
I
would
encourage
you
to
just
talk
about
this
setup,
for
example,
or
what
we've
been
learning
in
the
past
or
some
other
experiences
you
might
want
to
share
and
on
friday,
there's
a
session
hosted
by
tron
on
creating
a
good
talk,
help
with
the
storyline
coaching
and
other
things
which
I
would
recommend
to
attend.
A
C
A
That's
about
it
and
I'm
thinking
about
using
the
same,
not
the
same
calendar
but
similar
approach
of
creating
our
own
team
calendar.
I
just
need
to
figure
out
how
this
works
with
permissions
and
such
because
I
cannot
share
the
zoom
url
in
public,
so
this
needs
to
be
a
separate
invite,
but
for
the
for
the
topics
and
for
the
ideas
collection,
we
can
totally
use
the
public
calendar.