►
Description
- Welcome and Objective
- Announcements
- Cluster API Discussion (Fabrizio Pandini)
- PM Updates
- Engineering Updates
- Thanks and sign off
A
Good
afternoon,
everyone
or
whatever
time
of
day
this
message
is
reaching.
It
is
wednesday
december
15th
and
we
are
on
our
second
community
meeting
for
the
month
of
december
for
tanzu
community
edition.
Thank
you
all
so
much
for
joining
us.
I'm
gonna
get
our
agenda
pulled
up
so
that
we
can
all
see
it
for
those
of
you
that
don't
know
we
have
two
types
of
meetings
here
in
our
community.
We
have
our
community
meetings
and
our
office
hours.
A
Okay,
so
I
have
welcomed
you
and
told
you
what
the
objective
of
this
meeting
is
announcements,
so
we
are
not
gonna
have
any
meetings
for
the
next
three
weeks
next
week,
the
week
after
or
the
first
week
of
the
new
year
in
observance
of
holiday.
So
please
take
this
opportunity
to
rest
so
that
we
can
all
come
back
next
year,
energized
and
ready
to
push
the
project
forward
even
more.
A
Secondly,
we
have
an
adapters.md
file
in
our
repository.
I
know
we
have
the
show
and
tell
area
in
our
discussions-
and
this
is
a
it's
very
similar,
but
a
bit
bigger,
so
if
you're
using
tce
in
a
way
that
you
would
like
to
share.
We
definitely
would
like
that
from
you,
so
you
can
submit
a
pr
against
that
adopters.md
file,
which
is
in
the
top
level
directory
of
the
repository,
so
that
we
can
learn
about
all
of
the
many
ways
that
folks
are
using
tons
of
community
edition.
A
Next,
we
have
the
kubecon
europe
cfp
closing
on
friday.
If
you
are
interested
in
submitting
something
that
prefers
or
uses
a
tons
of
community
edition,
please
let
us
know
if
you
would
like
us
to
help
with
that.
I'm
working
on
one
right
now,
because
I
am
not
super
great
at
planning
ahead.
So
if
you
are
in
a
similar
boat
or
just
want
an
extra
pair
of
eyes
on
what
it
is
that
you're
working
on,
please
do
let
us
know
in
the
slack
channel.
A
A
The
next
thing
we
have
in
our
agenda.
We
want
to
introduce
you
to
cluster
api,
which
is
a
project
that
is
very
related
to
tons
of
community
edition
and
everything
that
we're
doing
with
the
all
of
the
all
of
the
tanzu
ecosystems.
So
I
want
to
hand
it
over
to
fabrizio
to
give
us
a
bit
of
a
of
an
introduction
to
cluster
api.
B
B
Basically,
with
cluster
api,
you
can
create
your
cluster,
your
machine
in
the
same
way
that
you
create
your
pods
and
your
deployments
so
yeah
you
have
a
similar
constructor.
We
have
machine
machine
deployments
in
kubernetes,
you
have
pod
and
and
deployment
and
stuff
like
that,
the
the
night,
the
project
went
a
long
way
and
we
reached
the
v1
0
recently
in
october
and
with
a
nice
blog
post
that
you
can
find
in
cncf.
That
shows
all
the
companies
that
are
using
cluster
api
in
production.
B
B
I
know
that
you
are
using
the
docker
provider,
the
sphere
provider,
the
ws
provider-
maybe
I'm
not
up
to
date
on
all
the
type
of
infrastructure,
the
azure
one,
probably
and
but
out
there.
There
are
many
for
different
type
of
infrastructure,
all
community
maintained
and
and
yeah.
The
the
last
things
that
that
is
always
nice
to
talk
about
is
that
like
tce
cluster
api
is
really
a
community,
so
we
have
also
our
meetings
every
wednesday
and
they
there
are
a
lot
of
people
from
different
companies.
B
C
I
see
you're
there
talking
please
yeah
yeah.
I
wonder
why
or
if
there
is
any
plan
to
make
a
docker
or
podma
or
something
like
that.
I
need
runtime,
continuous
runtime
on
your
laptop
and
infrastructure
provider,
because
I
know
there
is.
There
is
copy,
but
capti
is
not
really
a
pure
infrastructure
provider.
B
So
the
that
that's
a
that's
a
nice
question,
so
capd
started
like
a
development
project,
let's
test
cluster
api
locally,
and
then
we
we
saw
over
time
interesting
usage
of
it.
There
was
also
some
variation
instead
of
the
block
developing
cup
d
locally,
the
developing
of
the
in
a
kubernetes
cluster
stuff.
Like
that
now
we
recently
opened
an
issue.
B
B
A
D
B
Yeah,
so
let
me
say
we
are
getting
there
in
stages,
so
we
want,
but
due
to
the
declarative
model
of
cluster
api.
Basically,
we
we
were
facing
a
chicken
egg
problem.
We
need
a
cluster
to
spin
up
other
clusters
and
using
a
bootstrap
cluster
was
convenient,
given
that
at
the
time
the
kind
was
basically
created.
We
I
also
some
of
us,
contribute
also
to
kind
stuff
like
that,
so
it
it
was
convenient
in
the
first
release.
We
have
a
a
fairly.
Let
me
say.
B
Closed
project
that
was
creating
a
booster
cluster
and
pivoting,
and
now
with
cluster
cutter,
we
have
something
that
is
more
composable,
so
allows
you
to
pick
your
own
cluster
is
more
composable.
What
we
are
looking
for
is
something
like
like
kcp,
the
project
that
that
folks
are
working
on,
so
it
is.
It
is
basically
a
binary
that
contains
a
really
a
minimal
api
server
that
can
handle
crd,
and
the
idea
is
to
use
this
binary
as
a
seed
to
create
the
first
cluster
and
then
go
on
to
like
that.
B
A
B
Yeah,
if,
if
there
are
no
questions,
I
I
only
would
like
to
say
thank
you
to
tce
community
because
they
are
making
two
things
that
are
really
important
for
us.
First
of
all,
they
are,
you
are
putting
a
nice
ux
on
top
of
our
bootstrap
sequence
and
that
that
basically
brings
customer
api
near
the
user.
And
second,
you
are
really
unlocking
the
the
potential.
B
E
The
first
one
is
that,
while
we're
preparing
release
candidate
three,
we
discovered
that
the
build
of
andrea
cni
that
we
had
isn't
suitable
for
us
to
ship
in
tons
of
community
edition.
In
order
to
address
it,
we
need
to
collaborate
with
other
groups
inside
vmware
they're,
not
going
to
be
able
to
remedy
it
until
after
the
new
year.
So
as
of
now,
we
expect
to
have
an
rc3
in
early
january
general
availability,
not
long
after
that,
and
we
should
have
unlike
rc1
and
rc2.
E
Excuse
me
so
we'll
be
restating
the
high
level
roadmap
and
I
will
post
an
update
to
prompt.md
soon,
but
that's
going
to
mean
that
a
little
bit
of
the
things
that
you
see
in
zero
to
three
months,
specifically
the
developer
oriented
projects
and
the
bitnami
library
are
going
to
come
a
bit
later.
So
we
look
forward
to
your
help
in
the
future
prioritizing
development
and
technology
inclusions
in
tce.
F
F
So
I
won't
waste
all
your
time
by
describing
these
proposals
in
depth.
But
if
the
short
description,
I'm
about
to
give
interests,
you
you
can
click
on
the
link
in
the
hack
md.
We
welcome
comments
in
the
issue
or
the
design
docs,
which
some
of
them
do
have
design
docs
linked
to
them,
and
if
you
do
want
to
talk
in
a
more
synchronous
manner
about
some
of
these
proposals,
you
can
hit
us
up
in
slack
or
come
to
office
hours.
F
The
proposals
we
have
open
right
now.
2686
is
a
proposal
on
proposals.
We
are
vetting
our
process
to
make
this
more
formalized
and
allow
you
all
to
give
input
on
the
things
we're
thinking
about.
Doing
226
is
the
most
established
proposal
that
is
replacing
the
tonzu
existing
standalone
cluster
model
with
a
new,
more
minimal
bootstrapping
model.
F
That
one
is
very
close
to
getting
approved.
I
think
we
are
currently
addressing
the
most
important
engineering
topic
of
all,
which
is
what
to
name
it.
Two
four,
six,
two
and
two
six,
eight
nine
are
about
bringing
new
packages
into
our
package
repository,
namely
kbac,
k-pac
and
cert
injection
web
hook.
F
2717
is
a
behemoth,
that's
actively
being
written.
This
is
how
we
are
going
to
approach
creating
a
decoupled
release
of
community
edition
from
our
downstream
product.
So
this
is
how
we're
going
to
be
able
to
ship
newer
versions
of
kubernetes
on
treya
and
even
introduce
things
like
stable
channels
and
alpha
channels
with
you
know,
different
ways
you
can
deploy
and
distribute
community
edition
and
then
the
last
one's
quite
small,
but
1723
we
moved
from
a
pending
proposal
to
an
accepted
proposal.
F
It's
some
enhancements
on
our
image
linter
process
to
ensure
that
we're
linting
for
images
that
might
have
licensing
issues
in
a
more
eloquent
manner,
and
that
is
it
so
again,
if
any
of
those
piqued
your
interest,
bookmark
it
check
it
out,
read
through
it,
add
comments
and
do
let
us
know
in
slack
or
in
an
office
hours.
If
you
want
to
talk
about
some
of
these
in
a
in
greater
depth,
thanks.
G
Can
I
give
a
comment
here
just
because
I'd
love
to
hear
a
meeting
yeah,
you
can't
go
immediately.
First
of
all,
I
love
that
you're
wearing
a
puffer
on
the
call
good
call,
that's
a
good
good
wear.
Second
of
all,
I
you
seem
to
be
missing
the
most
important
comment,
which
I
mean
a
proposal
which
has
yet
to
be
written,
which
is
the
build
the
steve
platform
release
proposal,
which
is
out
of
the
box.
I
can
just
use
it
for
my
work,
I'm
waiting
for
that.
So
that's
I'm
giving
you
my
new
theme.
G
Every
meeting
from
now
on
that
nigel
cajoles
me
to
enjoy
join,
will
be
pushing
for
a
box
that
I
can
installation
that
I
can
use
right
out
of
the
box
rather
than
having
to
install
all
the
other
pieces
as
a
developer.
An
app
developer
is
this:
getting
back
to
that
opinionated
install
that
we
were
talking
about
before
most.
Definitely
it
doesn't
have
to
even
include
tap,
I'm
not
even
going
to
say
we
need
to
go
all
the
way
to
tap,
although
that
would
be
nice.
G
I
just
mean
something
where,
like
I
have
an
ingress,
I
have.
I
have
a
repository
probably,
but
just
basically
where
I
can
deploy
like
write
some
code
deploy
a
container
and
I
actually
can
see
it
rather
than
here's
a
container
drop
it
in
and
then
port
forward
and
do
all
that
other
stuff.
That's
what
I
mean
cool.
F
F
E
Yeah
and
and
steve,
the
idea
of
you
know,
patterns
or
meta
packages
is
definitely
something
that's
in
our
scope.
You
know
it
was
on
the
high
level
roadmap,
even
though
there
were
no
proposals
for
it
yet
and
tap.
For
example,
tap
oss
is
definitely
planning
on
having
a
single
install
for
the
for
their
pad.
Their
hook
hole
pattern.
G
G
Okay
and
roger,
I
also
want
to
commend
your
bravery.
I
know
it
may
not
be
a
a
star
trek
shirt,
but
I
really
commend
your
bravery
on
wearing
what
looks
like
a
red
star
trek
shirt
with
the
space
in
the
background
in
a
public
meeting
to
take
one
for
the
team
like
that
is
really
brave
of
you.
I
just
want
to
let
you
know
you
know
it's
in
the
job
description
right,
yeah.
I
know
the
red
you're,
the
red
shirt,
okay,.
F
I
just
want
to
call
out
one
quick
thing
too,
not
related
to
steve's
point,
but
just
to
make
sure
that
I'm
not
giving
off
the
wrong
impression.
A
lot
of
the
proposals
that
you
all
see
here
do
not
represent
the
only
work
that
we're
doing
we're
still
fixing
bugs
implementing
features,
we're
going
to
bring
these
proposals
and
their
statuses
to
community
meetings.
F
Just
because
these
are
the
larger
things
that
impact
the
project
in
its
direction,
and
we
just
want
to
make
sure
that
everyone
in
the
community
is
aware
of
them
so
that
we
can
get
input
as
we
progress.
But
again
it
is
only
a
subset
of
the
work
we're
doing.
I
don't
want
you
to
think
that
any
bug
or
issue
you
file
that
isn't
a
proposal
isn't
is
necessarily
not
going
to
get
worked
on.
So
thanks.
A
F
Yeah,
you
got
it
our
next
step,
roger
and
I
were
just
talking
about
it
before
this
call
is
with
the
updates.
The
roadmap
roger
alluded
to
we're
gonna,
do
a
better
job
of
getting
one,
the
roadmap
updated
and
then
two
having
those
bigger
items
linked
into
their
proposal
and
then
upon
the
proposal
being
accepted.
F
Having
the
proposal
track
the
many
many
work
items
it
would
take
to
realize
that
so
the
answer
took
nigel's
question
is
yes,
and
in
the
future
early
2022
we're
gonna
have
a
much
better
flow
here
where
you
all
can
see.
Here's
the
roadmap,
here's
the
proposal
on
a
technical
level
that
gets
us
there
and
then
here's
the
progress
of
what
we're
burning
down.
To
achieve
that.
So,
looking
looking
forward
to
that,
I.
F
A
A
A
So
you
know
the
next
time
you
see
us
we'll
all
be
one
year
older,
wiser
happier
for
just
having
have
having
had
very
fulfilling
and
relaxing
holidays
all
of
that
stuff
thanks
so
much
for
sticking
in
with
us
since
october,
since
the
public
release,
we
very
much
appreciate
you
being
a
part
of
our
community
and
we
will
see
you
next
year.
Happy
holidays
thanks,
y'all,
bye,.