►
From YouTube: Viktor and Mikhail on cli-utils docs for v14.0 release
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
B
What
does
it
mean
to
take
ownership
of
this
config?
I
mean.
B
B
B
A
A
B
It's
not.
This
is
not
how
it
works,
so
let
me
explain
so
we
read
all
the
files
from
the
not
all,
but
the
matching
files
from
the
repository,
the
github's,
manifest
3.3
will
look
for
a
config
map
with
a
label
a
specific
label.
That's
how
we
locate
the
inventory.
Template
inventory,
object,
template
in
in
those
files
that
you
have
in
your
objects
that
you
have
and
we
ensure
that
there
is
only
one
well
zero
or
one.
B
A
B
A
B
B
A
A
A
The
content,
okay,
I
got
it.
Thank
you
great
okay
then
this
is.
This
is
fine.
I
understand
now
perfectly.
The
next
question
is
then,
really
that
how
to
adopt
how
to
how
to
start
using
the
gitlab
to
bend
this
agent?
A
What
changes
might
be
needed
in
configuration
like
the
inventory
policy
management?
If
I
already
have
a
cluster
that's
set
up,
I
have
my
kubernetes
manifests
in
my
computer.
It
could
be
in
git
as
well.
The
only
thing
is
that
those
were
not
applied
using
the
engine
were
applied
in
some
other
way.
Then
how
do
I
get
started.
B
Well,
deploy
the
agent
configured
to
work
with
this
repository,
you
can
create.
B
Point
the
agent
at
the
repository
or
commit
it
there
so
that
it
picks
it
up
or
you
can
let
it
just
create
one
in
the
cluster
and
take
it
and
put
it
into
the
repository.
A
The
inventory
policy
to
adopt,
if
not
an
inventor
or
something
like
that.
B
Okay-
I
forgot
about
this.
Yes,
yes,
it
will.
You
will
need
to
change
that
once
to
make
it
adopt
those
objects.
Yes,
sorry,
I
forgot
about
that.
B
A
The
user
goes
changes
the
agent
configuration
to
adopt,
if
not
in
inventory,
and
then
it
works
it
adopts,
and
then
the
user
can
change
it
back.
The
inventory
policy
to
something
more
restrictive:
okay,
okay,
the
what
happens
if
there
if
it
was
deployed,
for
example,
with
kpt
that
uses
an
inventory
policy.
B
B
B
Sorry
one
more
thing:
I
think
it
also:
okay,
maybe
that's
for
okay.
So
so
there
is
a
thing
called
field
owner.
So
when
you
apply
from
a
different
tool,
you
will
have
it
it
acts
as
a
different
owner,
so
the
agent
acts
as
agent
k
owner
so
in
the
field
house
called
field
owners
or
something
there's
a
field
in
the
metadata
field
of
each
object.
That
stores
information
about
the
ownership
about
of
which
field
and
it
will
not
match,
and
that
means
server
side
apply
which
we
use.
Now
we
will
say:
hey.
B
B
Fields,
if
you
want
to
manage
the
same
objects
and
they
will
conflict
on
each
apply,
okay
like
they
will
try
to
take
ownership,
and
there
can
only
be
one
owner
of
a
particular
field.
If
you
manage
one
part
of
the
object
with
kpt
and
another
part
with
the
agent,
that
will
actually
be
fine,
but
that
probably
is
not
the
case,
so
the
user
will
need
to
decide
what
they
want
to
have
as
the
owner
and
then
use
the
force
force,
ownership
or
something.
There
is
an
option
which
I
exposed
to
take
over.
A
A
That
was
that
was
the
the
documentation
part
I
will
have
to
leave
soon,
and
I
think
that
our
next
topic
is
much
bigger
and
it's
more
of
a
discussion
that
I
just
wanted
to
share
what
I
see
right
now
and
actually
I'm
creating
a
proposal
for
the
product
organization
to
think
around
these
terms
and
and
to
organize
ourselves
around
these
terms,
so,
even
perhaps
with
with
some
new
product
categories
and
teams.
A
Let's
let's
discuss
this
next
week.
If
you
don't
mind.
A
A
Calendar
as
well
tomorrow
actually
might
work
yeah
tomorrow
could
work.
A
B
Yeah
works
for
me.
We
don't
need
to
wait.
We,
I
think
it's
kind
of
it
needs
to
be
discussed,
and
otherwise
we
we
are
just
like
wasting
time.
Basically.
A
Sure
good
idea,
okay,
I
I've
sent
you
an
invite
for
tomorrow
and
that's
good
okay
cool.
Then,
let's
discuss
it
tomorrow,
any
other
russian
lessons.
A
B
B
Don't
say
this
to,
I,
don't
know,
border
control
or
something
of
course,.
A
A
A
Okay,
so
thanks
for
the
call
see
you
tomorrow
as
well
and
talk
to
you
tomorrow,.