►
From YouTube: Kubernetes SIG CLI 20221102
Description
Kubernetes SIG CLI bi-weekly meeting on November 2nd, 2022.
Agenda and Notes: https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit#bookmark=kix.tnwq55ronxgq
A
Looks
like
we
have
a
pretty
short
agenda
today
and
let's
go
directly
into
the
announcements,
which
is
we
are
a
week
and
a
day
or
actually
one
week
exactly
away
from
the
code
freeze,
so
things
are
going
to
get
pretty
backed
up
so
earlier
is
better.
A
B
An
important
thing
about
the
code
free
state
is
different,
depending
on
where
you
are
so
remember
to
double
check
the
the
date.
But
if
I
remember
correctly,
it's
actually
only
a
it's.
B
So
the
next
Tuesday,
but
if
you
look
at
the
UPC
it
already
goes
to
the
nine,
but
in
general
the
date
is
set
as
end
of
the
day.
Pacific
I
think
it's
like
9
6
p.m,
Pacific,
which
translates
back
to
ninth
of
UTC
but
I'll,
give
you
a
link
double
check.
I
can't
remember
off
top
of
my
head
might
be
wrong,
but
that's
what
what
it's
usually
has
been
in
the
past.
A
Okay,
I'll
I'll.
If
anybody
could
can
update
that
five.
B
Pm:
here's
the
link,
5
p.m;
eighth,.
B
A
Okay,
great
thanks
for
thanks
for
that
mache.
So
there's
a
the
link
there
to
to
get
the
exact
time.
I'll
update
the
the
notes
shortly
after
our
meeting
to
make
sure
it's
exactly
correct
when
we
will
be
freezing
code,
does.
C
B
B
A
Okay,
this
is
the
part
of
our
meeting
where
we
generally
allow
or
encourage
those
who
are
here
for
the
first
time
and
or
for
those
who
haven't
been
here
for
a
long
time
to
introduce
themselves
as
a
chance
to
to
meet
your
other
6C
live
colleagues.
Is
there
anybody
else
who
would
like
to
introduce
themselves?
This
is
completely
voluntary.
A
E
A
D
I
will
go
next.
My
name
is
Islam
I,
also
attended
that
your
session
at
kubecon
and
got
interested
in
in
the
projects
and
subjects
that
you
brought
up
in
the
station
and
would
like
to
contribute.
Oh.
D
Thank
you,
I'm
I'm,
based
out
of
London
in
the
UK,
yeah
and
I,
will
create
the
place.
A
A
Okay,
why
don't
we
move
on
to
the
the
topics?
And
the
first
topic
was
about
an
issue
with
with
the
last
applied
configuration,
but
I
believe
that
this
may
have
been
a
resolved.
Is
that
correct,
Katrina
or
Antoine.
F
I
will
yeah,
so
we
had
a
good
meeting
with
Alex
and
Katrina
and
we
decided
we're
gonna
keep
the
last
supplied
annotation
in
126,
since
we
are
mostly
trying
to
fix
a
bug
and
we
wanted
the
behavioral
to
stay
the
same
in
this
specific
release
for
127,
we'll
come
up
with
a
plan
and
a
cap.
Well,
we
are
going
to
decide
what
happens
and
what's
next
for
the
migration,
probably
a
long-term
plan
to
make
someone
else
how
to
play
the
defaults
in
group
at
all.
F
We
want
to
give
a
chance
to
people
to
update
at
their
own
Rhythm
the
from
parental
reply
to
server
side
apply,
and
we
sort
of
want
to
have
like
a
picture
where
we
can
Auto
detect,
if,
if
we
should
clear
inside
ourselves
sort
of
like
objects,
and
so
we
we
want
to
discuss
this
and
think
about
this,
and
we
make
a
cap
for
127,
but
for
now
we
wanted
to
keep
these
things
as
similar
as
possible
to
what
we
have
today.
H
H
Yeah,
so
I
would
like
to
start
a
discussion
if
people
would
be
interested
in
having
a
Standalone
keep
control
epic
command.
Like
till
now,
like
you,
you,
like
you,
we
are
only
using
evict
and
using
drain,
and
this
one
is
too
broad.
You
can
also
use
that
one
and
do
specify
the
label.
So
so,
if
you
label
your
Bot
with
something
and
you
specify
the
labels
on
the
drain,
you
can
use
that
to
evict
these
spots
as
well,
but
it
will
also
make
the
node
unschedulable.
B
We
didn't
ever
put
a
particular
boundary
about
how
many
upvotes
will
guarantee,
including
or
an
r
in
a
default,
but
definitely
starting
with
a
plug-in
like
shown
right
and
in
the
comment
is
a
way
to
go,
because
just
having
a
plug-in
initially
will
allow
you
to
play
a
little
bit
with
the
with
this
idea
and
maybe
crystallize
the
function
of
the
a
little
bit
better
and
in
parallel
you
would
be
able
to
gather
some
feedback
from
the
users
as
soon
as
as
you
will
be
able
to
provide
that.
B
This
is
something
that
is
broadly
used
and
you
have
more
or
less
personalized
use
cases.
You
can
return
to
us
with
this
topic
and
and
we
can
reconsider
the
decision
for
including
that
as
a
default.
That
was
basically
what
we've
been
stating
a
couple
of
times
in
the
past
I
remember,
we
promised
to
write
it
down
eventually
and
I'm,
pretty
sure
that
we
will
eventually
write
it
down.
But
that's
that's
that's
what
we've
been
talking
about
on
and
off
on
several
occasions.
B
Basically,
that's
that's
somewhat
matches
your
opinion
or
your
approach.
H
B
Yeah,
whenever
you
have
the
plugin
ready
feel
free
to
to
mention
that
in
this
issue,
so
that
people
could
who
will
be
looking
at
this
issue
can
also
try
your
plugin,
whether
whether
the
plugin
will
be
developed
as
part
of
openshift
CLI
or
what
will
be
a
separate
binary,
feel
free
to
to
leave
a
comment
there,
that
for
those
who
are
interested
in
giving
a
try,
this
is
how
they
can
get
it.
B
And
then,
once
we
get
sufficient
feedback
from
users,
we
can
reconsider,
but
having
definitely
having
that
issue
open.
There
is
a
good
path
forward,
because
at
least
you'll
have
everything
in
a
single
place
and
then
just
link
and
keep
the
discussions
at
there.
C
G
I
Yes,
yeah
and
we
can.
You
should
send
an
email
to
the
mailing
list
too,
to
let
people
know
we're
looking
for
input
there
after
you
build
it.
G
A
Thanks
Phillip
for
putting
so
much
effort
into
this
new
interesting
command.
A
So
if
we
could
wrap
this
topic
up,
we
can
move
on
to
stand
ups
with
Brian
is:
is
there
anything
else
to
say
on
the
new
evict
man.
J
Yeah
so
I
mean
I,
nothing
new,
really
on
the
on
the
survey
itself,
at
kubecon
I
did
talk
to
siyoko
Sun
from
Sig
docs
who's,
the
Korean
translating
lead,
and
he
seemed
very
interested
in
in
keeping
translations
in
Coupe
cuddle,
which
I
mean
I,
think
we
were
kind
of
leaning
towards
that
way.
But
it
is
something
that
we
kind
of
that
was
I,
guess
sort
of
on
the
table
was
like
Hey
should.
J
Should
we
even
be
attempting
something
that
has
not
done
well
and
having
talking
to
him
and
hearing
some
of
the
other
I
went
to
a
presentation
where
some
Japanese
users
were
talking
about
not
not
Cube
cuddle
specifically,
but
you
know
how
a
lot
of
people
in
their
country
a
barrier
to
contributing
is
there.
Is
that
a
lot
of
this?
A
lot
of
the
information
is
in
English
and
they
prefer
to
have
it
in
Japanese
and
so
I.
J
You
know
I'm
kind
of
realizing
and
hearing
from
different
people
that
it
is
important
to
have
translations
and
so
I
guess
when
I'm,
when
I'm
coming
coming
around
to
is
I
mean
we
we
could
still
do
the
survey
but
I'm
kind
of
leaning
towards
you
know,
let's
open
an
issue
in
our
in
our
repository
in
Coupe,
cuddle
and
track
what
needs
to
be
done
to
bring
translations
to
a
good,
State
and
so
part
of
that
means.
J
Well,
I
mean
you
know,
maybe
learning
and
communicating
how
how
the
translations
get
updated.
You
know
there's
it's
not
it's
not
as
simple
as
just
editing
a
file,
there's
a
script.
You
need
to
run
a
python
script
and
then
it
does
some
pre-populates
some
files
and
then
from
there
you
can
do
the
Tran,
edit,
the
translations
and
so
I
guess
what
I'm
thinking
is.
Some
things
need
to
be
done,
like
perhaps
automating
that
script
so
that
it
happens
automatically
and
then
coordinating
with
Sig
Docs.
So
it
seems
like
there's.
J
Sig
docs
has
the
people
we
need
to
do
the
translations,
but
they
don't
at
least
talk
into
syoko's
son
that
there's
not
all.
It's
not
always
clear
how
they
can
help
us,
so
I
think
maybe
part
of
it
is
communicating
to
Sig
docs
more
so
anyways
I
just
said
a
lot
there.
Does
anybody
have
any
any
thoughts
on
on
localization
or
where
we
should
go
from
here.
B
There
was
a
discussion
last
week:
I
can't
remember
whether
that
was
made
official,
but
are
you
still
playing
with
the
idea
that
we
would
disable
the
translations,
which
are
some
percentage
incomplete?
So
let's
say
we
would
put
a
some
kind
of
a
boundary.
C
B
By
default
and
would
not
work
so
that
people
are
not
getting
some
outdated
because
if
something
is
below
the
threshold,
most
likely
it
is
not
being
maintained,
and
there
is
a
high
chance
that
it
is
out
of
the
day
for
for
quite
a
while.
On
that.
J
Yeah
so
as
far
as
I
can
tell
from
the
when
I
was
looking
into
it,
the
there's
not
a
risk
that
the
translation
will
be
wrong
if
the
if
somebody
goes
and
into
the
code
and
changes
the
English
text,
because
the
the
entire
text
is
the
key
that
it
looks
up
the
translation
on
so
as
soon
as
that
text
gets
changed.
It
no
longer
matches
up
to
the
translation.
J
Therefore,
the
the
result
is
that
it
would
just
show
the
English
instead
of
the
translated
text,
but
we
did
talk
about
having
some
threshold
and
saying
you
know
we
we
only
want
to
show
translations
if
we've
reached
for
a
language,
if
we've
reached,
say
50
of
the
text
being
translated
or
some
threshold,
it
sounds
reasonable.
J
I,
don't
know
I,
don't
know
if
it
really
helps
anything
to
do
that
or
you
know
certainly
I
think
it
helps
to
have
metrics
and
maybe
watch
them
and
say
look
you
know
here
we
have
a
release
coming
up
and
here's
the
status,
maybe
once
every
release,
we
have
a
report
that
says
here's,
here's
the
translation
percentage
for
each
language
and
then
it
would
be
great
to
have
this
be
totally
automated.
J
But
you
know
maybe
open
an
issue
with
in
our
repo
and
paying
some
people,
whoever
we
know
from
Sig
docs
or
maybe
there's
a
group
of
mailing
list
or
some
way
that
we
can
communicate
to
them
that
we
could
use
their
help.
C
I
think
there's
also
a
slack
channel
right,
Sig,
docs,
localization
effort
or
something
like
that
right.
Yes,.
J
There
there
is,
and
they
were
I
did
a
few
weeks
back.
I
did
post
something
on
there
and
they
were
pretty
responsive,
so
I
think
they
would
help
us
for
sure.
G
I
signal
thing
like:
if
we,
if
the
level
drops
below
a
certain
threshold,
we
want
something
to
start
failing
that.
We
will
then
see
no
matter
when
in
the
release
cycle
it
is
and
then
potentially
Drive
issues
off
of
that
I
don't
know
if
there's
a
way
in
the
framework
to
have
it
not
like
fail
arbitrary
PRS,
because
that
wouldn't
be
a
good
experience,
but
I
guess
that
leads
me
to
another
thought,
which
is
that?
I
J
As
far
as
issue
versus
cap
I-
don't
I
don't
know
I
feel
like
so
my
first
thought
is
to
get
it
into
an
issue
just
so
we
can
have
a
way
to
kind
of
track
and
record
conversation
in
a
text
way,
but
you
know
maybe
it
does.
Maybe
it
does
warrant
a
cap.
If
it's
I
guess
it
depends
I
I,
you
know
who
who
is
interested
in.
J
You
know
using
the
kept
I
guess
as
a
communication
tool.
Maybe
it's
a
better
way
to
engage,
stick
talks
or
other
people
who
might
be
interested
in
this
and
have
feedback
or
input
I.
Don't
know,
that's
interesting,
I,
any
any
other
thoughts
on
the
kept
idea.
K
One
thing
that
we
talked
about
while
we
were
hey
kubecon,
was
that,
like
we
can
only
do
so
much
in
terms
of
internationalizing
the
messages,
because
some
of
the
messages
are
coming
from
the
server
and
so
going.
The
kept
route
might
be
a
good
way
to
try
and
get
some
cross
domain
work
done
on
it
see
if
we
can
get
people
from
the
server
side
to
start
internationalizing.
Their
error
messages
I
know
that
we
assume
that
that
would
be
very
difficult
to
get
moving,
but
Maybe.
J
Yeah,
that's
we
did
talk
about
that
and
that's
kind
of
a
hard
problem
for
I
mean
it
doesn't
mean
we
can't
do
it,
but
it's
definitely
another
dimension
to
this
problem
and
then
also
when
you
throw
in
other
external
third-party
messages,
for
example,
that
may
be
coming
from.
J
You
know:
somebody's
crd
with
a
status
or
something
and
technically
all
that
could
be
translated,
but
coordinating
that
and
getting
everybody
to
do
things
in
a
in
a
way
that
that
makes
it
either
so
that
we
can
translate
it
or
they
give
it
to
us.
Translated
I,
don't
know
yeah,
but
that's
a
good
point.
I
mean,
maybe
maybe
there
is
something
that
could
be
done
kind
of
globally,
not
just
in
Cube
cuddle
but
everywhere
else
that
that
allows
translations
to
occur
at
all
levels.
J
You
know,
maybe
there's
a
header
I
think
maybe
this
was
brought
up.
Maybe
there's
a
header
that
that
we,
you
know,
only
make
a
request.
Part
of
that
is
telling
the
API
what
language
we
we
are
using
and
whether
they
maybe
that's
the
first
step
even
and
then
they
can,
you
know,
choose
or
not
to
respond
in
a
translated
response.
G
The
advantages
I
see
is
that
there
are
like
a
few
distinct
sort
of
avenues
of
action
that
we
could
take
here
in
terms
of
like
improving
the
way
translations
are
actually
managed,
improving
the
signaling
that
there's
a
problem
getting
more
translations
from
these
different
sources,
like
Marley's
saying
and
like
those
could
it's
easier
to
have
distinct
conversations
about
different
facets
of
the
topic
when
it's
in
that,
like
PR
format
for
the
cap,
I'm,
not
an
issue
that
might
have
like
a
cross-cutting
conversations
actually
about
different
things.
J
You
know
fixes
to
the
current,
like
you
know,
we
could
still
while
it
kept's
going
on,
we
can
still
try
to
you,
know,
coordinate
with
Sig
docs
and
and
have
them
use
the
existing
mechanism
to
update
our
our
translations
and
get
them
improve
them,
but
to
build
something
that
is
kind
of
like
going
forward
is
going
to
be
easy
and
sustainable.
That's
where
the
cap
comes
in
I,
guess.
J
Well,
no
I,
don't
actually
I
I
created
the
survey
I
have
not
like
pinged
anybody
or
anything
I
feel
like
there's,
probably
a
a
group
I
need
to
set.
You
know,
notify
and
say:
hey
I
created
this
survey
request
I
mean
if
you
want
to
click
into
the
survey
request
and
look
at
it,
I'm,
not
sure
how
much
the
questions
are
still
relevant.
J
As
far
as
I
mean
it's,
it
would
be
interesting
to
know,
but
there's
probably
oh
there's
a
link
if
you
scroll
down
a
little
bit
more
there's
their
link
to
draft
yep.
J
So
it's
just
like
five
questions.
I
think
what
language
do
you
use,
whether
you're
happy
with
it,
whether
it's
important
to
you
and
then
number
four
is
kind
of
the
the
main
thing
that
we
kind
of
want
to
know
is
like
hey.
If
it's
not
complete,
is
it
still?
Is
it
still
helpful,
I,
don't
know,
and
so
I
guess.
That's
the
the
question.
The
main
question,
but
I'm
not
I,
think
what
we
would
do
with
that
answer.
I
I
think
we
should
definitely
send
it
out.
I
saw
someone
commented
on
the
issue
there.
They
said
we
should
add
a
not
applicable,
preferred
English
option,
I'll
ping
sticking
trivex
and
see
what
the
next
step
is
for
you.
There,
okay.
G
If
we
had
a
cap
issue,
we
could
potentially
link
it
with
that
last
question
there.
So
we
have
like
people
giving
people
like
a
direct
Avenue
to
like
join
in.
J
Yeah
I
guess
I
was
thinking
that
we
would
it
I,
don't
know
what
I
guess
it
depends
on
how
we
get
the
responses,
but
we
would
probably
I
was
thinking
that
we
would
bucket
them
based
on
what
people's
language
is
on
the
first
question
and
then
obviously
like.
If,
if
you
chose
English
as
your
language,
then
question
four
doesn't
really
apply,
but
we
could
put
that
on
there
too.
It's
probably
not
a
bad
idea.
J
Yeah-
and
there
might
be
another
dimension
to
this-
that
like
if
just
because
English
is
not
your
primary
language,
doesn't
mean
that,
because
maybe
there's
still
somebody
that
would
say
not
applicable
I
prefer
English,
maybe
they're,
for
whatever
reason
they're
used
to
using
Tools
in
English,
even
though
that's
not
their
primary
language.
So
maybe
that
still
makes
sense
to
put
that
there
yeah.
J
And
so
I
think
the
timing
on
this
then
Katrina's
idea
of
you
know
hey
this.
This
might
be
a
good
way
to
drive
people
to
the
cat
to
comment
and
help
us.
You
know
with
ideas
there.
So
maybe
we
could
coordinate
this
survey
with
when
the
cap
is
created.
That
way
it
you
know,
helps
us
get
the
most
useful
information
possible.
J
Do
I
should
I
take
us,
take
a
take
a
crack
at
the
creating
a
tap
for
this.
Is
that
a
good
place
to
start
I
guess
after
this
meeting.
G
Yeah
that
sounds
good
to
me,
and
maybe
the
folks
who
were
interested
in
joining
the
Sig
with
the
internationalization
effort
could
be
collaborators
for
you
on
that.
One.
I
J
Was
that
who
was?
Was
there
anybody
in
particular
that
was
interested
in
in
that
topic?
Anybody
here
on
the
call,
I,
guess
or
anybody
else
that
I
should
make
sure
to
include
on.
C
C
I
G
Yeah
so
like
we
have
a
problem
with
specific
translations
not
being
adequate,
but
what
the
cap
is
going
to
tackle
more
generally
is
that
the
system
we
have
for
managing
translations
and
flagging
when
they're,
inadequate
and
updating
them,
and
all
that,
like
the
system
behind
the
internationalization,
is
not
working
super
well
for
us.
So
the
idea
is
that
we
need
folks
to
would
use
internationalization,
so
they
have
opinions
about
it
and
ideas
for
how
to
make
the
system
better
to
help
Brian
out
with,
with
with
the
effort
in
general.
E
I
also
help
with
this
the
best
I've
worked
a
little
bit.
You
know
not
to
to
help
translation
so.
G
I
A
So
so
Brian
I've
I've
attempted
to
to
keep
some
notes
for
these
discussions,
but
if
you'd
like
to
update
them,
if,
if
they're,
inaccurate
or
there's
other
information
that
you
want
to
add
to
those
notes,
please
do.
A
Okay,
it
looks
like
we
might
get
around
25
minutes
back
unless
there
are
any
other
issues
that
we
would
like
to
address
before.
We
call
it
a
wrap.
K
I'm
going
to
put
this
on
a
schedule,
but
Brian
or
sorry,
Tim
Tim
had
a
question
I'm,
pretty
sure
that
I
know
the
answer
is
I
just
wanted
to
double
check:
matcha
you're
you're,
the
one
that
closed
the
associated
PR
with
this
they
basically
just
want
to
have
config
map
secret,
be
able
to
be
used
with
Cube
pedal,
create
and
the
where
did
I
go
somewhere
in
here.
There's
a
I
think
it's
like
the
last
thing
yeah
here
and.
K
Yeah,
so
let
me
scroll
back
up,
so
basically,
they
want
to
be
able
to
set
a
label
flag
for
create
which
we
don't
have
currently,
and
the
answer
the
matcha
gave
was
basically
like.
This
is
not
the
intention
of
create
which
it
was
basically
what
I
thought
when
I
saw
Tim
posted
in
the
chat
too
I
just
wanted
to
double
check
and
see.
If
that's,
where
everybody
stole
that
a
year
later
from
the
last
time,
this
was
updated.
B
Yeah,
the
majority
of
the
create
command
should
be
very
simple.
To
get
you
started
and
we're
looking
at
more
sophisticated
uses.
You're
probably
shouldn't
be
using
Create
in
the
first
place,
so
probably
I
would
be
where
I
would
be
pushing
forward.
B
If
you
want
to
stick,
let's
create,
on
the
other
hand,
I'll
probably
suggest
using
Create
pipette
through
invoking
driver
on
to
a
file
and
then
pipe
it
through
label
command.
You
can
basically
achieve
the
same
thing.
It
should
work
if
piping
does
not
work.
I
can
that's
definitely
something
that
we
should
do
yes,
yeah,
and
then
you
can
only
after
that
operation.
B
You
will
be
able
to
the
creatives
on.
I
B
Server,
it
should
work
similarly
with
annotate
with
labels,
but
in
general
yeah
I
would
probably
push
people
towards
the
the
apply
flow
where
you
have
the
files
kept
and
the
in
some
kind
of
a
gidge
replay.
B
It's
it's
better
to
have
a
few
simple
composable
commands,
rather
than
one
which
will
allow
you
to
do
an
on,
but
then
to
get
whatever
option
you
you
need.
You
need
to
read
through
three
pages
of
a
man
of
that
command.
That's
something
that
we
used
to
have
with
with
run,
and
we
tried
hard
to
get
rid
of.
K
Yeah,
okay,
I'll
also
just
send
them
a
link
to
whenever
it's
up,
but
the.
G
B
I'm
happy
to
answer:
if
you
send
me
the
link
over
the
slide,
I'll
I
can
provide
the
conditional
additional
details
out
there.
G
This
is
sort
of
related
to
a
topic
that
we
discussed
at
I.
Don't
know
maybe
two
meetings
ago,
where
someone
wanted
to
add
like
a
new
sub
command,
to
create
for
a
different
resource
type
like
in
our
feq
I.
Just
wanted
to
link
to
the
issue
that
we
pointed
that
person
to
as
well,
which
is
the
sort
of
like
plan
to
redo
how
this
works
so
that
there
would
be
sort
of
well
at
the
resource
level,
more
flexibility
that
they're
looking
for
without
requiring
us
to
actually
have
support
for
every
single
thing.
B
Also
in
parallel
to
that
we're
working
on
getting
the
opening
to
create
some
commands
of
logins
until
we
get
the
full
bone
generation
mechanism,
I
will
try
to
open
up
create
projects,
because
currently
we
do
not
allow
supplements
or
any
of
the
built-ins
top
command
plugins,
but
we,
we
discussed
it
a
couple
weeks
before
a
couple
meetings
before
that
will
most
likely
open
it
up
for
create
only
there's,
a
bunch
of
soaps
has
been
approaching
me
being
the
having
the
ability
to
create
any
random
purities
for
their
or
their
resources.
A
Cool
great
for
thanks
for
bringing
that
up,
Marley.
F
A
Okay,
I
think
we're
gonna
get
about
20
minutes
back
unless
there's
any
other
issues
that
we'd
like
to
address.