►
From YouTube: Kubernetes SIG CLI 20230719 Bug Scrub
Description
Kubernetes SIG CLI bug scrub and triage on July 19th, 2023.
B
C
B
B
A
B
B
E
B
A
E
B
E
A
E
E
B
F
E
A
B
C
D
B
B
B
E
B
E
And
there
might
be
two
parts
to
it
as
well,
so
maybe
maybe
the
first
step
is
like
hey.
Let's,
let's
update
client
go
so
that
it
can,
you
can
programmatically
get
the
ports
and
then
once
we've
got
that
in
place,
then
we
could
look
at
adapting
the
coupe
cuddle
port
forward
command
to
then
provide
different
output
types
or
something
I'm.
Just
trying
to
think
I
haven't
looked
at
the
fork,
so
I
don't
know
how
big
of
a
thing.
F
E
D
A
B
B
C
F
A
A
C
A
B
E
I
mean
it's
not
a
bad
issue.
I
am
if,
if
somebody
wants
to
do
a
pull
request,
so
I
think
this
came
about
because
they
had
a
pull
request
about
some
cleaning
up
the
help
and
then
we're
kind
of
getting
going
down
the
line
of
finding
more
and
more
inconsistencies
and
I
was
just
like
hey,
let's
just
let's
just
fix
the
ones
that
you
started
to
set
out
to
fix.
Instead
of
because
I
mean
you
could
probably
go
through
all
the
commands
and
find
a
lot
of
improvements
to
to
the
help
text.
E
I
guess
you
know,
my
caution
would
be
against
just
like
word
smithing
and
trying
to
make
it
perfect
versus
good
enough,
and
you
know
we
don't
want
to
just
constantly
be
tweaking
the
health
text.
But
if
there's
places
that
are
where
things
are
clearly
missing,
then
it's
good
to
fix
that
yeah.
That's.
C
B
E
D
B
B
B
B
E
C
B
E
I
don't
know
I
mean
there
are
several
commands
that
are
popular
commands
that
do
support
those
flags,
but
it
doesn't
necessarily
mean
we
should
I
guess,
but
it
it
does
kind
of
add
more
weight
to
the
case
that
hey
you
know.
These
are
kind
of
kind
of
standard
flags
that
are
used
in
certain
situations.
C
D
A
B
B
A
D
B
E
D
E
Know
is
already
going
to
be
changed
anyway
to
websockets
in
the
future,
so
this
PR
didn't
I
mean
it
does
fix
some
of
the
it
does
fix
the
unexpected
eof
problem,
but
I
don't
know
if
there's
really
any
interest
in
in
merging
this
PR
or
not
and
I,
don't
know
if
it's
it
might
be.
This
problem,
it's
hard
to
say:
okay,.
E
E
A
B
A
B
E
E
B
A
E
B
B
E
F
B
A
B
E
E
And
these
a
bunch
of
these
are
untreated.
Our
needs
triage,
but
they're
really
old
in
the
cube
cuddle
repo,
and
this
was
one
of
them
and
it
it
came
up
because
it
it
went
rotten
or
something
and
then
I
looked
at
it
and
I
was
like.
Oh,
this
really
is
a
problem
and
in
fact
it
happens
all
the
time
in,
in
the
end,
tests
in
a
flake
situation
and
I
don't
know
so
I
guess
we
I
feel
like
we
should
at
least
triage
it.
But
I
don't
know
if
it's
a
simple
solution
or
not.
E
So
so
the
rule
of
the
matter
is
that
so
we
have
a
timeout
for
the
overall
HTTP
requests,
that's
made,
but
there's
a
TLS
handshake,
timeout,
that's
less!
So
it's
like
a
10
second
timeout
or
something
so,
regardless
of
what
the
overall
timeout
is.
You
can
have
a
TLS
handshake
timeout
that
happens
in
like
10
seconds
and
then
it'll
just
fail
and
it
only
happens
under
heavy
load
right.
B
A
E
A
E
I
guess
that
was
part
of
my
question
today.
I
mean
we
I
I,
don't
know
we
could
I
mean
I.
Could
post
something
in
I
could
maybe
go
on
slack
and
ask
in
the
API
machinery
Channel
what
they
think,
whether
that's
an
API
machine
or
anything,
the
the
triage
thing,
the
screenshot
one
of
the
screenshots
I
posted,
said
API
Machinery
on
it.
So
I
don't
know.
E
That's
probably
why
I
thought
that
one
like,
maybe
maybe
it
is
API
machinery
and
not
us
yeah,
or
at
least
they
should
be
involved,
probably
so
I'll
so
I
guess
we
could
accept
it.
I
don't
know
if
we
want
to
accept
it
or
not
before
we
figure
out
who
it
belongs
to
or
I'll
ask
in
the
slack
Channel
who
it
belongs
to.
B
Yeah
is
it
actually,
it
seems
like
well,
okay,
so
it's
being
reported
as
a
cute
head
also,
however,
it
may
end
up
being
something
that's
actually
inside
of
API
Machinery,
instead
of
especially
because
it's
a
client
go
thing,
probably
or
sorry.
What
what
Eddie
links
to
is
a
client
goes
thing.
I
would
not
say
that's
a
guarantee,
that's
where
the
source
of
the
issue
relies,
so
I
didn't
accept
it
as
six
a
lot
CLI
for
the
moment,
if
you
find,
if
it
is
Brian
when
you
talk.
C
A
B
D
F
B
This
is
probably
going
to
be
the
last
one
illustrate
some
surprising
Behavior,
with
apply
I
found
repeatedly
that
humans
are
bad
at
predicting.
What
apply
will
do
so
from
talking
to
a
lot
of
people?
The
apply
action
feels
like
it
means
create
or
replace,
but
it's
really
not
it's
much
more
sophisticated
resource
co-ownership
system.