►
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
Everything
invocation
is
just
mixed:
will
the
meet
have
a
tell
stuff
and
so
on,
and
it's
not
in
a
separate
spec
feared.
So
it
is
not
like
all
the
other
cabinet
objects
we
have,
or
we
have
the
meter
data
and
stop
on
the
on
the
very
left
side.
And
then
we
have
a
spec
feared
where
all
the
spec
for
this
particular
object,
dose
and
I
just
want
to
introduce
the
spec
field
there
as
well,
so
that
we
are
a
little
bit
more
flexible
when
it
comes
to
new
versions
and
so
on.
C
A
It's
very
to
almost
every
other
kubernetes
resource
I
mean
I,
I.
Think
I,
can't
think
of
anywhere
that
there
isn't
some
kind
of
specification,
except
for
things
that
don't
have
a
spec,
but
have
you
know
in
the
case
of
something
like
a
cluster
role
binding?
They
have
two
separate
fields
and
then
everything
else
underneath
them
is
is
a
sub
object.
You
know
that
a
sub
struct
inside
that
struct
I
guess
so.
A
C
A
Now
that
you
mention
it,
I
think
it
probably
came
from
the
original
CRD
implementation
because
see
our
keys
didn't
use
to
see
our
DS
didn't
use
to
have
some
resources.
Yeah
see
our
D
sub
resource,
which
enables
us
to
have
that
as
a
separate
struct,
whereas
before
it
had
to
be
one
piece,
because
you
couldn't
have
that
sub
resource
potentially,
but.
C
I
haven't
got
much
going
on
that
moment.
Yeah
I
think
there
might
be
some
interesting
now
you
can
stop
by
from
our
end
okay,
so
it
might
be
some
activity
but
pop
Nats
cool.