►
Description
Full Meeting Notes: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA
- Welcome Back
- Objective
- Announcements
- Meet the Release Engineering Team!
- PM Updates
- Engineering Updates
- Advocacy Updates
- Open Discussion
A
Hello,
everyone
happy
2022
welcome
to
our
very
first
community
meeting
of
the
year
2022..
We
are
so
excited
to
have
you
here.
I
hope
that
your
holidays
were
restful
and
for
those
of
you
that
have
been
back
a
little
sooner.
Maybe
you
were
here
last
week
for
our
first
office
hours.
We
had
some
great
discussions
and
looking
forward
to
continuing
that
here
in
our
community
meeting.
I'm
gonna
share
my
screen
here,
so
you
all
can
see
what
we're
working
through
today.
First
thing
welcome
back
happy
new
year
yay.
A
We
use
this
as
more
of
an
announcement
type
thing,
a
one-to-many
presentation,
so
we're
going
to
work
through
a
lot
of
those
and
let
you
know
what
the
state
of
tanzania
community
edition
is,
as
we
kick
this
year
off.
So
for
our
first
announcements
tomorrow
we
have
an
event
tons
of
to
go
in
dallas
texas.
I
am
actually
going
to
be
leaving
after
this
meeting
to
go
up
there
and
check
it
out.
A
A
The
next,
an
announcement
that
we
have
is
that
we've
got
an
adopters.md
file.
I've
spoken
to
a
couple
of
folks
who've,
been
helping
us
out
here
and
have
been
doing
some
using
tce
in
the
wild
and
we'd
love
to
recognize
that
effort.
So
if
you
wouldn't
mind
checking
out
the
adopters
itemd
file
and
adding
your
use
case,
your
logo
to
let
us
know
where
tce
is
outside
of
vmware
the
community,
shout
outs
are
going
to
go
out
a
little
bit
later.
A
A
A
B
B
So
this
devastating
pipeline
is
actually
triggered
every
time
there
is
a
golang
or
like
shell
script,
code,
change
of
any
golang,
related
code
change
and
shell
script,
and
there
is
also
so.
This
is
an
example
of
that
this
simply
does
a
full
build
and
then,
like
you
know,
it
checks.
If
the
build
is
good
and
not
broken,
so
the
bill
has
to
work,
and
then
we
have
daily
official
bills
which
gets
triggered
every
once
in
a
day.
So
you
can
see
how
this
has
been
triggered.
B
B
B
C
These
letters
resides
under
community
edition
hack
directory.
So,
as
you
can
see,
image
lantern
is
there.
Currently
url
enter
is
outside
the
tce
repo
and
other
lenders
resides
under
check,
so
here
misspell,
linter,
mdlint
and
vyaml
interest
there.
So
the
basic
functionality
of
these
linters
are
image.
Linter
is
checking
all
the
oci
images.
C
Currently,
it
is
restricting
alpine
image.
Url
intel
is
checking
all
the
urls
whether
they
are
returning
the
valid
status
code
or
not.
Misspell
inter
is
checking
all
the
spellings
in
the
all.
The
files
amd
lint
is
for
markdown
and
yml,
inter
is
checking
whether
all
the
yml
files
is
following
the
rules
set
by
viable
linter
or
not
for
the
logs.
You
can
navigate
to
actions,
and
here
are
all
the
pass
and
fail
logs.
B
Now
that
we've
seen
our
linters,
which
are
also
kind
of
like
tests,
because
they
verify
the
code
at
some
to
some
basic
level
for
many
things,
we'll
be
looking
at
other
tests
that
we
have
in
our
tc
code
base.
So
we
have
end
to
end
tests
over
here,
so
you
can
see
that
we
have
a
end-to-end
test
for
the
management
cluster
on
docker
and
then
standalone
cluster
on
docker
and
then
aws
management
and
workload.
B
Cluster,
aws,
standalone
cluster
same
for
azure
management
and
workload,
azure
standalone
and
then
the
same
for
vsphere
management
and
workload
and
then
vsphere
standalone.
So
we
also
have
end-to-end
tests
for
plug-ins.
Apart
from
you
know,
the
standalone
cluster
plug-in
management,
cluster
plugin
and
workload
cluster
plugin
there
are
like
plugins,
like
diagnostics,
plugin,
and
then
there
is
conformance
plugin.
As
of
now.
B
We
just
have
an
enter
index
for
the
diagnostics
plugin,
and
we
also
have
like
extra
checks
for
diagnostics
plug-in
over
here,
and
we
also
do
some
tests
at
the
package
level.
The
tc
packages,
which
is
you
know,
for
example,
grafana
prometheus
gatekeeper.
So
we
have
test
scripts
to
run
tests
for
these
packages.
On
top
of
any
cumulus
cluster,
including
tc
cluster,
so
we
currently
just
run
the
gatekeeper
and
we
plan
to
run
more
package
tests
in
these
pipelines.
As
of
now,
we
run
gatekeeper
tests
mostly
and
apart
from
tests.
B
B
B
A
D
E
F
A
G
This
time,
I'll
actually
remember
to
unmute.
Before
I
start
talking,
I
apologize
if
you
can
hear
my
very
indignant
dog
in
the
background,
so,
as
you
know,
we
run
into
some
roadblocks
in
being
able
to
release
zero
ten
zero.
As
of
now
we
have
in
the
in
the
logistical
sense,
cleared
that
in
the
build
sense
we
haven't
quite
cleared
that
yet,
but
we
have
right
people
working
on
the
right
things
right
now.
G
G
Cool
we're
it.
It
feels
like
we
are
likely
to
be
able
to
release
sometime
in
in
early
february,
but
we'll
see
how
the
things
we're
waiting
on
right
now
go
because,
as
I
said,
we
finally
have
the
right
people
trying
to
build
the
right
things,
but
they
haven't
had
a
clean
build
yet
so
you
know
we
can't
say
until
till
we
at
least
see
that
we
can't
start
really
even
guesstimating
effectively.
G
As
you
note,
the
roadmap
we
have
published
on
the
github
repo
was
a
six
month
forward.
Look
starting
at
october.
Well,
you
know,
half
of
a
half
of
that
is
gone
by
now
and
b.
Some
of
the
items
that
were
on
there
were
a
little
more
wish
list
and
we
didn't
have
as
much
exposure
as
to
who
would
be
working
on
what,
when
so,
let's
plan
at
the
next
community
meeting
we'll
be
able
to
to
talk
through
it.
G
But
the
plan
now
is
that
we
will
have
a
pull
request
up
and
ready
for
review
this
friday,
and
we
then
welcome
you
comments
on
it
in
terms
of
prioritization
things.
We
left
off
if
we're
doing
things
that
you
know,
you
think
are
just
dumb,
let
us
know,
and
from
there
forward
we'll
make
the
prioritization
visible.
G
Another
change,
that's
coming
in
the
way
we
publish
the
roadmap
is
we're
not
only
going
to
talk
about
time
frames
which,
as
you
know,
there's
always
a
disclaimer
there's,
always
a
disclaimer,
that's
about
as
long
as
the
road
map
for
companies
and
teams
that
publish
road
maps
talking
about
not
a
commitment
and
things
will
change
in
sequence,
etc.
But
one
of
the
things
you
can
do
you
can
see
as
a
way
to
to
really
get
a
good
feeling.
As
to
you
know,
what's
what's
wishlist
what's
been
specified?
G
What
if
we
agreed
we're
going
to
do
what's
resourced
and
planned?
Is
it
will
not
only
be
putting
a
time
frame
but
also
the
current
status
and
where
it
is
in
the
pipeline
from
awaiting
a
proposal
all
the
way
through
to
being
in
process
and
in
development,
so
it'll
be
more
informative,
easier
to
track?
What's
going
on
with
things,
and
as
always,
we
welcome
your
input
once
that
pr
is
up.
A
H
Oh
actually,
sorry,
we
have
a
couple
things
unmanaged
clusters.
This
is
a
new
functionality
to
enable
the
development
and
experimentation
of
tonzu,
giving
us
a
minimal
deployment
model
that
can
go
up
in
often
times
two
minutes
or
less
has
been
merged
into
main.
I've
sent
a
message
out
to
the
mailing
list
and
also
in
slack.
If
anyone
wants
to
get
ahead
of
the
train
and
try
it
out,
you
can
build
it
from
source
today
and
when
we
do
get
v010
out,
this
will
be
a
plug-in
that
we
offer
it
will
be
alpha.
H
As
far
as
v010
goes
echo,
what
roger
said
we'll
have
some
updates
as
soon
as
we
get
some
of
these
final
pieces
polished
up
and
then
the
final
engineering
update
that
we
have
for
now
is
that
some
proposals
have
changed
their
state.
One
is
the
new
unmanaged
cluster
model
or
what
will
hopefully
eventually
replace
the
existing
standalone
cluster
model
that
has
been
completed
with
merging
that
unmanaged
cluster
pr.
H
Other
two
proposals
that
have
been
accepted
now
are
the
inclusion
of
kpac
and
the
cert
injection
web
hook,
so
these
will
come
in
as
first
class
packages
in
the
tce
package
repository
and
they're
accepted
proposals,
but
some
work
still
needs
to
wrap
up
to
make
them
available.
Hopefully,
we'll
have
an
update
on
that
soon,
but
if
any
of
you
are
interested
in
using
those
two
packages
or
tools
that
should
be
available
soon
and
then
we
also
made
a
call
out
to
the
mailing
list
around
a
rfc,
that's
pending.
H
This
might
be
one
that
some
of
you
are
interested
in
checking
out
if
you've
felt
pain
with
bootstrapping
before
so.
Our
goal
is
to
improve
the
visibility
into
creating
management
and
workload
clusters.
We
found
time
and
time
again
with
new
users
of
tce
that
you
go
to
create
a
cluster
and
then
something
happens
behind
the
scenes
like
you
ran
out
of
resources
in
aws,
but
30
minutes
later.
All
you
know
is
that
your
cluster
creation
failed
and
now
you're
digging
into
the
log
messages
of
many
many
controllers
to
figure
out
where
it
failed.
H
We
want
to
bring
that
visibility
right
up
to
the
end
user's
face
so
that
you
actually
understand
what's
happening
and
potentially
failing
during
bootstrapping.
So
if
you're
interested
in
what
we're
planning
on
doing
there
check
out
that
proposal,
we're
going
to
keep
an
rfc
open
on
it
for
a
couple
weeks
and
refine
the
proposal
and
then
eventually
implement
it
and
those
are
our
engineering
updates.
A
Awesome,
thank
you
josh.
If
you
are
not
signed
up
on
the
mailing
list,
we
have
a
google
group,
which
is
how
we
manage
it,
and
we've
been
getting
a
lot
more,
sending
out
a
lot
more
messages
there
for
requests
for
comments,
like
josh,
has
been
saying,
and
then
one
email
per
week
to
serve
as
an
update
and
let
you
know
what's
coming
with
respect
to
the
meeting
later
that
week.
E
Lee
nice
thanks
friends,
just
also
wanted
to
say,
really
excited
about
the
rfc
for
the
improving
the
visibility
on
the
management,
cluster
creation
for
sure
the
recording
from
december
has
been
posted.
I
just
wanted
to
put
it
here,
because
you
know
we
had
the
holidays
and
they
didn't
get
to
think
about
it.
It's
where
john
you
know
does
that
doom
demo
on
tce.
So
if
we
want
to
pop
that
anywhere,
that's
the
link
tonsil
tuesday
with
scott
yesterday
was
awesome.
E
The
ytt
so
can't
wait
for
the
recording
of
this
one
there's
a
lot
of
gold
in
there
kind
of
not
directly
tce
related,
but
scott
is
going
to
be
joining
us
two
other
times,
and
one
of
them
is
about
tap
tons
of
application
platform,
and
I
think
the
plan
is
to
use
tce
as
the
host
cluster.
For
that.
So
we'll
definitely
be
highlighting
that
for
sure
it's
just
a
good
platform
to
use
tap
on
top
of
and
then
again
not
directly
tce
related
but
diving
into
the
guts
of
carvel
packaging.
E
You
know:
we've
all
seen
scott's
really
cool
tricks
on
previous
community
meetings
here
before
packaging
helm
and
doing
all
sorts
of
innovative
things
with
cap
controllers.
So
he's
going
to
be
doing
another.
You
know
hour
to
90
minute
demo
with
all
of
his
packaging
tricks
and
I'm
sure
that
that
will
feature
tc
heavily
so
yeah
february,
8th
and
february
22nd,
coming
up
also,
probably
we'll
just
update
the
slack
channels
when
we
get
those
recordings
posted
so
and
then
I
think
robert
as
well.
D
Yeah
the
the
first
coming
up
is,
is
we
have
an
iq?
We
have.
We
have
a
pretty
active
youtube
channel,
so
we
record
just
casual
conversations
between
consultants,
as
we've
talked
about
before
carlos
built,
an
automation
framework
to
basically
provision
tce
on
top
of
vmc
on
aws.
That's
they're.
All
lots
of
people
excited
about
that
within
itq,
because
it
gives
us
easy
to
spin
up
poc
environment
for
customers
and
just
messing
around,
and
you
know
it
can
be
leveraged.
We
could
deploy
it
on
google
as
well.
A
F
F
I've
been
in
vmware
for
about
10
in
10
months
or
so
now,
work
mostly
in
kubernetes
security
and
cncf
tax
security
done
some
work
there
and
continue
to
improve
kubernetes
security
for
all
in
general
and
tca
being
something
that's
a
big
thing.
That's
built
on
top
of
kubernetes
and
going
to
make
kubernetes
simple
felt
like
a
good
thing
for
me
to
explore.
F
So
I
started
a
slack
thread
and
talked
to
a
few
folks
in
the
call,
and
they
were
very
receptive
and
helpful
on
that.
But
just
wanted
to
bring
that
topic,
and
just
basically
understand
would
that
be
something
of
interest,
and
I
can
dive
deep
on
how
we
did
it
for
kubernetes
container
images
and
then
kind
of
go
from
there.
H
H
F
Okay,
yeah,
that
sounds
great
and
pro
and
test
rate
is
something
kubernetes
also
used
for
doing
something
similar.
So
with
the
tooling
common.
It
will
make
it
probably
easier
so
I'll.
Take
that
as
an
action
item
to
open
an
issue
and
probably
use
the
template
for
the
proposal
for
that
and
then
go
from
there.
G
A
A
So
what
we
have
coming
up
tomorrow,
the
towns
are
to
go
in
dallas
and
then
next
week
we
have
our
office
hours.
So
if
you
get
a
chance
to
think
of
any
questions
that
you
want
answered,
any
discussions,
you
think
we
should
have
synchronously
as
a
group.
Please
prepare
those
and
I
will
be
setting
up
the
hackmd
page
for
the
next
meeting
and
then
you
can
list
your
items
there
and
we'll
take
them
off
as
we
get
through
them.