►
From YouTube: Panel Discussion Kanchana Wickramasinghe, Eric Newcomer, Murali Paluru, Chamod Shehanka, Kemila De
Description
Sri Lanka has a growing group of Cloud Native enthusiasts, students, professionals, and technology leaders. KCD Sri Lanka offers a platform for this community to come together and connect with other tech communities in India and neighboring countries. It provides an opportunity to experience conferences like KubeCon / CloudNativeCon together with the rich cultural heritage of Sri Lanka.
A
Legislature,
it's
got
to
be
kind
of
exciting
one.
We
have
planned
to
have
a
panel
discussion
with
kanchana.
All
of
you
know
now
who
is
the
main
organizer
VP
and
GMA
wso2
Eric,
who
is
the
CTO
at
wso2,
and
we
have
murali
on
from
data
and
also
here
with
me
to
continue
the
discussion
with
our
panel
I.
Think,
first
of
all,
let's
get
to
know
how
we
started
our
container
plus
kubernetes
Journey.
A
From
my
end,
I
also
joined
a
company
called
platformer
for
my
internship
in
2018,
where
kanchana
was
the
co-founder
and,
as
you
remember,
on
that
day,
I
got
an
opportunity
to
join
the
first
day
of
kubernetes
Sri
Lanka
Meetup
organized
by
a
platform
together
with
kubernetes
community
honestly
I.
Don't
have
idea
about
the
session
that
had
it
on
that
day,
but
I
was
trying
to
understand
by
Googling
and
some
other
space
was
this
kubernetes
and
why
we
need
to
use
it.
A
B
C
When
I
was
hearing
about
your
stories,
actually
I
was
an
undergraduate
I
got
to
know
about
the
topic
kubernetes,
but
I
already
know
about
the
containers
and
docker
when
I
was
working
in
a
group
project.
At
that
time,
I
was
trying
to
troubleshooting
an
app
which
was
working
on
my
laptop,
but
not
working
in
my
friend's
laptop
due
to
a
dependency
issue.
C
D
D
D
E
D
I
think
it
was
kind
of
20
plus
years
ago
start
and
stop,
because
it
was
very
hard
to
use
a
kitchen
respect
in
which
wasn't
really
called
containers
but
yeah,
most
recently
with
the
advancement
of
Docker
and
so
on
and
so
forth.
That
was
kind
of
my
Journeys,
but
over
the
last
seven
eight
years
I
have
seen
significant
Improvement
in
this
and
and
will
continue
to
role.
E
There
were
implications
for
all
software,
and
this
is
why
we
have
Cloud
native
software,
why
we
have
Kafka
instead
of
mq
and
why
we
have
nosql
instead
of
SQL,
because
not
only
Applications
had
to
be
reinvented,
but
the
system
software
as
well,
because
the
different
way
in
which
the
infrastructure
worked
and
the
software
on
top
of
it
to
isolate
the
applications
from
the
consist
constant
failure
of
consumer
grade.
Hardware
Adrian
cockcroft
was
at
the
same
presentation,
I've
known
him
for
for
many
years
as
well,
when
he
was
his
son.
E
I
was
a
digital
and
I
followed
his
journey
to
Netflix
very
closely
and
from
that,
when
I
got
to
City
decided
to
follow.
Netflix
Adrian
came
to
talk
with
us
several
times
and
he
was
the
one
who
told
us
about
doctor
and
he
said
this
has
solved
the
problem
contained
organization.
The
next
big
challenge
is
container
orchestration,
which
turned
out
to
to
be
to
be
kubernetes,
and
during
that
time
I
was
working
primarily
on
service
rights
and
architecture,
designs
and
implementations.
E
First,
at
Credit
Suisse,
where
I
went
after
I,
was
at
Iona
I
hope
they
were
a
big
customer
by
owners
to
help
there
and
then
at
city,
but
I
had
an
interview
with
the
CIO
one
time.
I
did
catch
up
and
he
asked
what
I
was
working
on.
I
told
him
about
SOA
and
managed
Evolution
modernizing
I.T
systems,
and
he
said
I
don't
want
you
to
do
that.
You
might
break
something.
No,
no,
we're
not
going
to
break
anything.
E
That's
what,
but
you
might
so
I'm,
not
sure
you
should
do
that.
So
I
said
well.
What
about
this
stuff
Google
is
doing.
You
know.
Are
you
interested
in
that?
He
said?
Oh,
yes,
that
sounds
really
interesting,
so
he
allowed
me
to
sponsor
a
project
to
redesign
our
payment
processing
systems
using
microservices.
In
the
cloud,
so
we
spent
you
know
several
months
doing
this
and
instead
of
batch
based,
we
had
events
based
microservices
that
we
set
out
to
find
the
implementation.
E
We
had
first
evaluated
Cloud
Foundry,
you
couldn't
get
it
to
work,
then
we
got
openshift
and
that
worked,
and
then
we
started
our
journey
on
that
and
coming
to
wso2
I
found
when
I
spoke
with
sanjiva.
So
just
about
two
years
ago
now
what
he
was
working
on
for
ballerina
and
choreo
in
the
area
of
cloud
native
solves
a
huge
problem
that
we
found
at
city,
which
was
even
if
we
understood
the
benefits
of
getting
Payment
Processing
system
to
the
cloud
to
have
the
scale
up
the
auto
scale
and
scale
down
for
seasonal
workloads.
E
We
had
a
huge
challenge:
understanding
how
to
do
it.
Getting
people
who
understood
the
difference
between
microservice
and
monoliths
and
how
to
recode
them
and
the
stuff
that
we're
working
on
wso2
really
should
help
with
that
in
a
great
great
way.
So
this
is
kind
of
where
I
am
on
that
on
that
journey
and
I
hope.
It's
going
to
have
a
good
good,
ending.
D
F
Part
but
I
would
say:
I
formally
joined
the
band
back
in
in
probably
like
mid-2015.
You
know
when
I
started
looking
at
Docker
and
then
I
joined
the
startup
and
when
trying
to
build
a
container
and
service
platform
and
kind
of
didn't
pan
out
and
I
was
looking
around
and
at
that
time
there
were
not
many
options
right.
Like
now,
Docker.
F
E
A
D
E
Well
sure
I
can
say
what
we
did
at
the
city
while
I
was
there
I
left
about
a
year
and
a
half
ago,
and
before
that
I
was
leading
Cloud
migration.
For
one
of
the
the
divisions
we
had
chosen
openshift
as
kubernetes
on
the
idea
that
this
could
be
used
anywhere.
We
had
a
private
Cloud
internally
built
for
us
by
Dell
and
we
deployed
initially
internally
and
then
we
were
moving
to
AWS.
We
did
a
pilot
for
that.
E
I
did
that
myself
and
we
found
it
was
very
difficult
to
fit
openshift
into
all
of
the
AWS
Cloud
native
services.
So
I
think
the
value
prop
for
the
cloud
providers
to
have
a
managed
hosted
kubernetes
is
that
they
can
integrate
it
with
all
their
monitoring
tools
and
security
and
Reporting
and
Analytics
are
difficult
to
to
handle.
As
we
found
out
when
you're
bringing
a
separate
kubernetes
product
into
into
the
cloud
they
at
the
time
were
not
as
mature
and
in
the
consumer.
Part
of
the
bank.
E
They
were
trying
to
use
eks
from
I,
had
found
a
lot
of
security
challenges,
but
I
believe
they
have
been
working
on
those
the
last
year
and
a
half
or
so,
and
it's
all
most
of
them,
but
I
think
it's
it's
anything
else
for
them.
Part
of
the
value
proposition
of
moving
applications
to
the
cloud
kubernetes
is
the
default
deployment
and
providing
it
as
a.
C
G
D
F
F
E
F
Services
and
to
add
a
kind
of
a
another
Paradigm
is
you
know,
the
ramp
of
time
is
pretty
fast.
If
you're
trying
to
use
managed
services
like
you
know,
you
don't
have
to
deal
with
automation,
you
don't
have
to
train
your
team
to
you,
know
or
expose
them
to
tools
like
you
know,
k3s
or
you
know,
you
know
some
other
tools
like
openshift
or
launcher
right,
so
you
can
just
like
start
and
then
start
running
your
applications.
So
probably
these
are
some
of
the.
F
Is
you
know
if
you
are
a
customer
who
is
trying
to
run
kubernetes
on-prem,
then
pretty
much?
You
don't
have
much
options
there
right,
so
you
would
end
up
going
with
the
you
know:
building
your
own
kubernetes
stack.
So
in
that
case,
even
if
you
expand
your
footprint
to
the
cloud,
you
would
end
up.
You
know
building
your
own
kubernetes
side,
because
it's
kind
of
natural
you
build
the
stack
for
on-prem,
so
you're,
just
extending
it
to
the
cloud
so.
D
I
think,
that's
probably
why
I
think
and
especially
Google
like
on
another
step
ahead.
Isn't
it
like
the
Google
gke
autopilot
they
call
it,
which
is
completely
managed
and
kind
of
serverless
kubernetes
in
in
gcp,
where
you
don't
have
to
even
you
know,
figure
out
how
many
notes
and
things
like
that
you
want
and
they'll
actually
do
that
for
you,
okay,
thank
you
very
much.
Both
of
you
I'll
be
moving
on
to
the
next
question,
or
do
you
want
me
to
ask
the
next
question.
G
B
E
I
I
look
at
this.
Try
to
look
at
this
a
bit
from
first
principles
and
I.
Remember
I
was
attending
a
conference
in
2015.
acpts
in
California
we
had
a
speaker
from
Google.
His
name
was
John
Wilkes
and
he
gave
us
a
talk
about
a
borg
and
he
gave
us
a
demo
of
a
pork,
and
this
is
where
kubernetes
comes
from.
It
was
developed
initially
as
worked
by
Google
and
open
source
to
do
kubernetes
together
with
red
hat
and
some
other
some.
E
I
think,
as
we
know,
the
story
and
his
demo
was
to
show
how
he
could
deploy
10
000
copies
of
a
simple
hello
world
program
in
a
matter
of
seconds
using
using
board
and
I.
Think
what's
very
important
about
kubernetes.
Is
that
it's
it's
solving
a
very
important
problem
in
cloud
computing,
which
is
you
know,
as
he
mentioned,
he
was
showing
these
arrays
of
commodity
service,
which
I
think
you
can
see
if
you
Google.
E
If
you
check
for
Google
data,
centers
or
Azure
data,
centers
or
Amazon
data
centers,
you
see
racks
and
racks
of
consumer
grade
Hardware.
This
is
a
huge
difference
from
how
we
used
to
do
systems
on
Enterprise
grade
mainframes
and
servers
made
for
specific
loads
and
specific
programs
running
on
specific
nodes
and
in
this
environment,
where
you're
running
on
consumer
grade,
Hardware
you're
running
at
very
low
cost,
the
lowest
cost
possible,
but
you
have
a
highest
failure
rate
compared
to
Enterprise
software.
So
what
you
need
to
do
is
to
deliver.
E
I
have
the
lowest
cost
approach
to
it
possible,
but
in
order
to
make
the
low-cost
work,
I
have
to
be
able
to
sustain
the
failure
rates
of
consumer
grade
hardware
and
keep
everything
keeps
going
and
kubernetes
comes
out
of
that
and
becomes
became
the
default
way
to
deploy
your
container-based
microservices.
To
achieve
all
these,
these
benefits
of
cloud
computing
and
I
think
that's
the
key
problem
that
it
solves.
That's
why
it's
becoming
very
popular.
F
D
100
agree:
yeah
I,
think
that
was
one
of
the
biggest
things
that
the
community
send
Google
and
redhead
and
IBM.
The
early
contributors
were
able
to
do
compared
to
Dr
I,
think
Docker
kept
it
to
their
heart
very
close
to
right.
They
didn't
get
a
lot
of
community
involvement
and
so
on
and
so
forth.
I
think
I,
I
kind
of
at
one
point
saw
that
they
were
kind
of
almost
going
to
create
that
as
a
proprietary
thing
for
themselves,
rather
than
you
know,
engage
with
the
community.
We
saw
the
same
thing
happen
with
misos.
D
Misos
was
open
source,
but
they
also
did
not
entertain
a
lot
of
community
right.
I
think
that
was
one
of
the
other
key
things.
The
kubernetes
goes
so
popular
that
the
engagement
with
the
community,
so
it's
really
big
and
while
those
three
were
the
biggest
contributors
back,
then
I
think
a
lot
of
the
others.
There
are
a
lot
of
others
to
actually
contribute.
Now
they
have
kind
of
become
this.
They
are
still
a
significant
contributors,
but
they
are
more,
like
you
know,
less
of
a
contributors
rather
than
the
majority
of
the
other
contributors.
C
Yeah
next
question
from
me:
so
what's
your
perspective
of
using
an
open
source
monitoring
and
login
to
rather
than
going
with
a
subscription
one
for
a
production
environment?
I
know
some
of
the
companies
highly
recommend
to
use
a
stackdrive
elk
stack
and
New
Relic.
Likewise,
some
payable
monitoring
mechanism.
A
A
F
F
Most
of
the
times
you
know,
let's
say:
if
you,
if
you're
a
startup,
you
don't
have
much
time
to
you-
know
build
out
the
the
tech
team
around
you
know,
monitoring.
You
know
build
that
Focus.
You
know
with
that
automation
scale
out
everything
right.
So
what
you
would
do
is
like
you
know.
You
consume
the
readily
available
stacks
and
once
you
beyond
grow
Beyond
a
certain
critical
mass,
then
you
know
you
would
probably
evaluate
okay.
Does
it
make
sense?
You
know
the
cost
to
Value
ratio?
Is
it
still
does
it?
F
Does
it
still
make
sense,
you
know,
does
the
subscription
make
sense
or
would
it
make
sense?
If
we
build
out
our
own
stack,
would
there
be
cost
benefits?
Would
we
have
better
control
on
the
infrastructure
and
things
like
that
right?
So
this
these
decisions
are
kind
of
a
natural
progression,
as
the
teams
evolve
from
small
size
to
bigger
size.
So
it
it's
it's
more
on,
like
the
business
requirements,
I
think
you
know
this,
there's
no
hard
and
fast
rule.
You
know,
depending
on
a
particular
business
needs
or
a
team's
needs.
E
Absolutely
completely
agree,
one
thing,
I
could
add,
is
there's
an
inertia
Factor,
sometimes,
for
example,
at
City
they
were
using
Splunk
very
extensively
and
the
natural
thought
was:
let's
just
keep
using
it.
Even
when
we're
going
to
the
cloud,
it's
sometimes
it's
difficult
to
rethink
the
problem
in
the
context
that
you
just
explained
morally,
which
is
a
sensible
way
to
do
it.
D
D
It
is
also,
at
the
same
time
quite
challenging
to
move
on
to
either
an
open
source
or
another
product
right,
that's
also
in
their
minds.
I
think
the
the
subscription-based
monitoring
and
observability
teams
products
have
become
really
smart
in
terms
of
the
way
they
charge
right
and
and-
and
we
know,
even
Azure
analytics
was
like
driver.
They
charge
for
the
gigabyte
of
data
that
you
actually
push
and
that
can
grow
really
really
rapidly
over
time
with
microservices
right.
D
So
yeah
I
think
the
yeah
closing
on
that
one
I
think
like
morally
and
Eric
said
it's
pretty
hard
to
say
that
whether
you
should
go
on
one
or
the
other,
but
if
it's
a
startup
I
think
it's
it's
kind
of
highly
recommended.
You
know
you
start
with
some
of
the
readily
available
SAS
tools,
rather
than
actually
going
to
try
and
establ
your
own
stack,
because
you
can
actually
with
a
quite
a
lot
of
effort
and
time
and
money.
Also,
actually
getting
resources
to
do
that.
Yeah.
B
E
D
Right
I
think
it's
kind
of
into
two
questions:
isn't
it
so
yeah?
Maybe
maybe
we
should
break
it
up?
I
think
the
first
part
of
the
questions
I
think
shamoto
is
trying
to
ask
whether
the
dominance
of
VMware
will
fade
away
because
Google
and
AWS
and
others
are
coming
into
center
with
their
own
and
those
and
Google
outs
posts
and
Asia.
She
has
tags,
oh
whether
they
will
actually
completely
forget
about
all
that.
That's
the
second
question
and
yes,.
F
F
I
mean
my
thought:
process
is
like
you
know.
Vmware
still
has
a
strong
Hood
in
majority
of
the
Enterprises
right,
so
the
main
reason
is:
it
works
pretty
flawlessly
for
most
of
the
business
use
cases
and
the
reason
why
people
still
use
their
own
infrastructure
is
because
of
the
data
security.
You
know,
I
there
will
be
compliance
reason.
There
will
be
some
other.
You
know
reasons
where
at
a
particular
company
doesn't
want
to
push
out
the
sensitive
data
out
into
the
cloud
right.
So
in
that
case
you
know
VMware
makes
sense.
E
I
I
think
VMware
is
on
the
way
out.
Basically,
it's
going
to
take
a
very,
very
long
time.
That's
where
Ali
said
it's
very
well
established
and
a
lot
of
people
are
still
using
it
and
still
finding
a
value
in
it.
But
the
original
reason
it
was
created
to
virtualize
the
operating
system
in
a
large
Data
Center
and
to
create
virtual
machines
independently
for
applications
and
developers
to
segment
resources,
so
the
operating
system.
This
reason
is
really
not
very
compelling
in
the
industry
anymore,
for
something
like
the
VMware
to
exist.
D
Yeah
I
think
you
both
covered
it
really
really
well
and
I.
I
also
think,
like
both
of
you
said,
we
make
a
very
strong
pothole.
So
it's
going
to
take
a
while
to
you
know
fit
fit
their.
You
know,
increment
I,
guess,
insole
based
I
would
say
we
get
to
see
what
broadcom
will
do,
but
I
don't
I,
don't
think
customers
will
jump
the
ship
just
because
we've
got
required
by
broadcom
right
yeah.
D
G
Yes,
yes,
sorry
so
so
next
question
is
about
managing
complex
application.
So
when
managing
managing
complex
distribution,
application
on
case
is
still
a
challenge,
you
know
so
many
companies
are
coming
with
application:
packaging,
Frameworks
to
name
few
open
application
model,
Dapper
and
most
recently
conlabs.
So
what's
your
thoughts
on
that
actually
sofa.
E
It's
a
it's
a
difficult
question,
because
the
reason
is
we
talked
earlier
about.
The
recent
kubernetes
was
developed
was
to
to
deploy
small
pieces
of
code
onto
small
computers,
hundreds
and
hundreds
of
small
computers
automatically
and
yet
kubernetes
has
no
inherent
restriction
on
running
large
applications
of
large
programs.
It's
very
possible
to
take
a
monolithic,
Java
ee
server
and
run
it
in
a
kubernetes
pod.
E
Given
its
sufficient
resources,
it's
not
the
best
way
to
use
kubernetes
because
it's
not
consistent
with
what
the
problem
with
kubernetes
was
designed
to
to
solve,
but
it
can
be
a
transitional
step,
so
I
think
the
companies
who
are
thinking
of
this
and
we
and
we.
This
is
one
of
the
reasons
that
City
when,
when
I
actually
introduced
openshift
into
City
and
ran
the
initial
roof
of
Concepts
and
did
the
first
applications
on
it
and
one
of
the
reasons
we
chose
it
in
my
division
over
at
Cloud
Foundry,
for
example,
was
Cloud.
E
Foundry
was
much
too
strict
and
12
factors
and
they
they
also
didn't
have
a
capability
to
run
the
data
tier
very
well.
At
that
time,
which
was
2015
I.
Think,
anyway,
it
served
us
better
because
we
had
a
way
to
make
the
transition
in
steps
to
the
microservices
world
that
we
wanted
to
get
to,
but
microservices
being
such
a
different
way
to
compose
and
run
and
manage
applications.
It
requires
some
investment,
some
re-engineering,
and
it's
not
possible
to
do
that.
All
at
once.
E
So
openshift
and
kubernetes
version
of
openshift
sorry
open
shifts
version
of
kubernetes
allowed
that
transition
to
be
taking
place
gradually.
So
I
think
that
there's
some
often
confusion
between
the
fact
you
can
run
something
on
kubernetes
and
that
and
what
you
should
really
be
running
on
kubernetes,
just
because
it
works
doesn't
mean
it's
the
right
thing
to
run
there,
and
it
may
take
some
time
for
that
to
become
apparent
and
for
that
scenario
to.
B
F
You
know
with
the
intention
that
it
would
be
consumed
by
the
end
users
right,
so
you
always
need
some
kind
of
an
abstraction
or
some
kind
of
management
layer
on
top
of
it,
which
would
make
it
easy
to
work
with
the
entire
kubernetes
stack-
and
you
know,
platforms
like
openshift
Rancher
attempted
to
that,
and
they
got
a
lot
of
adoption
and
obviously
the
next
progression
is.
How
do
you
simplify
app
deployment?
How
do
you
compose
the
entire
app
specification?
You
know
people
fell
in
love
with
the
doctor
user
experience
right.
F
It
was
so
simple
if
you
look
at
her
kubernetes
manifest
files
like
no,
nobody
can
other
one
from
scratch
like
now.
If
you
look
at
a
simple
Docker
compost
file,
you
know
you
could
probably
just
hand
write
it
like
a
hand
code.
It
right.
You
can't
do
that,
but
any
of
the
kubernetes
Manifest
file.
You
need
to
copy
paste
or
you
need
to
use
some
kind
of
a
generator,
although
there
are
like
other
wrappers
on
top
of
it.
F
F
Now,
what
what
has
happened
is
kubernetes
has
become
the
defactor
standard,
just
like
Linux
kernel
right,
like
you
know,
this
is
Adopt
a
huge
adoption
and
very
similar
to
what
you
know
how
the
Linux
environment
evolved.
Right,
like
you
know,
I
I,
remember
back
in
my
College
days
you
know
I
used
to
have
like
three
series
of
this
Linux
Linux
distribution
and
getting
it
to
install
just
to
getting
it
to
install
on
my
desktop
was
a
pain
like
you
know.
D
D
E
F
D
E
D
F
D
D
Think
some
of
the
some
of
the
other
tools
are
also
trying
to
do
similar
a
way
of
simplifying
it.
But
yeah.
That's
right!
I
think
you
know
it's
it's
evolving
right!
It's
it's!
It's
not
going
to
it's
I
mean
kubernetes,
I!
Think
any
I
think
we.
When
we
talk
about
it,
we
talk
about
it
like
the
it's.
The
new
Linux
of
the
cloud
right.
E
Standard
like
this
I
think
I
was
also
a
good
comparison
of
the
evolution
of
Linux
at
one
time
was
not
a
standard
operating
system
and
over
time,
once
you
establish
a
standard,
you
can
start
working
above
it
and
start
to
abstract
it,
and
that's
what
we're
seeing
I
think
in
the
marketplace
as
well.
Raleigh
is
a
number
of
companies
now
coming
out.
You
know
ourselves
included
with
the
capability
of
abstracting
across
kubernetes
for
applications
that
are
deployed
on
them.