►
From YouTube: Kubernetes SIG CLI 20221130
Description
Kubernetes SIG CLI bi-weekly meeting on November 30th, 2022.
Agenda and Notes: https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit#bookmark=kix.yiuug0qj9hsm
A
So
welcome
to
the
November
30th
edition
of
the
kubernetes
6C
live
bi-weekly
meeting
I
am
your
host
Sean
Sullivan,
and
we
have
a
slightly
new
format
thanks
to
Katrina
for
modernizing
our
format.
A
I
will
get
into
the
announcements
immediately
and
then
we'll
follow
along
on
the
on
the
agenda,
which
looks
very
light
today.
So.
B
A
Only
thing
that
we
have
on
our
agenda
or
sorry
on
our
announcements
is
that
the
again
the
the
126
release
is
scheduled
for
Tuesday
December
6th
I
haven't
heard
anything
to
change
that
date.
Nor
have
I
heard
anything
about
the
127
dates.
A
If
anyone
has
any
sort,
any
updates,
please
let
us
know
whenever
you
get
the
chance,
does
anyone
else
have
any
announcements.
A
Okay,
so
why
don't
we
welcome
our
new
members?
So
if
there's
anyone
who
is
new
to
the
6C
lie
or
hasn't
been
here
for
a
while
and
would
like
to
meet
your
your
colleagues,
this
is
your
chance
to
to
speak
up
and
say
hi.
This
is
completely
voluntary.
A
B
Yeah
I
just
wanted
to
give
a
quick
note
that
something
that
we
provide
the
customization
at
previous
six
CLI
meetings
was
whether
or
not
it
would
be
acceptable
for
us
to
release
a
V5
that
had
some
breaking
changes
that
we
had
long
wanted
to
make
for
some
lifelong
deprecations.
That
sort
of
thing,
because
we
go
up
into
Cube
cuddle
and
the
consensus
had
been
that.
Yes,
we
can
do
that.
We
need
to
be
able
to
move
customize
forward
and
we
now
expose
the
version
of
customize
very
explicitly
in
Cube
cuddle.
B
Well,
we
have
decided
to
actually
do
that
to
take
the
opportunity
to
do
it
as
our
next
release,
so
we're
going
to
be
looking
at
cutting
of
the
25,
hopefully
sometime
in
December,
so
we
are
still
Gathering
what
features
are
going
to
be
included
and
and
which
of
the
deprecations.
We
can
actually
finish
as
part
of
that,
but
just
wanted
to
give
a
heads
up
that
that
we're
aiming
for
that.
B
So
if
you
have
any
feedback
or
any
things
that
you
think
really
really
should
be
included,
please
reach
out
to
you
Natasha
and
I.
B
Well,
we
we
always
have
to
write
that
all
up
in
the
release,
notes,
which
I
think
is
where
we
are
always
telling
people
to
look
and
the
automated
script
that
we
use
to
update
Cube
cuddle
like
puts
in
a
link
to
those
release,
notes
in
the
cube
pedal
release,
notes.
So
that's
like
the
chain
we
usually
use.
If
that's
not
sufficient,
then
we
could
definitely
consider
doing
something
else.
A
Okay,
shall
we
move
on
to
the
next?
A
the
next
Kip
or
sub
project
which
currently
doesn't
exist
in
the
agenda?
D
Happened
recently
on
the
kui
front,
so
nothing
much
to
report
there
just
working
on
internal
staff
for
the
last
couple
months.
D
On
the
translations,
cap
I
don't
really
have
a
really
good
update.
The
pr
is
still
Gathering
some
feedback.
There's
been
a
few
comments
made.
So
thanks
for
that
for
people
who
have
done
that
that
there's
a
PR
that's
sort
of
related
to
the
cap,
that
I
think
it
was
linked
in
in
last,
the
last
Sig
meeting
that
could
use
a
review
where
basically,
the
the
up
the
hack
update
translations
script
is
broken.
D
So
when
I
looked
at
that
and
fixed
I
fixed
it
when
I
re-ran,
it
I
realized
that
the
translations
haven't
even
been
updated
for
a
year
and
a
half.
So
that's
kind
of
some
context
for
how
far
behind
the
translations
are
getting,
but
so
yeah.
If
somebody
wants
to
review
that
that
PR,
that
would
be
great
or
definitely
comments
on
the
cap
or
appreciated.
There's
been
some
some
good
comments
already.
So
thanks.
A
Is
is
that
script
like
a
bash
script,
the
translations.
D
Yes,
it's
a
bash
script
and
it
calls
it
calls
another.
Some
executable
like
a
git
text
or
something
like
that
or
a
I
can't
remember
exactly
what
it
calls
some
other
executable
that
that
extracts,
the
all
the
I-18n
strings
out
of
the
code
and
puts
them
into
the
PO
files.
So
they
can
be
edited
using
something
like
Po
edit
or
something
like
that.
A
Okay,
if
we're,
if
why
don't
we
move
on
to
the
the
next
open
discussion
section
if
we're
finished
with
the
kept
updates
and
the
sub-project
updates,
the
first
item
on
the
agenda
and
the
only
one
so
far
has
to
do
with
the
the
maintainer
track
session
at
kukon.
Eu
next
April,
not
sure
who.
A
No,
no,
no
worries
so
so
what
did
you
have
in
mind?
First,
first
of
all,
the
kubecon
EU
2023
is
an
Amsterdam
in
April,
correct
and,
and
so
this
is
about.
Oh
sorry,
I'll,
just
let
you
discuss
it.
B
Yeah
looking
up
the
dates,
real
quick,
it
seems
to
be
mid,
April
17th
to
21st
yeah,
so
the
what
I
wanted
to
bring
up
is
that
the
maintainer
track
session
call
for
proposals
just
opened,
so
six
CLI
leads
will
be
submitting
a
proposal
for
what
we'll
speak
about
at
at
that
session,
that
we,
we
generally
do
and
the
standard
format
that
we
use.
B
We
like
to
update
everybody
about,
what's
been
going
on
in
this
egg
in
the
last
time,
especially
since
the
previous
kubecon,
but
we
also
usually
have
that
segment
at
the
end,
where
we
just
discuss
a
topic
that
we
think
is
of
interest
to
Folks
at
the
Sig,
and
so
you
know
we
want
to
talk
about
what
is
useful
to
you.
What
you're
interested
in
what
you
think
is
is
the
best
use
of
that
time.
B
So
if
you
have
ideas
for
for
topics
for
that
part
of
the
session,
please
let
us
know
on
in
the
6li
channel
on
slack,
and
the
other
thing
is
that
we
can
also
invite
other
Sig
members
who
are
not
necessarily
the
leads
to
talk
about
a
topic
themselves.
So
we,
if
you
have
some
something
that
for
your
sub
project
or
just
related
to
60
Li
in
general,
that
you
would
like
to
propose
to
speak
about
that
could
be
possible
too.
So
we
would
love
to
hear
your
ideas.
B
That's
that's
all
I
wanted
to
say
about
it.
If
you
have
anything
else
to
add
not
much
here,
Sean.
A
Yeah
so
I
think
in
the
past
it's
been
like
the
chairs
or
the
tech
leads
who've
who've
been
the
maintainer
track
speakers,
but
I
think
that
in
the
future
it
can
be
even
wider.
Anyone
in
the
Sig
who
wants
to
talk
about
something
that
is
is
of
general
interest
to
the
rest
of
the
Sig.
A
So
if
there's,
if
there
isn't
anything
else,
I'm
gonna
give
everybody
45
minutes
back.
Is
there
again?
We've
got
plenty
of
time.
So
is
there
anything
else
that
we
want
to
address
in
our
Sig
meeting.