►
From YouTube: Kubernetes & Cloud Native Berlin Meetup March Edition
Description
Welcome to the live stream of the Kubernetes & Cloud Native Berlin Meetup - March 2023. Doors open for the in person meet up at 5 pm. The talks will begin at 6 pm, so stay tuned.
Find more information here: https://www.meetup.com/berlin-kubernetes-meetup/events/292009720/
About this meet up: We are a group for people interested in discussions around working with, running and developing Kubernetes and other cloud native technologies. We’re excited about container infrastructure, distributed systems and learning more about managing and extending them as such.
A
Thank
you,
I,
don't
think
I
need
the
mic
actually,
but
what
I'm
going
to
do
is
use
it
so
that
we
get
it
on
the
stream
and
for
the
audio
and
for
the
social
media
so
that
you
can
all
go
subscribe.
So
hello,
everyone
anyway,
I'm,
Aditya,
I'm
gonna,
be
your
event
host
for
today,
not
a
lot
of
people
here,
but,
as
I
said
earlier,
only
the
smartest
have
survived
and
come
here.
So
thank
you
for
coming
right.
That's
what
I
always
like
to
start
off
with
I
know.
A
You
all
take
time
on
a
sunny
Berlin
day,
which
is
very
unusual
in
the
middle
of
winter,
to
come
here,
to
learn
something
and
to
network
with
other
kubernetes,
so
give
yourself
a
round
of
applause
for
actually
showing
up.
That's
the
first
step.
So
thank
you
all
right.
So,
let's
get
started.
I'm
gonna
start
off
with
thanking
the
event
sponsors
right.
So
Microsoft,
as
you
know,
is
sponsoring
this
Meetup.
For
today
we
are
here
at
the
beautiful
office
of
I'm,
going
to
make
it
a
trivia
who
knows
what
office
this
is
except
the
person.
A
There
is
no
hint
somewhere
anyway
cut
it
short.
There
is
this
company,
which
was
called
Kinfolk,
used
to
participate
quite
a
bit
in
the
kubernetes
community,
got
acquired
by
Microsoft,
and
this
is
now
like
a
Kinfolk,
slash,
Microsoft
Office.
That's
why
we
have
all
these
startup
Vibes,
School,
wipes
and
Microsoft
has
been
kind
enough
to.
Let
us
use
the
space
for
the
kubernetes
Meetup.
So
thank
you
to
Microsoft,
we'll
have
some
food
and
beverages
also
thanks
to
the
organizers,
so
yeah,
pretty
cool.
A
So
today,
I'm
very
excited
for
two
Talks
by
Powell
and
Julia.
Powell
is
going
to
tell
us
about
running
Mac
OS
running
kubernetes
workers
on
Macos,
which
is
pretty
interesting,
and
he
has
some
things
to
say
about
the
open
source
project
that
they're
working
on
and
then
Julia
is
going
to
tell
us
about
Giants
form
and
their
Journey
with
the
community
right
very
excited
for
the
talks
here.
I'm
gonna
just
go
into
the
agenda
real
quick!
So
we'll
have
a
talk.
We'll
do
the
Q
a
we'll,
have
a
break
for
pizzas
and
drinks.
A
You're
welcome
to
still
grab
a
drink
before
the
talk
start,
we'll
do
a
q
a
again
and
then
we'll
have
some
time
for
networking
and
debriefs
and
just
connecting
with
other
people
right,
so
I
encourage
you
all
to
participate.
We
are
a
very
intimate
group
here
today
and
I
encourage
everybody
to
ask
questions
and
give
your
feedback
on
the
talks
in
the
talks
or
after
the
talks,
and
let's
keep
that
going
and
finally
Logistics
we
are
going
to
have
drinks
in
the
back.
A
If
you
haven't
found
that
already
food
is
going
to
show
up,
we
have
some
vegan
and
meat
pizzas,
so
we'll
have
a
lot
of
pizzas
each
today,
which
is
going
to
be
awesome
and
the
restrooms
are
over
there
and
yeah.
That's
it.
Finally,
we
follow
the
cncf
code
of
conduct,
so
please
be
nice
to
everyone.
That's
the
tldr
and
if
you
find
a
code
of
conduct,
violation,
you're
always
welcome
to
reach
out
to
one
of
the
organizers,
wherever
you
feel
comfortable
and
without
further
Ado.
A
A
B
B
A
Will
just
LinkedIn:
this
is,
if
you
just
type
it
yeah
and
here
are.
A
B
Patient
around
those
three
questions,
hopefully
the
how
will
be
the
longest
part
because
I
think
it's
it's
the
most
interesting.
So
we
needed
to
run
the
the
kubernetes
workloads
on
Macos
worker
nodes
because
we
got
asked
by
a
customer.
Is
it
possible
to
consume
the
Mac
Mini's
instances
as
kubernetes
nodes?
And
it's
all
the
the
whole
topic
started
when
AWS
starts
start
providing
Mach
1
metal
instances
as
ec2
instances,
so
Mach
1
metal
is,
is
basically
Mac
Mini,
but
with
M1
chip.
B
So
a
lot
of
people,
a
lot
of
people
got
interested
in
that
because
they
were
hoping
to
get
their
iOS
builds
faster
and
because
the
the
Mac
minis
were
offered
as
like
ec2
instance.
They
were
also
hoping
they
could
like
put
the
instance
up
when
they
need
it
and
then
turn
it
down
when
they
don't
need
it,
which
is
which
is
really
cool,
especially
for
for
Max
continuous
integration
system,
because
those
are
usually
pretty
expensive.
B
So
our
goal
here
was
to
run
iOS
builds
on
kubernetes,
basically
and
and
why
on
kubernetes?
There
are
a
few
reasons
so,
first,
like
the
customer
already
had
their
their
CI
system
built
in
around
kubernetes
cluster.
That
was
already
a
lot
of
tooling
around
a
lot
of
monitoring
and
things
like
that.
So
we
decided
like
we
should.
We
should
try
integrating
those
instances
as
like
first
class
kubernetes
worker
nodes.
B
We
are
also
hoping
to
get
like
Auto
scaling
features
from
kubernetes,
not
only
on
the
on
the
Node
level,
where
you
can
basically
scale
those
nodes
like
up
and
down,
but
also
based
on,
like
a
horizontal
pod,
Auto
scalar.
There
is
a
way
right
now
to
to
scale
horizontal
pod,
Auto
scalers,
not
only
on
the
resource
usage,
but
you
can
provide
any
custom
metrics.
If
it's
in
kubernetes
format,
you
can
instrument
your
horizontal
pod,
Auto
scalar.
B
So
it's
basically
scales
up
when,
when
the
metric
that
you
provide
goes
up
or
so
that
that
that
was
our
initial
plan
to
hook
the
metrics
from
the
CI
system,
which
was
built
kite
in
in
that
case
and
whenever
there
is
bigger
demand.
So,
like
probably
middle
of
week,
when
a
lot
of
people
is
is
trying
to
to
build
their
apps,
then
then
we
will
just
provide
more
CI
agents.
B
Yeah
so
that
that
was,
that
was
the
goal
that
we
set
for
ourselves.
So
we
wanted
to
run
this
build
kite
agent
with
the
node
selector,
meaning
that
it
will
only
run
on
the
nodes
which
has
this
Mach
1
metal
instance
type,
which
is
which
is
Mac
menu
with
M1
chip.
But
it's
not
a
VM,
so
ec2
are
usually
Linux
VMS.
So
this
one
it
isn't
a
VM.
It's
like
bare
metal,
Mac,
Mini
machine.
B
So
now
we
come
to
the
question.
How
so
kubernetes
provides
a
lot
of
like
extension
points?
There
are
like
interfaces,
you
can.
You
can
write
your
own
plugins,
so
we
decided
to
integrate
it
as
like,
first
class,
first
class
worker
node,
but
it
wasn't
like
it
wasn't
our
initial
faults
before
we
we
work
with
like
virtual
cubelet,
which
is
library
that
allows
you
to
to
provide
like
virtual
node
provider.
B
But
it's
it
has
some
cons,
basically
it's
confusing
for
people
because
they
may
have
like
multiple
Parts,
but
they
seem
to
be
running
on
the
one
note,
but
under
the
hood,
the
virtual
cubelet
provider
spins
up
like
many
nodes,
but
they
are
not
reported
back
to
the
control
plane.
So
that's
confusing
for
many
users
and
it
doesn't
work
well
with
monitoring
tools
and
other
things
which
are
based
on
like
core
kubernetes
apis.
B
So
we
decided
to
pick
like
another
extension
point.
So
on
every
kubernetes
worker
nodes
there
are
free
free,
essential
components,
so
there
is
cubelets,
there
is
Cube
proxy
and
there
is
container
runtime,
so
Cube
proxy
is
is
responsible
for
for
providing
for
proxying
the
the
traffic
from
pods
on
the
host
to
the
kubernetes
cluster
cubelets
is
responsible
for
for
dispatching
pods,
providing
like
pod
sandbox.
Also,
if
you
run
Cube
CTL
commands
like
exec
or
logs,
it's
also
initially
handled
by
by
cubelet
but
cubelets
delegates.
B
A
lot
of
a
lot
of
those
calls
to
The
Container
runtime
so
on
the
classic
Linux
node
container
runtime
is
usually
containerd
or
cro,
but
it's
very
easy
to
swap
the
the
container
runtime
on
the
Node
and
it's
easy,
because
the
the
contract
between
container
runtime
and
cubelet
is
well
defined.
It's
called
container
runtime
interface
and
yeah
that
we
decided
that's
what
we
will
do,
we'll
just
swap
the
container
runtime
with
something
which
can
satisfy
our
requirements
so
because
the
workflows
that
we
wanted
to
run
were
very
specific.
B
There
were
IOS
app
builds,
so
you
built
your
IOS
app
with
you
need
an
X
code
and
it
usually
it.
It
is
not
optimal.
To
run
like
more
than
one
iOS
build
on
one
machine,
you
will
get
them
the
most
of
performance
if
you
run
just
one
build
at
the
time
and
at
the
one
machine,
so
we
immediately
know
that
we
can
constraint
our
our
nodes,
so
they
can
only
run
like
one
POD
at
the
time
right
and
that's
how
Pros
CRI
was
was
born
so
cross.
Cri
is
a
shortcut
for
process
wrapper
CRI.
A
I,
don't
want
to
add
the
Cliffhanger
there,
but
would
you
mind
checking
if
you
have
the
right
screen
shape
because
on
the
screen
it
appears
that
you're
sharing
your
terminal
window.
C
B
You
made
it
right
now,
yeah,
so
back
back
to
our
slide,
so
we
decided
to
implement
very
simple
basic,
basically
like
container
runtime,
but
we
actually
didn't
need
even
containers,
because
iOS
builds
is
usually
just
start.
The
process
with
like
xcode
build
CLI
or
something
like
that.
So
what
we
really
needed,
we
needed
a
way
to
start
the
process
on
the
on
the
MAC
machines
and
then
to
just
drag
the
process
status
like
if
it's
failing,
then
you
know
we
need
a
way
to
restart
it,
and
so
on.
B
So
we
also
needed
like
to
compile
the
cubelet
and
Cube
proxy
for
Mac
OS,
so
the
cubelet
the
cubelet
was
like
actually
is
a
bit
easier
part
because,
because
with
cubelet
we
only
like
when
we
start
when
we
try
to
compile
it
for
for
Darwin.
B
We
just
noticed
that
there
are
few
things
missing,
so
the
the
C
advisor
was
in
there
like
the
the
library
that
was,
that
was
usually
there
for
for
Linux,
as
well
as
few
others,
but
thankfully
those
few
weren't
needed
for
for
our
workloads
and
for
our
for
our
needs.
So
we
just
implemented
the
stops
there
so
that
we
can
compile
the
cubelet.
If,
if
you're
curious,
like
what
changes
we
need
to
make
there
is,
there
is
a
link
at
the
bottom,
so
Cube
proxy
was
a
bit
more
challenging.
B
So
Cube
proxy
on
Linux
nodes
usually
operates
on
ipe
tables.
On
Windows
notes,
there
is
like
a
wrapper
around
Net
sh
command
and
we
we
tried.
B
We
took
some
inspiration
from
like
that
wrapper
around
netsh,
but
there's
no
netsh
on
MAC
machines,
so
we
just
simply
use
EF
config
in
a
way
that
if
we,
if
Q
proxy
needs
like
IP
address
for
for
the
Pod
running
on
the
on
the
nodes,
we
will
just
like
use
ifconfig
to
to
to
link
the
IP
address
to
the
virtual
interface
and
and
those
changes
are
also
open
source
yeah.
B
So,
as
I
said,
we
we
didn't
need
virtualization
really,
but
we
still
needed
those
dependencies
or
tools
that
were
required
to
run
those
builds.
So,
let's
say
like
with
with
any
any
CI
build
that
that
you
will
run
on
the
Linux
node.
You
would
usually
prepare
the
docker
image,
which
has
everything
that's
that's
needed
so
for
Mac
OS.
B
We
we
use
like
Amazon
machine
image
to
install
the
xcode
there
to
install
like
build
kite
agent,
and
everything
quotes
was
needed
for
the
workload,
so
that
was
kind
of
like
our
not
virtualization,
but
that
was
a
way
to
to
create
like
environment
that
can
be
easily
reproduced
on
on
any
node,
and
we
also
need
to
configure
cubelet
Cube
proxy
and
our
CRI
to
to
run
on
those
nodes.
So
we
decided
to
run
those
files
launch
the
agents
so
launch.
The
I
think
it's
very
similar
to
systemd
on
Linux
machines.
B
I
think
systemd
was
actually
like
inspired
and
created
after
launch
the
yeah
so
back
to
our
container
runtime
interface,
the
container
runtime
interface
itself,
it's
it's
a
grpc
API
and
it
exposes
two
Services.
The
image
service
and
also
the
the
runtime
service,
and
the
image
service
in
in
CRI
is
responsible
for,
like
basically
cubelet
uses
that
service
to
to
tell
the
the
container
runtime
to
pull
image
to
check
if
the
image
is
already
on
the
host
or
like
what
images
are
already
there
or
to
remove
image.
B
B
B
So
what
we
implemented
for,
create,
container
and
start
container
was
just
starting
a
process
on
the
Node
and
we'll
just
save
the
process.
Id
and
we'll
watch
the
basically
for
that
for
that
process,
whether
it's
still
running
the
interesting
ones,
are
exec
and
and
attach
so
that's.
We
also
implemented
those
and
using
exec.
You
can
actually
kind
of
like
SSH
on
the
host,
because
there
is
no
virtualization
layer,
so
you
can
do
like
Cube,
CT
or
exec
to
the
Pod
and
you
land
on
the
host
itself.
A
B
B
A
B
Sure,
oh
maybe
here
yeah,
okay,
okay,
yeah!
Sorry
about
that!
We
are
back
yeah,
so
there
are
other
also
other.
D
B
Other
procedures
in
that
in
that
service,
so,
for
instance,
like
version
it's
it's
just
reporting
like
the
name
of
the
container
runtime
and
also
a
version
and
I
think
right
now.
B
I
think
right
now,
I
can
play
a
demo.
They
have
pre-recorded.
A
B
Sure
so,
basically
we
are
in
the
terminal
and
I'm
running
just
Cube
CTL
get
nodes
and
I
have
two
notes
in
that
cluster.
B
So
one
is
a
Linux
node
and
you
can
tell
that
from
from
container
runtime,
which
is
like
the
column
on
the
on
the
far
right
and
the
container
runtime
for
Linux
node,
says
Docker,
which
is
like
expected
and
for
for
the
other
notes,
which
is
like
Mac
OS
note,
and
you
can
recognize
that
from
OS
image
column
here,
which
says
like
10.15,
the
container
runtime
is
actually
the
pros
URI,
which
is
the
the
thing
that
I
was
talking
about
before
and
in
that
demo
we
are
trying
to
run
the
the
deployment
which
is
like
build
kite
agent
and
we
specify
the
node
selector.
B
So
we
are
sure
that
it
will.
It
will
land
on
our
Mac
nodes
and
we
Define
like
two
containers
here.
So
one
container
will
be
build
kite
agent
and
the
other
container
is
it's
just
like
yes
command.
So
it's
it's
kind
of
like
for
a
demo
to
show
you
that,
basically,
most
of
the
features
that
you
would
normally
have
in
the
deployment
are
supported.
So,
in
that
case,
the
build
kite
agent
will
start
as
a
one
process,
and
if
the
other
process
is
other
process
which
is
other
container,
it's
not
interrupting
it.
B
Yeah,
so
if
I
go
ahead
and
apply
this,
so
we
can
see
that
now,
when
you
run
Cube
CTO
get
pods
the
you
actually
see
that
they're
in
the
build
kite
agent,
there
are
two
containers
running
and
the
status
is
reported
in
like
exactly
the
same
way
as
as
for
for
regular
pods
right.
B
B
So
if
you
run
exec,
you
actually
land
on
the
host
itself,
so
it's
kind
of
like
sshing
to
The
Host,
so
just
to
show
that
you
know
the
normal
workflow
of
operating
airport
works,
you
can
run
like
Cube,
CT
or
logs
and
and
the
logs
of
the
process
are,
are
there
as
well,
so
for
the
build
kites
you
can
see
the
logs
and
for
like
yes
commands,
it
will
be
just
wise
on
way
down
so
on
the
right.
B
If,
when
we
are
when
we
are
in
the
Pod,
which
means
that
we
are
on
the
host
machine,
we
can
basically
try
interrupting
one
of
the
process.
So
one
of
the
containers
just
to
see
if
the,
if
from
operator
perspective
on
the
left,
who
is
running
like
Cube
CTO,
get
pods
and
he
watches
for
it.
B
We
can
see
that
if
we
kill
one
of
the
process,
it
will
get
reported
on
the
left,
yeah,
so
I'm,
just
getting
the
the
process
ID
on
the
right
and
I
will
run.
I
will
kill
that
process.
Basically.
B
Yeah,
so
if
I
kill
this
process
for
for
a
second,
you
can
see
that
the
cubelet
immediately
like
that,
our
CRI
immediately
reports
that
the
the
process
is
down.
So
you
can
see
like
status
with
the
exit
code,
and
you
can
see
that
there
are
one
of
two
containers
currently
running.
But
the
good
news
is
that
cubelet
will
issue
the
command
to
restart
another
process
which
which
happened
here.
So
we
still
have
like
two
out
of
two
process:
slash
containers,
running
right.
B
Yeah
so
I
know
I've
been
talking
for
like
over
20
minutes,
but
I
will
try
to
convince
you
that
this
is
a
very
simple
setup,
because
the
the
process
CRI
itself,
it's
just
like
few
hundreds
lines
of
code.
So
it
was
really
easy
to
write
and
because
there's
not
a
lot
of
code
involved.
B
B
So
the
entire
iOS
teams
was
basically
using
this
for
over
a
year
without,
like
any
major
hiccups.
So
we
had
also
a
few
other
components
in
that
setup.
So
one
of
them
was
custom,
auto
scalar
for
that
nodes,
and
that's
allowed
them
to
save
a
lot
of
money,
because
you
would
normally
expect
that
iOS
team
just
works
during
the
week,
not
during
the
weekend,
so
over
the
weekends.
B
You
can
just
scale
down
those
notes
as
well
as
you
can
scale
down
those
thoughts
outside
of
working
hours
and
just
leave
a
few
yeah
and
we
are
open
and
sourcing
all
of
it.
B
So
in
this
repository
we
have
free
free,
major
things,
so
we
have
Packer
config
for
building
the
Amazon
machine
image
for
for
those
Mac
OS
notes,
and
we
are
posting
it
as
a
reference
we
we
haven't,
used
it
for
a
while,
but
I
think
it
should
be
quite
easy
to
replicate
or
like
it
should
be
quite
easy
to
to
build
those
images.
B
B
So
that
way
you
can
create
a
cluster
and
you
have
a
launch
templates
which
you
can
use
in
your
node
group
to
just
create
like
the
node
pool
of
Mac
OS
nodes.
Again,
it's
we
post
it
as
a
reference
because
we
haven't
used
it
for
over
a
year
and
we
also
are
open
sourcing
cross
CRI.
So,
as
I
said,
it's
very
simple,
but
in
case,
if
in
the
future
you
want
to
write
your
own
CRI,
I
guess
it's.
It
could
be
a
good
starting
point,
because
it's
it's
quite
simple.
B
C
B
The
other
links
I
mentioned
that
we
use
the
the
metrics
from
continuous
integration
platform
to
power,
horizontal
pod,
Auto
scalar,
and
for
that
we
had
to
also
write
very
simple
service
for
translating
metrics
from
the
format
of
CI
provider
to
the
kubernetes
metric
format
and
I
gave
a
presentation
about
that
last
year.
I
think
on
the
cloud
native
free
Jack.
So
is
the
link
and
I
wanted
to.
Thank
you.
B
A
A
B
So
so
the
so,
the
question
was
about
registration
of
the
cubelet
or
on
the
Note
itself
right
in
in
the
cluster.
So
like
one
thing
we
had
to
do,
we
had
this
cubelets,
which
was
slightly
modified
for
our
needs,
as
well
as
cube
proxy,
as
well
as
our
container
runtime
interface,
and
what
we
had
to
do
when
we
are
building
an
image
for
for
those
nodes.
We
just
need
to
specify.
We
just
need
to
configure
those
as
launch
agents.
B
B
So
so,
not
necessarily
the
distribution,
because
we
only
maintained
the
image
for
worker
nodes.
The
the
control
plane
was
exactly
the
same
and
when,
when
like
the,
we
didn't
bake
the
you
know,
cluster
name
or
any
cluster
specific
information
in
the
in
the
machine
itself,
but
you
can
configure
it
as
a
user
data.
So
when
you,
when
you
start
using
the
image
you
can
specify
like
what
cluster
it's,
that
instance
should
join
right.
C
A
D
E
You'll
see
pizzas
marked
with
veg
there
they're
vegan
cheese,
so
don't
actually
think
they're
just
cheese
cheese
and
we
didn't
actually
pay
attention
to
anyone's
dietary
preferences.
We
try
to
make
room
for
as
much
as
possible
yeah.
Sometimes
it's
just
super
special
requests
and
we
have
to
go
according
to
that.
That's
one
two
we
have
Cloud
native
rejects
coming
up
soon.
It's
next
month,
it's
not
very
far
away.
We're.
Also
organizers
of
cloud
native
rejects.
E
That's
Andy,
Chris
me
Lexi
and
quite
a
few
of
us
in
our
team
at
the
the
Kinfolk
team,
now
part
of
Microsoft.
So
if
you're
there
before
cubicon
to
plan
to
and
do
try
and
check
rejects
out,
try
and
stop
by
if
you
need
tickets,
if
you
need
discount
codes,
Etc
do
come
by
and
speak
with
me
and
I'll
try
and
see
how
I
can
pass
that
along
for
you
and
your
friends
and
any
colleagues
who
are
interested.
E
We
also
have
some
job
Seeker
promo
codes,
so
we're
very
happy
to
distribute
that
as
well.
A
lot
is
one
of
our
sponsors
as
well.
It's
a
great
Community
Conference
ahead
of
the
noise
of
kubecon.
So
do
do,
try
and
check
it
out.
I
know
that
travel
is
restricted
and
not
everyone's
planning
to
go
and
be
there
in
Amsterdam.
E
Today,
Aditya
was
telling
me
that
he
may
or
may
not
make
it,
but
for
those
of
you
who
do
plan
to
make
it
and
want
to
come
even
a
day
earlier
or
something
like
that,
we're
rejects
is
on
16th
and
17th
of
April,
so
yeah
try
and
make
it
and
be
there
and
I
promise.
You
there'll
be
lots
of
chats
lots
of
networking
a
fun
relaxed
atmosphere
before
kubecon
for
all
of
the
noise
of
kubecon.
E
So
and
that's
that's
something
we
pride
ourselves
with
so
and-
and
it's
also
the
platform
for
the
rejected
talks
of
kubecon
so
yeah,
which
is
why
we're
rejects,
but.
A
A
Gets
rejected
at
the
rejects
conference
we
have
kubernetes
Berlin
you're
always
welcome
to
come.
Give
a
talk
here
and
yeah
I
would
love
to
chat
over
pizzas
now,
which
I
think
are
getting
cool.
So,
let's,
let's
go
right
into
it.
Thank
you,
Powell
and,
let's,
let's
reconvene
in
20-ish
minutes
is
20
minutes
fine
for
everyone,
for
we
have
a
lot
of
pizzas
and
not
a
lot
of
people
so
enjoy
and
see
you
in
20
minutes.
Then.
A
A
D
Perfect,
okay.
So
a
couple
of
weeks
ago,
Benazir
reached
out
to
me
asking
me
to
give
a
talk,
and
my
first
instinct
was
this:
so
I
felt
like
I'm.
Never
gonna
do
that.
I
haven't
talked
in
front
of
people
in
I.
Don't
know
four
years,
maybe
covert
made
it
possible
right.
We
all
could
hide
behind
our
screens,
but
then
I
thought
well
I
do
relationship
building
at
Giant
swarm.
D
Why
should
I
hide
I
talk
to
you
all
the
time
on
conferences
and
events,
so
I
can
also
do
that
here
up
front,
so
I
stood
up
and
faced
my
fears
and
I'm
going
to
tell
you
a
little
bit
about
giant
swarm
and
what
we
built
with
our
community
and
I'm,
going
to
start
with
our
culture
of
Open
Source,
and
why
we
think
it's
important
how
we
live
it,
a
giant
swarm
and
with
our
customers
and
friends,
which
obviously
would
be
all
of
you.
D
D
We
also
believe
in
the
power
of
collaboration,
transparency
and
Community
Development,
and
that
is
why
we've
built
our
entire
platform
on
open
source
Technologies
and
actively
contribute
to
numerous
projects,
including
kubernetes,
Linker,
D,
Prometheus,
cuberno
and
others.
I
think
we
have
more
than
20
people
contributing
to
over
50
different
projects,
open
source
projects
at
the
moment,
which
is
great,
I,
think
yeah.
D
D
So
how
it
all
came
into
being
is
with
covet.
Almost
three
years
ago,
I
started
with
giants
warm
as
a
partner
manager
and
back
then
we
did
not
really
have
a
partner
strategy
in
place
and
I
felt
was
really
difficult
because
you
could
not
go
out
and
meet
people.
Usually
I
would
have
gone
to
a
nice
conference
like
kubecon,
that's
taking
place
next
month
and
would
have
just
walked
over
to
people
and
said
who
I
am
and
what
we
are
doing
and
what
we
could
do
together,
and
that
was
not
possible.
D
D
So
we
had
a
really
nice
little
Meetup
virtual
and
people
really
enjoyed
it.
It
was
an
engaging
discussion.
People
had
a
lot
of
questions
and
they
shared
a
lot
of
yeah
things.
They
were
dealing
with
in
their
everyday
work
and
and
I,
don't
know
problems
issues
they
had
and
we
figured
okay.
That
was
nice.
We
should
do
that
again,
so
we
figured-
and
we
should
not
only
do
that
again
with
partners,
but
we
could
do
that
with
our
customers
also
because
we
have
not
seen
our
customers
in
ages
as
well.
D
So
that's
what
we
did
next.
So
in
2021,
in
the
beginning,
we
had
our
first
what
we
call
Giant
swarm
in
France
evening
and
that's
actually
an
evening
event
now.
So
we
start
at
8pm.
We
invite
people
to
this
first
one
we
had
customers
only
and
we
the
thing
is
we
as
Giants
form.
We
only
organize
those
events,
so
we
usually
don't
speak.
It's
Talks
by
customers.
For
example,
in
this
first
meeting
we
had
Adidas
giving
a
talk
on
how
they
did
hype
sales,
and
it
was
a
very
small
first
event.
D
I
think
we
invited
about
20
people
and
13
of
them
showed
up.
We
ship
beer,
we
usually
ship
beer
to
every
event
now
and
I
select
the
beer,
and
then
we
have
a
little
beer
introduction
to
each
beer.
Before
these
events,
I
didn't
know
anything
about
beer
and
now
I
feel
I've
learned
a
lot.
So
there's
a
lot
of
interesting
little
breweries
everywhere
around
the
world
and
a
lot
of
fun,
interesting
beers.
So
but
that's
just
a
side,
note
yeah,
so
this
first
event
worked
also
really
well
and
we
figured
okay.
Why
is
that?
D
D
What
we
created
was
a
safe
space
where
people
could
meet
and
interact
and
chat,
enjoy
a
beer
and
have
a
nice
time
and
talk
about
what
was
going
on
in
their
work
life
and
that
substituted
a
little
bit
for
yeah
meetups
and
get
togethers
at
conferences,
for
example.
So
we
usually
have
an
verbal
NDA
going
on
in
these
events,
we
don't
record
them.
We
don't
take
notes,
we
don't
share
anything
outside
of
the
event.
D
D
And
yeah
we
have
our
CEO
Oliver
Truman,
he's
doing
the
moderations
all
the
time,
which
is
also
quite
nice.
He
is
a
really
good
moderator
and
in
Virtual
meetings.
Sometimes
the
danger
is
that
some
people
might
get
lost.
They
are
behind
the
screen.
They
are
very,
very
yeah,
not
interacting
a
lot.
They
can
hide
behind
their
screen
and
he
is
very
good
and
asking
questions
engaging
making
people
talk.
So
that's
actually
quite
nice.
D
So
I
have
some
numbers
prepared
for
you
now,
which
might
be
nice
to
see
how
the
events
developed.
So,
as
you
can
see
here,
I
hope
you
can
see
that
in
the
back
we
had
this
first
event
in
February
2021,
quite
a
few
participants,
but
the
numbers
grew
steadily,
so
we
had
by
May
2021.
We
already
had
over
30
people
attending
and
then
we
had
a
little
drop
in
numbers.
D
What
happened
obviously
covet
was
less
dangerous.
In
summer
people
went
out
again.
People
were
very
happy
to
go
on
vacation
and
not
behind
the
screen,
all
the
time
so
in
summer.
That's
what
we
realized
so
far.
The
numbers
are
always
a
little
bit
lower
than
during
the
rest
of
the
year.
So
then
we
had
in
Fall.
D
Actually
the
events
were
the
most
participants
up
until
the
mid
60s,
and
these
were
actually
quite
big
events
and
we
figured
that's
quite
nice,
but
maybe
we
don't
want
to
have
a
hundred
people
in
a
Google
meet
because
then
you
also
lose
people
and
you
lose
attention
and
you
cannot
really
engage
anymore
and
what
we
did
is
we
tried.
We
opened
the
events
up
in
general,
so
we
not
only
had
customers
in
the
meetings
anymore,
but
we
also
invited
friends
Community
people
to
also
participate.
D
That's
why
the
numbers
Rose
so
much,
and
then
we
decided
to
have
also
focused
events.
We
have
General
broader
ones
where
we
invite
everyone,
and
then
we
have
smaller
ones
for
specific
Industries,
for
example
Financial
Service,
because
we
felt
they
have
similar
problems
and
issues
they
are
dealing
in
their
everyday
work
with,
for
example,
we
had
an
event
last
year
where
we
had
a
lawyer
speaking
about
compliance
and
gdpr
and
moving
actually
into
the
Azure
Cloud
how
to
make
that
safe
right
and
not
have
troubles
on
a
law
side
afterwards.
D
That
was
also
very
perceived
because
a
lot
of
banks
have
this
issue.
So
and
then
here
you
can
see
it's
again,
this
summer
drop
of
the
numbers,
and
here
we
also
skipped
an
event.
You
can
see
that
maybe
not
so
well
in
the
back.
We
had
one
in
April
and
then
in
June
last
year
and
in
may
obviously
we
had
kubecon
and
Valencia,
which
a
lot
of
us
attended
and
we
figured
it
doesn't
make
sense
to
have
a
virtual
meeting
as
a
competition
to
kubecon.
D
Let's
do
something
nice
at
kubecon,
so
we
had
for
other
community,
a
big
party
where
we
invited
I
think
we
had
over
350
people
in
the
end
that
showed
up
to
this
party
and
then
we
started
off
end
of
August
again
and
it
was
really
nice
to
see
that
a
lot
of
people
remembered
and
came
back.
So
we
also
had
almost
50
people
showing
up
and
then
last
fall.
The
numbers
dropped
again,
which
I
found
interesting
because
the
year
before
with
covert
restrictions,
the
numbers
went
up,
but
what
happened
was
in
fall.
D
All
kinds
of
conferences
took
place
at
the
same
time
like
container
con
container
days
and
Hamburg
cubecon
in
Detroit,
a
lot
of
things
and
people
who
are
traveling
to
those
events.
So
we
were
quite
happy
with
February
this
year.
We
we
had
a
big
one
again
with
almost
50
people,
so
it
shows
us
if
you
do.
The
events
regularly
people
remember
them
and
they
maybe
even
have
blockers
in
their
calendar
and
they
come
back.
D
So
that's
the
nice
thing
about
it
and
the
next
event
we
will
actually
have
have
after
kubecon
and
it
will
be
on
open
source,
so
yeah.
But
that
said,
there's
of
course,
always
things.
You
learn
and
challenges
that
come
up
when
you
organize
events,
so
I
guess
benazia.
You
know
that
it's
not
always
just
running
smoothly
and
let
me
see
if
I
can
change.
I
lost
my
yeah,
so
the
biggest
challenge
I
feel
is
always
coming
up
with
a
good
topic
and
finding
the
right
speaker
for
it.
D
So
it's
always
important
to
have
something
that
people
are
interested
in.
Otherwise
they
won't
sign
up
and
won't
come
that
the
best
meeting
is
nothing
without
a
nice
talk,
so
we
usually
have
a
kickoff
meeting
internally
where
we
discuss
what
kind
of
topic
would
be
nice
to
have,
and
then
we
reach
out
to
speakers
and
sometimes
it
happens.
Well,
it
happened
to
me
once
that
I
had
a
last
minute
drop
out.
D
D
Luckily
we
had
two
speakers
for
that
evening,
so
we
still
had
a
main
act
and
then
I
remembered
one
of
the
people
from
the
community
that
signed
up,
and
he
also
was
a
very,
very
expert
in
the
topic
we
had
and
I
asked
him
if
he
could
share
some
things
without
having
slides,
prepared
or
anything
just
talking
a
little
bit
about
his
experiences,
and
that
worked
very
well.
He
did
that.
So
in
that
case,
I
was
lucky,
but
the
learning
from
that
was
of
course,
always
be
prepared
and
have
a
backup.
D
So
what
I
try
to
do
now
with
the
team
is
having
someone
in
the
back
that
could
substitute
and
jump
in
if
the
Speaker
gets
sick
or
cannot
make
it
and
I
said.
Usually,
we
don't
speak
as
Giants
form,
because
we
are
the
problem
we
just
organized,
but
in
that
case
I
usually
asked
someone
from
the
team
that
could
substitute
and
tell
something
related,
so
just
that
the
event
can
take
place
yeah.
D
Then,
of
course
you
saw
the
challenge
already
numbers
dropping
in
summer
when
people
go
out
more
and
maybe
are
not
interested
in
sitting
behind
the
screen,
but
want
to
meet
real
people
like
here
at
this
event,
but
I
think
we
overcame
that
challenge
a
little
bit
with
regularity
and
having
this
the
events
taking
place
on
a
regular
basis,
then
I
had
a
nice
problem.
This
February
actually
for
the
first
time,
I
never
had
that
before.
D
So
it
happened
this
we
were
out
of
beer,
so
we
had
more
people
registering
than
I
expected
because
the
previous
events
went
less
attended.
There
were
no,
not
so
high
numbers,
so
I
reserved
less
beer
than
people
that
registered,
but
we
have
a
very
nice
company
that
we
are
working
with
so
I
called
them
and
asked
them
hey
Susanna,
her
name
is
Susanna.
Can
you
help
me
out?
D
We
have
more
people
coming
in
and
we
need
more
beer
and
then
she
said:
yeah
I
don't
have
this
particular
beer
anymore,
but
I
can
recommend
you
something
else,
and
then
that
was
fine,
so
some
people
got
different
beer
problem
solved
or
good
in
the
end,
yeah
I
guess
that's
some
challenges
and
I'm
sure
there
will
be
more
when
we
have
more
events,
there's
always
something
coming
up
that
you
don't
expect,
but
it's
fine
I
have
really
nice
colleagues
that
always
help
out
a
nice
team
yeah.
D
So,
moreover,
it's
a
journey
and
it's
always
under
construction.
You
always
can
improve
things
and
can
do
things
better.
So
we
all
try
to
improve
the
events
on
a
regular
basis.
My
colleague,
Tommy
I,
told
him
I
told
about
him
before
and
he
built
a
very
nice
landing
page
for
people
to
easily
sign
up
without
filling
in
any
more
information
than
necessary,
just
your
email,
and
if
you
want
beer,
of
course
we
need
your
address.
Otherwise,
it's
not
possible.
D
We
have
automated
emails
going
out
as
reminder
emails
one
week
and
one
day
before
the
event,
shipping
also
the
calendar
invite
again
so
that
really
nobody
misses
the
meeting
and
we
also
what
we
usually
usually
do.
Is
we
have
our
colleagues
inviting
in
the
first
step,
because
we
feel,
if
you
know,
people
in
the
community
or
with
our
customers-
it's
nice.
D
If
you
are
the
one
inviting
the
person,
you
know
it's
more
personal,
so
we
usually
do
that
first,
but
of
course
everyone
is
very
busy,
and
sometimes
you
might
forget
someone
and
we
overcame
that
by
having
a
special
email
going
out
to
everyone
that
ever
signed
up
to
our
events.
D
Checking
in
with
people
are
that
not
registered
yet
saying
hey,
I
saw
you're
not
on
our
list.
Yet
do
you
want
to
come?
This
event
takes
place
in
two
weeks?
If
you
want
beer,
please
sign
up
by
next
Monday
or
whatever,
and
usually
that
gives
us
five
to
ten
more
people
that
register.
So
that's
quite
nice
yeah.
These
are
some
improvements
we
set
up
already.
The
next
thing
we
are
working
on
is
to
reward
people
from
the
community
that
are
very
active
and
are
showing
up
every
time.
D
D
If
you're
coming
five
or
ten
times
asking
questions
participating,
giving
a
talk
whatever
in
the
future,
the
SE
people
will
get
some
Giants
from
swag
a
reward
whatever
we
are
working
on
that
right
now,
because
it's
really
nice,
if
you're
an
active
member
of
the
community
and
yeah
show
up
regularly.
D
Moreover,
we
also,
what's
also
nice
to
know-
is
that
our
events,
they
usually
have
two
talks
and
they
end
at
10
30
officially,
but
people
like
to
stay
because
they
don't
have
a
long
way
back
home,
I
guess-
and
maybe
it's
also
because
we
have
a
nice
setting.
So
a
couple
of
them
usually
stay
until
after
midnight
and
have
very
intense
Tech
discussions
until
the
very
end
I
usually
go
to
bed
before
that,
because
at
some
point
I
cannot
follow
anymore,
but
yeah.
That's
really
nice
actually
yeah.
D
So
this
leads
me
to
the
last
Point
already
and
I
lost
my
mouse
again
how
our
community
can
grow
and
how
you
can
become
part
of
it
and
help
us
grow
it
and
ways
of
improving.
We
have
created
a
page
where
that
we
send
to
people
where
you
can
register
and
where
you
can
show
your
interest
in
becoming
part
of
our
community,
because,
as
I
explained
earlier,
it's
an
invite
only
Community
to
have
that
safe
space
and
to
really
have
open
discussions.
D
So
people
can
sign
up
and
we
always
look
for
speakers.
So
if
you're
interested
in
becoming
a
speaker
contributing
giving
a
nice
Tech
talk,
you
can
reach
out
to
me
afterwards.
I
will
hang
around
here
a
little
bit
and
we
can
have
a
chat
and
connect.
So
that
would
be
really
nice.
D
Last
but
not
least,
we
also
try
to
grow
inside
the
ecosystem
and
work
together
with
yeah
Community
people.
For
example.
We
are
having
discussions
with
the
women
people
at
the
moment
and
we
will
most
likely
have
an
event
with
them
coming
up
in
May,
because
we
feel
it's
really
nice
to
engage
and
interact
and
yeah
make
something
valuable
for
everyone,
so
I
think
giant.
Woman
friends
really
has
become
a
nice
thing
to
do.
D
D
A
I
have
a
question
for
you
actually,
yes,
what
do
you
find
the
most
rewarding
about
the
kubernetes
community,
specifically
I
know
giant
swarm
has
been
doing
this
since
the
beginning
of
the
company.
It's
part
of
the
ethos,
what's
most
rewarding,
for
you
personally
saying
going
through
all
of
the
tough
Logistics
that
technical
glitches
of
the
events.
What
keeps
you
here
all
this
time.
D
I
only
have
met
really
nice
people
so
far
since
I
started
at
Giant,
swarm
and
Everyone
is
always
I'm.
Not
a
tech
person
and
I
often
need
a
little
more
explanation
to
take
topics
than
maybe
you
would
need,
but
everyone
I
met
and
talked
so
far
has
always
been
really
nice
and
helpful.
That's
what
I
appreciate
a
lot
and
people
really
love
what
they
are
doing.
This
is
also
really
nice.
D
So
if
you
talk
to
someone
at
kubecon,
even
though
I
cannot
follow
them
after
a
couple
of
minutes
anymore,
they
you
really
see
that
they
live
for
that
and
they
are
enthusiastic
about
it,
and
it's
really
nice
people
being
so
happy
with
what
they
do
and
then,
of
course,
when
you
do
those
events-
and
you
see
people
hang
until
there
until
one
in
the
morning,
then
you
feel
okay.
Something
was
right,
so
it
must
have
been
a
nice
evening
even
behind
the
screen
and
not
in
a
virtual
in
a
yeah
meeting
room
like
this
year.
A
D
So
the
question
was
how
we
motivate
our
speakers.
So
in
the
beginning
it
really
was
a
lot
of
customers.
We
asked-
and
we
still
do
that
so
I
have
some
colleagues
here,
so
they
work
on
with
the
customers
on
a
daily
basis.
So
they
know
them
very
well.
That
always
helps
when
you
have
a
good
connection
already
to
ask
people
for
that
kind
of
favor
and
then
I
don't
know
it's
actually
that's.
D
Why
I
said
it's
the
biggest
challenge
to
find
speakers
that
want
to
do
that
and
it's
more
like
I,
don't
know
it's
just
maybe
it's
nice
to
be
part
of
that
community
and
the
events
and
to
share
your
story
and
what
you
have
built,
what
you've
done?
Maybe
what
challenges
you
have
overcome
and
you
also
I,
think
you
also
get
something
back,
because
the
audience
usually
is
very
active
in
discussing
and
suggesting
alternative
ideas
or
telling
what
other
people
have
done
and
what
obstacles
they
have
overcome.
C
C
A
Kind
of
setting
yes
yeah,
I
I,
would
like
to
share
that
I
feel
the
same
here.
I've
been
part
of
the
kubernetes
community
for
about
six
six
years
now,
and
for
me
this
is
home.
I
come
here
because
I
see
this
as
something
giving
back
and
back,
and
there
was
like
a
2
000
people
here.
It
would
still
be
okay,
because
The
Same,
Spirit
and
I'm
usually
nervous
giving
talks
in
front
of
people.
But
this
is
our
community
and
it's
a
safe
space.
B
D
But
everyone
can
yeah,
I,
know
what
you
mean
and
it's
not
that
I
only
come
to
you
and
say
you're
invited.
D
So
that's
why
we
have
that
page
that
I
had
before
invite
only
means
we
don't
advertise
it
on
social
media
like
Twitter
or
LinkedIn,
so
that
because
we
want
to
keep
it
a
safe
space
right,
so
we
don't
want
things
to
go
to
I,
don't
want
to
say
leak
outside.
That
sounds
too
negative,
but
we
feel
if
we
have
too
much
advertising
and
maybe
recording
people
don't
open
up
that
much
anymore,
but
you
can,
of
course
that's
why
this
showed
this
page.
E
D
Like
my
talk,
we
once
had
a
talk
by
someone
about
self-setting
salaries
or
how
to
acquire
Talent
during
covert,
which
was
Troublesome,
but
then
sometimes
we
do
the
more
specialized
ones
that
we
ship,
for
example,
to
people
that
are
in
Ecom
because
they
have
similar
problems
and
then
the
talk
is
also
very
specific
to
I,
don't
know
the
shop
that
they
are
building
and
the
technology
behind
that
and,
of
course,
we
could
also
ship
that
to
everyone.
But
probably
not
everyone
would
be
interested
in
these
specific
problems.
D
So,
but
if
people
are
interested,
they
still
get
the
invite
it's.
Of
course
we
invite
everyone,
but
usually
only
the
people
from
that
area
sign
up
because
it
makes
sense
to
them.
D
What
we
have
now,
we
would
see
that
over
time,
I
guess
yeah
and
that's
what
I'm
doing
I'm
running
around
at
kubecon
talking
to
people
and
checking
people
that
come
to
the
booth,
for
example,
I,
always
ask
them:
okay,
what
are
you
doing?
Are
you
interested
in
maybe
giving
a
talk
at
some
point
during
the
events?
That's
what
we
are
doing
and
then
usually
we
have
the
badge
scanned
and
then
we
reach
out
to
those
people
afterwards.
D
I
also
like
to
see
people
rejoining
so
for
me,
it's
not
only
being
there
once
but
coming
several
times
and
really
have,
as
Cedric
mentioned
this
trustful
environment,
where
people
start
to
know
each
other
and
feel
comfortable
sharing
what
they
are
doing,
and
also
not
only
give
back,
but
also
get
information
back
right
and
also
maybe
help
on
discuss,
also
very
problems.
They
deal
with.
A
All
right,
any
final
questions.
I
I
wanted
to
add
something
to
that.
If
there's
no
other
questions,
so
we
just
wanted
to
share
I
I
know
it's
a
tough
time
right
now
in
the
market
and
a
lot
of
companies
are
letting
go
of
people.
One
of
the
to
answer
to
your
question:
what
is
the
success
criteria
for
the
Meetup?
For
me,
it's
like
people
connecting
with
each
other
and
perhaps
finding
new
opportunities.
A
I
know
a
bunch
of
people
who
have
found
jobs
through
coming
to
the
Meetup
and
just
saying
hey,
you
know
what
I'm
working
on
something
we
have
a
role
sounds
like
it's
interesting:
they
get
a
new
opportunity,
they
evolve
in
their
careers
and
then
two
years
later
they
come
back
to
you
and
tell
you
that
hey
I
found
a
job
through
that
Meetup
and
I'm
really
happy.
Now,
that's
for
me,
the
long
term
reward
that
you
get
as
as
a
Meetup
and
Community
member.
A
D
A
That
was
a
great
talk
on
community
and
I
was
just
like
sitting
there,
reflecting
on
how
far
we
have
come
with
this
Meetup
just
wanted
to
share.
We
started
this
Meetup.
What
four
months
ago
now
restarted
it
actually
Chris
did
a
really
good
intro
on
how
this
Meetup
originally
started.
We
have
Andy
here.
A
This
is
again
the
Kinfolk
office
right,
so
it
has
some
background
and
this
Meetup
has
been
going
on
for
a
while,
and
it's
just
amazing
to
see
faces
which
Cedric
we
met
last
time
we
we
had
some
pizza
together.
It's
always
nice
to
see
people
come
back,
so
I'm,
looking
forward
to
you
coming
back
next
time
and
again,
I'm
gonna
do
the
closing
Spiel
here
so
bear
with
me,
but
always
always
looking
for
feedback
today.
I
know
there
was
logistic
challenges
right,
so
the
barricade
and
the
6A.
A
Sometimes
you
do
you
just
get
some
of
that
Randomness.
Sometimes
the
video
setup
doesn't
work,
but
that
means
that
there's
always
opportunities
where
you
can
help
right.
So
if
any
of
you
would
like
to
come
over
and
help
with
the
next
Meetup
always
feel
free
to
get
in
touch.
We
could
always
use
some
more
hands
you.
You
could
just
come
over
one
hour
before
and
help
us
set
up
the
AVN,
hopefully
you'll,
learn
something
out
of
it
as
well.
A
It's
very
rewarding
over
a
long
period
of
time
to
see
the
community
grow
and
I
hope
you
all
see
each
other
bump
into
each
other
at
kubecon
really
soon
and
before
Benazir
says
it.
There's
another
conference
before
kubecon,
which
is
cloud
native,
rejects
right.
So
if
you
want
to
go
attend
Cloud
native
rechecks,
please
reach
out
to
Benazir,
if
not
find
Benazir
and
Julia,
perhaps
Andy
and
a
bunch
of
other
people
at
kubecon
and
say
hello
and
Wednesday.
Do
you
wanna,
say
something
and
then
close.
E
We
have
a
bunch
of
promo
codes
for
cloud
native
rejects,
so
you
can
just
just
come.
Have
a
chat
with
me,
we'll
see
what
you're
interested
in
and
all
of
that
and
I
can
share
those
quotes
for
you
and
your
network
and
your
communities
and
yeah.
It
would
be
great
if
you
share
that
around
spread.
The
word
Cloud
native
rejects
is
on
April
16th
and
17th
in
Amsterdam,
ahead
of
kubecon
yeah,
Andy
I,
don't
know
if
you
also
want
to
talk
a
little
bit
about
it
and
share
a
little
something,
but.
E
Of
thoughts
around
Cloud
native
rejects,
there's
like
so
much
we'll,
try
and
see
if
we
can
yeah
someday,
maybe
have
something
like
reject
special
and
everything,
and
you
know,
share
all
our
highlights
over
the
years
I'm
fairly
new
to
this.
But
it's
it's
exciting
for
me
too
and
yeah.
E
That's
why
I
think
this
is
the
second
time
this
evening
that
I'm
reiterating
there's
also
information
online
you'll,
find
it
on
on
Kinfolk
handles,
of
course,
and
you'll
find
it
on
the
rejects
handles
too
so
yeah
do
come
by
if
you're
in
Amsterdam
to
Rejects
and
to
well
we'll
see
we'll
see
after
rejects.
But
if
you're,
if
you're
sticking
around
for
kubecon-
and
you
come
a
day
ahead
a
day
earlier
and
everything
just
yeah
come
by
to
reach
reaction.
A
Items
for
everyone
really
basically
check
out,
rejects,
check
out,
julias
and
giant
swarms,
Community,
there's
always
opportunities
and
you're
welcome
to
join
the
next
time
and
then
finally
grab
some
more
pizza.
There's
some
still,
some
pizza
left
and
grab
some
pizza
grab.
Some
T-shirts
grab
some
stickers
and
hang
around
for
a
while.
We
usually
stick
around
for
another
hour
or
so
or
maybe
we
stick
around
until
someone
kicks
us
out
right.
At
least
I
don't
work
here.