►
Description
Full Meeting Notes: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA
- Welcome and Objective
- Announcements
- Meet the kpack team
- PM Updates
- Engineering Updates
- Advocacy Updates
A
Good
afternoon,
everyone
today
is
wednesday
february
2nd.
It
is
our
first
community
meeting
for
the
month
of
february
and
we're
excited
to
have
you
here.
Give
me
a
second.
I
will
share
my
screen,
so
we
can
all
collectively
look
at
our
agenda
if
you're
here
and
want
to
add
your
name
to
the
attendees
list.
Please
do
so
up
at
the
top
there.
I've
dropped
the
hackmd
link
in
the
chat.
A
A
The
objective
of
our
community
meetings
is
to
give
you
an
update
about
the
project,
the
roadmap,
how
things
are
going
with
engineering
essentially
to
give
you
updates
and
announcements
so
that
you
understand
what's
coming
up
next
and
then
on
the
week
after
our
community
meetings,
we
have
our
office
hours,
which
is
an
open
format
for
you
to
come
and
get
your
questions
answered.
We're
going
to
start
off
with
some
announcements.
First.
Is
that
a
reminder
that
we
have
our
adopters.md
file
there?
A
I
want
to
thank
scott,
carlos
and
robert
for
opening
prs
against
that
adopters
file
to
get
our
first
adopters
added
to
the
tons
of
community
edition
repo,
hopefully
we'll
work
out
everything
and
get
those
prs
merged
soon.
Community,
shout
outs:
this
is
everyone
who
submitted
and
had
prs
merged
in
the
month
of
january.
So
thank
you
to
all
of
you.
You
can
click
each
of
those
links
and
see
those
pr's
that
folks
have
added
so
for
those
that
might
have
missed
it.
B
B
We
are
a
small
team
of
of
four
engineers
and
a
product
manager.
I
guess
I
will
say
we
do
have
working
groups
every
tuesday
at
10
a.m,
eastern
time,
and
we
have
a
slack
in
both
the
build
packs
slack
and
the
k-pack
slack.
If
anyone
ever
has
any
questions
or
wants
to
chat
about
anything,
k-pac
related
yeah,
that's
where
you'll
find
us
is
there
anything
else,
nigel
that
you
wanted
me
to
talk
about.
A
No
tom,
I
think,
that's
great
and
if
folks
want
to
have
a
look
at
what
we
have
in
the
hackmd,
there
was
a
pretty
great
demo
from
tom,
where
you
can
find
all
of
the
code
there.
I
have
it
linked
there,
the
repository
for
tom's
demo,
and
then
we
had
a
thread
during
the
office
hours
that
answered
a
lot
of
questions
and
had
a
pretty
lively
discussion
about
the
project
and
what
to
do
with
it.
So
I
would
encourage
you
to
check
out
those
two
things.
B
A
Yeah,
it
was
great
to
see
so.
Hopefully
we
get
a
lot
more
feedback,
a
lot
more
synergy
between
the
tce
users
to
get
kpac
working
better
for
everyone.
So
thanks
again
tom
for
being
here
thanks
for
the
demo
last
week
and
for
the
intro
to
the
team.
Just
now,
we've
got
a
lot
of
updates
from
our
about
our
road
map,
so
I
want
to
hand
it
over
to
our
product
manager,
roger.
C
C
D
D
C
D
C
The
format
well,
why
don't?
I
just
talk
through
it
instead
of
time
frames,
which
are
you
know
as
unreliable
as
in
many
road
maps?
You
know
they
all
have
the
disclaimer
about
not
a
commitment
and
time
frames
can
change
and
so
on.
Since
that's
true,
we
thought
that
what
would
be
at
least
as
meaningful
to
people
in
looking
at
the
project
is
the
state
or
stage
in
the
process
of
the
item
you
know
is
it
just
submitted
is?
Was
it
just
submitted?
Is
it
waiting?
Is
it
awaiting
a
proposal?
C
C
This
was
this
was
last
updated,
I
think
about
what
josh
about
20
minutes
ago
and
as
before,
we'll
group
things
that
are
out
there
into
themes.
They
will
be
updated,
we're
going
to
when
it
is
targeted
for
a
release.
We
will
show
the
target
release.
Sometimes
activities
span
more
than
one
release,
so
they'll
be
shown
as
ongoing
things
that
either
are
general
groups
of
things
or
our
efforts
that
aren't
specifically
in
a
release
will
probably
show
you
know
a
phase
of
na.
C
C
C
It
is
a
goal
that
we
don't
have
any
approach
in
mind
and
it
may
very
likely
be
work
that
has
to
be
done
outside
of
this
team.
So
we
can't
really,
you
know,
put
a
time
frame
around
it
to
reduce
time
to
cluster
availability
in
the
public
clouds.
We
did
a
great
version
on
you
know
with
unmanaged
cluster
for
the
local
machines,
but
we
really
need
to
we
getting
clear
signals
that
we
need
to
reduce
time
to
cluster
availability
on
in
the
clouds
as
well.
You
know
private
and
public.
C
One
upcoming
in
the
next
release
is
as
of
right.
Now
you
can
take
a
tce
cluster
and
attach
it
to
tons
of
mission
control,
which
means
you
can
do
some
management
functions
in
it.
But
you
can't
do
life
cycle
management
and
in
version
0.11
it
will
be
registerable,
which
means
that
you
can
register
management
server
and
have
it
control
the
management,
server
and
all
of
its
workload
clusters.
C
E
F
Yeah,
no
thanks
steve
for
bringing
that
up,
there's
actually
a
design
dock
proposal
for
specifically
the
meta
package
capability
available
in
in
the
tc
repo
right
now.
The
application
platform,
I
think,
you'll
see
so
down
there
in
rogers
roadmap
as
one
of
the
items
that
is
sort
of
planned
to
come.
I
I
was
literally
just
started
this
meeting,
creating
a
pr
to
like
share
the
links
of
those
proposals
to
rogers
roadmap
and
then
github
went
down
so
that
couldn't
happen.
F
C
I
did
not
speak
about
what
our
life
cycle
for
kubernetes
packages
is
because
there's
still
some
alignment
to
be
done
on
that,
especially
since
right
now
our
ability
to
be
out
of
sync
with
kubernetes
is
dependable
or
is
dependent.
I
should
say
on
some
work
that
is
being
planned
and
should
be
underway
soon
to
uncouple
some
of
the
interlocking
between
tonsu
community
edition
and
thompson
kubernetes
grid,
but
that
will
rear
its
head
in
this
section.
C
When
we're
really
ready
to
talk
about
it,
we,
the
two
areas,
we're
looking
at
now,
are
first
of
all
air
gap
support,
and
we
call
we
call
this
category
limited
internet.
It
ranges
from
proxies
to
full
air
gap
and
I
think
a
first
step.
If
I
can
find
somebody
who
can
do
it
soon,
would
be
simply
to
test
the
air
gap
documentation
for
tkg
against
tce.
We
want
to
simplify
from
there,
but
that's
a
great
first
step.
C
We
haven't
done
anything
with
it
yet,
but
it's
it
has
been
raised
to
us
by
people,
and
it's
pretty
important,
and
the
other
is
just
an
ongoing,
is,
is
just
being
able
to
be
sure
that
we
have
end-to-end
tests
that
are
meaningful
across
all
providers
and
that
everything
gets
tested
everywhere.
It
needs
to
be
questions
there.
C
C
This
is
the
issue
I
talked
about
before
about
making
changes
to
allow
us
to
separate
some
of
these
key
resources
from
tkg
and
then
be
able
to
move
to
be
really
fully
upstream
of
tkg
and
then
in
the
domain
of
the
application
platform
having
a
installable
environment
with
the
pre-configured
tools.
I
think
this
talks
to
what
you
receive
have
the
the
tools
and
processes
and
documentation
for
package
contribution
and
maintenance.
C
No,
I
think
that
covers
it,
just
okay
cool
and
finally,
we
are
working
with
the
bitnami
folks
to
or
conversations
with
the
vietnamese
folks
that
should
that
we
hope
turns
to
work
soon
to
expose
through
cube
apps
the
the
packages
in
bitnami
library
and
have
them
be
manageable
in
a
compatible
way
to
packages
in
the
repo
that
is
either
either
cube.
Apps
will
deal
with
both
film
charts
and
cargo
packages
or
bitnami
will
also
add
packaging
as
carpet
packages,
and
then
there's
some
other
areas
that
are
just
general.
C
C
And
finally,
we
have
had
a
fair
number
of
requests,
especially
for
mac
users
for
arm
either
worker
nodes
or
workload
clusters
and
we're
dependent
on
some
work.
That's
upstream
of
us,
so
we
can't
really
schedule
it,
but
that's
you
know
we
would
like
to
get
on
like
to
be
able
to
run
on
first
of
all,
footstep
from
and
then
run
locally
on,
macs
that
are
newer
than
a
year
and
a
half
old.
A
C
C
G
We
are
actively
validating
what
will
be
the
v010
release,
can't
wait
to
get
that
out
to
y'all,
hopefully
in
a
week
or
so
we'll
be
going
we're
going
to
release
engineering
validation.
Now,
there's
some
promotion
stuff.
We
have
to
to
get
done.
So,
if
you're
not
aware,
this
has
been
heavily
delayed,
we've
learned
a
ton
of
stuff
about
how
to
release
software
in
the
open
and
we're
hoping
future
releases
will
go
a
little
bit
smoother
than
this
psych.
G
To
get
that
out
to
you
all,
both
with
all
the
package
updates
and
the
unmanaged
cluster
model.
Our
proposal
updates
are
pretty
light.
This
week
we
did
have
the
kpac
introduction,
which
many
of
you
have
already
heard
about.
So
that's
a
proposal
that
is
fully
completed
and
implemented.
Thank
you
so
much
kpac
team
and
tom,
especially
for
shepherding
that,
through
with
very
little
guidance
and
as
a
reminder,
we
have
a
request
for
comments
open
for
how
we
plan
to
improve
the
visibility
of
management
and
workload.
G
G
We
have
some
stuff
about
how
the
tanzu
cli
can
be
used
in
the
context
of
both
tce
and
tkg,
without
overwriting
and
killing
your
whole
environment,
and
we've
got
this
ui
thing
that
roger
was
alluding
to
to
help
people
on
ramp,
so
lots
and
lots
of
cool
stuff
coming
soon
and
I'll
have
an
update
for
you
next
office
hours.
That's
it.
A
H
Hey
yeah,
so
the
recordings
for
korra's
kpak,
talk
and
scott's
tons
of
communication
and
carvel
talk
are
now
on
youtube.
This
friday,
cora
and
whitney,
I
believe,
are
doing
a
tgik
session
on
kpac
and
then
on
february,
8th.
So
next
tuesday
we
have
a
tap
overview
which
last
I
checked
scott
mentioned
he's
here,
so
you
can
say
if
I'm
wrong,
but
mentioned
that
times,
communication
would
be
involved
in
that
as
well.
There's
also
one
on
february
22nd,
but
that
pr
is
in
the
works
right
now.
A
Awesome
thanks
so
much
that
does
it
for
all
of
the
updates
that
we
have
for
our
community
meeting
this
week.
I
want
to
say
again
a
huge
thank
you
to
all
of
you
for
being
here.
It
means
a
lot
that
we
have
a
community
that
is
growing
and
having
a
lot
of
active
participants,
both
submitting
prs
and
comments
and
also
coming
to
our
community
meetings
and
watching
the
recording.
So
to
all
of
you
who
came
and
all
of
you
who
are
watching
the
recording.