►
From YouTube: Kubernetes SIG CLI 20210721 - bug scrub
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
Good
morning,
good
afternoon,
good
evening,
depending
on
where
you
are
thank
you
for
joining
us
for
the
july
21st
six
eli
bug
scrub.
My
name
is
eddie
zaneski
and
I
will
be
your
host
today.
A
We
don't
really
have
any
announcements
other
than
the
contributor
summit
for
kubecon
is
hopefully
going
to
happen,
and
hopefully
we'll
see
folks
there
if
they're
going
so,
does
anyone
have
any
thing
they
want
to
jump
on
first
or
look
at.
A
C
D
C
On
on
that,
I
I
have
today's
or
yesterday
at
midnight
was
the
docs
deadline
and
I
have
a
pr
out
for
adding
this
cuddle
command.
Headers
environment
variable,
it's
really
small
one
I'll
throw
it
in
the
chat.
If
anybody
wants
to
have
a
look,
it's
just
a
really
small
one.
So
I
I
added
an
environment
variable
section
to
the
part
that
has
the
coop
control
flags.
C
I
only
put
in
two
environment
variables
the
most
important,
of
course,
the
config
environment
variable,
but
that
now
I'm
adding
this
control
command,
headers,
environment
variable.
I
mentioned
that
it's
version
122
or
later.
Let
me
actually
throw
this
in
the
chat.
You
know
if
you
guys
have
any
any
feedback
on
the
wording
or
you
know
if
other
details,
please
let
me
know
so.
C
One
of
the
docs
contributors
was
asking
about
putting
how
we
how
we
insert
these
headers
for
plug-in
development,
so
they
could
put
it
in
the
headers
as
well.
That's
quite
detailed-
and
I
didn't
really
want
to
do
that
for
this
initial
pr.
A
That
out,
no
that's
fine.
Is
this
waiting
on
us
for
approval
or
doc.
C
A
A
Awesome,
I
don't
think
we
have
anything
else
in
the
release.
A
A
Yeah
completions
went
in
the,
so
we
still
need
to
upgrade
cobra
again.
That
is
blocked
on
a
there's
another
issue
that
paco
was
working
on.
It's
this
one,
this
one.
So
this
changed
a
bunch
of
dependencies
that
are
the
same
as
cobra,
but
paco
did
all
the
work
of
fixing
all
the
tests
and
stuff
that
broke
and
changed.
A
Apparently
there
was
a
one
of
the
google
api
libraries
changed
their
resource
path
or
something
which
probably
should
have
been
a
breaking
change,
but
it
wasn't
and
it
messed
up
a
bunch
of
our
tests
or
something
that
we're
relying
on
that
path
to
market.
So
as
soon
as
this
is
merged,
we
can
upgrade
cobra.
C
So
so
maybe
this
isn't
the
correct
forum,
but
I,
when
I
most
recently
have
been
running
make
test
the
unit
tests
for
kubernetes
in
general.
There's
only
one
unit
test
that
I
see
fails
and
it's
in
our
code
base.
It's
the
test
for
the
version.
C
The
coupe
pedal
version.
Has
anybody
else
seen
that,
or
is
that?
Do
I
have
a
sometimes
I
have
a
wrong
setup
with
the
wrong
go
version
or
something.
A
I
actually
have
a
fix
for
that
that
I
need
to
push
up.
It
was
annoying
me
too.
Actually,
so
I'm
just
mocking
out
the
http
call
to
the
version
server,
because
I
think,
though
the
test
was
currently,
it
was
actually
hitting
a
server.
It's
like
making
a
request
which
we
shouldn't
be
doing
from
unit
tests.
C
E
A
Yeah,
I
know
it's
all
good.
It
was
an
easy
fix.
All
right,
cool
I'll,
share
my
screen
and
we
will
walk
through.
A
I
have
ignore
my
million
tabs
open,
don't
judge
me,
so
let
me
grab
these
tabs.
A
Okay,
so
I
have
to
I
told
people
earlier:
I'm
actually
I'm
talking
to
arno
this
week
to
my
great
triage
party
to
cube
infra,
and
so
I
think
something
broke,
because
we
actually
do
have
a
few
recent
issues
that
should
be
showing
up
here.
So
I
don't
know
why.
They're
not
I'll
have
to
look
at
that.
A
A
A
A
E
E
So
it
is
the
issue
that
they're,
using
like
a
unicode
space
instead
of
a
regular
space.
Is
that
what
that's
saying
I'm
trying
to
understand
what
so
it's
like
interpreting
this,
the
the
the
weird
space
after
the
dash
in
as
the
name
space,
not
as
a
space?
Is
that
what
it's
saying
what
what
this
issue
is
saying.
A
A
D
C
A
Yeah
there
was
a
whole
bunch
of
back
and
forth
around
it
because
there
was
a
bunch
of
cves,
so
it's
definitely
a
piece
of
code
that
I'm
always
afraid
to
touch.
A
A
A
A
A
A
A
A
A
A
Okay,
this
one
is
taken
care
of.
We
have
a
pr
that
we
just
need
merged.
A
C
Does
this
have
to
do
with
different
since
we've
upgraded
the
version
of.
B
Yeah,
presumably
customize
and
the
customized
inside
keep
going
are
subtly
different.
I
expect
this
is
not
on
purpose
but
which
I
understand.
E
Isn't
there
a
generic
deprecation
check
that
looks
for
underscores
and
flag
names
and
spits
out
that
message?
So
it's
saying
load
underscore
restrictor
is
deprecated.
A
A
B
But
yeah
the
command
in
cube
kettle
is
built
up
independently.
It's
not
like
executing
the
other
binary
or
anything.
It's
it's
separate.
So
you
could
try
this
with
any
number
of
things
and
and
the
flags
aren't
dislikes
that
are
not
the
same,
but
it
is
weird
that
they
get
a
deprecation
warning
for
a
flag
that
doesn't
exist
about
another
flag
that
doesn't
exist.
E
A
39.,
do
we
want
to
change
something
there.
E
E
A
E
C
D
A
A
A
D
E
Yeah
I
mean,
I
guess
one
way
would
be
just
remove
the
warning,
and
I
mean
this.
I
don't
know
it's
kind
of
weird.
I
guess
if
it
auto
converts
the
underscores
to
dashes,
but
it's
doing
that
now.
If
people
have
something,
that's
for
whatever
reason
still
using
underscores,
it
would
still
work,
but
no
warning.
D
Maybe,
as
this
is
like
something
that
receives
that
receives
the
the
flag
and
returns
another
flag
normalize
it
maybe
just
just
replacing
the
code
all
of
those,
because
because
it
seems
to
me
that
this
function
is
just
used
to
normalize
this,
the
separator
right,
even
the
name
of
it
it's
about
separator.
So
so
maybe
we
just
could
clean
up
everything
using.
A
A
C
C
D
D
E
It's
kind
of
weird,
it's
kind
of
weird
how
we
use
this
now
it's
it's
called.
I
just
posted
a
link
in
the
chat,
but
it's
actually
called
twice
in
a
row,
one
time
with
the
warning
and
the
other
time
without
so
I
wonder
if
we
just
get
rid
of
the
line
with
the
warning
and
let
the
regular
normalize
happen
if
that
would
be.
A
E
Confusing
or
or
we
just
change
the
wording
on
the
warning,
it
just
says
we
don't
imply
that
it's
a
real
flag,
we
just
say
hey,
you
gave
us
a
flag
with
an
underscore.
It's
going
to
be
auto,
can
we
just
say
underscore
separator
automatically
converted
to
dash
or
whatever,
that
might
be,
maybe
a
good
middle
ground.
There.
C
A
A
A
We
can
probably
close
this,
so
they
had
a
bunch
of
questions
about
how
we
do
discovery
and
caching
and
one
of
their
big
questions
was:
why
does
cubecontrol
need
to
make
discovery?
Calls
for
well-known
object
types,
and
my
answer
was
there's
really
no
such
thing
as
a
well-known
object,
type
to
the
client.
C
A
E
E
A
A
A
A
A
I'll
take
a
look
at
this
as
I'm
looking
through
the
port
forward
code
for
the
speedy
stuff
and
we'll
see
what
we
can
do,
because
I
wonder
if
we
could
keep
track.
I
don't
know
if
it's
a
fork
or
not
right,
because
if
it's
a
fork
we
get
a
pid
and
then
we
could
keep
track
of
pids
and
then
have
a
you
know
an
interrupt
listener
or
something
that
cleans
up
after
itself.
A
All
right
I'll
take
a
look
and
see
what
we
can
do.
A
A
C
E
D
B
D
B
It
seems
like
it
would
be
relatively
easy
to
script
and
it
would
be
rather
heavy
as
a
as
a
command
to
get
all
the
name.
Spaces
go
over
them
check.
Their
labels
then
make
a
request
per
namespace
to
get
each
thing.
So
this
wouldn't
be
a
very
performant
feature
in
a
large
cluster.
C
So
one
other
wrinkle
I've
always
seen
with
namespaces,
is
that
you
could
actually
set
a
namespace
in
your
coop
config
file
for
your
context
and
that
always
trips
me
up
whenever
I
try
to
play
around
with
namespace
choosing
which
namespace
for
particular
resources
how
that
would
interact
at
what
level.
B
A
E
E
E
A
A
Okay,
so
someone
wanted,
you
want
to
type
that
reply,
ricardo
or
brian
yeah
I
can
I
can.
I
can't
take
a
look
into
that
on
the
weekend.
Sure
we
can.
We
can
say
something
like
this
might
make
more
sense
as
a
controller,
because
I
you
brian
you're
right,
it
is
an
anti-batter
like
you
should
shouldn't
be
relying
on
the
name
space
label.
D
I
mean
our
decision
is
not
to
implement,
but
maybe
to
give
some
some
some
paths
like
using
creating
a
plugin
or
relying
on
a
controller
to
label
everything
behind
below
the
the
name
space
right.
A
A
D
D
D
But
even
even
a
plug-in,
you
need
to
mount
that
pvc
somewhere.
So
if,
if
the
pvc
is
just
running
inside
the
cluster,
so
you
you,
you
won't
have
the
the
the
local
mount
right.
So
you
need
to
bootstrap
a
pod
in
your
cluster
mount
that
pvc,
and
if
that
pvc
is
like
read,
write
owns
and
that's
already
mounted
somewhere
else.
What
happens?
C
I
would
I
wouldn't
know
which
particular
yeah,
which
particular
file
paths
have
been
mounted.
Because
of
that
claim
I
mean
there's.
I
don't
know
where
that
connection
is
between
the
the
p.
You
know
persistent
volume
claim
and
then
you
know
trying
to
determine
whether
or
not
that
location
was
created
because
of
that
claim.
A
D
D
So
if
someone
wants
to
work
on
something
funny
because
we
are
like-
I
am
putting
myself
on
the
other
perspective
like
I
am
the
user,
I
am
proposing
something
cool
and
someone
say:
hey
just
write
a
plugin,
but
we
don't
say
to
to
people
like
we
need
to
code
or
to
contribute
that
they
can
write
a
plugin
to
help
someone.
So
my
feeling
here
don't
know
if
we
have
an
faq.
D
Really
got
written
to
yeah,
but
but
I
mean
like
a
label
or
something
that
says
hey.
This
should
be
a
plugin.
If
someone
in
outside
world
wants
to
implement
this,
if
someone
wants
you
like,
like
do,
do
you
want
to
help
someone
write
a
plugin
have
some
fun.
D
How
many,
how
many
things
could
be
a
plug-in,
and
we
are
just
right
here
just
closing
and
saying
this
could
be
a
plug-in
to
maybe
people
that
don't
know
how
to
call.
Then
we
have
like
students
and
people
willing
to
help,
but
they
don't
know
how
that's
just
like.
I
don't
know
if,
if
you
get
it
like,
I'm
missing
some
some
some
plugin
catalog
that
needs
to
be
developed
like
a
weekend
project
as
an
example.
D
This
is
something
that
we
need
help
for
someone
waiting
and
like
announced
that
maybe
6
li
is
doing
a
wanted.
Plugin
catalog
using
like
help
wanted-
or
I
don't
know,
I'm
just
thinking
that
that
maybe
we
are
losing
some
good
opportunities
here,
just
oh
so
yeah.
So
if
you
have
right
permission,
you
can
also
add.
C
So
maybe
the
wording,
just
the
wording
itself
on
the
label,
should
be
something
that's
more
that
maybe
more
focused
like
plug-in
first
or
create
plug-in
first
just
so
you
know,
if
it
just
said
plug-in,
then
it
might
not
be
as
descriptive,
but
if
we
had
something
that
was
far
more
focused
and
descriptive,
which
you
know
just
reading,
the
label
would.
C
A
D
You
can
you
can
I
do
that
all
of
the
time
in
ingress.
I
hope
that
no
one
figures
out,
but
you
can,
you
can
add
the
label
yourself.
The
bot
will
work
when
I
do
slash
triage
plug-in
needed
or
whatever
yeah.
So
I
don't
know
if
this
works.
I
I
guess
so
because
I've
added
manually
the
air
area
helm
in
ingress
in
ginex
and
it
worked.
It
worked
just
fine.
You
just
need
to
be
careful
if
someone
tries
to
add
that
label
in
the
in
the
bot
bot
is
gonna,
probably
overwrite.
D
D
A
A
B
Yeah
I
we
agreed
to
that
about
a
month
ago
at
a
6a
live
meeting
and
I
never
got
around
to
it,
but
I
finally
did
it
this
morning.
I
would
love
to
have
you
all
there
at
those
meetings
as
well,
if
you're
interested.