►
From YouTube: 2022 02 22 Jenkins Infra Meeting
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
Perfect,
hello:
everyone
welcome
to
the
jenkins
infrastructure
weekly
online
public
meeting.
We
are
the
22
february.
2022
today
is
a
an
is
it
anagram
you
can
take
the
date
from
left
to
right
or
right
to
left,
hey
nice,
okay.
So
today
we
have
mark
stefan
team
under
here
with
us
who's
missing.
Here,
stephen
I'm
here,
nice
first
announcements.
A
B
C
C
D
A
C
B
A
A
Okay,
I
don't
have
any
other
announcement
so
propose
we
start
straight
to
it.
So,
first
of
all,
what
did
we
do?
Congrats
survey
for
the
work
on
digital
ocean.
We
are
now
using
digitalocean
machines
in
productions.
A
D
A
D
B
B
D
B
A
A
List,
let's
say
coast
measure,
cost
consumed
and
also
do
you
mind
updating
the
ci
jenkinso
documentation.
I
will
give
you
the
link,
the
page
where
we
list
all
the
agents
and
labels
available
for
developers
to
add
the
two
new
label.
Kubernetes
labels
that
you
added.
So
they
know
they
can
opt
in
or
opt
out.
If
they
start
to
see
issue
and
there
they
will
be
autonomous
for
continuing
working.
If
we
don't
respond
immediately.
D
A
And
then,
yes,
we
have
digital
ocean.
We
need
to
improve
and
nurture
the
sponsorship.
A
C
C
A
C
A
A
So
my
proposal,
that's
a
proposal,
so
you
can
say
no,
you
can.
You
can
stop
me,
but
my
proposal
is
start
from
an
empty
repository
again.
We
can
always
use
git
to
consult
the
older
knowledge
if
we
need
to-
and
we
start
from
scratch
and
we'll
start
to
add
terraform
resources.
So
the
new
private
cluster
to
be
created,
we
migrate
everything
then,
and
then
we
start
either
import
existing
resource
or
create
new
ones.
A
B
A
Yep,
the
upcoming
resources
I
see
in
the
short
term
are
the
price,
the
new
private
cluster.
I
guess,
instead
of
the
temp
that
we
have
right
now,
the
dns
reference
to
the
caa,
dns
recording
and
the
new
mysql
database
for
writing.
That's
not
priority,
but
that's
a
good
exercise
to
get
started
with.
A
So
that's
the
status
on
azure
on
the
area
of
our
dependencies
to
be
kept
up
to
date.
It's
like
a
never-ending
topic,
of
course,
thanks.
Stefan
for
the
effort
on
keeping
all
the
hashicorp
dependencies
updated,
you
drove
that
change.
So
terraform
there
are
four
modules:
terraform
provider
and
packer.
All
these
are
shikop
tools
are
kept
up
to
date,
thanks
to
update
cli
and
stefan's
work
and
tracking.
A
A
A
Okay
continuing
then
there
has
been
a
request
from
security
team
around
account
up
key
cloak.
So
it's
it's
not
the
first
time
that
this
request
is
emitted
to
the
jenkins
infra
team.
It
has
been
four
months
season
years.
A
A
Key
cloak
is
the
same,
except
that
key
cloak
allows
us
to
have
a
public,
frontend
and
admin
backends
for
administration.
It
provide
way
more
feature
and
it's
not
on
homemade
application,
like
account
app,
so
the
risks
are,
let's
say
a
bit
lower
using
that
and
that
project
was
never
finished.
There
were
some
blockers
and
I
will
need
help
from
the
people
who
worked
on
that
in
the
past.
A
A
I've
listed
here
on
pure
infrastructure,
the
three
main
blockers
or
almost
blockers,
a
step
that
we
need
to
fix
in
order
to
fully
switch
out
from
account
up
and
dump
that
project
forever,
not
that
it
was
really
useful,
but
key
cloak
is
safer
as
for
today
and
for
the
future.
A
So
I
don't
know
if
there
are
other
elements
that
we
did
not
track
on
that
list,
things
that
you
would
remind
mark
or
team
or
the
others.
B
D
A
D
That's
one
question,
because
there
are
some
hurdles
with
some
yeah.
I
don't
know.
A
Dex
wasn't
providing
airbag.
Dex
was
only.
D
D
D
A
A
I
don't
know
if
the
board
had
time
to
validate
that
change
proposal.
I
don't
remember
form
it
was
occurred
for
vedic.
That
means
that
the
county
clock
sits
in
the
middle
of
these
two
areas.
So
that's
why
we
should
ask
them,
but
we
might
expect
that
it's
also
our
responsibility
to
define
that.
So
we
have
to
ask
them
for
what
are
the
requirements
from
their
point
of
view,
so
we
need
them
to
act
as
consultant
and
not
as
doers.
A
Yes?
I
agree
thanks
mark,
so
I
don't
know
if
anyone
is
willing
to
work
on
that
topic,
if
let's
keep
it
by
default,
I
plan
to
to
keep
it
as
infrastructure
resources.
Since
it's
my
security
new
brand,
newer
responsibility,
but
we
need
to
finish
the
private
azura
ks
thing,
because
we
need
a
private
cluster
to
run
a
key
clock
with
it.
A
A
A
A
So
if
they
are
okay
for
that,
we
just
we
only
have
to
proceed.
That
will
be
mainly
adding
error
data
for
that
specific
machine.
That
should
be
work
with
the
same
image
and
some
config
exception.
I've
listed
what
is
needed.
Two
elements
are
as
code.
We
might
need
to
ask
them
to
insert
a
credential
because
credentials
are
manually
managed.
B
A
Okay,
thanks
yep.
Let
me
write
this
down.
B
A
I
think
the
runebook
might
have
the
definition,
I'm
sure
yeah.
If
it
does
once
cool,
I
have
access
to
search
ci
by
default
so
worst
case.
I
can
always
compare
other
settings
to
mine,
so
we
can
find.
A
A
But,
okay
thanks!
So
stefan
that
will
be
your
next
task.
We
don't
have
an
help
desk
issue
for
this
one,
because
search
ci
is
a
kind
of
let's
say
area
that
can
go
some
city
very
quickly.
So
that's
why
we
have
to
keep
talking
internally.
A
A
Convinced
yeah,
it's
just,
they
are
okay
for
us
to
speak
it
publicly
on
that
meeting.
So
I
agree
with
steam
that
should
be
on
help
desk,
but
we
never
know
so
better
to
ask
first
better
safe
than
sorry
on
that
area,
but
yeah
you're
a
correct
team.
I
agree
with
you
that
should
be
public
easier
to
track
and
to
delegate.
B
Yeah,
I
think
you
might
have
added
cert
ci
to
most
people
anyway.
I
think
he
thinks
the
conflict
to
be
the
same
for
all
the
files
in
december
2021
on
the
30th
of
december.
Yes,
yeah,
so.
A
A
A
Okay,
sorry,
I
didn't
hear
your
the
beginning
of
your
sentence.
Maybe
there
is
also
an
ongoing
issue
from
security.
Since
a
few
weeks
around
disabling
anti-spam
for
the
search
team,
I've
put
the
link.
That's
a
help
desk.
A
Just
a
reminder
mark
so
at
around
christmas,
I
think
after
oh
in
january,
a
few
weeks
ago,
you
blocked
thanks
a
lot,
an
iep
at
epa
table
level
on
the
sea
agent
inside
a
virtual
machine
because
they
were
spamming
cigar.
It
was
done
at
the
linux
scanner.
A
C
I've
done
nothing
since
then.
It's
embarrassing
to
admit
that
I've
done
nothing
at
all
since
then
that
ip
is
still
blocked,
and
we
just
need
to
take
an
action
to
probably
by
now
unblock
it
and
watch
that
it's
not
an
issue
and
get
rid
of
that
single
iptable
hack.
That
I
put
in
assume
you
just
restart
iptables.
B
C
B
C
A
B
D
We
reconfigured
it's
kevin,
who
showed
us
the
send
by
the
mailing
list
are
sent
by
the
user
and
it's
apparently
configured
to
be
sent
by
the
mailing
list.
So
about
that
I
don't
see
what
we
can
do
about.
E
A
So
can
you
share
the
link
on
rc
or
in
the
meeting?
Not
it's
just
to
so.
If
we
see
that
again,
can
you
share
knowledge
and
elements
on
that
issue,
so
yeah
anyone
could
take
it
or
start
studying
it.
It's
not
a
big
priority,
but
it's
really
annoying
for
most
users
facing
that.
So,
if
we
can
anyone
with
email
knowledge
could
help.
That
could
be
great.
A
So,
let's
say
next
big
thing:
once
most
player
has
been
done,
will
be
enabling
a
custom
irc
channel
used
for
notification,
maybe
multiple,
depending
on
the
topic.
I
still
don't
know,
that's
another
part
where
I
don't
know
anything
but
rv.
On
tim,
you
seem
to
have
worked
on
jenkins
in
front
notification.
Irc
channel.
D
A
D
A
D
A
A
Stuff
are
applied
and
it
received
message
when
a
puppet
agent
apply
it's
puppet,
manifest
on
a
given
vm
and
that
machine
is
almost
not
manager's
code,
it's
kind
of
hidden
somewhere,
and
this
is
also
where
the
I
underst
I
understand,
based
on
the
recent
feedbacks
that
that
machine
is
responsible
for
connecting
to
irc
and
sending
messages.
So
that's
where
we
would
have
to
interact,
maybe
moving
the
the
puppet,
but
from
there
I
I
don't
know
it
works,
so
we
will
have
to
to
diagnose
at
least
the
both
of
us,
but
about
notification.
A
A
D
No,
I
was
I
was
thinking.
We
can
also
have
a
specific
channel
in
in
our
proprietary
slack,
but
complementary
to
this
irc
notification.
A
And
as
team
as
tim
and
daniel
suggested
during
the
past
days
and
weeks,
we
might
want
also
jenkins
release
notifications
that
will
receive
messages
from
release.ci
to
help
or
maybe
do
jenkins
release
channel.
I
don't
know,
but
when
a
weekly
release
starts,
it
sends
the
first
message
and
when
it's
finished
it
sends
another
message
at
least
and
same
for
lts,
so
that
will
be
part
of
the
release
process.
A
A
And
also
there
has
been
issues
reported
by
raul
borossa.
One
of
our
contributors,
where
at
the
credential
github
use
for
infra
report,
is
lacking.
Some
permissions
on
some
plugins
resulting
on
the
maintainer,
the
correspondence
between
plugins
and
maintainer
and
plugins
changing
cyo
not
being
correct
on
some
cases
yeah.
It's
the.
D
A
E
I
I
took
on
myself
to
add
online
92
an
option
to
handle
the
new,
in
case
of
spamming,
on
the
kernel
to
use
the
fail
to
ban
to
automatically
lock
eyepiece.
If
you,
if
you
want,
you,
can
erase
that
or
not,
but
that's
90.
E
A
D
A
E
Failure,
man
is
watching
your
log
files
and
is
taking
an
intensive
action
depending
on
what
you
tell
him
to
do.
For
example,
if.
B
E
Fail
on
on
three
or
four
times
to
log
using
the
ssh
team
on
ssh,
it
will
be
locked
out,
but
we
can
do
whatever
we
want,
as
a
declaration
for
failed
to
ban
to
ban
an
ip.
E
A
B
B
E
E
E
Crowd
sharing
that
we
need
to
make
sure
is
that
the
sharing
of
the
ips
is
compliance
with
any
google.
A
Okay,
interesting,
I
didn't
know,
I
knew
failed
to
ban
for
ssh
it's
installed
on
most
of
the
cloud
server
and
works
yeah.
A
D
A
C
Sorry
for
one
one
old
topic,
the
the
2.336
release
is
not
complete,
at
least
in
the
sense
that
I
can't
see
linux
installers.
Yet
so
I've
got
to
do
some
more
research.
Nothing,
no
actions
from
others
require
yet.
But
when
I
look
at
when
I
attempt
to
do
an
install
of
a
weekly
on
my
on
my
test
machines,
the
weekly,
as
far
as
I
can
tell,
is
not
visible.
Yet
it's.