►
Description
Tanzu Community Edition Community Meeting - April 6, 2022
We meet every Wednesday at 11am PT. We'd love for you to join us live!
This week we demo'd the v0.11.0 release of Tanzu Community Edition, which introduces new supply chain choreography capabilities powered by the open source Cartographer project. We also discussed the status of v0.12.0 release. Full notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA?both#April-6-2022-Community-Meeting
A
A
India
standard
time
and
if
you
still
aren't
able
to
to
meet
up
with
us
in
person
on
either
of
those
options,
you
can
still
find
us
in
the
tonzu
community
edition
channel
on
the
kubernetes
slack
workspace.
You
can
find
us
in
github
discussions.
You
can
add
your
request,
question
or
suggestion
in
our
issue
list.
You
can
also
email
us
and
you
can
find
us
on
twitter,
so,
hopefully
you're.
A
You
know
if
you
are
able,
if
you
need
to
reach
out
to
us
any
of
those
options,
you
can
find
us
at
we're
happy
to
help
when
you
attend
these
meetings,
and
you
do
have
something
you
want
to
discuss.
Just
add
that
down
at
the
discussion
topic
section
of
the
agenda
and
we'll
get
to
it
towards
the
end
of
the
meeting.
A
A
For
those
that
are
using
the
tonzu
community
edition,
we
would
like
to
know
more
about
how
you're
using
it
so
we've
created
this
pinned
issue
when
you
go
to
it,
there's
just
a
few
details.
We
request
from
you
so
just
fill
that
out
add
a
comment
here
and
that
just
helps
us
to
learn
more
about
how
folks
are
using
it
and
help
us
with
product
development
as
well
as
it
helps
other
members
of
the
community
understand
better
of
of
how
to
use
it
in
ways
that
they
may
not
have
known
before.
A
Moving
on
to
announcements,
so
if
you
have
been
attending
our
meetings
and
office
hours
previously
and
you've
been
watching
the
video
recordings-
and
you
notice
that
I
didn't
mention
the
office
hours
at
the
beginning
of
this
video-
that's
because
we've
decided
to
no
longer
have
office
hours
and
instead
we're
just
moving
to
community
meetings
every
wednesday,
and
these
will
be
45
minutes
long,
offering
a
little
bit
more
time
to
go
into
more
depth
of
any
discussion
topics.
Anything
that
you
need
may
need
help
with
as
well.
A
B
Yeah
sure
thing
so
for
those
who
don't
watch
the
xcd
mailing
list
very
quick,
very
constantly
there
was
a
data
inconsistency
issue
found
in
xcd,
and
this
version
of
that
cd350
is
in
v0110
of
tce.
So
just
we
wanted
to
give
the
community
a
heads
up
on
this
being
a
pre
1.0
project.
It
might
not
be
wise
to
run
tc
as
your
production.
You
know
container
orchestrator
today,
anyways,
but
you
know
in
case
you
are
doing
production
oriented
use
cases
which
is
totally
fine.
B
B
I
know
we
have
some
people
on
this
call
who
also
use
tkg,
which
is
the
vmware
product
of
tonzu,
so
just
note
that
this
is
also
something
in
one
five
to
be
aware
of,
because
many
people
do
run
that
in
production
in
our
next
release
of
tc,
which
we'll
talk
about
later
today.
This
will
be
addressed
and
then
in
a
patch
release
of
tkg
coming
up,
it'll
be
addressed
as
well.
So,
just
let
us
know
if
you
have
any
questions
in
slack.
We
just
wanted
to.
A
C
Yeah
hi
everyone
for
those
who
don't
know
me:
I'm
karthik
pm
at
vmware
doing
mostly
app
toolkit
and
cartographer
and
those
kinds
of
things.
I'm
also
glad
to
have
a
lot
of
the
members
of
the
cryptographer
team
here.
So
they
can
keep
me
honest
and
correct
me
in
the
during
the
demo
and
help
me
out
in
case
I
go
somewhere
where
the
democrats
don't
help
me
so
we'll
see,
I'm
also
going
to
kind
of
do
a
much
more
like
the
beginner
version.
C
In
fact,
the
cryptographer
team
recently
put
out
an
amazing
first
supply
chain
tutorial.
I'm
really
gonna
walk
through
that
with
pce
as
a
way
to
sort
of
how
we
can
use
cartographer
to
to
create
to
create
a
place
where
app
operators
can
create
a
supply
chain
and
how
app
developers
can
leverage
it.
So,
let's,
let's
go
through
it.
Let
me
share
my
screen.
C
C
So
you
may
have
like
a
test,
build
scan
and
deploy
as
part
of
your
path
to
production
and
having
kind
of
tools
for
each
of
those
pieces
and
being
choreographed
by
cryptographer
is
kind
of
like
the
main
pro
value
proposition,
in
a
way
that
it's
set
up
once
by
app
operators,
and
then
multiple
ad
teams
can
take
can
take
benefit
out
of
that.
So
that's
kind
of
like
a
brief
summary
about
it
and
I'm
gonna
jump
to
the
demo.
C
At
this
point,
you
can
see
my
blank
screen,
I'm
skipping
the
steps
of
which
you
probably
are
more
familiar
with,
or
are
on
the
known
for
you
from
a
transit
community
edition
perspective,
which
is
that
I
already
have
a
an
unmanaged
cluster
created.
So
if
I
do
this,
it
should
give
me
that's
the
demo.
I
have
that's
the
cluster
that
I
have
running.
What
I
will
start
with
is
installing
the
cryptographer
package
in
from
tce.
So
if
I
do.
C
C
Also,
as
this
happens
just
once
again,
if
I'm
just
going
to
put
it
in
chat,
if
you
want
to
check
out
cartographer,
I'm
just
going
to
put
the
link
there.
Also,
the
demo
that
I'll
be
doing
is
one
of
the
tutorials
that
are
provided
there.
So
you
could
very
much
take
it
for
your
first
spin
as
well
right
now,
I'm
gonna
go
ahead
and
install
cartographer,
so
so
I
I
had
two
two
packages
that
I
had
installed
search
manager
is
only
the
only
prerequisite
required
for
it
oops.
It
doesn't
look
like
that.
C
C
While
josh
said
that
this
is
not
your
production
environment.
For
now.
Imagine
this
tce
cluster
as
your
production
environment,
all
right.
So
what
I'll
do
is?
I
will
construct
the
templates,
the
kubernetes
templates
by
hand
for
the
first
time
I
do
have
the
pre-built
ones,
if
I,
if
I'm
not
able
to
do
it
right,
but
I'm
going
to
attempt
doing
attempt
creating
those
templates
by
hand.
So
the
first
one
that
I
make
sure
I
share
adam
okay,
so
just
create
a
new
file
and
say
curve
supply
chain,
template,
ammo
and.
C
Oh,
but
by
the
way,
when
I
meant
by
hand,
I
don't
I
didn't
really
mean
my
hand,
because
I'm
still
copying
it
from
my
script.
But
what
you'll
see
here
is
this
is
a
cluster
template.
Crd,
it
has
is
part
of
the
template.
It's
part
of
the
spec
itself.
It
has
a
template
for
deployment
and
it
has
some
fields
that,
as
the
comments
say,
some
are
unique.
Some
are
hardcoded
and
some
are
known
only
to
the
developer.
So
some
of
these
things
we
can
get
some
of
these
things.
C
I
might
be
an
app
operator
and
configure
it
for
all
developers
or
all
dev
teams,
for
example,
the
number
of
replicas
that
you
can
run
so
I'll
go
ahead
and
make
this
three
some
of
these
fields
can
be
got
by
the
objects
that
will
get
created.
So
we
can.
This
is
not
something
that
will
be
specific
to
developers,
but
with
something
that
is
unique
for
every
app
that
is
running
oops,
so
I'll
just
go
ahead
and
do
this.
C
So,
as
you
can
see
this
spec,
what
it
does
is,
it
has
a
template
for
deployment,
and
it
also
specifies
what
kind
of
pods
that
all
kind
of
containers
that
that
need
to
be
created
and
the
number
of
them
as
well
as
sort
of
the
selector.
So
this
really
is
a
is
a
template
for
how
a
deployment
should
happen
all
right.
So
now
that
I
have
this,
I
still
don't
have
what
the
image
should
be,
what
the
image
should
be
expected.
C
So
what
we'll
do
is
this
will
be
one
of
the
like
parameter
parameters
that
we'll
expect
that
the
developers
actually
enters
so
they
need
to
provide.
That
is.
This
is
probably
the
only
variable
that
they
use
that
the
app
developer
might
need
to
specify
all
right.
So
we
have
the
supply
chain
template.
C
C
C
I
will
also
add
the
role,
probably
don't
need
to
have
the
quotes
there
and
then
I'll
also
add
the
role
binding
to
that
service
account.
So
what
we
have
here
is
a
service
account.
We
have
a
role
which
allows
specifically
the
api
group
of
apps
and
specifically
resource
being
deployments
and
allows
you
to
create,
update,
delete
and
watch
get
some
of
the
sort
of
basic
actions
on
those
deployments.
C
This
is
what
will
allow
cryptographer
to
actually
create
the
deployment
on
behalf
of
the
developer,
so
all
right
now
that
I'll
save
this
and
finally,
what
I
need
is
the
actual
supply
chain.
So
the
reason
you
had
a
template
is
because
then
you
can
use
that
template
for
multiple
supply
chains.
If
you'd
like.
C
C
All
right,
so,
finally,
the
supply
chain
itself:
the
supply
chain-
is
a
cluster
supply
chain,
so
I'll
start
with
kind
of
just
specifying
the
api
kind
of
metadata
part
of
it
and
then
get
into
the
spec.
So
in
the
spec,
I'm
gonna
have
the
resources.
So
this
is
the
this
is
the
actual
supply
chain.
This
is,
in
my
mind,
like
the
actual
set
of
events
that
will
happen
in
in
this
in
the
power
production
setup.
C
C
Whatever
the
app
developer
needs
to
write
in
terms
of
their
yaml
and
hopefully
that
yaml
isn't
there
isn't
a
lot
honestly,
because
that's
the
whole
purpose
is
cartographer.
Sets
up
these
supply
chains
and
app
operators
can
set
up
the
supply
chains
and
then
the
developer
has
to
do
pretty
minimal
things
in
terms
of
of
using
them.
So
all
I've
done
is
created
like
a
api
version
for
sort
of
tying
in
with
workload
with
metadata
about
hello
and
also
just
the
label
of
pre-built
images.
C
This
is
actually
pretty
key,
because
this
is
actually
what
the
supply
chain
will
look
for.
To
know
that
I
need
to
use.
I
need
to
actually
create
deploy
this
image
based
on
this
workload
type.
This
is
the
label.
It's
going
to
look
for
all
right
now
that
I
have
all
of
the
yaml
files
constructed
I'm
going
to
go
ahead
and
come
back
to
actually
running
things.
C
C
C
C
C
So
looks
so
the
state
status
conditions
are
good
things
to
look
at.
Oh,
I
should
say
in
those
of
the
observation
section.
We
may
not
see
all
of
the
detail
because
I'm
using
cryptographer
0.2.2
in
pce,
but
I
think
some
of
the
new
features
from
cartographer
come
in
v
0.3
and
that's
going
to
make
it
to
tce
soon
as
well.
C
I
just
want
to
give
you
a
heads
up,
but
but
if
you
look
at
sort
of
the
status
that
conditions
you'll
see
that
you'll
be
able
to
see
that
you
can
see
the
specific
the
supply
chain
itself
is
ready.
So
what
it
looks
like
to
me
the
resources.
Some
submissions
are
complete,
so
it
it
should
indicate,
hopefully
that
things
are
in
place.
C
C
D
D
C
C
Cool
and
then
I'll
move
on
to
my
updates,
really
just
some
of
the
features
that
are
coming
cool.
Thank
you,
john.
Some
of
the
features
that
are
coming
in
as
part
of
the
just
to
kind
of
call
out
I
trans
application
platform
is
a
is
a
commercial
product
from
vmware,
but
some
of
the
open
source
technologies
we
are
bringing
into
transit
community
edition
which
make
it
the
so
the
story
of
getting
started
with
development
locally
way
easier.
One
of
the
things
that
are
coming
in
is
the
tenzoo
apps
cli
plugin.
C
C
I
am
a
developer
and
I
have
some
source
code
in
my
git
repo,
but
I
want
to
have
it
running
as
a
key
native
service
with
the
steps
between
going
from
source
to
image
to
a
actual
running
kinetic
service.
That's
the
supply
chain
package,
that's
coming
into
pce
and
app
toolkit
yeah.
I
think
I
also
saw
zero
there
so
he's
the
one
kind
of
spread
heading
that
effort
we're
also
working
on
trying
to
simplify
the
setting
up
the
keypad
dependencies.
C
So,
as
you
may
be
aware
already
that
you
can
install
kpac
today,
but
you
still
have
to
kind
of
go
through
a
set
of
steps
to
set
up
the
cluster
store
stack
builder.
All
of
the
all
the
things
you
really
need
to
be
able
to
build
images.
So
that's
something
that
we
are
working
on
and
then
finally,
I
think
you
saw
today
in
the
demo.
C
I
have
to
set
up
service
accounts
roles,
bindings
and
roles
for
me
to
for
for
me
to
tell
cryptographer
to
create
resources
in
my
namespace,
we're
we're
working
on
kind
of
making
that
easier
for
the
first
time
user
that
so
that
the
user
does
not
have
to
understand
all
of
the
sort
of
the
service
account
and
credentials
for
the
first
time,
do
it
for
in
their
default
name
space
and
then
going
forward.
They'll
still
be
talks
on
how
to
set
that
up
in
other
namespaces
yeah.
E
Yeah
any
thoughts
about
moving
like
a
lightweight
registry
or
even
tripping
down
harbor
as
a
registry
into
app
toolkit,
because
I
mean
that's
part
of
my
local
flow.
If
I'm
using
tce
locally
is,
I
know,
I'm
gonna
have
to
push
to
a
registry
and
then
pull
from
a
registry
right
because
that's
the
flow,
and
so
I
would
love
to
have
some
sort
of
local
to
use.
It
could
just
be
a
super
almost
like
a
flat
file
system
with
an
api
server
that
behaves
just
something
or
it
could
be
harbor,
but
not
all
of
harper.
C
Yeah,
that's
something
I've
been
kind
of
exploring
trying
to
figure
out
what
kind
of
image
registries
could
help
with
that.
I
think
nick
had
shared
an
image
registry
that
is
a
very
sort
of
temporary
one,
but
that
may
not
be
good
enough
for
like
kpac
to
use,
because
you
would
want
to
be
able
to
store
images
so
definitely
exploring
that.
C
Surprisingly,
it's
oh
looks
like
it's
got:
yeah,
okay,
good
to
know
scott
yeah,
definitely
on
on
my
mind,
to
explore
and
make
that
part
easier,
because
I
I
agree
for
local
development
and
for
a
lot
of
app
developers
who
are
not
wanting
to
learn
new
concepts.
Image
registry
is
one
of
those
that
we
have
to
today
and
we
have
to
be
aware
of
it
so
yeah
so
on
the
radar.
I
don't
have
more
concrete
answer
of
what
that
looks
like,
but
it's
definitely
on
top
of
mind.
B
B
What
are
we
on
right
now?
Two,
I
think
two
probably
v
zero,
eleven
four
there's
some
risk
there
with
dates
and
stuff,
but
the
reason
we
wanna
get
it
in
is
because
there's
some
backboarded
patches
that
will
improve
ux
like
there's
been
some
weird
log
messages
and
things
that
we've
cleaned
up
and
a
couple
other
nice
to
haves
and
then
also
there's
going
to
be
a
new
feature
in
that
framework
version
that
lets
you
see
what
addition
your
cluster
is
working
in.
B
So
for
those
of
you
who
do
work
with
like
tkg
and
tc
clusters,
you'll
be
able
to
see
whether
the
workload
cluster
is
a
tce
based
or
a
tkg
based
cluster,
which
can
be
helpful
in
some
automation.
Stuff.
Then
a
lot
of
our
work
for
this
release
cycle
to
may
10th
will
be
in
unmanaged
clusters,
one
that
I'm
gonna
call
out
real,
quick
and
then
just
have
john
talk
about.
Some
of
the
features
he's
excited
about
is
that
we
are
trying
to
switch
back
to
andrea
as
our
default
cni
for
unmanaged
clusters.
B
We
do
now
support
arm
machines,
so
m1
max
and
things,
and
unfortunately,
the
andrea
binary
is
having
some
issues
with
like
the
standard,
docker
desktop
vm,
so
long
story
short
we're
exploring
getting
back
to
entree
as
our
default
cni,
it
might
happen
in
0
12
or
we
might
push
it
out
a
little
bit,
but
that's
kind
of
the
boring
stuff.
John.
Do
you
want
to
tell
us
about
some
of
the
features
you're
excited
about
in
012
for
unmanaged
yeah.
F
Yeah
there's
a
lot
of
really
exciting
stuff.
Coming,
that's
already
been
implemented
or
is
pretty
much
on
the
way.
A
big
one
is
a
dynamic
resolution
with
the
tanzu
kubernetes
releases
via
a
compatibility
file.
So
now,
when
you
run
unmanaged
cluster
create
you
will
actually,
it
will
query
a
compatibility
file
up
on
the
hardware
registry
and
then
pull
that
down
and
then
inspect
what
versions
of
tkrs
are
compatible
with
that
version
of
the
unmanaged
cluster
binary
that
will
enable
us
to
not
have
to
recompile
a
binary.
F
Some
of
the
stuff
that's
being
worked
on
that
also
is
really
big.
Is
the
mini
cube
provider
is
coming
so
that
will
be
in
0
12.
That
means
that
you
could
define
tact
provider
and
with
mini
cube,
and
it
will
install
with
a
mini
cube
vm
and
all
the
install
options
and
stuff
are
going
to
be
there
with
that
as
well.
So
that's
a
really
big,
exciting
thing
as
well.
F
I'm
trying
to
think
what
else
start
stop
life
cycle
hooks
are
coming.
Josh
has
been
working
on
that
that'll
be
really
close
behind
the
mini
cube
provider
and
then
that's
all.
I
can
think
of
right
now,
some
other,
like
sugary
things
with
the
cake
there,
I'm
working
on
the
raw
kind,
config
merging
with
some
of
the
flat
configs
as
well.
That'll
just
give
users
the
ability
to
have
kind
of
a
template
that
they
have
with
the
config
file
and
then
be
able
to
modify
that
with
the
clip
flags
as
well.
F
B
F
Yeah
yeah,
absolutely
from
a.
I
guess:
that's
a
bit
of
an
implementation
detail,
but
the
mini
cube.
Libraries
are
not
really
exposed,
so
we
can't
really
go
out
and
grab
them
from
a
programming
perspective.
Instead,
we
expect
the
binary
to
be
on
the
system
and
in
our
preflight
checks,
we'll
actually
see
if
that
binary
is
on
the
system.
F
If
it's
runnable,
if
it's
like
ready
to
go
and
then
we'll
lock
out
some
useful
messages
user,
if
it's,
if
it's
not,
but
it
won't,
try
to
actually
go
and
install
that
binary
or
try
to
get
it
for
your
system.
That's
a
bit
out
of
scope
for
a
managed
cluster
itself,
but
outside
of
that,
it
will
then
call
out
to
the
binary
to
actually
do
all
that
stuff.
Yeah
so
expect
the
binary
to
be
there.
F
Looks
like
scott
asked
if
mini
cube
is
still
limited
to
one
cluster
per
machine.
No,
actually
you
can.
You
can
install
multiple
mini
cube
clusters.
Mini
cube
does
have
what
they
refer
to
as
profiles
again
a
bit
overloaded,
but
a
mini
cube
profile
is
essentially
a
mini,
cube
cluster
that
it
knows
about.
So
you
could
have
a
bunch
of
these
mini
cube
profiles
which
are
in
themselves
clusters.
Their
core
abstraction
is
mini,
cube
start,
which
starts
the
er,
creates
the
default
mini
cube
cluster
named
mini
cube
as
the
profile
right.
B
Yeah
I
was
testing
out
john's
pr
and
one
of
the
things
that
I
loved
seeing
is
with
minicube.
As
my
provider,
I
had
a
cluster
set
up
running
container
d
off
of
qmu,
and
then
I
had
a
cluster
right
next
to
it
running
off
of
docker
using
the
docker
driver,
and
then
I
had
a
kind
cluster
as
well
sitting.
Next
to
that,
because
so
just
seamlessly,
you
know
you
have
these
kind
of
back
ends.
We
can
plug
into
and
get
the
same
uc
or
unmanaged
cluster
functionality
again.
B
A
F
That
is
actually
existing
an
existing
feature
that
is
in
011
right
now,
where
you
can,
I
forget
the
flag,
I
think
it's
tac
e
for
existing
cluster.
You
can
actually
point
that
to
an
existing
config
to
kind
of
attach
to
that
existing
cluster.
So
if
you
had
a
mini
cube
cluster
or
something
else
on
your
system
running,
you
could
attach
to
that
and
it
will
install
the
the
tan.
Zoom
quote:
unquote:
bits
mostly
cap
controller
and
all
that,
but
it
won't,
it
won't
try
to
create
the
cluster.
B
G
I
don't
think
may
have
had
to
drop,
but
we're
a
little
yeah,
it's
a
little
like
this
this
week,
but
I
added
the
link
to
a
demo.
They
did
with
pce
flux
and
pinniped
and
dex
at
a
local
meet
up,
and
then
steve
knows
that
he's
working
on
some
pizza
data
operator,
demos
so
he's
starting
to
work
more
than
the
data
things,
and
we
have
probably
three
or
four
things
around
cartographer
coming
out
over
the
next
couple
weeks.
So
we'll
start
to
see
those
populated
in
here.
A
E
A
H
Yes,
I
am
thanks
yeah,
so
we
have
a
proposal
out
for
what
we're
calling
a
concierge
and
I
just
put
a
link
to
it
in
the
chat.
It's
also
what
nancy
is
showing
here
just
wanted
to
draw
attention
to
it.
I
don't
need
to
walk
through
every
point
of
it.
You
know
in
this
meeting.
People
can
do
that
offline,
but
want
to
draw
attention
to
what
our
purpose
here
is.
H
With
the
concierge
we've
heard
from
the
community
that
there
are
pain,
points
around
getting
the
tonzu
cli
installed
and
running
and
configured
correctly
and
troubleshooting
it,
and
this
idea
is
to
have
a
native
application
that
the
user
can
just
download,
run
it
and
it
installs.
The
tonsilli
gets
the
versioning
right
reports.
H
Any
problems
like
if
you
have
an
existing
tkg
version
and
you're
trying
to
install
tce
on
top
of
it,
that's
a
problem
and
actually
then
hands
off
to
the
ui
of
the
tanzu,
cliff
the
kickstart
ui
for
creating
a
management
cluster
and
in
the
future
it
can
hand
off
to
any
other
ui.
That's
available,
so
appreciate
feedback
on
this.
I
already
have
gotten
some
comments
on
it,
but
I
wanted
to
draw
attention
to
it:
we're
very
excited
about
the
possibilities.
H
I
see
scott
in
the
chat.
The
name
concierge
is
just
at
this
point
and
more
informal
name
that
that
we're
calling
it
sort
of
the
working
project
name
internally,
just
to
talk
about
it,
but
you're
right.
There
could
certainly
be
a
confusion
with
the
concierge.
In
fact,
we
already
had
a
question
previously
about
that,
so
we
we
may
want
to
rename
it
I'm
open
to
suggestions
for
what
would
be
a
happy
name
for
this.
A
A
I
looked
at
the
slack
thread
and
it
had
been
decided
to
go
to
google
groups,
but
looking
more
into
that,
I
thought
it
could
get
a
little
annoying
for
those
almost
300
folks
that
are
in
google
groups
to
be
bombarded
with
questions
popping
into
through
email
and
then
conversations
going
back
and
forth
through
there
and
just
kind
of
flooding.
Folks
inboxes,
so
yeah,
there's
slack
but
slack,
is,
is
kind
of
annoying
with
searching.
A
I
think
the
idea
is
to
just
have
one
so
that
it's
not
like
people
can
go
to
github
discussions,
certainly
to
ask
questions,
but
I
think
it's
more
so
like
creating
like
one
central
point,
to
put
any
questions
that
come
up.
Try
to
to
have
something
there
could
have
all
the
things
kartik
yeah.
I
agree.
A
E
This
kind
of
came
up
just
a
little
bit
and
somewhat
related
is
we
are
running,
nightly,
builds
and
we're
also
doing
status
updates,
and
we
don't
actually
because
of
the
way
kubernetes
slack
is
administered
for
good
reasons.
We
cannot
post
those
somewhere
on
slack,
I'm
used
to
irc
days
when
you
know
the
nightly
bills
would
get
posted
to
irc
or
they
get
put
somewhere.
E
I'd
be
interesting
to
hear,
if
there's
other
people
in
the
community
who
have
found
who
are
like
in
the
kubernetes
community
who
have
found
projects
that
do
a
good
job
of
doing
that
and
how
they
do
it,
because
I've
been
trying
to
think
about
what
would
be
a
good
way
for
us
to
do
that,
and
you
know
I'm
still.
Let's
do
it
in
irc,
because
irc
is
what
I
lived
and
died
by
for
a
while,
but
it
seems
the
world
has
moved
on.
E
A
Think
these
are
some
things
we
can
noodle
on
and
if
anyone
has
any
feedback
for
either
what
I've
proposed
or
what
stephen's
looking
for,
please
let
us
know
versus
you
know
you
can
come
find
us
on
slack
or
email
or
you
can
join
next
week's
meeting
and
provide
your
feedback
and
any
ideas
you
may
have.
We
would
love
to
hear
it
as
well
and
also
post
stephen's
issue
to
this.
The
discussion
topic
section,
so
you
can
go
to
find
more
information
about
what
he
just
talked
about
too.
A
Okay,
so
where
we
are
at
time,
I
will
stop
sharing
my
screen
all
right,
thanks
everyone
for
joining
today,
if
you're
watching
this
from
home
again,
please
come
join
us
live.
We
meet
every
wednesday
at
11
a.m,
pacific
time
and
if
you
want
to,
if
you
have
a
different
time
zone
that
might
be
suitable
for
you,
we
meet
monthly
second
thursday
of
the
month
at
9
a.m.