►
From YouTube: Kubernetes SIG CLI 20220413 - Kustomize 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).
B
C
Plug-In
sorry
not
plug-in
whatever
is
called
whenever
you
use
the
customize
the
package
with
cube
kettle.
They
don't
mention
until
the
very
last
line
of
the
issue.
Oh.
A
That
is
curious
because
they
specifically
say
this
customized
version,
which
is
definitely
not
the
one
in
any
currently
available,
cube
control.
A
Yeah
I'm
trying
to
reproduce
with
independent
customize
right
now.
Sorry,
my
screen
isn't
shared
for
that.
A
A
A
The
sample
isn't
syntactically
valid,
there's
something
wrong
with
the
ammo.
Sorry,
I'm
kind
of
struggling
with
that.
What's
going
on
here,.
A
Yeah
I'm
having
trouble
with
the
reproduction,
because
this
is
there's
something
wrong
with
the
sample
I'll
come
back
to
this
one
later,
unless
somebody
else
has
time
to,
in
the
background
to
like
try
to
figure
out
the
syntax,
I
don't
want
to
keep
us
all
in
the
call
watching
me
do
nothing.
So,
let's
see
maybe
try
this
one.
D
A
Yeah,
I
honestly,
I
don't
know
if
we
support
bitbucket,
I
certainly
haven't
used
it
myself.
We
did
make
a
bunch
of
changes
to
the
remote
url
handling
that
reduced
what
we
supported
a
long
time
ago,
because
we
couldn't
keep
the
hashicorp
dependency.
A
D
A
Because
it
does
work,
we
do
support
remote,
urls
or
remote
bases
in
general,
and
I
imagine
that's
not
generally
broken
or
we'd
have
a
lot
more
issues
open
about
that.
Does
anyone
else
have
an
idea?
What
what
specifically
could
be
wrong
here?
Otherwise,
I'm
inclined
to
ask
them
to
provide
the
entire
sample
so
that
we
can
look
into
it
in
more
detail.
A
Oh
thank
you
oleg
for
answering
on
the
storage
class
issue
that
we're
looking
at
before
very
much
appreciated.
Thank
you
very
much.
B
A
This
my
immediate
reaction:
this
could
be
an
ordering
issue,
the
home
charts
transformer
and
the.
A
I
guess
home
charts
is
a
generator
and
they're
saying
components,
field
which
is
something
that
pulls
in
bases
ultimately
resources
from
a
specific
kind
of
base,
attempting
to
use
a
patch
in
a
component,
okay
yeah.
So
let's
see
reproduction
helm,
charts.
A
So
if
this
is
the
problem,
one
likely
components
runs
first
and
then
helm
charts.
But
let's
see.
A
A
D
A
D
A
Right
resource
is
special,
it's
it's
currently,
not.
Actually
it
has
a
bespoke
implementation
that
runs
first,
it's
not
it's
not
plugged
in
externally,
like
the
rest
of
the
generators
are,
as
you
can
see,
right
here
in
helm
is,
and
it's
actually
last
of
those
generators,
so
necessarily
components
is
going
to
run
first
and
then
helm
is,
is
gonna
run
last
the
generators
and
then
the
transformers
are
gonna
run
so
yeah
it
isn't.
It
is
an
ordering
problem.
A
You
can,
let's
see,
no,
because
you
can't
there's
an
open
issue
about
this,
actually
that
you
can't
use
resources,
generators
separately,
let's
see
if
I
can
find
it
if
you
were
able
to
use
yeah
here
we
go
this
one.
If,
if
we
fixed
this,
then
you
could
do
a
custom
ordering
by
using
the
transformers
field
which
would
accept
generators
and
transformers
transformers
as
a
more
generic
word
than
generators.
A
So
you
would
be
able
to
specify
the
helm
first
and
then
the
component
generator
second,
and
then
you
would
get
the
behavior
that
you
want,
but
right
now
there's
no
way
to
reorder
it
because
there's
special
behavior
around
resources
and
components
field.
Okay.
So
that's
the
answer.
D
D
Generators
resources,
including.
A
Configmap
generator,
oh,
I
I'm
sorry.
I
mean
to
post
these
as
I
click
on
them,
so
that
everyone
can
go
and
open
them
up
read
at
their
own
pace.
There
you
go.
Here's
the
latest
one
in
the
chat
and
think
about
generator.
Double
quote:
handling
incorrect
when
generating
config
microphone
properties,
file,
double
quotes
from.
A
Yes,
you're
absolutely
right,
there's
problems
in
the
underlying
yaml
library
or
one
of
one
of
them
that
customizes
uses.
A
And
it
actually
applies
to
some
problems
that
surface
in
cube
cuddle
as
well
and
they're
all
sort
of
ultimately
sourced
from
this.
This
problem
in
the
apple
library,
so
yeah
searching
for
things
like
double
quotes
and
integers
on
both
of
those
repos
will
give
you
a
collection
of
issues.
Let's
just
verify
that
I
think
the
the
property
support
is
like
the
dot
end
file
support
is
pretty
rudimentary,
so
it's
not
out
of
the
question,
there's
an
independent
bug
here
as
well.
A
A
Would
someone
be
able
to
reproduce
this
in
the
background
make
sure
that
the
sample
gets
exactly
what
they're
saying
it
does,
because
if
so,
I
think
like
this,
for
example,
that
doesn't
look
like
the
problem
that
we've
traditionally
seen
where
the
tip
typically
the
problem,
that
marcus
is
alluding
to
those
the
way
it
surfaces
is
the
quotes
being
stripped.
So
this
is
different
and
surprising.
A
A
And
here
the
quotes
being
added,
that's
fine!
It
is
a
string
field.
So
like
this,
this
one
is
not
a
problem.
It's
these
ones
that
I'm
thinking
are
something
that
we
could
potentially
fix.
Could
I
have
a
volunteer
to
reproduce
this
while
we
move
on
to
the
next
issue.
A
I
think
values
are
not
allowed
in
this
context.
It's
usually
an
area
that
you
get
when
it
actually
did
find
the
file
just
fine
and
there's
something
wrong
in
it.
That's
not
a
very
helpful
error
to
be
fair.
A
A
Okay,
what
changed
between
four
five
two
and
four
five?
Four,
some
of
the
big
things
include:
yaml
anger,
support,
proper,
proper,
yellow
maker
support.
A
D
A
Yeah,
I
appreciate
the
confirmation
that
it
works
with
the
previous
version.
That's
for
sure,
interesting.
A
A
I
I'm
not
sure
how
to
proceed
without
any
sample
that
I
can
actually
use
honestly
or
or
even
like
an
example
of
the
the
line
that's
causing
the
problem
like
this
one's
good.
But
I,
if
they
didn't
provide
what
line
it
actually
is,
and
it
looks
very
simple,
but
are
they
actually
getting
the
exact
same
error?
A
There's
the
same
ordering
it's
a
very
common
point
of
confusion.
You
have
a
project
to
rework
the
docs,
that's
something
that
we
should
probably
make
sure
is
explained
more
clearly
in
the
new
version.
A
Yeah,
that's
exactly
what
they're
asking
for
customize
is
really
averse
to
accepting
features
that
make
unstructured
edits
of
any
kind
and
once
you
add
regex
into
the
mix,
that's
getting
pretty
fuzzy.
A
We
really
want
to
be
dealing
with
the
semantic
structure
of
of
the
documents,
and
I
I
can
see
the
use
case,
but
this
is
something
that
would
have
to
undergo
careful
discussion
and
consideration
with
the
maintainers
and
my
first
impulses
like
that's,
probably
not
the
way
that
we
would
solve
the
problem
and
customize,
but
without
natasha.
Here
I
don't
think
we
can
really
dive
into
this
conversation.
So
I'm
gonna
have
to
save
this
one
for
later.
A
Replacements
is
trying
to
replace
the
vars
field,
so
we
have
a
lot
of
folks
who
were
doing
things
with
bars
who
come
in
trying
to
do
the
exact
same
thing
with
replacements,
and
we
have
to
find
sort
of
alternative
approaches.
It's
a
replacement
says
more
customized
native
than
far
as
ones,
okay,
missing
transformer
config,
and
once
again,
I've
been
forgetting
to
put
these
in
the
chat.
Here
we
go.
A
A
Yes,
that
looks
covered
yep,
so
you
can
see.
A
A
A
A
That's
that's
a
custom
resource
thing.
It
has
no
idea.
A
A
A
That
field
that
we
were
just
looking
at
configurations
field,
which
I
know
unfortunately,
is
not
documented
properly.
It's
not
in
the
documentation.
B
A
Okay,
so
we
have
a
more
complete
sample
that
might
be
helpful,
I'm
a
little
confused
about
how
they're
trying
to
modify
and
from
standalone,
which
is
which
contains
configmap
references
and
like
are
they
trying
to
actually
compose
the
properties
from
the
various
things
or
references,
because
this
would
not
compose
the
individual
properties
right.
A
We
only
have
one
minute
left,
though,
so
I'm
going
to
try
to
continue
to
reproduce
this
and
dig
through
what
the
situation
is
here
on
my
own
after
the
meeting,
because
we
yeah,
we
only
have
one
minute
left
so
with
that
last
minute.
Does
anyone
have
any
questions
or
anything
else,
I'd
like
to
bring
up
before
we
close.
A
Thank
you
so
much
for
everyone
for
coming
and
attending
this
customized
butt
scrub.
It
was
really
great
to
have
you
here.
Thank
you
for
your
help,
triaging
and
talking
through
these
issues,
and
I
hope
to
see
you
next
time
have
a
great
day.