►
From YouTube: Kubernetes SIG K8s Infra - 20230816
Description
A
A
A
B
B
Yeah,
actually,
just
I
just
wanted
to
learn
more
about
this
stage
and
getting
involved
in
it.
So
though,
it's
1
30
in
my
time
it's
feeling
a
bit
sleepy
but
still
thought
about.
Let's
get
started
enjoying
the
meeting.
Yes,
I
am
here.
Thank
you.
Well,
I'm,
looking
forward
to
contributing
this
space,
yeah.
B
A
A
E
D
A
B
A
A
A
A
F
A
In
the
probability,
okay,
that's
about
it,
we
don't
have
folks
who
can
show
us
the
AWS
cost.
So
that's
fine,
okay,
I'm
gonna
stop
now,
unless
people
have
some
specific
things
that
they
want
to
look
at
one
twice:
okay,
okay,
now
any
action
items,
reviews
I,
don't
see
any
action
marked
from
the
previous
meeting.
We
skipped
one:
did
we
Skip
One?
No,
we
didn't
Skip
One.
A
D
Okay,
I
can
just
briefly
discuss
the
topic,
so
I
left
a
red
some
time
ago
on
slack
on
our
Kate
sequeline
Pro,
and
it
was
about
how
do
we
want
to
manage
githubs
in
between
our
clusters?
So
basically,
we
have
two
clusters
calorie
cluster,
in
which
we
test
things
and
the
production
one
which
is
a
build
cluster
that
is
connected
to
our
Pro.
D
So
basically
we
don't
expect
to
have
more
clusters,
so
we
are
not
looking
for
anything
highly
scalable,
but
we
want
to
yeah.
We
want
to
have
everything
in
GitHub,
so
I
listed
here
free
Solutions,
how
we
want
to
keep
our
manifest
so
that
we
can
yeah.
Basically,
the
first
one
is
about
duplicating
the
the
Manifest,
which
is
like
the
the
ugliest
one,
but
at
the
at
the
same
time
the
the
easiest
one
to
extend,
because
it
doesn't
require
any
knowledge
of
tools
like
customize
or
helm,
the
other
one.
D
This
is
the
one
I
started
with
the
customized
I
had
some
PR,
but
then
we
were
discussing
with
Arnold
that
that
might
be,
but
to
confusing
for
people
I
mean
we
were
losing.
The
idea
of
you
know
having
it
very
simple
because
yeah
this
this
requires
basically
knowing
how
customers
work
and
the
reaper
structure
is
specific
and
so
on
and
the
last
one
it
was
not
implemented.
But
we
could
also
leverage
like
an
umbrella,
Helm
charts
to
wrap
everything
and
then
provide
dedicated
values
for
each
of
two
clusters.
D
D
G
D
D
It's
convenient,
the
cost
is
not
that
high.
We
don't.
We
didn't
connect
to
brow.
So
it's
also
not
very
useful
in
terms
of
testing
jobs,
but
for
testing
some
eks
specific
things.
It's
pretty
convenient,
but
I
mean
we
could
probably
scale
it
down,
but
still,
if
we
want
to
have
it
be
able
to
deploy
it
at
any
time,
we
would
still
need
to
have
some
place
for
those
manifests.
G
A
D
If
I
can
add
something
to
the
complexity,
so
also
I
mean
you
mentioned
upgraded
so
on,
but
we
also
leveraged
terraform
to
provision
it.
So
testing
transform
script
itself
was
also
nice.
I
mean
it
was
nice
to
have
category
to
test
changes
before
applying
or
production.
Yeah
I
know
that
terraform
is
now
like
a
hot
topic,
but
let's
leave
that
aside.
A
G
G
We
have
a
lot
of
existing
automated
deployments
and
things
I
I'm,
not
sure
I
would
want
to
encourage
adding
another
CI
tool
like
we
already
have
to
maintain
proud
for
ourselves,
and
we
already
use
terraform
and
Bash
or
whatever,
and
to
the
point
of
terraform
being
a
Hot
Topic.
It
is,
and
we
have
lots
of
existing
usage
that
like
if
that
becomes
a
problem.
You
know
this
wouldn't
be
any
different.
We
have
a
bunch
of
other
places
that,
if
that
needs
addressing
it
will
get
addressed.
G
A
F
A
F
H
Our
backgrounds
I've
been
having
some
conversations
with
GV
last
couple
of
months
and
I
joined
some
of
the
kubernetes
game
from
meetings
and
in
addition,
that
I've
been
looking
for
a
big
relief
Shadow
program
as
well
in
the
past.
I
actually
want
to
apply
to
it
and
during
my
conversations
with
TV
we
said,
would
it
make
sense
to
have
a
conversation
around
possibility
of
having
a
similar
program
for
the
kubernetes
Sig
infra
as
well,
and
then
the
easiest
way
we
said
like?
H
We
can
perhaps
create
a
proposal
and
share
it
with
the
community
to
get
a
preliminary
feedback
see
if
it
is
a
viable
path
forwards,
and
if
it
is,
we
can
perhaps
put
more
time
on
it.
But
today,
I
just
want
to
share
the
comment
with
you
and
get
your
initial
feedback
coming
weeks.
And
then
we
can
bring
this
topic
again
and
have
a
longer
conversations
if
it
is
deemed
valuable.
A
I'm
very
supportive
of
this.
We
need
to
do
this
and
you
know
the
information
and
knowledge
gets
pulled
and
it's
it's
hard
to.
We.
We
end
up
relying
on
a
few
people
to
do
this
for
various
reasons
car
you
know
earning
Karma,
but
also
you
know
making
sure
that
only
a
few
people
can
touch
the
really
sensitive
stuff
and
things
like
that.
But,
yes,
we
need
to
grow
the
pool
of
people
who
who
can
come,
come
on
board
and
help
us
out.
A
I
think
there's
a
lots
of
lessons
that
that
we
can
learn
from
their
experience
that
we
can
roll
into
this.
So
I'm
definitely
supportive
from
from
hey.
We
need
to
do
more
of
this.
We
need
to,
and-
and
one
one
caveat
that
I
have
is
people
the
people
who
are
coming
in
need
to
know
that
this
is
like
a
long-term
commitment
and
not
like
they
can't
just
vanish.
A
They
can't
do
hey.
This
is
a
three-month
program.
I'm
gonna,
be
here
for
three
months
and
then
I'm
gonna
We
invest
time
and
effort,
and
it
is
only
useful
if
people
are
going
to
be
sticking
around
for
a
long
time.
Yes,
individuals
might
have
so
this
that's.
Why,
like
I,
hesitate
to
do
like
a
LFX
mentoring
program
around
this,
because
then
that
is
like
calendar
time
specific
time,
and
you
know
people
are
gone
as
soon
as
that's
on
same
with
the
release
team.
A
All
right,
there's
absolutely
no
guarantee
that
people
are
going
to
be
around
so
I.
Don't
know
how
to
get
commitment
from
folks
that
they're
they're
going
to
be
around
that
that
and
we
will
have
to
expect
attrition
as
well.
Just
because
you
know
life
comes
at
you
fast
right
and
you
know
things
change
as
well,
so
I'll
stop
talking
and
let
others
have
a
turn
go.
Go
ahead.
Bob.
I
I
This
will
probably
be
less
of
an
issue
too
in
terms
of
potential
people
that
aren't
as
committed,
because
we're
going
to
be
being
more
aggressive
with
the
like
org
cleanup
and
we've
gotten
more
aggressive,
I
shouldn't,
say
more
aggressive,
but,
like
you
really
have
to
demonstrate
more
of
a
commitment
before
becoming
an
org
member.
Now.
G
G
I've
thought
about
this
problem
a
lot
and
it
seems
like
more
or
less
like
what
Bob
is
saying.
The
thing
that
the
thing
that
seems
to
work
is
just
sort
of
observing
people
that
have
been
repeatedly
showing
up
and
then
starting
to
like
help
them
move
up.
I
think
we
could
do
with
more
of
a
program
for
in
a
structured
way
like
you've,
been
people
who've
been
participating
in
the
Sig.
G
B
G
Think
that
if
you
can
get
people
to
to
to
show
that
they're
like
committed
and
invested,
that
we
definitely
have
a
gap
in
following
up
with
those
people
and
and
making
sure
that
we're
moving
them
into
to
owning
things
and
whatnot,
and
there
is
room
for
actually
mentoring.
Sig
testing
did
open
call
for
chairs,
but
we
kind
of
did
somewhere
in
between
this,
where
we
didn't
really,
it
was
kind
of
a
very
low
time
commitment
thing
until
folks
had
been
participating
for
a
while.
I
One
other
quick
comment
on
actually
hitting
org
Members
First
for
potential
candidates.
The
most
recent
customized,
like
Mentor
cohort,
was
limited
to
order.
Member
only
and
there
was
like
I
think
it
was
like
around
100
people
applied
and
they
got
it
down
to
I
think
it
was
around
25
candidates,
but,
like
all
of
those
actually
looked,
you
know
pretty
solid
for
going
into
this,
and
most
of
those
people
do
understand
the
type
of
types
of
things
being
asked
of
them.
H
It's
just
it's
some
of
the
comments
you
made.
Actually
these
are
things
that
came
up
during
my
conversations
with
GP
as
well
the
old
member
topic
and
I.
Think
like
again,
even
though
I'm
learning
about
Community,
it
makes
a
lot
of
sense
to
me
because
infrastructure
things
are
sensitive.
Things
like
it
requires
people
to
you,
know,
have
access
to
certain
resource
and
which
might
have
you
know
risked
or
Community,
as
I
saw.
That
is
something
I
can
work
with
GV
to
incorporate
into
the
proposal.
H
In
addition
to
that
about
the
time,
commitment
and
this
proposal
was
heavily
influenced
by
the
release
Shadow
program,
but
because
of
that
reason
we
actually
put
a
minimum
two
release
Cycles.
As
you
know,
the
term
for
the
shadow
shuttles
that
can
be
adjusted
as
well
to
see
you
know,
the
first
cycle
could
be
to
learn
the
community,
the
people
who
are
doing
good
work
and
complete
on
going
up
and
upcoming
work,
so
they
can
become
there
with
all
these
things
and
during
the
second
release
cycle,
they
can
actually
perhaps
start
becoming
more.
H
You
know
into
the
details
and
start
and
some
contributions
because
it
is
like
challenging
to
you
know
even
to
understand,
what's
happening,
what
is
used,
what
is
required
and
so
on.
So
that
is
what
we
put
there,
but
that
can
obviously
be
changed
in
addition
to
that,
we
put
something
called
area
pokes
based
on
the
conversations
we
have
been
observing,
like
public
clouds,
reporting
and
metrics
they
to
cost
management,
GIC
icdm
testing.
H
So
this
could
be
different
types
of
roles
based
on
you
know
the
interesting
individuals
and
their
you
know,
competence
and
experience,
but
what
I
am
hearing
this
made
sense,
so
we
can
continue
working
with
this
and
obviously
we
need
to
sort
of
conversations,
but
it's
great
to
hear
positive
feedback
about
this
I'm.
Sorry,
mentioning
I,
see
your
Hunter.
G
The
release
Shadows
really
has
the
benefit
of
there's
like
very
structured,
regular
things
that
need
to
occur
versus,
like
you
know,
back
when
we
were
still
manually
applying
DNS.
That
was
just
ad
hoc
as
needed
when
there
is
a
new
entry
and
now
that
something
like
that
is
automated.
The
few
people
that
have
access
to
it
are
rarely
touching
it
I
I'm
a
really
big
proponent
of
in
most
cases.
G
If
you
want
to
document
something
like
how
to
work
on
a
project,
you
should
you
should
document
it
instead
of
instead
of
having
meetings,
because
then
everyone
can
benefit
from
it
and
it's
a
it's
a
Perpetual
resource
so
like,
for
example,
in
kind
when
I
wanted
to
grow.
Maintainers
I
spent
my
time
on
writing
a
contributor
guide
and
documenting
some
issues.
H
Yeah,
that's
yeah.
You
need
to
put
something
there,
so
we
kind
of
told
like
okay,
if
you
can
sync
this
program's
applications
with
release,
Cycles
done
yeah
avoid
you
know,
onboarding
people
when
the
release
comes
in,
so
the
applications
start
after
the
release
is
done.
It's
that
way.
It's
not
just
like
happening.
Vanderlies
happens
to
the
initial
starts,
it's
kind
of
to
protect
the
release
work
by
not
introducing
or
unnecessary
changes
to
infrastructure,
but
yeah
that
that
is
up
for
conversation.
C
Would
it
not
also
be
possible
to
have
like
that?
You
say
we
have
these
mental
programs
that
that
are
around
and
are
kicking
up
like
once
a
year,
or
something
like
this-
that
you
basically
use
this
as
a
as
a
generalized
time
frame,
so
to
decouple
it
basically
from
the
from
the
release
cycle,
because
the
S
Ben
already
said
I
mean
if
the
Elisa
is
coming
up.
G
A
A
G
Yeah
I
feel
like
the
biggest
thing
that
I
need
like
going
back
to
the
registry.
Again
is
just
so
it's
just
some
isn't
necessarily
something
to
teach
people
I
think
most
people
have
enough
that
work
in
a
space
have
enough
experience
to
poke
at
these
things
or
or
it's
documented.
It's
the
building,
the
trust
with
people
that
just
requires
regularly
showing
up
I'm,
not
sure
how
to
do
more.
For
that.
G
But
wherever
possible,
we've
tried
to
automate
things
and
and
not
have
people
taking
manual
actions,
because
that
scale's
better
and
that's
something
that
I've
even
have
feedback
for
the
release
process
like
we.
Finally,
automated
the
release
fast
forward
like
building
things
so
that
there
aren't
so
many
humans
and
that
it
is
just
things
and
git
and
anyone
can
can
read
and
interact
with
that,
and
we
just
need
a
few
people
with
break
glass.
We
probably
don't
actually
want
to
substantially
grow
that
group
because
of
the
sensitive
access.
A
F
A
That's
what
I
was
saying
right
like
what
are
the
activities
that
we
need
to?
If
we
have
to
make
that
so
we
can,
we
can't.
We
can
definitely
not
do
September
right,
like
the
earliest
we
can
do
is
probably
you
know
when
all
of
us
come
back
from
the
Christmas
New
Year
vacations,
so
best
case
scenario
would
be
second
half
of
Jan
right
like
that's.
A
When
we
can
start,
then
the
question
is
like:
what
do
we
need
to
do
before
that,
so
when
people
do
show,
when
we
do
roll
out
a
program
and
announce
to
people
that
hey?
Secondly,
you
know
second
half
of
January,
we
are
going
to
do
applications
and
then
February
we're
gonna
get
started
with
this
program
and
like
so,
we
need
to
figure
out
like
how
many
people,
what
can
we
do
with
them?
What
are
the
activities,
so
we
have
to
go
about
thinking
about
this.
A
Also
I
think
we
had
a
bunch
of
things
and
you
know
I
think
we
are
wrapping
up
a
bunch
of
things
now
right,
like
so
yeah,
so
we'll
probably
have
to
think
about
like
what
is
the
next
set
of
things
that
we
want
to
think
about
right
in
some
ways
you
know
when
Mario
and
Patrick
came,
it
was
like.
Oh,
we
are
doing
eks,
which
is
new,
so
it
was
easier
to
you
know
let
them
free
on
some
new
areas
where
we
needed
work
done.
E
Yes
sure,
hello,
everyone,
I'm
the
open
source
program
manager
at
AWS
and
I'm
the
one
in
charge
of
the
karate
program,
probably
I,
should
bring
good
news.
First,
the
20,
the
250k
credit,
has
already
been
loaded
to
the
account.
So
we
really
appreciate
the
great
work
that
whole
team
is
doing
for
migrating.
E
The
kubernetes
infrastructure
to
Amazon
and
then,
like
I,
would
love
to
work
with
the
community
closer
to
really
understand
our
whole
plan
of
the
workload
to
AWS,
so
that
we
can
have
better
understanding
about
budget
and
then
that's
the
reason.
I
put
together
the
estimation
that
I
sent
out
one
two
weeks
ago,
and
then
there
were
like
3.5
pointed
out
and
I
think
the
biggest
puzzle
to
me.
There
actually
is:
do
you
want
me
to?
Does
it
have
like
a
question?
Does
anyone
has
have
you
already
seen
the
email
I
shared.
E
E
Oh
like
it,
if
we
look
at
this
area,
there's
the
raw
data
from
January
to
June,
that's
the
detail,
invoice
information
I
put
there
and,
like
I,
said
all
those
invoices
they
were
sent.
I
think
that's
to
the
infrastructure
account.
So
if
you
want
to
look
into
the
invoices,
you
should
have
access
somewhere.
A
E
And
then
well,
like,
like
I,
said
I
think
the
biggest
puzzle
to
me.
Actually
is
this
number
the
ec2
AWS
ECT
amount
because
it
was
tripled
kind
of
from
March
to
February,
and
then
it
dropped
back
in
April
and
then,
like
the
consistency,
actually
continues
from
a
protein.
So
to
me,
this
one
is
the
biggest
puzzle
and
then
I
wonder
where
or
what's
the
factor
that
drives
there
and
also
it'll
be
great
if
everyone
can
shine
some
lights
here,
as
we
do.
The
analysis
like.
A
C
Went
so
high,
I
I
think
this
was
the
time
when,
when
Marco
and
Patrick
started
moving
the
pro
and
we
we
we
played
around
with
different
machine
types,
because
we
had
issues
there
and
I
know
that
we
that
we
scaled
up
different
different
machine
sets
so
I
think,
and
then
we
did
some
cost
optimization
where
we
said
like
we
can
use
specific
machine
types
better.
That
fits
the
cluster
and
this
was
around
March
to
April.
If
I
ever
remember
correctly,.
A
A
A
D
A
The
number
is
not
that
much,
so
we
should
be
fine,
I.
Think
the
the
total
itself
is
like
you
know,
not
too
much
yes,
but
we
we
can
watch
the
trend
and
see
where
it
goes.
But
in
to
your
question
what
is
coming
next,
we
have
two
two
sets
of
things
coming.
One
is
the
scalability
test.
The
scalability
tests
are,
we,
we
are
still
stabilizing
it.
We
have
one
CI
job
that
is
doing
500
node
testing
and
that
is
I'm
gonna.
A
Once
we
have
it
ready,
then
we're
going
to
turn
it
on
periodically
and
that's
when
that
money
is
gonna,
it's
gonna
burn
up
money,
so
that
is
one
the
other
one
is.
We
do
have
a
new
test
Suite
that
we
are
experimenting
with,
but
that
might
come
later.
So
scalability
is
going
to
come
first
and
then
some
other
things
are
going
to
come
after
that.
A
So,
like
I,
think
Arno
mentioned
that
we
are
constantly
turning
things
on.
So
we
do
expect
this
to
go
up
by
year
end,
but
it
is
still
under
a
million
for
the
year.
So
you
know
I'll
be
happy
if
you
push
it
to
just
past
million,
but
you
know
that
that's
probably
not
going
to
happen
I'd,
but
you
know
we
have
to
check
again
in
a
few
months.
A
A
B
E
G
I
I
there's
one
thing
that
we
need
to
look
at
in
the
future,
so
we
rolled
out
the
fastly
right.
I
just
want
to
see
these
people's
minds.
We
should
not
have
a
long
discussion
here
and
and
we're
not
going
to
solve
it,
but
something
for
people
to
be
thinking
about,
and
maybe
helping
at
some
point
when
our
note
gets
back,
our
no
primarily
launched
the
fastly
CDN
and
front
of
the
release
bucket.
G
However,
best
I
can
tell
it's
basically
just
a
pull
through
proxy
right
now
that
isn't
caching,
anything
that
is
going
to
have
to
be
fixed
if
we're
going
to
actually
migrate
to
fully
Community
bucket.
Behind
that
we
will
not.
We
will
want
that
to
actually
be
cached
from
what
I
can
tell
it's,
not
being
cached,
so
that's
going
to
need
fixing
and
then,
when
that's
fixed,
we
still
need
to.
A
G
Don't
I
do
not
have
good
visibility
and
I
can't
tell
you
like
how
much
of
that
is
because
it
because
people
are
just
hitting
the
bucket
directly
but
yeah
like
squinting
at
the
at
what
graphs
I
do
have
I,
don't
think.
We've
cut
the
bandwidth
at
all
and
just
the
behavior
of
the
end
point
and
the
discussions
around
the
size
of
things
so
I'll
go
file
an
issue
in
case
IO,
but
that
might
be,
that
might
be
a
fun
project.
To
look
at
I.
G
A
And
I
do
want
to
see
like
you
know
how,
if
people
are
using
the
new
Deb
and
RPMs,
and
you
know
how
is
that
going,
you
know
we
will
have
some
numbers
by
then
right,
like
the
release
was
just
yesterday
so
Rick,
do
you
want
to
share
some
some
of
your
numbers?
Do
you
want
to
screen,
share
and
show
us
how
far
you've
gotten
and
if
you
have
any
blockers-
or
you
know
something
to
talk
about.