►
From YouTube: Kubernetes SIG CLI 20220713
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
and
thank
you
for
joining
us
for
the
July
13th
kubernetes
6
CLI
bi-weekly
meeting,
my
name
is
Eddie
zaneski
and
I
will
be
your
host
today
or
mache.
Someone
will
quick
reminder
that
this
meeting
and
all
meetings
abide
by
the
cncf
code
of
conduct.
So
please
be
excellent
to
each
other
and
to
kick
us
off.
We
have
two
announcements
with
dates:
code
freeze
is
August,
2nd
wow
that
is
coming
up
fast
and
release
day
is
August
23rd,
any
other
announcements
from
folks.
A
That
takes
us
into
introductions.
Do
we
have
any
folks
that
are
new
to
the
call
or
haven't
been
here
for
a
while?
That
would
like
to
introduce
themselves.
A
A
So
a
couple
of
I
don't
know.
Last
week,
maybe
somebody
is
came
in
and
said
that
they
were
noticing.
It
was
like
a
huge
wait
time
for
trying
to
find
out
where
to
go
for
using
Cube
Kettle.
A
When
there's
a
lot
of
crds
this
person
they're
the
one
that
said
it,
so
they
work
or
work
on
the
cross-plane
project
Downstream,
and
so
they
put
together
a
PR
to
address
it
and
the
main
thing
to
note
I,
don't
understand
why
I
don't
know
who
lava
lamp
is
Daniel
I
think
is
their
name
I,
don't
understand
the
desire
to
use
cryptographic
hashes
here
because
it
feels
pointless,
but
we
can
discuss
that.
A
You
know
whenever,
but
the
the
reason
that
I
wanted
to
bring
it
up
is
it
has
some
report,
interaction,
I,
don't
know
it
kind
of
conflicts
with
a
PR
that
Sean
has
made
and
that
PR
is
oops.
A
Sorry,
let
me
link
it
in
the
chat
here
that
one
is
just
to
compact
the
disk
cache
so
that
it
will
kind
of
net
not
have
like
a
hard
upper
boundary
but
kind
of
keep
the
local
HTTP
cash
under
control,
and
so
I'd
suggest
that
they
bring
it
up
on
the
meeting,
but
they
said
they
were
unable
to
join
so
I
told
them
that
I
would
do
it
for
them.
D
A
It's
solely
to
do
with
the
fact
with
how
it
writes
out
to
disk
basically-
and
so
I-
don't
know
if,
if
they,
if
what
Sean
is
working
on
changes
that
then
the
the
period
that
was
linked,
that
he
said
that
there
would
be
issues
between
the
two
of
them,
he
said
that
he
attempted
to
use
that
PR
to
resolve
it,
and
it
was
still
pretty
slow.
A
There's
some.
You
know
in
the
weeds
details
about
why
it's
specifically
is
slow.
That
has
to
do
with
how
Mac,
like
rights
to
the
file
system,
but
yeah.
E
D
It
looks
like
Nick
is
the
guy
who
wrote
the
pr
he
also
built
Sean's
PR,
even
though
that
there
are
inconsistent
changes
in
both
of
the
PRS.
It
looks
like
he.
He
did
the
same
test
with
regards
to
this
and
observe
the
same
slowness
when
writing
to
disc
on
Mac
OS,
so
I
think
the
two
PRS
could
be
complementary.
D
A
A
D
Yeah,
if
you
Nick,
wrote
it
down
in
his
PR
description,
there's
a
pretty
in-depth
description
of
why
and
where
this
is
coming
from.
What
specifically
on
Apple
and
what's
the
Apple
recommendation
to
minimize
the
behavior.
A
D
D
But
that's
still
a
separate
thing
because.
A
D
But
the
initial
right
will
still
be
big
okay,
so
we
one
solved
the
initial
one
we
will
sell.
We
should
solve
the
subsequent
because
we
won't
be
having
every
like
a
full
full
guests.
Every
single
time,
you'll
just
get
information.
Oh
only
this,
these
bits
are
are
different,
but
the
initial,
the
initial
read
will
always
be.
Oh
I
have
to
read
everything.
F
I
actually
have
a
question:
would
it
be
easier
just
to
do
the
syscall
on
Mac.
A
B
All
right,
so
we
just
have
a
little
bit
of
housekeeping
to
do
with
this
group
mentoring
program
and
then
I
think
we're
off
so
I
think
we're
just
a
few
clicks
of
away.
Clue.
Two
excuse
me
a
few
clicks
off
and
we
are
up
and
running
so
first
thing
we
need
to
do
is
get
the
kickoff
scheduled
and
I
explained
in
the
notes
that
the
kickoff
is
a
30-minute
meeting.
B
The
intentions
here
is
to
overly
explain
the
Rules
of
Engagement
with
people
to
meet
you
all
as
mentors
face
to
face
outside
of
this
setting,
meaning,
like
you
know
the
stand-up
setting
and
things
like
that,
how
you
all
got
there,
what
you
look
for
in
reviewers.
B
This
is
like
that
level.
Setting
kind
of
30
minute
kickoff,
right
and
I
have
like
a
little
template
for
that
like
when
we
get
there,
but
from
a
kickoff
day
time
perspective
does
August
3rd
work
for
you
all
I
think
that
I
looked
at
your
calendar
of
CLI
update
meetings
and
I'm
thinking,
maybe
30
minutes
before
this
meeting
or
30
minutes.
B
After
because
we
could
have
the
mentees
obviously
start
to
to
Really
attend
these
meetings
as
as
like
requirements
of
the
job,
and
things
like
that,
so
upvotes
down
votes
on
on
any
of
those
times.
Would
that
work
for
y'all
that
are
that
have
signed
up
to
Mentor.
B
Yeah
so,
as
you
check
yep
sure,
which
one
before
or
after
and
then
I'll
get
I'll
get
a
schedule,
I'll
probably
go
after
okay,
okay,
so
we'll
do
after
then,
so
after
the
August
3rd
meeting
will
kick
off
next
steps
after
that,
though,
is
picking
your
bi-weekly
30
minute
time
so
again,
I'm
going
to
I
actually
need
to
add
a
bullet.
B
For
that,
too,
should
we
go
with
the
idea
of
having
the
group
meet
bi-weekly
after
CLI
meetings,
30
minutes
I
feel
like
that
seems
to
be
the
easiest
with
y'all.
That's
from
my
past
experience
like
hooking
this
on
to
the
meetings,
it
seems
to
work
for
kind
of
everyone,
but
also
allowing
a
separate
space.
That's
the
key
here
too!
So
all
right!
So
let's
do
your
bi-weeklies!
B
Then
we'll
do
30
minutes,
post,
CLI
meetings
and
again
these
bi-weekly
meetings
are
not
intended
for
all
mentors
to
show
if
y'all
want
to
show
up
great,
like
that's
more
than
fine,
but
each
each
bi-weekly
session,
it'll
just
be
one
mentor
and
the
group
together,
and
that
one
Mentor
has
to
present
on
a
topic
and
those
topics
are
in
the
hack
MD,
which
is
our
next
step
to
fleshed
out
and
lucky
for
y'all.
We've
done
this
a
few
times
already,
so
we
have
some
bare
bones
things
that
we've
already
done
with
other
code.
B
Words
like,
for
instance,
like
the
release
process
in
a
deep
dive
for,
like
everything
the
reviewer
needs
to
know
about
cherry
picking
and
like
all
of
the
good
stuff,
like
actually
doing
a
deep
dive
on
that,
especially
how
you
like
to
do
things
in
that
area
as
compared
to
other
cigs,
because
you
know
every
Sig
is
a
little
bit
different
in
their
operations.
B
So
our
next
thing
to
do
now
is
to
have
the
mentors
pretty
much
either
assign
themselves
a
sub-project,
deep
dive
or
a
like
a
review,
Deep
dive
walkthrough,
and
what
a
review
Deep
dive.
Walkthrough
is:
is
you
literally
looking
at
your
review
queue
for
30
minutes
and
going
through
your
review
queue
and
talking
it
out
loud?
That's
what
a
review
deep!
Does
it's
Tim
Hawkins?
B
Does
it
all
the
time
for
us
so
that
it's
just
literally
going
30
minutes
all
right,
I'm,
a
reviewer
I'm
going
to
show
you
what
it's
what
it's
like
to
be
a
reviewer
here
and
then
people
get
to
ask
you
questions
so
I.
Don't
necessarily
want
to
work
on
this
hack
MD
on
the
phone
with
y'all,
because
I
don't
want
to
take
up
all
your
time.
But
let's
work
on
this
async
and
then
my
I
think
I
may
have
almost
cut
someone
off.
D
Yeah
going
through
the
review
to
30
minutes
for
my
past
experience
that
will
depend
on
the
size
of
the
pr
30.
D
B
Explaining
that
too,
though,
is
really
important
because,
like
what
everything
you
just
told
me
would
be
great
for
like
that
session
like
so,
if
you
were
like
here's,
my
review,
cue,
I'm,
not
gonna,
do
these
because
of
here's,
some
things
that
I'm
already
seeing
as
to
why
I'm
gonna
have
a
lot
of
time.
I
need
a
lot
of
time
allocated
so
yeah
all
that
time.
Management
stuff
is
the
stuff
that
we
don't
really
train
on
in
open
source
right,
like
there's
no
manual
here
of
you,
know
how
you
manage
your
time.
B
So
are
there
any
subproducts,
though,
that
y'all
don't
want
to
Deep
dive
on,
because
you
do
have
a
lot
of
sub
projects.
We
don't
have
to
do
everything
in
this
three
months
right.
B
Those
would
be
good
projects
to
do
deep,
Dives
on
as
well.
Do
you
see
anything
on
this
list
now
that
you're
like
nah?
Let's
leave
this
out
completely.
D
Yeah
I
feel,
like
I,
think
I
feel,
like
you,
girls
feel,
like
experimental
I,
don't
think
we
want
to
do
crew
with
regards
to
carry-on
functions
and
customize
I'll.
Probably
ask
Katrina
if
I
remember
if
she
was
signed
up
for.
G
For
mentoring,
I
did
I'm
here.
Can
you
hear
me.
E
Yeah
I
didn't
sign
up,
but
I'm
available
to
do
the
customer
side.
If,
if
we're
able
to
include
customize
and
if
the
folks
who
signed
up
are
interested
in
joining
our
reviewers
list,
we
do
desperately
need
reviewers
on
the
customized
side
as
well.
So
I
would
be
happy
to
do
that.
Cli
experimental,
for
what
it's
worth
is
the
customizing
key
control
docs.
So
it's
not
that
unrelated.
E
If
we
want
it,
just
it's
like
also
pretty
simple:
it's
just
a
Hugo
site,
so
I
wouldn't
mind
scoping
that
in
but
carom
functions
needs
contributors,
not
reviewers,
there's
just
not
enough
activity
on
it
to
be
worth,
including
in
my
opinion,
and
if
we're
trying
to
Target
like
getting
reviewers
into
specific
reviewers
files.
Having
fewer
projects
scoped
in
I
think
makes
a
lot
of
sense.
Yep.
B
B
D
C
A
Want
to
include
CLI
runtime,
just
in
Cube
control
mache,
because
we
definitely
need
to
get
people
in
there
too.
Oh
right.
E
How
does
it
work
in
terms
of
like?
Are
we
trying
to
get
all
of
the
folks
into
all
of
these
files,
or
is
it
more
like
that
this
is
giving
them
an
opportunity
to
choose
which
one
they
actually
want
to
focus
on
over
the
course
of
the
program
and
the
expectations
they'll
get
into
one
at
the
end,
yep.
B
Both
yeah,
because
obviously
I
feel
like
we
need
folks
who
are
interested
in
the
subject,
because
obviously
they
want
to
stick
around,
but
we
also
need
to
focus
on
areas
where
we
need
folks,
so
I
think
it's
like
a
combo
of
both
that
we
have
to
play
with,
and
the
expectation,
though,
with
the
program
is
one
owner's
file
at
the
end
of
three
months.
B
If
you
meet
the
criteria,
so
no
there
is
nothing
that
says
that
we
have
to
put
these
folks
in
owner's
files
if
they
didn't
meet
the
criteria,
I'm
going
to
say
50
of
them
won't
and
that's.
Okay,
like
I,
said:
that's
our
expected,
like
that's
something
that
I'll
share
and
kick
off.
You
know,
that's
that's
the
rate.
You
know
we're
moving
fast,
it's
three
months
and
but
at
the
end
of
the
day
they
don't
necessarily
need
to.
B
You
know,
what's
what
I'm
looking
for?
They
don't
need
to
like
the
oh
God
I'm,
just
like
losing
track
of
my
mind.
It's
been
a
long
day
already.
It's
only
9
A.M,
so
yeah,
though
at
the
end
of
three
months,
there's
nothing
there.
That
says
we
have
to
do
this,
but
at
the
same
time
there's
nothing
said
that
says
that
they
can't
stick
around
and
complete.
B
You
know
an
owner's
Journey
after
that
three-month
period
I
just
kind
of
like
to
look
at
this
three-month
period
as
an
accelerated
onboarding
Journey,
because
one
of
the
problems
that
we
have
with
growing
maintainers
here
is
that
you
need
that
bit
of
hand-holding,
and
this
is
giving
that
bit
of
hand-holding
and
giving
it
in
a
way
where
it
accelerates
people
to
still
keep
going,
because
I've
noticed
that
we
lose
so
many
folks
who
say
that,
like
their
jobs,
will
support
them,
etc,
etc,
but
they
weren't
necessarily
being
handheld
maintainers,
didn't
necessarily
talk
to
them,
Etc
et
cetera,
so
from
y'all's
perspective,
as
owners
of
as
owners
of
some
of
these
areas.
B
I
would
not
necessarily
like
think
that
you
have
to
rush
folks
or
that
you
have
to
that.
You
have
to
put
them
in
an
owner's
file.
The
other
thing,
too,
is
we'll:
have
a
check.
Wait
we'll
have
like
a
halfway
point
like
at
you
know
like
a
month
and
a
half
after
a
few
sessions,
and
that's
when
people
really
kind
of
start
going
and
I,
don't
know
if
I'm
going
to
do
this
and
you
know
so
and
then
and
then
from
there
on
then
you
kind
of
already
know
after
that.
B
After
that,
halfway
mark,
you
kind
of
already
know:
okay
I'm,
going
to
focus
on
these
like
five
folks
who
are
really
in
it
and
that's
it
so
I'm
gonna
start
adding
some
dates
to
some
of
these
topics
in
the
hack
MD.
So
we
can
get
a
structure
going
and
then
I'll
also
get
the
kuntravex
coordinators
to
come
up
with
a
calendar
for
us
and
we'll
publish
the
calendar
and
then
you'll
know
when
you're
speaking
when
you're,
not
speaking,
who's
going
where
and
what
and
things
like
that.
B
Yeah
I
literally
just
created
it
like
two
seconds
ago,
as
we
were
as
Marcus
was
presenting
so
yeah,
we'll
have
a
dedicated
private
slack.
Channel
folks
will
be
instructed
that
they
can
use
this
to
ask
any
silly
questions,
especially
the
the
people
stuff
right,
because
as
you're
a
reviewer
you're
dealing
with
personalities,
that's
the
stuff
that
I
think
a
lot
of
folks,
don't
like
asking
in
public
channels
right
like
Hey.
How
do
I
deal
with
this
person?
That
seems
like
they're
being
a
jerk
to
me.
B
D
Another
question
that
I
had
was
with
regards
to
the
day
that
we
are
more
available
than
others
for
the
people.
Do
we
pick
each
of
us
separate
day
whenever
suits
us
or
it's
more
like?
D
Oh,
we
have
to
figure
out
one
day
within
a
week
where
most
of
us
are
available,
because
I
understand
that
each
and
every
single
one
of
us
will
have
different
schedules
and
I,
don't
know
for
Katrina
on
Monday
will
be
better
for
me.
Let's
say
Thursday
will
be
better
and
for
Eddie
it'll
be
better
to
do
it
on
Tuesdays
and
so
forth.
G
D
B
B
However,
if
you
really
do
want
to
accelerate
these
folks,
please
like
be
on
all
all
days
right
so
like
if,
if
Katrina
wants
to
hop
in
on
Fridays
and
cease
and
see
some
questions
or
wants
to
maybe
even
just
say,
hey
everybody
I'm
here
what's
up
and
that
kind
of
thing
that's
great,
but
the
expectation
from
a
time
commitment
is
it
should
be
super
light
on
y'all.
Like
that's
the
deal
here
because
we're
it's
sort
of
the
group
peer
mentoring
that
we're
latching
on
to
as
the
benefit
here
and
not
necessarily
one-on-one.
B
The
other
important
thing
that
I
didn't
put
on
the
agenda,
but
it
has
come
up
several
times
through
mentors,
which
is
what,
if
these
folks
are
just
so
lost
right
like
it's,
not
your
job
to
be
a
teacher
at
the
end
of
the
day,
like
being
a
mentor,
doesn't
necessarily
mean
being
a
college
professor
some
folks
have
already
given
us
like
YouTube
links
and
like,
if
you
see
folks
struggling
in
like
a
foundational
base
area,
give
them
reading
materials
and
give
them.
B
E
Somewhat
related
to
that
sort
of,
if
we
end
up
with
more
people,
I
know,
we
already
have
like
a
lot
on
the
list
at
this
point
in
this
I
think
the
date
we
listed
was
the
end
of
the
month
for
final
selection.
We
we
already
caught
it
off.
Oh,
we
did
okay.
So
it's
like
a
first
come
first
serve
not.
B
E
B
But
first
come
first
serve
if
they're
qualified
and
all
of
them
right
now
are
self-selecting
that
they're
qualified,
because
this
is
the
part
where
it's
like.
Do
you
really
know
how
to
write
a
controller
right
and
feedback
from
for
me
that
I've
already
taken
for
like
the
next
cohort,
is
to
a
make
sure
we
give
that
stuff
ahead
of
time
and
B
also
maybe
say,
prove
it
in
some
way
right.
B
It
doesn't
and
not
in
a
in
a
bad
way,
prove
it.
But
you
know,
hey,
send
me
a
PR
even
if
it's
not
to
a
kubernetes
repo
right,
send
me
something
where
you've
written
a
controller
right.
B
So
that's
my
that's
what
I'm
gonna
I'm
already
retroing,
believe
it,
or
not
so
I'm,
already
collecting
retro
items
that
next
next
cohort,
like,
for
instance,
with
API
Machinery
crew
like
I'm
gonna,
get
we'll
get
real
like
down
to
the
wire
with
that
cohort
right,
but
yeah
I
at
least
wanted
y'all
to
know,
though,
to
like
don't
feel
like
burdened.
If
you
ever
feel
burdened
I
want
you
to
immediately
DM
me,
because
that's
not
the
point
of
this
and
again
that
would
be
another
retro
item.
B
For
me
here
is
okay,
something's
got
to
give
in
that
area,
but
if
there
are
folks
that
come
to
y'all
as
chairs
tech,
leads
owners
Etc
in
the
next
couple
of
weeks
before
we
kick
off
and
they
want
in
get
them
in
here,
just
literally
got
them,
especially
if
you
feel
like
they're
qualified
if
they're
people
that
you
know
have
already
been
putting
in
work,
get
them
in
here,
because
just
because
we
know
that
we're
gonna
have
Fallout,
like
I
said
I
I'm
guaranteeing
it
like,
if
not
I
mean.
B
Obviously
you
know,
I
owe
y'all
breakfast
or
something
a
cubecon
but
I'm
guaranteeing
it
that
you're
gonna
lose
at
least
three
of
ten.
So
and
again,
that's
not
bad!
It's
because
people
time
things
get
in
the
way
life
whatever.
So
if
you
have
someone
or
folks
are
listening
right
now
and
have
been
contributing
to
CLI
for
quite
some
time
have
the
experience
that
you
know
CLI
is
looking
for
with
reviewers
and
want
to
sort
of
EX
the
this
path.
A
Awesome
excited
to
get
this
started.
That
was
the
end
of
the
topics
on
the
agenda.
If
no
one
has
anything
else
to
bring
up.