►
From YouTube: Kubernetes SIG Security 20230223
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
Okay,
it
is
for
after
so,
let's
call
it
be
gone
good
morning,
good
afternoon.
Everyone
thank
you
for
coming
to
another
kubernetes
Sig
security,
I'm
Tabitha,
Sable
I'm,
one
of
the
co-chairs
she
and
they
and
I'm
happy
to
be
here
to
help
us
make
this
space
to
be
able
to
do
things
together
to
improve
kubernetes
security.
B
Hi
I'm
Ian
Coldwater
I
am
the
other
co-chair
of
kubernetes
security
I'm
here
to
make
friends
at
the
planet
hack
plan
it
with
my
friends.
A
Yeah
yeah,
as
we
as
we
do
anybody
else
who
wants
to
introduce
himself
for
the
benefit
of
Friends,
new
and
old.
C
F
Yeah
work
in
healthcare
and
I
am
returning
to
the
group
just
catching
up
and
seeing
where
things
are
going.
G
Hello,
hello,
my
name
is
Saida
I
am
a
devops
engineer
and
it's
my
first
time
attending
these
meetings
and
also
in
six
security.
I
met
Kaden
in
this
the
security
conference
in
Seattle.
So
she
introduced
me
to
the
to
the
community,
so
yeah
I'm
here
to
learn
and
meet
new
people
and
also
contribute
to
the
open
source
sounds
exciting.
Yay
welcome.
A
E
Hi
I'm
Bill
Branson
I
work
over
Google
in
GK
security.
I
was
also
at
CNS
C
in
Seattle
and
got
me
kale
in
there.
So
I
get
to
see
y'all
online
again,
it's
great
to
see
if
you
be
in
person
and
yeah
I
guess
today,
I'm
talking
about
here
to
talk
about
some
cbss
thoughts,
I'd
posted
to
the
team
a
few
weeks
ago.
H
J
I'm
chairman
today,
I'm
all
right,
NetApp
doing
kubernetes
security
and
it's
looking
and
listening
and
seeing
where
I
can
help.
A
Right
so
as
we
do,
we
will
hear
some
of
what
has
been
going
on
in
various
sub-projects
today.
Rey
is
not
able
to
make
it
does
anyone
else
want
to
talk
a
little
bit
about
what's
going
on
with
third-party
audit
subproject,
otherwise,
I'm
happy
to
do
so.
Myself.
K
A
Right
no
further,
if
there's,
if
there's
no
further
comments
or
questions
that
folks
have
about
that,
then
we
will
move
to
docs
Savita
unable
to
make
it.
Would
anyone
like
to
share
status
of
Docs
or
again
otherwise,
I'll
be
happy
to
do
so?.
A
All
right,
so
we
have
in
the
meeting
notes
Here
a
list
of
things
to
go
through
with
various
improvements
that
folks
have
identified,
would
like
to
to
check
out
and
update
with
respect
to
security
related
documentation.
So
there
is
a
shout
out
for
that
list.
If
you
are
interested
and
have
some
bandwidth
to
look
at
those
and
see
if
there's
any
that
lines
up
with
something
that
you
would
like
to
be
able
to
improve
check
it
out,
it's
there
in
the
notes,
thoughts,
questions
or
discussion
about
the
status
of
docs
things.
H
H
So
we
have
this
this
part
of
the
pr
that
is
in
security
for
the
Python
3
for
the
Syria
CV
Jason
fit
thing
which
is
approved
and
and
everything,
but
there
is
still
like
the
website
part
that
is
a
bit
of
a
blocker
right
now,
so
maybe
it
will
unblock
this
week
and
I
just
submitted
a
new
RSS
feed
PR
for
like
adapting
the
CV
feed
to
RSS
format.
So
if
you
want
to
take
a
look
at
it,
it
will
be
very
nice
and
pushka
also
mentioned
the
the
blog
post.
H
We
need
to
release
so
basically
I
think
we
will
release
a
very
short
blog
post
about
like
the
new
features.
It's
it's
mostly
Json
feed
compliance,
because
people
were
complaining
about
that
and
maybe
RSS
and
yeah.
That's.
A
H
Yeah
yeah,
so
now
that
with,
if
we
merge
the
next
API,
it
should
be
okay.
Now
so
it's
nice,
because
the
tool
will
be
able
to
take
this
thing
but
yeah.
That's
it
and
we
did
the
RSS
thing
on
top
of
this,
because
why
not-
and
maybe
it
could
be
useful
for
some
people
so
yeah,
that's
it!
So
we
need
to
write
the
blog
post
now.
So
if
you
want
to
help
I
think
it
will
be
a
very
short
blog
post,
so
it
will
be
easy
to
write.
L
That
next
tooling
meeting
we
are
going
to
have
a
session
about
God.
So
anyone
interested
to
look
to
the
next,
maybe.
M
L
First
level
of
details
about
God,
then
we're
almost
welcome.
A
All
right,
then,
we
will
move
here
to
security
self-assessments,
which
I
will
read
out
first
thing
here
is:
there
is
a
pull
request,
improving
some
of
the
initial
documentation
for
security
self-assessments
Caitlyn.
Do
you
want
to
share
any
more
details
about
that.
D
No
I
think
it's
pretty
self-explanatory.
I
pulled
in
the
original
PR.
So
there
are
comments
by
me
on
my
own
PR,
reviewing
the
work
that
I
pulled
in
with
questions
mostly
for
Ella,
but
if
anyone
else
wants
to
chime
in
push
cars
offered
some
really
helpful
feedback
and
there
are
some
like
potential
decisions
to
be
made
that
I
think
came
up
in
the
documentation.
So
if
you
have
opinions
about
self-assessment
decisions,
please
feel
free
to
weigh
in.
A
All
right,
the
rest
of
the
readout
here
is
on
Monday.
There
is
a
call
scheduled
for
the
beginning
of
the
sphere,
CSI
driver,
self-assessment,
DM.
All
of
for
details,
if
you
want
to
join
that,
there's
a
note
here
for
me,
which
is
to
get
that
scheduled
in
the
scheduling
tools,
so
I
will
take
care
of
that
for
us
after
the
call
and
the
slack
channel
for
that
self-assessment
has
now
been
created.
A
There
is
a
link
to
it
in
the
meeting
notes
and
if
I
remember
correctly,
it
has
a
name
that
should
be
fairly
recognizable.
If
you
see
it
when
you
search
for
it
on
kubernetes
slack,
if
you
do
Sig
security
Dash,
it
should
come
up
in
the
list
and
you
should
be
able
to
tell
it
by
its
name
any
further
thoughts.
Questions
discussion
about
self-assessments.
K
Yes,
we
have
several
threads
in
parallel,
we've
been
working
on
formalizing
the
policy
report
CR,
so
we
have
a
cap.
It's
not
it's
not
a
kept
ready
to
submit.
Yet
it's
more
of
a
cap
punch
list
linked
there
and
then
there's
more
technical
discussion
that
that
fired
off
in
the
gatekeeper
repo.
So
those
of
you
who
are
interested
in
the
mission
control
and
how
how
reporting
those
results
and
how
that
might
scale
up.
K
That's
a
good
discussion
forced
me
to
go
spelunking
in
some
of
the
code
and
an
hcd
there's
also
white
paper
effort
to
kind
of
version
up,
one
of
our
previous
discussions
on
how
to
manage
policy
in
kubernetes
and
I
think
the
group
wants
to
add
a
bit
more
context
around
operationalizing.
So
how
do
you
author?
How
do
you
distribute?
How
do
you
manage?
How
do
you
align
that
with
governance
and
compliance
and
risk
Frameworks?
So
it's
it's
a
big
effort.
It's
got.
K
I've
lost
track
of
how
many
folks
are
contributing,
but
at
least
six,
probably
forgetting
a
few
others
who
are
asynchronously
contributing.
So
it's
a
pretty
big
effort
hope
to
have
that
wrapped
up.
It
was
supposed
to
be
wrapped
up
by
this
week.
I
think
we're
probably
going
to
be
a
couple
weeks
delayed,
but
we'll
have
that
out
for
everyone
to
review,
and
then
we
are
also
working
with
nist
on
an
effort
they
call
oscow,
which
is
a
standardized
schema
for
expressing
security
controls
and
assessments
and
assessment
results
and
findings.
K
So
they've
asked
us
to
help
in
some
of
their
research
around
very
real
world
specific
types
of
system
controls
and
how
that
might
be
expressed
in
oscow,
so
we're
working
with
them
to
write
up
some
of
that
research
based
off
of
a
kubernetes
environment
that'll
probably
be
a
fairly
drawn
out
effort
over
several
months.
So
those
of
you
are
interested
feel
free
to
jump
on.
The
policy
work
group
calls
every
other
Wednesday
so
in
the
off
week,
so
next
Wednesday
8
A.M
Pacific,
that's
all
I.
A
Got
I
mean
it
sounds
like
quite
a
bit.
Could
I
ask
the
favor
to
drop
a
link
to
your
meeting
notes
doc
into
the
meeting
notes
here,
so
that
that
way
it
can
provide
a
nice
on-ramp
for
anybody.
K
J
A
Well,
the
next
thing
that
we
have
here
on
the
list
is
you
Bill
what
what
is
going
on
with
the
CVSs
discussion,
yeah.
E
So
yeah
big
thanks
to
Rory
and
Tim
Minister
for
dropping
some
comments
in
the
chat
there
just
wanted
to
raise
this
up.
The
group
again
say
it's
out
there.
Please
give
it
a
read
and
talk
kind
of
about
next
steps,
so
I
think
the
my
feeling
is
the
end
state
for
cbss
scoring
is
to
produce
a
page
on
the
official
kubernetes
website
to
talk
about
hey.
These
are
the
ways
the
parameters
that
we
score
for
CVSs.
E
When
you
find
yourself
doing
cbss
and
so
discussion
is
started,
but
I
think
you
know
next
is
to
maybe
get
a
more
focus
discussion
towards
putting
together
that
agreement
that
we
could
actually
publish
as
official
guidance
as
to
what
to
score
how
to
score
and
how
to
think
about
cdss
and
kubernetes
land,
so
soliciting
thoughts,
feedback
on
how
close
we
are
with
the
document
and
what
our
next
steps
yeah
any
any
insights
into
where
to
go
next
with
it
in
terms
of
the
Sig,
would
be
very
welcome.
E
A
A
N
N
E
Great
thanks
for
that
yeah
I
can
also
because
there's
a
couple
of
proposed
approaches,
they're
meant
to
see
discussion.
I
can
try
to
do
that.
That
analysis
for
the
sort
of
second
proposal
too.
If
you
think
that
would
be
helpful
to
yeah
to
kind
of
do
the
worked
examples
here
and
see
how
it
would
look
to.
E
Great,
it's
all
about
a
poke
at
that,
unless
those
are
the
comments
and
I'll
check
in
again
in
two
weeks,
see
if
other
folks
have
thoughts
on
next
steps,
as
more
people
have
a
chance
to
read
it
and
yeah.
Thank
you
for
your
feedback.
A
B
Okay,
I
got
a
swipe
message
actually
like
10
minutes
ago,
which
was
some
timing
in
a
good
way
and
I'll
just
read
it
to
y'all
and
then
pose
the
question,
which
is
from
a
person
named
Carl
Wright,
Hi
Ian
I'm
on
the
cncf's
analyst
relations
team.
We
help
key
researchers
in
the
tech
industry
with
their
research
on
cncf
projects.
Taylor
dolezal
told
me:
I
should
contact
you
to
set
up
a
call
between
a
member
of
six
security
and
key
security
analysts
at
Forester,
a
large
research
firm
for
context.
B
B
Do
you
know
if
anyone
on
that
team
would
have
the
bandwidth
for
a
30-minute
call
and
because
we
here
at
Sig
security
tend
to
like
to
do
things
collectively,
I
figured
instead
of
personally
volunteering
I
would
take
it
to
the
meeting
and
say:
does
anybody
here
have
the
bandwidth
for
said
quick
30-minute
call,
because
I
want
to
put
that
opportunity
out
to
anybody
who
would
be
excited
in
or
interested
in
doing
that?
Would
any
of
you
be
excited
or
interested
in
doing
that.
I
L
B
Asked
if
they
were
looking
for
one
person
or
a
group
of
people,
they
said
one
person
would
be
fine,
but
I.
Don't
know
that
they're
opposed
to
talking
to
more
than
one
person.
Necessarily
if
it's
a
single
call,
so
I
didn't
clarify
that
bit,
but
you
feeling
it
Rory.
I
I
I'm
happy
by
the
way,
if
anyone
says
like
a
strong
desire
to
do
this,
then
I've
done
a
couple
times
so
I'm
totally
happy.
If
someone
else
wants
to
I
just
don't
mind
doing
it.
If,
if
no
one
else
is
feeling
really
strong
about
it,.
A
I
would
like
to
suggest
that
one
of
the
best
things
about
the
way
that
we
handle
these
things
in
kubernetes
is
that
we
do
them
together
as
a
group,
and
so
if
someone
else
wants
to
participate
in
this
I
would
encourage
that.
We
do
bring
two
or
three
folks
rather
than
Rory
aggressively
stepping
back,
because
someone
else
put
their
hand
up.
N
N
So
a
few
key
points
that
we
want
to
cover
that
we,
you
know,
make
sure
we
cover
with
the
analysts
and
project
like
kubernetes
maturing
it's
a
software.
It
has
vulnerabilities,
but
this
is
how
we're
addressing
them
and
hardening
it
is,
is
a
good
way
to
go.
C
I
I
That
might
be
weird
because
I'm
not
sure,
because
that's
quite
a
general
area
Community
that
could
be
anything
from
they
want
to
talk
about
like
product
things.
They
want
to
talk
about
where
the
Project's
going
so
yeah
yeah.
M
B
And
I
can
pass
on
whatever
questions
and
whoever's
contact
info.
One
one
data
point
is
that
they
wanted
the
interviews
completed
by
end
of
month,
so
like
just
like
as
a
as
a
data
point
for
document
creation.
Talking
point
workshopping
that
kind
of
thing:
it's
it's
chop
chop.
O
I
Yeah
I'm
happy
to
try
and
help
yeah
and
see
what
they
yeah
I'll,
see.
I
think
we'll
have
to
see
what
they're,
what
they're
like
I'm
I
was
saying,
as
he
was
saying,
is
by
the
end
of
the
month.
There's
probably
not
a
huge
scope
for
back
and
forth
depending
on
how
responsive
they
are.
If
they're
responsive,
then
awesome
fall.
If
they're
not,
then
we
probably
don't
have
a
lot
of
time
for
that,
but
yeah
I'm,
happy
to
to
help
out
there
for
sure,
hopefully
Timeless
to
spawn
I
know
that's
an
odd
definition.
B
Hey
we
all
have.
We
all
have
the
things
that
we're
into
thank
you
for
being
on
top
of
it
Rory,
and
thank
you
all
for
your
interest
in
that
I
will
distill
these
questions
and
whatnot
pass
them
on
to
this
person
and
maybe
pass
this
person
onto
Rory
so
that
you
all
can
figure
this
out
and
by
maybe
I
mean
definitely.
B
It
seems
like
they're
doing
a
report
from
from
the
way
the
message
was
written
if
I
were
to
try
to
interpret
it
on
kubernetes
security
in
general
and
I
mean
you
know,
we've
seen
reports
on
kubernetes
security
I'm,
not
sure
why
the
timing
right
this
minute
and
it's
cool
I'm
glad
that
people
are
thinking
about
it
and
talking
about
it.
B
C
N
I
wonder
how
many
of
you
are
aware
of
this
project
called
confidential
containers?
Would
anybody
be
interested
in
like
a
readout
of
what's
happening
there
and
and
I
see
things
that
we
can
do
in
regular
kubernetes
that
you
know
touches
on
confidential
containers
for
one
because
you're
running
this
container
of
yours
in
a
trusted
execution
environment?
It's
like
okay,
everything
is
locked
down.
N
Nothing
can
look
into
it,
neither
the
root
process,
neither
the
infrastructure,
owner,
etc,
etc,
but
we
also
want
to
like
track
down
and
measure
what
the
input
arguments,
environment,
variables,
I
think
that's
something
useful
for
you
know
non-confidential
kubernetes
too,
and
then
another
thing
that
you
know
customers
would
like
to
see
is
yes,
I
have
my
workload.
It
is
exactly
what
I
want
running,
but
I
also
want
to
be
sure
that
the
cube
admin
can't
get
into
it.
N
The
cluster
admin
can't
get
into
it
so
being
able
to
lock
down
that
access
to
your
container
for
exit,
exec
and
then
debug
and
logs.
That
might
be
a
feature
that
regular
kubernetes
users
to
want.
So,
do
you
see
value
in
me
bringing
something
like
that,
like
maybe
10,
15
minutes
and
then
discussing
and
seeing
if
we
can
get
something
common.
A
I
mean
speaking
for
myself
as
an
individual.
Yes
put
my
Sig
chair
hat
on
you
know.
We
have
had
occasional
discussions
here
within
this
group
about
some
of
the
confidential
kubernetes
I'm
gonna
say
it
confidential,
kuberneting
concerns
and
they
have
always
generated
they've
always
generated
a
fair
amount
of
Interest,
so
so
yeah
as
an
individual
I
would
love
to
see
that,
as
a
representative
of
the
group,
I
would
be
pretty
sure.
The
group
would
be
interested
in
that.
N
N
So
we,
you
know
what
we
can
simplify
the
word.
It's
called
Coco
confidential
containers
is
what
they
call
it.
Sometimes
I
joke
Coco
and
coffee
so
make
it
simple
call
IT,
Coco,
okay,
I,
like
that
foreign.
D
Yeah
I
don't
know
if
there's
that
many
notes,
I
just
I'm
every
time,
I'm
out
in
the
world
talking
to
security,
folks,
I'm
telling
them
about
sex
security
and
then
I
hit
the
wall
of
not
being
able
to
easily
Point
them
toward
our
mailing
list
and
information,
because
our
readme
is
still
just
the
template
and
so
there's
a
PR
up
and
ready
to
go
and
I
personally
would
love
that
PR
to
be
merged.
So
if
there's
anything
specific
I
or
anyone
else
can
do
to
get
that
merged,
tell
me
and
I
will
do
it.
A
I
kind
of
love
that
idea
and
I
would
like
to
put
a
bug
in
someone's
ear
that
once
we
have
a
nicely
improved
readme,
it
would
be
a
great
thing
to
take
to
Sig,
contribex
and
say:
hey,
we
kind
of
want
this.
We
could
just
implement
it
ourselves
with
you
know
by
choosing
a
random
service,
but
would
you
be
interested
in
taking
this
as
an
idea
of
something
to
offer
to
all
of
the
sigs
rather
than
us
just
simply
trying
it.
D
D
N
D
A
O
D
D
And
personally,
my
motivation,
for
it
is
that
I've
met
several
people
and
been
telling
them
about
how
impactful
this
group
has
been
to
me
and
my
security
journey
and
then
immediately
struggled
to
tell
them
how
to
join,
because
it's
a
little
bit
hard
to
navigate
finding
the
mailing
list,
but
I'm
sure
there's
a
whole
bunch
of
other
motivations.
D
Just
the
likelihood
of
people
happening
upon
Sig
security
when
they're
deciding
where
to
contribute
in
kubernetes
and
it
being
populated
I,
think,
would
increase
the
number
of
people
that
show
up
to
this
meeting
and
then
stay
because
we're
awesome.
A
I
think
you're
absolutely
right
about
that,
and
there
is
the
like
generated
readme
in
K,
slash
community
in
the
security
directory
there,
but
that
you
know
again
is
kind
of
a
dry
listing
of
facts
and
doesn't
really
convey
the
spirit
of
of
who
we
are
as
a
group
and
how
we
do
things
and
also
has
discoverability
problems
of
its
own,
so
yeah.
Thank
you.
Thank
you.
So
much
for
lighting
of
fire
underneath
us
I
appreciate
it.
B
Yeah,
second,
that
thank
you,
I,
really
appreciate
it
too,
like
six
security
is
great
and
and
more
people
should
be
able
to
easily
discover
and
know
what
we're
about.
So,
thank
you
for
pointing
that
out.
O
What's
the
best
way
to
to
provide
feedback
on
this,
or
would
it
be
like
a
comments
in
the
pr
or
discussion
in
slack
and
and
just
coming
back
to
Civic
security,
I'm
still
kind
of
faced
with
the
same
dilemma?
I
guess
as
a
newbie
right
is
that
the
resource
list
is
awesome.
I
love
that
I
am
hesitant
to
get
involved
because
I,
don't
know
what
kind
of
time
commitment
is
is
required
or
what
level
of
expertise
is
required
or
needed
right
and.
O
Like
yeah
like,
if
you,
if
you'd
like
to
contribute,
attend
our
meetings
right
and
and
you
know,
if
you
get
involved,
you
know
like
close
a
PR
or
something
right,
just
something
simple
to
say:
here's,
the
kind
of
barrier
to
entry
or
whatever
I'll,
say.
O
You
say
like
I:
don't
want
to
end
up
like
coming
in
and
committing
myself
to
a
six-month.
You
know
security,
audit
or
code
project
right
off
the
bat
necessarily
right
so
and
and
with
security
that
tends
to
be
kind
of
a
high
stakes,
All
or
Nothing
kind
of
a
Viewpoint
and
I
just
want
to
make
sure
we
dilute
that
and
say
hey
just
come
join,
participate,
yeah,
yeah,
foreign.
A
A
A
Thank
you
further
thoughts,
discussion,
questions
about
lighting,
a
fire
under
improving
the
readme.
B
J
D
Seems
like
maybe
What's
blocking
is
that
we
want
to
add
into
it
some
like
holistic,
Mission,
culture
stuff,
which
might
actually
be
nicer
like
in
a
in
an
additional
page
that
we
link
to
it's
like.
If
you
want
to
know
what
six
Securities
about,
like.
That's
a
that's,
an
important
special
document.
That's
going
to
take
a
whole
bunch
of
collaboration
and
talking
about,
but
this
is
just
like
the
very
basic
information
needed
which
I
agree
would
be
great
to
just
have
out,
and
then
we
can
talk
about
all
of
the
cool
ways.
D
We
can
elaborate.
A
A
B
A
I
want
to
go
back
to
the
question
that
you
asked
Benjamin,
which
you
sort
of
answered
on
your
own,
but
it
was
a
fabulous
question
about
like
what
is
a
good
way
to
make
comments
or
or
to
to
participate
in
improving
the
readme.
Here
you
seem
to
have
figured
it
out
and
done
a
fantastic
job
of
doing
so
in
real
time
and
I
super
appreciate
that,
but
also
that's
a
soapbox
that
I'm
always
happy
to
pull
out
of.
A
Like
you
know,
sometimes
the
best
thing
is
to
make
a
comment
on
a
PR
Sometimes.
The
best
thing
is
to
say
something
in
a
meeting
Sometimes.
The
best
thing
is
a
message
on
slack,
and
you
know
that
depends
on
what
the
situation
is
and
and
how
a
person
feels
about
it
in
their
own
heart,
and
so
thank
you
so
much
for
bringing
your
input
into
this.
A
O
B
And
like
I,
just
just
want
to
sort
of
like
tailgate
on
that
and
and
say
that,
like
being
new
and
having
fresh
eyes,
is
a
superpower
like
I
think
a
lot
of
new
people
are
like?
Oh
no
I,
don't
you
know,
I,
don't
have
enough
experience
to
speak
in
the
space
like
I,
don't
know
enough,
but
actually
in
real
life.
B
What
happens
is
that
senior
people
tend
to
kind
of
forget
what
it's
like
to
be
new
and
so
having
that
power
of
like
fresh
eyes
and
like
fresh
perspective,
is
really
really
valuable
and
like
thank
you
for
bringing
it,
and
if
you
are,
you
know
in
the
room
or
watching
us
on
recording
and
worried
about
being
new
like
no
that's
awesome,
please
come
be
new.
We
really
really
welcome
that.
So
thank
you.
O
I'll
take
10
seconds
to
throw
my
my
industry
likes
to
keep
things
quiet
and
kind
of
like
in
special
groups
right
and
whereas
the
consciency
of
community
tends
to
be
more
open-minded
and
accepting,
which
is
really
cool,
but
from
a
security
culture.
It's
definitely
like
a
friction
right.
I,
don't
want
to
come
in
here
and
put
my
name
on
a
security
vulnerability
in
kubernetes,
for
example,
right.
A
B
Fortunately,
for
you
actually,
State
security
is
not
responsible
for
doing
that.
That
is
the
purview
of
the
security
response
committee,
which
is
a
different
group
of
people.
So
unless
you
want
to
join
the
SRC,
you
do
not
have
to
worry
about
showing
up
at
this
meeting
and
putting
your
name
on
a
phone.
A
Much
much
like
a
go
program.
We
have
fallen
off
the
end
of
the
main
function,
which
means
we
are
almost
set
to
return.
This
is
a
space
in
time
that
we
make
for
ourselves
and
for
each
other,
so
before
I
hit
the
end
button.
I
want
to
make
sure
there's
a
last
call
for
any
topics.
Questions
discussions
that
folks
would
like
to
share
with
the
group
at
this
time.