►
From YouTube: Kubernetes SIG CLI 20221214
Description
Kubernetes SIG CLI bi-weekly meeting on December 14th, 2022.
Agenda and Notes: https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit#bookmark=kix.tcnxjxgucz2l
A
B
Welcome
to
the
December
14th
version
of
the
kubernetes
6C
live
bi-weekly
meeting
I'm
Sean
Sullivan
I'm
your
host.
Today
we
have
a
very
small
agenda:
I'll
get
directly
into
the
announcements,
so
we
were
able
to
get
the
version.
B
126
named
electrifying
version
of
kubernetes
released
last
Friday
took
a
couple
extra
days,
but
that
was
released
and
I
I
haven't
seen
or
heard
of
the
new
127
release
dates
and
if
we
do
get
them,
we'll
add
them
to
this
this
agenda,
so
I
was
hoping
to
get
feedback
from
you,
the
60
Liars
on
whether
or
not
we
should
cancel
the
next
meeting,
which
is
in
the
middle
of
the
holidays.
A
B
Okay,
great
so
I'll
say
that
that's
passed.
If
anyone,
let
me
ask
if
anyone
has
any
problem
with
that
and
would
like
to
have
the
next
meeting.
B
Okay,
let's
say
that
the
motion
is
passed.
If
there's
any
other
discussion
on
it,
please,
let's
do
it
on
Slack.
B
If
that
is
the
case,
and
the
next
meeting
will
be
the
11th
of
January
of
next
year,
so
this
short
meeting
will
be
our
last
get
together
for
6cli
in
2022,
and
so
this
next
part
is
where
we're
going
to
welcome
new
members
and
I'm
gonna
have
a
look
at
our
participants
to
see
if
I
don't
there's
a
couple
of
names
that
or
at
least
one
name
which
which
see
which
I
haven't
heard
of
before.
B
If
there's
anybody
who
would
like
to
to
introduce
themselves
to
the
six
CLI
and
meet
your
sexy,
like
colleagues
Now's
the
Time,
this
is
voluntary.
If
you
don't
want
to
do
it,
that's
fine
foreign.
C
I've
been
to
one
before,
but
I
haven't
really
introduced
me
myself,
so
based
in
Atlanta
Georgia
work
for
statistic
currently
happy
to
be
here.
B
B
A
We
I
mentioned
before
that
we're
targeting
a
5.0
release
for
our
next
one.
There
is
a
lot
that
we're
trying
to
get
in
there,
so
we're
going
to
discuss
later
today,
whether
or
not
we
think
we
can
do
that
before
the
holidays
or
we'll
push
after
the
more
important
thing
is
to
get
in
everything
that
that
we're
targeting
so
we're
gonna
we're
gonna
make
that
decision
later
today.
A
I
guess
I
could
also
mention
we
talked
about
this
at
at
kubecon
as
I
say.
The
initiative
that
Sean
and
I
presented
about
to
improve
pruning
I've
been
working
on
the
kep
for
that
with
Justin
Santa
Barbara
and
we've
been
making
some
good
progress.
It's
not
quite
ready
to
present
yet,
but
it
will
definitely
be
ready
by
the
next
meeting.
A
B
So
I
put
one
quick
item
on
if
we
move
on
to
the
open
discussion,
which
was
just
to
to
point
out
what
we
had
gotten
into
the
b126
release,
and
so
I
mentioned
the
aggregated
discovery
so
Discovery,
as
we
we've
mentioned
many
many
times
in
our
meetings,
has
been
a
kind
of
sore
point
for
Coupe
control
and
for
all
clients
and
the
number
of
Discovery
requests,
as
well
as
the
fact
that
we
were
downloading
the
same
information
multiple
times
and
that
has
been
fixed.
B
So
there
are
now
only
two
downloads
there's
one
at
slash
API
and
one
at
slash
apis
which
download
the
endpoints
and
they
also
use
HTTP
etags.
So
they
send
a
hash.
We,
the
server
is
not
going
to
they're
going
to
send.
The
service
is
going
to
send
a
304,
not
modified
if
nothing
has
changed.
B
So
if
you
haven't
added
any
crds,
you'll,
never
download
the
discovery
again
and
that
actually
is
behind
a
feature
flag.
So
it's
actually
not
going
to
be
easy
to
to
get
to
that
feature
for
this
release.
Unless
you
enable
that
Alpha
feature,
but
you
can
play
around
with
it
and
then
it'll
be
beta
for
127.
it'll
it'll
be
on
by
default
for
the
next
release.
A
B
B
Cool
yeah,
in
fact,
there's
we're
cleaning
up
Coupe
control
to
in
all
places,
use
V3
and
right
now,
there's
been
some
refactors
once
so
so
I
forgot
to
mention
the
the
code.
Freeze
has
ended
when
we
released,
and
so
as
most
of
us
already
know,
we
can
get
our
code
in
and
there's
been
a
few
submissions
to
refactor
for
to
get
V
V3
get
ready
for
open,
API,
V3
and
Coupe
control
throughout
group
control.
B
And
just
to
mention
the
open,
API
V3
is
more
expressive
than
open,
API
V2,
and
so
that's
one
of
the
reasons
why
we're
we're
making
these
changes.
B
Is
there
anything
else
anybody
would
like
to
mention
that
got
into
the
v126.
B
Okay,
well,
it
looks
like
we'll
get
50
minutes
back,
as
we
had
mentioned,
I
think
off
camera.
We
have
resolved
to
to
cancel
meetings
that
do
not
have
anything
in
the
agenda
a
day
before
and
as
we've
also
mentioned.
Next
meeting
is
canceled
and
we
will
see
all
of
us
again
on
January
11th
of
2023.