►
From YouTube: Kubernetes SIG Security 20220825
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Right,
hello,
good
morning,
everybody
thank
you
for
coming
to
another
kubernetes
sig
security.
It
is
a
delight
to
see
everybody
here
today,
as
we
do
we'll
go
around
with
some
introductions.
I'm
tabitha
I'm
one
of
the
co-chairs.
B
Hi
I'm
ian
pronouns.
Are
they
them?
I
am
the
other
co-chair
of
six
security
and
I'm
here
because
I
wanna
be-
and
I'm
happy
to
be
here
with
all
of
you.
C
Hey
folks,
I'm
ola
dewberry,
I'm
the
self-assessments
subproject
lead
super
happy
to
be
here
very
I'm
proud
to
be
part
of
this
I'll,
be
on
camera.
In
a
minute,
I'm
just
finishing
up
lunch
thanks.
D
Hey
folks,
I'm
ray
I'm
the
audit,
the
project
lead,
and
you
might
see
me
around
another
place
in
the
community.
I'm
also
part
of
sigdocs
and
sick
release
as
well.
B
Yeah,
so
I
guess
I'm
gonna
reintroduce
myself.
I
was
hanging
out
here
a
bit
some
time
ago,
but
it
was
not
part
of
my
job
so
now
it
is
so
now.
I'm
a
product
manager
for
security
on
tanzu
kubernetes
grid
on
vmware.
So
now
I
have
a
work
excuse
to
to
come
to
these
things.
All
the
time
yay.
B
And
yeah
just
popping
in
and
see
what
it's
all
about
here.
D
B
D
E
I'm
xander
first
time
on
this
call
the
open
source
product
manager
at
microsoft
and
yeah
excited
to
be
here.
F
Hi
this
is
pushkar,
I
am
the
security
tooling
lead.
I'm
also
tech
lead
for
cncf
tax
security
and
love
to
make
my
and
other
people's
dreams
to
make
kubernetes
more
secure.
G
This
is
avita
here
I
lead
security
documentation
project.
I
am
here
to
meet
my
like-minded
friends
and
learn
and
share.
A
All
right,
so
next
thing
we
next
thing
we
often
get
through
here
is
to
hear
about
the
work
that
folks
have
been
doing
inside
subprojects
and
so
ray.
D
D
Ish
findings
have
already
been
sent
out
to
the
src,
but
we
also
need
to
talk
about
what's
next
in,
like
in
2023.,
we
previously
talked
about
doing
smaller
scale
and
more
frequent
audits,
maybe
scoped
to
certain
parts
of
the
project
or
certain,
I
guess
other
out
of
tree
parts
of
the
project
as
well.
D
So
that's
something
that
we
need
to
start
to
talk
about,
so
I'm
just
trying
just
starting
to
open
that
discussion
up
here,
I'll,
put
some
thoughts
down
on
paper
and
us
and
send
it
out
the
next
quarter
or
so,
but
we
still
we
even
though
we
are
quite
a
way
that
we're
it's
august.
I
know
we're
still
quite
away
from
2023,
but
we
still
need
to
start
talking
about
that.
A
It'll
be
good
to
have
it'll,
be
good
to
have
some
some
consensus
plans
together
for
what
to
do
in
2023
before
2023
is
upon
us.
I
think
that
you're
really,
I
think,
you're
really
smart
to
be
starting.
These
discussions
now.
G
So
the
updates
are
informational.
If
you
haven't
read
the
historical
context
of
the
psp,
it's
live
thanks,
mahi
and
all
the
amazing
reviewers
who
provided
inputs
and
reviewing
the
blog.
G
I
really
like
the
little
graph
like
a
timeline,
one
that
is
in
the
blog.
So
it's
it's.
It's
it's
nice
to
know
like
yeah
work
with
something,
and
I
when
I
was
in
the
release
cycle,
I
was
a
part
of
the
duplication
cycle,
so
it's
so
nice
to
know
about
like
what
happened
before
or
like
what
was
the
real
reason
for
the
feature
and
what
it
got
replaced
with
so
that
and
then
there
are
a
couple
of
in
progress
items.
One
is
by
rory.
G
The
apa
server
bypass
risk
page
been
getting
reviews,
and
I
saw
him
come
at
something
like
two
minutes
before
this
meeting.
So
I
think
it's
going
on.
Thank
you
and
the
next
one
is
the
security
checklist
for
clusters.
It's
been
a
group
effort
by
so
many
contributors
and
my
has
been
again
doing
an
amazing
job
with
addressing
all
the
review
feedback,
and
I
saw
like
a
few
new
review
comments
on
on
that
pr.
So
I
think
it's
in
progress.
G
The
last
one
is
a
post
on.
I
saw
this
post
on
sigdocs,
so
I
just
wanted
six
security
docs.
So
I
just
wanted
to
like
give
a
shout
out
and
highlight
highlighted
here.
Thank
you.
Shannon
shan's
been
putting
up
a
new
concept
page
for
secure
service
account,
and
some
of
the
folks
have
been
already
reviewing
it.
Pushkar
tim
banister
so
nice
to
see
you
and
they
have
been
reviewing
it
and
chan
had
mentioned
that
they're
gonna
open
it
up
for
more
reviews.
G
H
So
I
just
want
to
say
that
I
was
I've
been
checking.
You
know
the
news
feeds
like
you,
know,
cloud
cloud
native
journalism
for
mentions
of
the
pod
security
policy
going
away.
You
can't
use
that
anymore.
Did
we
explain
it
very
well,
nothing.
H
So,
from
a
doc's
point
of
view,
absolute
success
from
a
marketing
point
of
view,
you
know
we
need
to
create
some
of
this
friction.
This
thing
to
you
know,
create
a
sense
of
aggression
to
get
in
the
news
to
get
those
twitter
storms
out
so
like
from
a
marketing
point
of
view,
it's
a
failure,
but
no,
no,
I'm
being.
A
G
A
You
know,
complaints
about
pain,
related
to
psp
removal,
and
I
mean
surely
somebody
is
having
some
pain
related
to
psp
removal
somewhere.
But
if
it's
not,
if
it's
not
loud,
then
that
is
at
least
a
good
sign
that
the
efforts
that
so
many
people
put
in
were
somewhat
successful
like
you
can
never
know
for
sure,
but
it
is
really
nice
to
hear.
I
think
it's
a
great
testament.
A
Then,
in
that
case,
tell
us
about
tooling,
and
let's
all
do
a
group
note
taking
while,
while
he's
telling
us
about
this,
because
trying
to
trying
to
talk
and
take
notes
at
the
same
time
is
really
hard.
F
Yes,
for
sure
two
updates:
we
had
a
couple
of
folks
from
shopify,
danny
and
john
vieff,
who
presented
a
tool
that
they
have
been
using
internally
called
cube
audit
and
it's
basically
a
tool
to
scan
for
pod
manifest
and
see
if
there
are
any
insecure
fields
or
missing
fields.
That
would
make
a
pod
more
secure.
F
A
Question
from
text
is
whether
the
recording
of
that
demo
is
up
or
not,
and
the
answer
to
that
is
that
it
is
not
those
recordings
go
up
manually
and
they
are
not
up
yet,
but
I
will
get
through
those
recordings
and
prioritize
these
couple
of
demos
that
have
been
that
have
been
really
well
received.
I
think
I
can
probably
take
care
of
at
least
the
demo
ones
this
afternoon,
so
I'll
post
back
into
the
notes
and
on
slack
when
that
has
been
when
those
have
been
updated.
F
Yeah
we
had
one
from
microsoft
on
eraser
and
this
one.
I
think
those
two
would
be
great
next
update
is
a
big
one
and
I'm
so
glad
that
tim
is
on
the
call,
because
he
has
been
very
instrumental
in
getting
this
done.
F
So
we
were
working
on
a
cap
3203
which
is
creating
an
auto
refreshing
cve
feed
for
anyone
who
wants
to
know
when
the
cv
is
for
kubernetes
show
up
so
with
the
release
of
125,
it's
now
actually
live.
If
you
click
on
the
link
in
the
notes,
you
can
see
it,
you
can
also
look
at
the
json
feed,
that's
linked
in
it.
The
couple
of
blog
posts
are
coming
in
soon,
which
will
explain
what
they
are
about,
how
you
can
contribute
how
you
can
improve
the
feed
and
how
also
it
was
implemented.
F
A
Yeah,
I
was
clicking
through
it
earlier
today
and
like
it's
beautiful
and
the
data
are
there
and
the
implementation
is
relatively
simple,
like
bravo
to
bravo
to
everyone
involved
in
that,
and
I'm
just
so
proud
to
be
to
be
associated
with
with
progress
like
that
and
and
to
be
able
to
do
a
little
to
help
make
space
for
it
to
happen.
Y'all
are
so
awesome.
Thank
you
anything
else
about.
What's
been
going
on
with
tooling
yeah.
F
If
no
more
comments
on
this
one
thing
I
would
implore
and
encourage
everyone
is
use
the
feed
if
you
are
an
end
user
or
even
if
you
are
not
an
end
user.
This
is
exactly
the
right
time
to
give
your
feedback,
because
we
are
in
alpha
stage
of
the
feature,
so
anything
you
can
share.
We
have
already
gotten
a
couple
of
good
feedback
on
slack,
but
if
you
have
more
please
share
and
then
we'll
make
sure
we
can
do
whatever
is
reasonable
to
incorporate
it.
A
Well
then,
allah
how's,
how's
things
going
with
with
self-assessments.
I
know
that
I
know
that
bird
is
developing
its
feathers
pretty
rapidly.
C
So
yeah
I
was,
I
took
some
time
the
other
day
to
write
up
the
awesome
information
that
bushker
gave
me
the
other
day
in
terms
of
like
what
were
just
the
steps
and
like
what
was
kind
of
the
project
plan
for
the
happy
self-assessment,
because
I
was
realizing,
as
I
start
to
think
about
going
to
other
cigs
and
saying
hey.
This
is
a
tool
that's
available
for
you.
You
know
to
make
your
corner
of
kubernetes
more
secure
that
I
was
like
wait.
I
don't!
C
I
don't
actually
know
what
the
process
is.
So
I
took
some
time
to
write
that
up
and
I
have,
I
think
it's
actually
a
merge
request,
I'm
also
like
kind
of
a
beginner
with
git,
so
I'm
still
learning
the
ropes
there
to
just
create
a
folder
in
the
self
assessments
folders
for
just
basic
documentation
for
like
how
does
this
work?
C
What's
the
workflow,
so
that
and
really
just
getting
to
the
point
where
I
kind
of
like
I
can
almost
like
automate
or
like
document
myself
out
of
kind
of
being
the
only
person
who
can
do
this
because
that's
silly
so
it's
like!
Oh,
like
you
know,
here's
an
example
of
how
it
works.
C
Here's
an
example
of
this
to
just
like
federate
that
knowledge
and
then
what
that
will
what
that
collateral
will
allow
me
to
do
is
then
go
to
other
sig
meetings
like
this
and
say:
hey
here's,
this
nice
folder
of
collateral,
for
how
this
works
here
are
the
resources.
Here's
you
know
it's
like
here
are
the
monkey
bars
as
it
were
that
you
need
to
like
climb
on
to
get
this
done,
and
so
that's
kind
of
my
that's
been
my
focus
recently.
C
I
feel
like
I
was
kind
of
getting
out
over
my
skis
in
terms
of
like
going
and
like
promoting
stuff,
and
I
I
think
it's
it's
a
better
strategy
for
me
to
take
some
time,
get
organized.
Make
sure
that
I
have
a
full
understanding
of
just
the
lay
of
the
land
before
I.
I
can
really
be
a
resource
to
the
rest
of
the
community,
so
yeah,
that's
it
for
me,
but
yeah.
C
I
think
someone
needs
to
merge
my
merge
request,
because
then
I'll
have
my
little
folder
that
I
can
put
all
my
little
write-ups
in.
So
if
I
could
have
a
hand
with
that,
that
would
be
very
fabulous.
G
A
You
for
thank
you
for
calling
that
out
and
we
will
have
a
look
at
that
and
do
what
we
can
to
keep
you
rolling
there.
Thank
you
any
other.
Any
other
thoughts,
questions
things
to
bring
up
about.
A
Self-Assessments
all
right,
then
we
have
some
things
that
folks
have
brought
with
to
to
bring
to
the
group
today
and
xander.
I
think
you're
first
on
the
list.
E
Yeah,
thank
you.
So
I
just
wanted
to
chat
a
little
bit
about
eraser.
We
did
a
presentation
for
the
tooling
subproject,
I'm
not
sure
if
the
video
for
that
is
available
yet,
but
that's
not.
E
Sounds
good
I'll
post
a
link
right
in
the
chat
there
to
the
project,
so
we
are
interested
in
in
donating
this
as
a
kubernetes
sigs
project,
ideally
with
sig
security,
as
as
the
sponsoring
sig,
I
think,
that's
probably,
which
would
make
the
most
sense-
and
we
wanted
to
just
chat
with
their
group
about
like.
Is
that
something
that
the
sig
would
be
open
to?
You
know
currently
it's
under
the
azure
org,
but
we
we
definitely
view
it
as
like,
like
we
don't
want
it
to
be
an
as
your
own
project.
E
We
want
it
to
be
a
community
owned
project
and
I
think
kubernetes
sigs
is
probably
the
best
place
for
it.
So
I
guess
I
wanted
to
just
find
out
about
like
what
the
process
for
that
is
and
and
what
the
the
general
sentiment
there
is.
A
So
I
can
speak
a
little
bit
to
process,
at
least
which
is
which
is
to
say
that
if
it
is
coming
in
to
be
picked
up,
for
you
know,
maintenance
and
ongoing
development
by
a
kubernetes
sig.
You
know
whether
that
would
be
whether
that
would
be
this
one
or
whether
that
would
be
like.
Perhaps
I
don't
know
cli
or
you
know,
or
some
some
other
sig
that
that
found
it
you
know
within
their
within
their
scope,
then
you
know,
I
believe
that
there
are
some
licensing.
A
You
know
check
boxes
to
make
sure
are
appropriately
checked
and
things
like
that.
But
but
beyond
that,
it's
a
general
sort
of
community
building
question
of
is
there?
A
Is
me
assuming
that
that
an
open
source
project
that
is
coming
out
of
your
organization
is
already
you
know
already
prepared
by
having
the
right
licenses
and
things
like
that
on
it
or
that,
if
that
isn't
the
case,
that
it
would
be
relatively
easy
to
fix
like
assuming
that
the
logistics
don't
bite
us,
then
the
hard
part
is
really
finding
a
loving
home.
C
A
A
What
would
it
look
like
sharing
information
about
it,
and
so
from
from
that
standpoint,
I
think
that
you
are
that
you
are
doing
all
of
the
things
right
as
far
as
making
it
easy
for
folks
to
know
what
they
are,
possibly
considering
adopting
that's
a
place
where
getting
more
information
there
out
about
it
is
important,
and
on
a
on
a
personal
note,
I
will.
A
E
E
E
Awesome
yeah,
I
think
you
know
from
a
maintenance
perspective.
We
certainly
intend
to
like
continue
to
maintain
it.
We
have.
We
have
two
engineers
that
are
are
full-time
on
it
and-
and
we
would
certainly
continue
in
that
regard,
but
yeah,
I
guess
in
the
meantime,
if
there's
any
any
questions
that
anyone
has
about
it
or
you
know,
if
there's
anything
in
the
documentation,
that's
not
clear.
E
I'm
happy
to
jump
in
there
and
I
think
when
we
did,
the
presentation
pushkar
mentioned
that
it
likely
would
either
be
like
security
or
sig
node.
That
would
be
ultimately
the
right
home
for
it,
and
you
know
the
the
maintainer
group
kind
of
talked
about
it
and
felt
that
sig
security
probably
made
more
sense
for
what
the
goals
were
for
the
project,
but
yeah
open
to
to
anyone's
thoughts.
E
A
Yeah
tim,
I
I
think
that
I
think
that
you
are
having
a
thought
and
I
want
to
make
sure
you
have
space
to
have
space
to
share
it
with
us.
H
Sure
so
that
there's
a
thing
that
somehow
I
think
amazon
web
services
do
do
a
thing
which
is
that
when
they
are
launching
a
new
product
really
early
on,
they
start
writing
the
release
announcement
for
the
thing
and
they
say:
okay,
you
know
this.
This
new
80
west
acme
is
brilliant.
Acme
is
a
thing
now
80
west
fubar
is
a
thing,
and
this
is
why
and
it's
great
and
then
they
kind
of
work
backwards
from
the
release
out
announcement
and
and
to
the
code.
H
How
about
you
start
looking
at
the
adoption
announcement
as
a
little
blog
article,
if,
if
someone's
got
the
capacity
and
that
could
be
from
like
the
you
know,
the
signature
security
adopting
side
or
it
could
be
from
the
proud
former
parents
at
microsoft
side
or
it
could
be
a
joint
thing,
a
blog
article
to
say:
hey,
there's
this
official
kubernetes
thing
would
be
great,
it
doesn't
have
to
be
long,
it
could
be
six
paragraphs,
it
could
be
two.
A
But
like
as
a
as
a
as
a
daydreaming
exercise
and
and
also
as
sort
of
a
thing
to
help
folks
who
might
be
considering,
you
know,
contributing
to
something
or
picking
up
maintainership
or
something
to
like
imagine
themselves
in
the
future.
H
If
you,
if
you
put
up,
I
mean,
depends
how
far
you
get
if
you
get
up
to
hack
md,
you
can
share
that.
Camden
say
this
is
what
we're
thinking
of
doing.
If
you
get
up
to
a
pull
request,
you
automatically
get
a
net
the
fly
preview
and
it
won't
be
crawled
because
we've
heard
of
robots.txt,
but
you
can
send
people
like
this,
is
what
the
blog
article
looked
like
here
is
an
actual
preview
of
the
article.
Does
this?
Does
this
sound
like
you?
This
is
a
dream.
This
is
a
dream.
Is.
E
Awesome
yeah,
that's
a
great
idea!
Thank
you
for
that.
That's
yeah
I'll
definitely
go
forward
with
that.
A
Question
that
question
that
I
have
about
it,
and-
and
forgive
me
for
not
having
seen
the
demo
yet
is
what
does
usership
look
like
so
far
like
is,
is
this
is?
Is
this
a
popular
thing
that
has
has
a
lot
of
folks
who
are
who
are
currently
enjoying
and
appreciating
it
is
this
the
thing
that
that
that
is,
that
is
solving
a
particular
need
that
that
you
have,
and
it
seems
right
to
share
because
of
the
assumption
that
other
folks
have
similar
pain
like.
E
Yeah,
so
we're
at
about
150
stars
on
github.
Most
of
the
users
right
now
are
internal
to
microsoft,
because
the
the
project
came
out
of
microsoft
does
on
all
of
the
kubernetes
clusters
that
internal
teams
create.
They
do
image
scanning
for
non-running
images,
and
then
those
teams
will
get
alerts
about.
E
You
know
cves
for
cached
images
they
have
on
their
nodes,
and
you
know
each
of
those
teams
was
kind
of
developing
a
bespoke
way
to
like
clean
up
those
images
and
solve
that
problem,
which
is
where
this
ultimately
came
from,
and
it
actually,
in
the
relatively
near
future,
like
early
next
year,
will
be
on
by
default
for
every
new
aks
cluster
that's
created,
and
so
they,
it
kind
of
came
out
of
that
and
yeah
we're
at
that
stage.
E
Now,
where
we're
trying
to
go
from
like
a
lot
of
internal
microsoft
usage
to
growing
some
of
that
community
usage,
so
that
we
can
get
those
like
other
perspectives
of
like
what
features
folks
might
find
useful.
A
Thank
you
thank
you
for
thank
you
for
sharing
any
any
further
thoughts,
questions,
ideas
about
about
eraser.
F
One
thing
santa
I
shared
last
time
with
the
group
was
this
tool
can
be
used.
Even
if
you
are
not
a
aks
customer
or
don't
care
about
azure.
Can
you
just
confirm
that.
A
Like
it's
a
it's
a
kubernetes
tool
which
you
all
happen
to
develop
because
you
had
needs
yep,
that's
that
I
that
I
think
is
is
one
of
the
best
places
to
see
open
source
come
from
is,
is
someone
needed
something
they
needed
it
badly
enough
to
develop
it
for
themselves
and
then,
given
the
possibility
that
others
have
similar
needs
share
it
in
the
hope
of
in
the
hope
of
it
being
useful
so
like
yeah?
This
is.
This
is
good.
A
All
right:
let's
talk
about
owner's
file.
F
Yeah,
so
savita
is
out
for
lunch,
so
I'll
try
to
cover
this-
and
tim
is
also
here
so
tim,
please
chime
in
as
well,
because
this
was
originally
your
idea.
F
We
have
a
directory
in
k
website
repo,
which
is
called
issues
security,
and
it
has
about
two
pages
which
are
about
cves
and
security
disclosure
information,
so
tim
was
sharing
that
we
could
have
a
custom
owners
file
there,
where
maybe
perhaps
six
security
leads
alias
could
be
the
reviewer,
not
sure
who
the
approver
would
be
if
we
should
also
add
see
src
members
there,
because
that
they
might
have
some
say
as
well,
so
just
wanted
to
open
this
up
as
a
discussion
point
for
everyone
and
get
some
feedback
tim,
please
correct
me
add
anything
I
may
have
missed.
H
So,
there's
a
there's
a
tempering
risk.
Essentially
it's
kind
of
someone
who
is
authorized
to
work
on
the
website
might
change
the
cv
feed
and
when
I
see
a
thing
like
that,
I
like
to
narrow,
I
like
I,
I
do
lots
of
role
based
access
controls
and
things
I
like
to
narrow
who's
got
the
access
and
we
have
all
the
mechanism
for
that.
H
So
there's
a
couple
of
pages
on
the
kubernetes
website
that
I
can't
touch.
So
I
can't
put
a
banner
on
the
front
page
of
the
website
that
says
whatever
and
I
can
kubecon's
coming
up
or
whatever
without
like
the
steering
committee.
Approval
and
para
has
a
mechanism
to
say
don't
inherit
ownership,
and
this
feels
like
a
place
to
not
inherit
ownership
and
say
security
folks,
not
english,
docs
reviewers.
H
We
basically
need
a
pr
bit
of
agreement
and
sort
of
a
commitment
to
to
not
disappear
and
fail
to
maintain
things.
That's
what
we
need.
A
B
A
Think
it,
I
think
it
is
a
reasonable
idea,
and
what
what
do
we
want
to?
What
do
we
want
to
do
with
this
with
this?
Next,
I
guess
kind
of
the
the
question
there
is:
what
do
we
see
as
the
identity
of
this
directory,
because,
like
there's
the
there's
the
security.md
file
in
here,
which
feels
like
an
src
kind
of
you
know,
which
feels
like
an
src
kind
of
responsibility
and
then
the
you
know
the
cve
feed
rendered
html,
which
is
yeah.
A
That's
a
bit
of
a
shared
responsibility,
so
I
guess
talking
through
that,
like
in
real
time,
seems
like
the
sensible
next
thing
would
be
to
bring
this
idea
to
the
rest
of
the
src
folks,
see
if
there's
any
see,
if
there's
any
strong
feelings
over
there
and
then
put
in
you
know,
put
in
the
pr
do
you
do
you
have
a
feeling
tim
about
what
the
rest
of
the
website
maintainers
feelings
on
this
will
be
like.
Do
you
expect?
Do
you
expect
this
to
be
controversial
among
the
website,
maintainers
or.
D
I'd
all
right
with
my
sig
docs
co-chair
hat
ron.
I
don't
think
this
will
be
a
controversy.
I
think
this
is
a
fantastic
idea
and
to
have
that
little
protection
by
that
protection
on
this
subdirectory.
A
Well
then,
yeah
bushker,
you,
you
and
me,
would
take
it
to
the
rest
of
the
src
and
then
and
then
one
of
us
would
put
in
a
pr.
A
Next
thing
on
here
is
alan:
wants
to
talk
about
our
group
project.
C
Yeah,
I
just
wanted
to
give
folks
a
quick
update,
so
I
was
able
thank
you
ray
for
sharing
the
kubecon
north
america
powerpoint
deck
template.
I
updated
the
kind
of
the
outline
that
I
put
together
into
that
deck
and
I
just
wanted
to
share
here
and
let
folks
know
that
that
exists,
the
the
bit
that
I
have,
which
is
talking
through
self
assessments.
At
the
end,
I
want
to
have
that
kind
of
like
buttoned
up
just
because
I'm
like
a
preparation,
paranoid
person
and
be.
C
Ready,
like
I
like
to
say
by
end
of
september,
I
know
that
coupon
isn't
actually
until
end
of
october,
but
yeah
just
just
wanted
to
share
here
that
the
deck
is
there.
If
anyone
has
any
feedback
on
like
the
outline,
I
I
know
ray
pushker
you
tabby
and
ian,
and
some
other
folks
have
already
waited
on
it.
But
yeah
just
wanted
to
share
an
an
update,
and
I'm
super
excited
that
yeah
we
get
to
talk
about
this
and
share
our
goodness
with
the
community.
C
It
also-
maybe
it's
worth
noting
that
I
decided
to
do
a
virtual
speaker
pass
just
being
cautious
about
my
my
kobit
risk
budget
and
trying
to
reduce
travel
where
I
can
so.
I
will
be
a
virtual
for
that,
but
it
looks
like
they
have
chops
to
accommodate
that.
So
I'm
excited.
A
C
B
I
mean
thank
you
for
jumping
in,
like
you
know,
sync
security
is
what
everybody
makes
it
right
and
if
you
come
in
with
an
idea
and
enthusiasm
and
want
to
make
a
thing
happen
like
this
is
a
great
place
to
make
a
thing
happen
and
like
again
like.
Thank
you
for
being
a
good
example
of
what
that
can
look
like.
A
A
All
right,
that's
our
traditional
signal
that
we
have
done
the
things
that
we
came
together
today
to
do.
It
has
been
wonderful.
Thank
you
all
so
much
for
coming
and
periodic
reminder
that
slack
is
open,
24
7.,
so
anything
that
anything
that
that
you're
thinking
about
feel
free
to
bring
it
to
slack
and
otherwise
we'll
see
everybody
again
at
the
next
one.