►
Description
KCD 2022 CZ & SK virtual - Prvá CNCF cloud native konferencia v regióne Čiech a Slovenska. kcd.live
B
All
right,
hopefully,
everyone
is
able
to
see
my
screen
today
without
any
glitches
lucy's
introduced
me
fantastically.
I
didn't
understand
much
of
it,
but
I
could
get
gather
something
from
the
words
that
she
met
I'll
just
quickly.
You
know
start
off,
I'm
extremely
extremely
honored
to
be
presenting
to
you
know.
Y'all
today,
on
this
kubernetes
community
day
check
in
slovak
and
as
lucia
mentioned,
I
am
a
technical
writer
with
susa.
B
Although
lucia
has
introduced
me
pretty
well,
I
think,
because
this
is
the
first
time
I'm
actually
meeting
you
guys.
I
you
know,
I
need
to
be
customary
and
actually
introduce
myself
a
little
bit
better,
so
the
technical
right
of
it
and
the
cncf
ambassador
lucy
has
covered
pretty
well,
I'm
also
the
co-chair
for
cool.
B
Yes,
my
personal,
you
know,
branch
have
been
learning
more
in
the
aws
ecosystem
and
I'm
also
an
author
of
the
friday
phone
newsletter.
We
are,
which
you
know
I
keep
tabs
on
the
high
mind
of
of
the
client
cloud
native,
what
everybody
is
thinking
and
what
are
the
latest
goings
on
in
the
cloud
native
system.
So
please
do
consider
subscribing
if
that's
something
up
your
alley,
but
today
is
not
about
me.
B
B
So
what
problem
did
web
assembly
solve
and
you
know
how
does
it
fit
into
the
cloud
native
ecosystem?
So
this
is
a
very
rough
diagram,
I'm
not
very
good
at
drawing.
I'm
really
sorry
to
all
the
artists
out
there
who'll
get
offended
with
this.
So
you
know
web
assembly
was
in
place
and
for
people
who
have
guessed
that
you
know,
web
assembly
is
related
to
the
browser
you're
not
partially
right
at
this
point.
So
before
this.
B
B
And
this
was
all
good
because
you
know
in
the
early
days
of
the
internet,
we
all
know
what
the
internet
looked
like.
It
was.
It
was
composed
mainly
of
static
pages,
lower
levels
of
interactivity,
lower
levels
of
dynamism,
and
it
was
working
fine
and
when
we
moved
to
you
know
more
dynamic
nature,
a
more
dynamic
nature
of
the
web
with
higher
levels
of
interactivity
is
when
there
started
to
be
a
problem.
B
B
B
B
I'm
very
well
aware
that
this
graph
only
shows
till
2019,
and
this
is
the
best
graph
that
I
could
find,
because
after
2019
there
is
a
lot
that
comes
in
in
terms
of
you
know,
advancements
in
this
space,
which
we
shall
talk
about
in
the
next
couple
of
slides,
but
coming
back,
we
are
still
in
early
2000s.
We
have
like
only
javascript
as
a
for
the
web.
B
We
want
alternatives,
because
we
are
always
on
the
search
of
alternatives
right
as
an
industry.
So,
with
respect
to
you,
know
javascript
what
came
up
as
alternatives
in
the
very
first
place
were
plugins
and
we
all
know
how
that
went
down.
Adobe
sorry,
flash
pi,
adobe,
silver
light.
All
those
plugins
were
really
mainstream.
B
B
It
was
what
javascript
tried
to
do
as
well,
but
it
did
not
fail.
I
mean
it
did
not
succeed
as
well
as
we
thought
it
would
so.
Llvm
was
released
in
around
2003
with
the
aim
of
bringing
more
languages
to
the
front
end.
Now
as
time
passed
around
2011,
there
were
two
major
events
that
sort
of
brought
us
closer
to
the
web
assembly
spec,
which
was
the
release
or
the
announcement
of
the
mccrypton
project
and
the
portable
native
client
project.
B
Now
both
these
projects
were
introduced
with
the
same
aim
of
bringing
c
and
c
plus
plus
to
the
front
end,
but
both
of
them
were
disjointed
efforts.
They
were
started
by
two
separate
organizations
and
building
upon
the
m
script
and
project
in
2013
was
the
asm.jspec
now
asm.jspec,
as
you
pro
from
itself,
is
a
structure
subscript
constrictor
subset
sorry
of
the
javascript
programming
language.
What
does
this
mean?
So
the
step
pretty
much
remains
the
same.
Your
end
goal
is
still
going
to
be
javascript,
wherein
you
know
it.
B
Everything
compiles
to
javascript,
but
the
asm.js
had
a
strictest
set
of
rules
on
what
it
would
allow
and
not
allow.
So,
for
example,
it
allowed
only
simple
constructs
and
it
did
not
allow
any
of
the
fancy
memory
management
techniques
that
javascript
and
javascript
as
a
programming.
Language
was
known
for
now,
because
all
of
these
efforts,
accepting
probably
the
one
that
I'm
going
to
talk
about,
were
disjointed
once
meaning
they
were
worked
upon
by
really
separate
people.
B
B
Now
we've
talked
about
how
we
reached
web
assembly
from
you
know
javascript,
but
we
still
haven't
looked
at
what
webassembly
is
so
abbreviated
as
w
capital
and
asm
small.
This
is
something
that
I
learned
recently
as
well.
It
is
a
binary
instruction
format
and
it
borrows
from
the
stack
based
virtual
machine
concept
that
you
know
the
native
client
project
had
sort
of
introduced.
B
Now
it
is
designed
to
be
a
compilation
target
which
means
that,
as
opposed
to
javascript,
you
know
it
is
a
little
more
efficient.
So
to
say,
and
it
because
of
the
binary
instruction
format,
it
is
also
sort
of
cpu
architectures
and
can
be
used
on
both
the
client
and
server
applications
so
in
between
2017
and
today,
although
the
is
only
up
to
2019.
B
B
Day-To-Day
applications
are
also
going
to
leverage
the
efficiency
and
speed
of
the
web
assembly
specification,
but
we're
getting
a
little
too
ahead
of
ourselves
at
this
time,
because
I
yet
have
to
cover
how
is
it
different
from
javascript,
because
as
of
right
now,
with
what
I've
explained,
web
assembly
doesn't
seem
like
something
that
is,
you
know
novel,
because
it's
just
replacing
that
block
in
that
diagram
that
I
showed
a
couple
of
slides
back
wherein
you
have
instead
of
javascript,
you
have
web
webassembly.
So
how
is
that
different?
B
So
for
that?
I've
actually
come
up
with
another
diagram
and
it's
equally
bad
badly
drawn
as
as
was
the
previous
one.
So
javascript
and
web
assembly
differ
on
a
lot
of
counts.
This
is
one
of
the
very
first.
You
know
examples
of
that.
The
web
assembly
is
spec
or
a
code
that
is
compiled
to
web
assembly
basically
doesn't
go
through
a
lot
of
steps.
Given
that
you
know
the
web
assembly
spec
itself
is
in
the
binary
instruction
format.
B
The
compiled
code
that
you
will
get
at
the
end
of
compilation
would
be
a
binary
instruction
for
format.
So,
there's
not
going
to
be
a
lot
of
fancy
memory
management
stuff
like
garbage
collection,
although
it
is
in
the
proposal
for
inclusion
in
subsequent
versions,
but
as
of
version
one.
There
are
no
fancy
memory
management,
automations
like
garbage
collection,
and
given
that
the
you
know
it's
it's
the
binary
instruction
format.
The
actual
process
of
execution
for
a
web
assembly
code
is
significantly
lesser.
B
B
If
you
know
if
the
program
can
actually
interact
directly
with
the
memory,
how
you
know
do
you
prevent
a
malicious
actor
from
gaining
access
to
it,
so
the
web
assembly
spec,
has
actually
taken
care
of
that
as
well.
Now,
in
the
web
assembly
specification,
what
has
been
written
down
as
the
structure
of
a
web
assembly
program
is
that
the
program
is
a
bunch
of
modules.
B
B
A
B
Is
declared
as
a
bunch
of
offsets
and
if
the
program
tries
to
access
anything
else
other
than
the
memory
that
it's
allotted,
the
module
actually
tries
to
allow
access
anything
else
other
than
the
memory
it's
allotted
it
doesn't
allow
it
to.
That
is,
like
definition,
within
the
specs,
so
so
suppose,
a
malicious
actor
is
code
and
it's
trying
to
access
another
modules
memory.
B
It
will
not
allow
for
that
to
happen.
Webassembly
allows
for
every
module
to
access
only
its
own
linear
memory
and
does
it
the
module
will
not
have
access
to
the
entire
process
memory.
Unlike
other
programming
languages,
of
course,
you
know
mod.
The
modules
are
able
to
share
memory,
I'm
not
going
to
say
that
it's
completely
impossible,
but
it
requires
explicit
calls
to
be
made
and
the
risk
of
that
malicious
actor.
Attacking
your
core
and
gaining
access
to
your
process.
Memory
is
significantly
lower
as
compared
to
other
programming
languages.
B
Now,
when
we
speak
up
when
I
spoke
about
these
different
sections,
I
also
mentioned
that
they
had
to
be
arranged
in
a
particular
way
right.
So
because
of
that
particular
sequence,
what
happens?
Is
that
the
speed
and
efficiency
and
the
performance,
you
know
drawbacks
that
we
had
with
javascript
sort
of
you
know
gets
conquered,
because
what
happens-
and
this
is
something
that
you
don't
even
have
to
explicitly
do
when
you
are
writing
a
code
into
something
that
can
compile
to
web
assembly.
B
B
Many
more
languages
are
actually
coming
and
coming
forward
with
compilers
for
web
assembly
and,
for
example,
even
python,
so
the
this
is.
These
are
like
some
of
the
advantages
and
how
it
differs
when
it
comes
to
javascript,
and
when
we
talk
about
all
this,
we
also
need
to
understand
before
we
talk
about
the
intersection
with
the
cloud
data
system
where
the
webassembly
ecosystem
is
currently
because
till
now,
what
I
have
said
is
javascript
javascript.
How
is
it
different
from
javascript?
B
So
if
you
think
that
you
know
it's
just
the
front
end,
it's
not
just
the
front
end
any
longer.
Everyone's
favorite
chat
server.
These
days,
discord
basically
uses
web
assembly
modules
as
well
over
and
about
what
is
displayed
here
on
the
screen.
Right
now,
if
we
talk
about
photoshop
by
adobe,
it's
one
of
the
biggest
you
know
adopters
of
web
assembly
as
an
enterprise
there's
also
the
google
earth
google
meet
figma.
B
So
that's
that's
a
bit
about
where
we
are
currently
with
respect
to
the
webassembly
ecosystem,
but
when
we
look
at
how
it
intersects
with
the
cloud
native
ecosystem,
the
cloud
native
ecosystem
is,
as
it
is,
humongous
right
now.
If
I'm
asking
you
to
check
out
what
is
there
on
your
screen,
you
will
not
even
be
able
to
see
half
of
the
cards
on
it,
the
reason
being
it's
it's
just
you
know
growing
out
of
at
the
fastest
pace
possible.
B
Right
now,
where
we
are
currently
is,
we
do
not
very
much
worry
about
the
operating
system
or
where,
where
we
are
deploying
our
particular
applications.
Sure
a
lot
of
us
are
still
you
know
doing
a
mix
of
cloud
native
and
traditional
on-prem,
I'm
not
going
to
say
that
we've
completely
switched
to
cloud
native,
but
when
we
speak
about
the
traditional
premise
of
having
your
own
data
center,
knowing
which
os
and
which
computer
or
which
server
and
what
libraries
and
what
specific
programming
languages
we're
using.
B
We
have
come
a
long
way
from
that
tightly,
covered
architecture
and
with
the
current
premise
of
cloud
native,
we
are
looking
at
distributed
applications
and
where
web
assembly
fits
in
into
the
cloud
native
paradigm
is
that
it
offers
that
additional
layer
of
abstraction.
So
if
you
see
in
this
particular
diagram,
what
cloud
native
is
currently
doing?
I
mean
not
currently
doing.
What
it
has
been
doing
is
that
we
just
have
to
worry
about
the
application,
specific
libraries
and
the
actual
app
that
we
with
webassembly.
B
What
tends
to
happen
is
that,
since
we
just
are
going
to
have
a
binary
instruction
format,
to
which
our
actual
you
know,
application
compiles
to
this
could
virtually
be
run
anywhere
and
by
anywhere
I
literally
don't
mean
run
it
anywhere.
You
could
have
it
run
on
the
edge
you
could
have
it
run
inside
a
k8
container.
You
could
have
it
run
on
a
browser
you
could
have
it
run
on
devices
such
as
raspberry
pi.
B
What
are
all
these?
You
know
web
assembly
applications
and
what
is
that
assembly?
It
brings
us
to
this,
which
are
the
cloud
native
projects
currently
using
or
supporting
wasn't.
This
is
again
not
an
exhaustive
list,
because
cloud
native
projects
using
or
supporting
boston
are
pretty.
You
know
it's
it's
it's
like
keeping
track
of
on
ever
an
ever
expanding
landscape.
B
So
why,
at
this
point,
are
we
using
web
assembly
it's
because
of
its
binary
instruction
format?
The
speed
is
actually
at
this
point,
not
as
important
as
the
fact
that
the
policies
that
we
write
for
dynamic
admission
control
can
be
written
in
any
programming
language
that
can
compile
the
web
assembly.
So
for
policy
writing
you
basically
do
not
need
to
rely
on
a
new
language.
B
There
are
very
few
languages
supported
today,
I'm
not
going
to
say
that
we've
increased
support
for
every
conceivable
language
in
the
ecosystem,
but
as
and
when
you
know
the
ecosystem
of
web
assembly
develops
is
when
we
will
see
a
subsequent
development
in
these
projects,
for
example,
even
even
in
one
of
the
projects.
That
is
not
really
cloud
native.
B
B
You
know
pretty
amazing
at
this
point,
so
solomon
heights,
who
was
who
is
the
founder
of
docker
and
the
creator,
so
he
mentioned
that
how
important
web
assembly
would
have
been
had
it
been
in
2008
can
be
sort
of
attributed
to
the
fact
that
if
web
assembly,
along
with
the
wasee
specification,
which
is
a
specification
for
network
interface
modules,
if
that
had
existed
in
2008,
they
wouldn't
have
had
to
create
docker
because
docker.
What
it
essentially
does
is
provide
that
between
your
operating
system
and
your
application.
B
So
docker
does
that
with
the
help
of
containerization.
So
with
wasm
and
wazi,
we
eliminate
that
last
layer
of
abstraction,
but,
like
I
talked
about
in
the
previous,
I
mean
in
one
of
the
previous
slides.
It
basically
eliminates
that
last
level
of
abstraction
and
creates
a
standardized
system
interface,
which
was
the
missing
link,
and
this
was
this.
Tweet
was
still
there
on
twitter
if
you're
gonna
go
check
it
out,
and
it
was
on
the
announcement
of
wazi
that
basically
solomon
heights
said
this.
B
B
B
So
it's
not
replacing
javascript
and
javascript
is
not,
unfortunately,
going
anywhere
for
those
who
are
hoping
that,
but
that,
aside
what
you
know,
what
is
you
know
the
future
of
cloud
native
so
gartner,
which
is
one
of
the
leading
analyst
publications
in
the
ib
industry?
It
has
postulated
that
by
2025,
which
is
just
like
three
years
ahead.
B
B
So
if
you
look
at
that
meteoric
rise,
you
can
already
imagine
the
kind
of
you
know.
You
can
already
visualize
the
how
the
landscape
is
going
to
look.
It's
going
to
have
way
more
many
tools,
it's
going
to
have
way
more
many
certified
providers
and-
and
it
definitely
is
going
to
have
web
assembly
as
a
part
of
it.
It
already
has
it
as
of
today.
B
B
B
It's
one
of
the
you
know,
goals
to
bring
compute
closer
to
edge
and
with
that
obviously,
the
number
of
cpu
architectures
that
we
sort
of
support
are
going
to
diversify
and
web
assembly,
given
its
binary
instruction.
Format
is
a
perfect
candidate
to
fit
in
into
this
requirement,
and
that
is
where
you
know
I
actually
see
web
assembly
going.
Given
that
you
know
we
already
have
a
lot
of
these
initiatives
underway.
B
If
anybody
want
to
tell
you
that
we
would
have
distributed
logging
and
chasing
systems
or
if
anybody
were
to
tell
you,
we
would
have
you
know
stuff
like
years
engineering
in
place,
would
you
have
believed
them
because
I
sure
would
have
not,
given
that
a
I
was.
I
was
in
college
at
that
point
in
time.
The
second
thing
is
what
what
I
was
you
know
introduced
to
when
I
entered
the
industry
in
2012
was
just
plain
vlogging
and
chasing
no
fancy.
Friends.
B
Nothing
great
in
terms
of
you
know:
visualization
tools,
just
the
basics,
plunk
and
wiley
and
apm
infrastructure,
but
when
containerization
came
in
it
reimagined
the
whole
way
we
look
at
observability
and
the
kind
of
stuff
we
had
right.
We
have
right
now.
We,
I
don't
think
we
could
have
imagined
that
back
when
we
did
not
have
containerization.
B
Similarly,
with
security,
security
is
everyone's
favorite
buzzword
these
days,
especially
supply
chain
security,
and
it
should
be
given
that
you
know
the
number
of
attack
vectors.
Given
the
number
of
you
know:
malicious
actors
in
this
space,
reimagining
security
when
it
comes
to
web
as
the
web
assembly,
is
going
to
be
equally
important
because
there
will
forever
be
newer
attack
vectors
coming
up,
even
though
you
know,
webassembly
is
relatively
secure
as
of
now,
but
with
technological
progression
and
with
advancements.
B
You
know
it's
not
like
hackers
are
reading
1990s
books,
they
are
going
to
keep
themselves
updated
and
there
are
always
going
to
be
newer
attack
vectors,
so
reimagining
security
paradigms
there
is
going
to
be
another.
You
know
I
think
direction
in
which
web
assembly
will
branch
out
and,
of
course,
like
I
said
before,
edge
and
iot,
are
you
know
another
set
of
buzzwords
that
have
been
you
know
floating
around
since
a
lot
of
time
we
finally
might
actually
be
able
to
bring.
B
You
know
the
edge
and
compute
closer
for
specifically
iot
use
cases,
given
that
you
know
there
is
an
increasing
requirement.
Sorry
there's
an
increasing
requirement
for
you
know
a
language
or
a
specification,
or
even
like
that
standardized
system.
Interface
to
do
the
you
know
do
that
bridging
of
the
gap-
if
I
can
say,
put
it
in
the
most
crude
way-
and
I
mentioned
databases
here
and
there's
already.
A
B
Of
work
underway
in
this,
for
you
know,
implementing
udfs
in
the
web
assembly
context
a
quick
google
search.
Can
you
know
literally
give
you
three
four
pages
of
valuable
information,
and
I
don't
think
you
know
I.
I
want
to
go
too
much
into
depth,
but
adding
that
extra
level
of
isolation
and
security
when
it
comes
to
the
humongous
amount
of
data
that
we
produce.
I
think
that
is
another
interesting
direction
where
I
see
web
assembly
sort
of
branching
out
is
the
database
side
of
things
as
well.
B
B
We
are
looking
at
more,
you
know,
more
applications
that
can
run
on
diverse
architectures
and
that
help
developers
focus
on
the
actual
coding
and
development
aspect
rather
than
you
know,
reimagining
their
applications
for
different
environments,
and
with
that
I
think
I
you
know,
want
to
open
up
the
floor
for
any
questions
that
you
might
have
and
before
that
I
would
like
to
really
thank
the
organizers
as
well
as
all
the
lovely
audience
that's
attending
today
for
their
time
and
patience.
Thank
you
so
much
and
have
a
fantastic
day.