►
From YouTube: Config Working Group 2.15.18
A
All
right
so,
let's
started
tracking
the
work
items
and
I
pull
up
this
expression.
That
again,
as
for,
if
the
checking
our
progress
and
by
ourselves
and
not
really
a
request,
asking
people
to
do
put
a
lot
of
work
in
this,
and
so
Galle
and
prototyping
was
done.
Also
has
an
awesome
demo
last
week.
If
you
guys
missed
it,
please
go
to
the
recording
and
link.
That's
how
to
put
down
over
here.
I'm,
not
sure
how
persistent
the
zoom
recording
document
space
but
I
think.
A
C
C
I
am
still
trying
to
figure
out
the
right,
Albert
right,
cheap
algorithm,
to
make
sure
that
the
synchronization
is
written
correctly,
I
kind
of
stopped
spending
time
on
it
now,
I'm
just
trying
to
like
great
test
clean
up
the
whatever
code
I
have,
and
you
know,
try
to
get
it
in
and
then
try
to
solve
a
problem
later
on,
because
I
suspect
it's
just
gonna,
be
building
up
on
the
current
code.
Anyways.
A
A
A
So
DM
has
just
a
had
a
design
meeting
and
yesterday
in
the
security
working
group,
and
so
the
cluster
and
name
space
Grove
and
Brutus
Coker,
at
least
for
the
floor
matter,
has
been
settled.
We're
gonna,
follow
the
coup.
Vinod
is
same,
similar
thing
that
cluster
row
and
the
row,
but
a
few
details
and
I
will
roll
that
into
the
API
and
style
guide.
A
So
no
other
worker
in
this
area
has
been
pretty
much
started.
So
if
your
style,
the
style
guide,
is
in
unhone
check
the
incas
PR,
but
that
suggests
the
first
load
of
the
stager
that
we
were
adding
those
the
fine-tuning
and
things
over
the
next
month.
We
expect
this
to
be
stable
by
the
end
of
this
quarter
in
terms
of
word
style,
the
better
work
to
and
follow
this
new
style
I'm
still
working
on
the
pilot
code
to
allow
the
pilot
to
and
be
able
to.
A
Access
different
CR
DS
from
the
different
API
version
so
currently
and
pilot
only
has
one
client
and
because
we
expect
all
the
CR
DS
in
the
same
API
group
and
the
version
and
that's
not
gonna
work
in
the
long
term,
as
also
cried
the
waste.
What
we
want
to
do
with
in
galley.
We
want
to
have
two
different:
a
peer
groups,
internal
and
external,
so
this
worker
will
helps
to
move
that
forward.
But
the
top
part
about
this
is
the
pilot.
A
It
kind
of
expected
there's
only
one
kind
everywhere
in
the
codebase,
so
in
order
to
have
multiple
clients,
there's
some
kind
of
a
deeper
refraction
it
to
be
done,
and
this
nothing
else
has
been
move
along
very
well
and
Jason
is
out
for
this
week,
and
so
you
can
go
to
the
issue
to
check
the
validation
progress.
Oh
well,.
B
A
A
D
B
Have
a
lot
of
config
is
stored
as
V
1,
alpha
v,
1,
beta
and
main
that
way,
and
with
me
for
a
first-class
midis
resource,
there's
a
mechanism
to
automatically
alias
these
names
so
that
if
you
come
out
with
a
1.0
version,
you
can
create
a
1.0
into
point
and
it
will
access
the
same.
The
same
underlying
resource,
even
called
beta
order
or
v1,
and
that
does
not.
That
facility
does
not
exist
for
CR
east.
So
we
need
to
figure
out
what
to
do
about
this.
B
A
Yeah,
this
is
the
meeting
notes.
It's
also
linked
to
the
issue
we
tracks,
so
we
had
an
initial
meetings
and
there's
some
action
items,
basically
being
so
in
the
testing
our
plan
B,
it's
it's.
Basically,
we
didn't
assume
this.
We
have
to
freeze
the
CR
D
and
the
config
so
doing
epic
raid,
how
we
kind
of
accepting
two
versions
and
then
duplicated
one
working
world
work,
always
the
scripts
and
the
migration.
B
B
E
Had
a
piece
that
I
forgot
to
throw
in
here,
kubernetes
has
the
concept
of
component
configs,
whereby
you
can,
instead
of
passing
like
we
do
now,
a
bunch
of
templates
that
resemble
command
flags,
which
is
the
process
you
can
adapt
the
components
or
accept
the
actual
component
config,
which
is
a
Cooper.
Ladies
type.
Do
you
think
that
that
would
be
of
any
benefit
to
us
and
creating
component
configs
for
things
like
pilot
and
or
mixer?
Or
are
we
happy
with
what
we
are
kind
of
working
with
now
so.
E
A
E
B
Yes,
our
intent
there
was
always
do
we
want
to
remove
all
the
command
line
options
make
those,
if
possible,
be
dynamically
configurable
things.
Not
everything
can
be
dynamically
configured.
Sometimes
it's
just
a
start
up
thing
and
right
now,
we're
not
like
mixer
has
20
options
or
something
that
really
most
of
those
should
be
dynamic.
A
Okay,
so
if
nothing
else,
I
will
quickly
move
into
the
next
walk
agenda
and
I
will
do
a
quick
demo
I
with
the
CIT
with
the
revisions
and
the
sum
disclaimer.
This
is
a
kind
of
very
early
work
for
Demetri
violations
and
how
we
can
using
uncontrolled
revisions
and
to
to
save
some
of
the
revisions
for
the
CID.
A
So
we
enter
two
Canaries
API
server
and
this
work
having
on
getting
a
lot
of
help
so
from
Janet
and
and
and
if
you
have
any
question
I
think
the
main
purpose
is
I
kind
of
showing
through
the
damn
on
the
concept,
and
then
we
can
talk
a
bit
about
how
that's
meant
to
our
configure
model
for
each
do
and
how
we're
gonna
use
it
in
easter
config.
So
so
so,
basically,
the
the
demo
is
showing
now
moving
through
the
demo
mode.
A
A
So
it's
the
kind
of
empty
mini
coopers
cluster
and
there
is
some
resource.
Is
there,
are
gonna?
Remove
this,
so
I
can
make
sure
it's
a
thing.
I
remove
all
this
year.
These
there's
only
one
I
remove
the
one.
I
have
right
now,
so
in
the
demo.
Basically,
what
I
have
is
I
gonna
run
a
controller.
I
ended
my
build
the
controller's
through
the
central
controller,
because
I
want
to
do
in
parallel
was
a
galley
prototyping,
but
in
future
everything
about
this
will
move
up
and
into
it
galley
when
it's
a
bit
more
stable.
A
A
It's
got
a
little
bit
to
compile
and
after
that
it
will
run
once
it's
run.
It
will
stands
a
lot
of
error
message,
that's
because
they
cannot
find
the
facility.
So
in
this
demo
there's
only
one
CID,
it's
a
called
as
empo
example
for
so
to
get
a
peek
of
what
it
looks
like,
and
it's
it's
a
very
simple
example.
Basically,
it's
a
spec
has
two
Springfield's.
A
You
don't
need
to
care
what
these
are,
and
these
are
nothing
to
do
with
with
this
replica-
has
nothing
to
do
with
the
revisions.
So
basically
says
it's,
it's
just
a
random
things.
Okay,
now,
my
controller
is
up
because
it's
a
strongly
typed
and
tech,
the
clients,
so
they
cannot
find
the
food
that's
expected
now.
I
goes
into
to
run
to
load
that
CID.
A
Okay,
so
I
run
this,
then
the
full
CID
has
been
created
just
giving
a
peep
of
who
this
one
defines
what
what
the
CID
is.
So
after
that
the
controllers
starts
workers
and
stop
complaining,
but
until
now
there's
no
CID
objects.
So
what
I'm
gonna
do
is
that
I
cannot
create.
That
example
for
I
just
showed
you
guys
and
I'm
gonna
create
that
one.
Then
the
control
are
gonna,
do
some
work.
They
will
watch
the
CID
and
the
behind
the
scene.
It
will
create
a
revision
for
that
CR
the
objects.
A
A
So
you
see,
this
is
new
and
this
controller
revision
is
not
visible
when
you
type
a
get
off
it's
not
registered
and
for
and
for
that
command.
But
if
you
just
go
to
looking
for
that,
a
particular
kind,
you
will
see
this.
This
provision
has
been
created
and
also
you
can
do
is,
and
that's
the
you
see
the
objects.
The
name
matches
the
name.
D
B
A
Controller
vision,
given
apps
is
a
beauty
in
communities
resource,
ok,
so
upon
a
creation
of,
for
example,
for
the
controller
which
I
run
here
will
create
a
controller
revision
objects
that
estores
a
revision
of
that
example.
Ok,
so
if
you
could
take
a
look
at
what's
in
there,
you
can't
looking
at
basically
so
this
is
all
custom
defined,
so
basically,
I
define
the
patch
of
and
of
of
example,
for
basically
stores
everything
in
spec
and
there's
some
of
the
building
metadata
about
that
thing,
control
revision.
C
A
One
the
for
hash-
this
is
the
I
I
put
it
in
that
over.
Yes,
you
can
put
it,
and
so
this
is
the
you
can
put
in,
but
the
some
of
the
fields
is
building
with
the
only
fields.
Okay.
So
now
what
I
gonna
show
is
so
cute
cuddle,
and
so
consular
revision
is
currently
used
by
a
few
of
the
kubernetes
resource
like
a
stateful
set
and
the
demon
sects.
A
So
for
those
resources
you
can
have
a
comment
like
you
can
looking
for
the
history
for
those,
for
those
see,
are
these,
but
the
problem
is
this
way:
it
doesn't
work
because
it's
all
done
in
the
client,
so
you
need
to
modify
the
client
to
be
able
to
recognize
example,
foo
and
the
full
type
and
also
show
the
history.
So
in
order
to
this,
that
I
did
a
hack
on
the
client,
and
this
is
my
special
Cuba
kado.
A
A
Now
Cuba
kado
every
on
types.
If
you
want
to
implement
the
controlled
revision
you
have
to
put
in
some
special
code,
there's
no
generalization
mechanism.
At
this
moment,
let
me
quickly
show
how
to
update
that.
That's
a
version.
So
let
me
do
a
thing
is
I
know:
I
need
to
changes
at
the
example.
So
I
will
just
quickly
show
like
update.
The
update
is
basically
changed,
the
deployment
name
and
into
a
different
name
and
the
developer
cap,
and
that's
different
from
example
for
and
the
replica
one.
A
You
will
see
it
has
been
updated
too
joyful
and
the
different
replicas
and
you
will
see
it's.
The
revision
has
been
moved
along.
So
if
you
go
to
my
previous
command
to
get
a
cultural
revisions
now
you
see
there's
different
Euler
revisions,
because
every
time
you
update
this,
you
will
get
a
new
country
revision
and
one
thing
to
note
is
API.
Server
is
level
it
never
triggered.
A
B
A
A
C
What
is
the
platform
is
a
wiling
you
so
like
if
I
were
to
do
this
naively
I
would
still
have
that
controller.
I
have
a
different
Sierra
TSA
of
instability
revisions
and
then,
as
the
thing
changes
I
just
keep
inserting
entries
into
that
right.
So
this
is
a
naive
approach.
So
what
is
the
framework
providing
you
in
this
world
that
makes
it
easier.
C
We
don't
get
anything
like,
for
example,
all
I
want
to
do
a
replacement
kind
of
like
a
higher-level
operations
along
with
it's
just
that
it's
just
a
storage
area.
That's
not
really
visible,
as
as
a
regular
see
air
needs.
It's
a
random
type
of
thing.
Is
that,
because
that
is
that
the
additional
value
and.
A
Long
term
questions
it's
kind
of
if
they
want
to
extend
some
of
the
used
to
so
anyway,
and
so,
if
you
go
through
the
robot
history
now
you
see
there's
two
revisions.
So
now
you
can
do
something
like
you
can
do
undo
so.
I'll
do
is
a
row
back
and
there's
a
you
can
provide
parameter
like
the
two
revisions,
something
like
those
and
say
you
can
do
two
revision,
one.
This
one
doesn't
actually
work
and
the
reason
is
I
will
tell
you
guys.
I
said
the
demo.
I
did
something
or
I
run.
A
The
reason
is
the
cubic.
Odo
is
the
type
the
clients
and
this
example
foo
is
not
a
registered
with
was
their
standard
resource.
So
it
will
be
a
lot
more
work
to
get
example,
food
to
be
in
these
types,
so
they
can
find
that
a
particular
example,
an
example
for
object
and
then
link
to
all
the
revisions.
So
I
didn't
do
that.
A
That's
why
it's
just
like
a
demo
shows
you
can
undo
to
those
revisions
when
when
we
go
back
so
it's
gonna
expect
to
work
in
the
same
mechanism
as
if
you
are
familiar
with
and
Humanities
deployment
and
on
the
Diploma
record
fast.
That
you
can
kind
of
run
is
the
roll-out
undo
to
certain
replica
sata2
who
go
back
to
certain
deployment.
So
that's
that's
a
you
can
also
do
with
control
revision.
That's
just
what
I'm
showing
ok.
B
A
Exactly
so,
I
see
it's
not
very
easy
if
we
want
to
put
this
into
cuddle,
but
there's
much
easier
if
we
do
this
in
still
sitio,
so
something
I
just
noticed
is
for
CID
to
be
able
to
to
do
the
the
revisions.
So
all
the
east
you
see
are
these.
They
need
to
add
a
special
status
message
of
ratio
here.
Something
like
this
thing
is
not
coming
by
itself.
Basically,
all
the
C
IDs
we
need
to
having
some
dis
fields
and
putting
our
status
message.
A
They
didn't
do
it
for
us,
so
we
need
to
add
this
up,
but
those
status
message
expect
to
be
on
building
and
fields
that
you
cannot
change
it
by
the
users.
This
is
something
new
we
need
to
add
and,
as
I
just
discussed,
cue
picado
is
the
client.
So
if
you
want
to
do
ourselves,
we
need
to
figure
out
how
to
code
again
cid
types
and
it
might
be
just
easier
to
do
a
nice
new
cuddle.