►
From YouTube: Create Your First CNCF Serverless Workflow Project with Kogito and Kna... Ricardo Zanini Fernandes
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Create Your First CNCF Serverless Workflow Project with Kogito and Knative - Ricardo Zanini Fernandes, Red Hat
Serverless Workflow is a declarative workflow specification at CNCF for describing service orchestrations. Kogito is an open-source project by Red Hat and implements the Serverless Workflow Specification. In this session, you will learn in a live demo how to create your first CNFC Serverless Workflow project from the ground up with Kogito and how to deploy it on the Knative platform. Kogito is a developer-centric platform that can execute, test, and deploy workflows on Knative environments. The outcome is a REST microservice that can orchestrate other services and events. It is a perfect fit for an Event-Driven architecture and can integrate with Knative Eventing resources to solve complex business use cases. Kogito handles all the heavy lifting when deploying on Kubernetes by generating the resources necessary to deploy on Knative. After this session, you will be able to create a CNCF Serverless Workflow project, test it, and deploy it on Knative to be part of your architecture.
A
The
first
one,
the
cncf
service,
workflow
specification,
our
implementation,
red
hat.
What
we're
doing
for
that
spec
and
a
little
bit
of
demonstrations
use
cases
and,
as
promised
in
the
description
of
this
talk
by
the
end,
hopefully
you
guys
will
be
met
will
be
able
to
create
your
own
workflow
project
using
this
technology
right.
A
Okay,
first
thing
about
the
spec
itself:
this
is
a
cncf
sandbox
project
for
quite
some
time
we're
working
towards
incubation
right
now
it
is
a
a
dsl
to
describe
workflows.
So
we
are
working
through
this
to
be
a
vendor
neutral
specification
to
describe
workflow
so
any
kind
of
technology
or
implementation
on
projects
out
there
being
you
know,
open
source
or
not,
can
use
this
pack.
You
know
all
the
the
workflows
descriptors,
the
parts
of
the
specification
to
do
the
all
the
implementation
in
your
site.
A
A
So
it
is
like
open
api
jrpc,
all
those
kinds
of
things,
all
those
kind
of
things
it
is
related
to
the
spec
as
well.
I'm
gonna
explain
that
a
little
bit
more
and,
of
course,
there's
a
lot
of
projects
and
companies
already
helping
us
there
in
the
in
the
in
this
back
side,
and
we
are
of
course
working
looking
for
contributors.
So
if
you're
interested
in
workflows
or
if
your
company
is
somewhat
interested
in
workflow,
it
would
be
nice
to
have
you
there.
A
A
Everything
is,
you
know,
open
to
talk,
so
it
is
a
very
well
welcome
and
warm
community
so
go
there,
and
if
you
scan
the
qr
code
you're
going
to
the
surveillance
workflow.io
there's
all
the
information
is
there.
We
also
have
a
slack
channel
at
the
cncf
like
so
you
go
for
servlets
workflow
and
we
have
a
channel
there.
We
can
connect
and
talk,
and
you
can
ping
me
offline
if
you
want
okay,
let's
talk
about
a
bit
a
bit
more
about
the
specification
itself,
so
it
is
based
on
standards.
A
Like
I
said,
the
first
thing
is
cloud
event,
so
a
workflow
running
on
serverless
infrastructure
is
supposed
to
have.
You
know:
support
for
events,
support
for
cloud
events,
of
course,
because
we
are
tied
to
that
specification
as
well.
Well,
so
any
we
choose
cloud
events
because
of
obvious
reasons:
it's
like
a
standard.
It
is
open,
it's
not
within
cncf
as
well
and
has
a
way
to
structure
your
events
and
for
workflows.
That
would
be
super
in
handy
because
you
can
use
events
to
start
a
workflow.
A
You
can
produce
a
workflow
from
now
from
you
can
produce
an
event
from
a
workflow.
You
can
consume
an
event
from
the
workflow,
so
it
is
pretty
handy.
I
will
show
you
a
little
bit
more
about
that
in
a
minute
also
to
connect
to
other
services.
You
know
like
we
have
a
workflow,
you
need
to
compose
other
services.
You
usually
have
to
connect
to
external
services.
A
So
for
that
you
can
have
open
api
specification
to
connect
with
your
workflow
to
describe
your
service
and
methods
that
you
want
to
call,
and
you
use
open,
api's
specification
to
that
as
well.
Async,
api,
jrpc
and
graphql.
All
of
them
are
supported
by
specs,
so
you
can
describe
your
functions
within
the
workflow
using
all
those
standards
and
of
course
we
have
workflow
patterns
like
control
flow
for
execution
order,
error,
handling
data
management,
data,
filtering
data
transformation.
A
We
have
an
expression
link,
not
we
don't
have
an
expression
language
itself,
but
we
do
support
jq
and
jsonpath.
So,
while
you're
running
your
workflow
and
imagine
that
you're
composing
with
other
servers,
you
are
calling
other
servers
and
orchestrating
your
services.
Sometimes
you
need
to
change
the
the
payload
or
you
need
to
change
the
the
json
that
you're
receiving
or
doing
anything
with
the
data
itself,
so
you
can
use
gqueue
or
jsonpath
within
the
workflow
runtime
to
change
the
data.
A
A
So
there
you
describe
how
you're
going
to
call
those
functions
and
how
that
functions
should
look
like
the
arguments,
inputs,
authentication
and
and
other
things
events,
so
you
can
describe
which
event
that
you
are
you're,
producing
or
or
which
event
you
are
consuming
within
the
workflow
via
the
events,
payload,
sorry,
the
event,
definitions
and
then
the
the
last
but
not
least,
states
they're
going
to
describe,
of
course,
the
states
of
your
workflow
right.
So
this
is
basically
the
backbone.
A
The
the
the
fundamental
structure
of
the
our
workflow
based
on
the
service
workflow
specification,
there's
a
lot
of
more
much
more
things.
But
in
a
nutshell,
that's
how
you
describe
a
workflow,
so
you
can
use
either
json
or
email
files
to
describe
you
support
both
and
you
can
go
to
the
serverless.io
and
we
have
like
there,
of
course,
the
specification
itself
that
describes
everything
in
detail
and
how
you're
supposed
to
manage
all
of
that.
Okay.
A
So
let's
move
forward
on
that
and
now
speaking
about
the
project
that
I'm
also
involved
with,
that
is
the
implementation
of
the
specification.
So
we
have
this
work
on
cncf
working
with
the
specification,
which
is
super
nice.
There's
a
lot
of
people,
a
lot
of
companies
helping
us
there,
but
also
to
engage
with
the
specifications
to
have
something
we
need
an
implementation.
Of
course,
implementation
is
a
runtime
that
is
capable
to
run
the
workflow
definitions
that
you
that
you
have
defined
before
you
know
you
know
json
or
gamma
file.
A
A
So
we
are
leading
a
path
you
know
within
the
within
company
to
to
bring
that
to
the
product.
Unfortunately,
I
can't
disclose
anything
about
that,
but
yeah.
It
is
like
a
a
project
based
on
kubernetes
and
canadian.
That
is
the
our
idea
of
infrastructure
in
the
cloud.
So,
for
obvious
reasons,
k
native
would
be
our
you
know
chosen
in
serverless
infrastructure
to
build
on
top
of,
and
I
don't
know
who
knows,
quarkus
just
raise
your
hand,
okay,
nice
well
quarks
is.
A
It
is
a
framework
for
java
applications,
so
you
can
create
your
java
applications.
Usually
in
the
past,
people
use,
don't
know
springboard,
jboss,
there's
a
lot
of
a
lot
of
tooling
there.
Now
red
hat's
talking
about
quarkus
quarkus,
it
is
a
a
java
framework.
That's
focused
on
cloud
native
applications
for
us
would
make
a
lot
of
sense
to
be
on
top
of
quercus
our
platform,
because
our
language
of
choose
was
java
and
the
the
runtime
offered
a
lot
of
things
among
like
extensions.
So
in
these
extensions
we
have
authentication
persistence.
A
You
know
network
a
lot
of
things
that
we
decided
would
be
a
nice
addition
to
the
project
as
well,
and,
of
course,
on
top
of
that
we
have
the
engine
itself
that
parse
the
workflow.
That
runs
the
work
for
the
have
the
definition,
and
we
have
advanced
that
you
can
have
well
for
this
workflow.
I
wish
to
persist
on
postgres
database,
or
I
wish
first
my
workflows
instance
and
on
a
mongodb
whatever
or
I
need
to
engage
with
kafka
or
any
other
broker
technology.
A
So
in
this
case
we
have
a
dom
that
you
can
like
create
and
your
application
your
workflow
application
mount
like
a
puzzle.
You
know
with
building
blocks
of
all
those
technology,
so
you
can
deploy
your
application
in
the
serverless
platform
all
right.
So
this
is
super
nice.
I
will
with
this
just
just
talking
right,
so
it
is
nice
to
start
in
doing
some
demonstrations
and
what
we
can
do
with
this
technology
that
we
have
now
in
this
care
code.
You
can,
you
can
scan
and
save
for
later.
A
A
So
imagine
that
you
have
this
unused
case
of
a
newsletter
subscription.
So
someone
enters
in
your
enters
in
your
website
or
you
know
your
your
platform
and
wish
to
subscribe
to
a
new
your
newsletter
or
something
that
you
have
there.
So
the
next
step
is
like.
Well,
let's
verify.
If
this
mayo
is,
you
know,
okay,
this
exists
in
our
database
or
not.
A
We
subscribe
and
we
send
an
email
to
the
person
that
subscribed
to
the
to
the
newsletter
or
whatever,
and
we
wait
for
that
verification,
because
someone
could
have
your
email
and
go
there
and
subscribe
for
you
and
you
start
receiving
spam,
and
you
don't
like
it.
So
it
is
nice
to
have
a
way
to
verify
the
person
that
sends
that
email.
It
is
that
person
in
that.
In
that
part,
the
workflow
should
what
out
and
wait
for
the
verification
itself
for
the
person
that
subscribed
to
say,
hey
yeah.
A
I
I
did
that
subscription
and
I
wish
to
have
that
newsletter
in
my
in
mailbox
and
in
the
end,
after
receiving
a
verification,
we
can
broadcast
this
new
subscription
into
the
platform.
What
that
means.
Well,
we
can
produce
a
cloud
event
within
the
platform
and
other
you
know:
stakeholders,
actors,
other
services,
brokers,
whatever
can
listen
to
that
and
act
upon
that
event
and
do
a
new
thing.
Imagine
I
don't
know
maybe
broadcast
into
your
marketing
team
and
say:
hey.
We
just
received
a
new
subscription.
A
Why
not
send
you
know
a
welcome
email
for
them?
Something
like
that.
So
this
is
a,
I
believe,
a
simple
use
case
that
people
can
you
know,
understand
and
how
that
could
be,
how
we
could
leverage
our
workflow
technology
to
implement
this.
So
imagine
now
that
we
have
this
service
that
has
our
subscription
database.
So
it
is
a
rest
service
in
your
platform
and
you
need
to
interact
with
that
service
and
then
need
to
call
that
service.
You
say
hey
I
wish
to
I
wish
to
subscribe
in
a
new
person.
A
A
This
is
the
infrastructure
that
I
come
up
with.
You
know
like
I
described
the
coach.
The
project
is
like
building
blocks
with
based
on
quarkx
kubernetes,
k
native.
So
we
give
you
the
tools
for
this
first
iteration
of
the
project.
This
is
more
focused
on
developers.
So
if
we
give
you
the
tools,
so
you
can
you're
capable
to
implement
something
like
this,
and
in
this
case
you
have
like
us,
I
receive
a
new
request
of
a
new
subscription.
A
A
So
in
my
workflow
we
make
you
know,
requests
to
the
subscription
service.
So
how
can
we
do
that?
For
this
demo?
We
are
using
the
open
api
definition,
so
we
can
call
that
service.
The
service
has
their
own
database.
You
know
do
all
their
stuff
there
and
our
workflow
will
house
the
execution
and
waiting
for
a
confirmation
emails
as
soon
as
the
people
click
on
the
confirmation
email.
We
come
up
with
ko
21
in
the
canada
platform
and
we
resume
the
execution
and
the
the
final
subscription.
A
So
let
me
show
you
this
application
running
all
right.
So
this
is
the
front
end
of
our
subscription
application.
It's
just
a
demo.
Please
don't
take
that
they
take
that
with
a
grain
of
salt
in
the
qr
code
that
I
showed
you
in
a
couple
of
slides
ago.
You've
you
have
the
the
link
for
the
github
project
that
has
you
know
all
these
services
in
there,
the
description
and
everything
else
I
will.
You
can
take
a
look
later
if
you're
interested
and
let's
get
back
to
the
application
all
right.
A
So
if
we
go
in
our
kubernetes
instance,
we
don't
have
any
pods
in
this
namespace.
We
have
only
the
postgres
database.
That
is
the
technology
that
we
are
using
to.
You
know
persist.
Our
information
persist,
all
these
subscription
things
and
workflow
executions,
etc,
and
as
soon
as
they
like
create
a
new
subscription.
A
All
right,
I
supposed
to
add
a
loading
screen,
but
when
I
do
the
first
request
my
paul
starts
working.
You
know
we
scale
to
one,
because
we
need
that
service,
the
workflow
to
start
execution,
the
execution
and
wait
for
the
confirmation
to
be
done.
So
we
can
resume
the
the
the
the
execution
of
the
workflow.
A
So
we
can
wait
a
couple
minutes
a
couple
of
seconds
and
you
see
that
all
the
pods
will
just
you
know,
be
escaped
to
zero
because
we
are
using
the
serverless
infrastructure
technology
and
I
don't
know
if
you
guys
were
yesterday
in
the
canada.com,
but
we
had
a
lot
of
great
talks.
One
of
them
was
about
code
starts.
So
that's
why
you
know
I
didn't
do
all
the
the
things
that
I
supposed
to
do.
You
know
like
caching,
the
image
or
things
that
would
be
able
to.
A
A
All
right,
so
this
is
a
java
project.
I'm
gonna
explain
to
you
guys
in
a
few
moments
how
you
create
your
own,
but
yeah.
This
is
a
just
a
regular
json
resource
file
within
my
project.
That
is
the
description
of
my
workflow.
So
in
the
first
part
we
have
the
events
here
we
have
two
events,
one
that
I
can
produce
and
one
that
I
can
consume
the
one
that
I
can
produce.
It
is
described
like
well
as
soon
as
I
end
the
workflow.
A
I
will
create
a
new
subscription
event
and
I
have
one
that
I
can
consume.
That
is
the
confirm.
The
the
subscription
confirmation
event
and
also
this
is
the
description
of
my
functions
so
my
functions-
they
all
are
all
based
on
open
api
specifications,
so
they
within
my
project,
I
have
a
emo
file.
You
know
describing
my
open
api
and
in
the
end,
after
the
hashtag,
you
can
see
the
method
name
of
that
openapp
spec
this
file
for
demo.
A
So
json
is
a
little
bit
odd.
You
know
to
see.
So,
let's
take
a
look
into
the
image
itself.
I
think
it
is
easier
to
understand
this
is
based
on
an
editor
that
we
are
currently
working
on
that
you
can
now.
Just
you
can
type
your
workflow.
We
have
intel
sense
and,
in
the
other
hand,
of
dvs
code
you
can
see
the
the
workflow
being
created.
A
I'm
gonna
show
you
in
a
couple
of
minutes,
so
the
first
thing
is
like
well,
we
received
the
request
with
verified
images,
is
valid
or
not,
and
and
if
x
is
in
our
database
and
if
it
exists,
we
just
finished
the
workflow
there's
nothing
to
do.
We
just
received
something
someone,
that's
already
subscribed
and
that's
it
and
on
the
other
hand,
if
we
don't
have
this
this
email
on
our
database,
we
subscribe.
A
We
insert
this
this
this
this
information
in
our
data
in
database
or
we
call
this
the
service.
We
call
the
the
subscription
server
and
say
hey:
this
is
a
new
subscription,
save
it
and
we
hot
we
stop.
This
is
a
callback
type
of
state.
So
we
stop.
We
hot,
like
I
showed
you
in
the
demo
and
let's
see
we
don't
have
any
pause
anymore
and
I'm
going
to
confirm
my
subscription
as
we
confirm
our
subscription.
A
This
person
is
now
subscribed
to
our
newsletter
and
by
the
end
of
the
workflow,
we
produce
a
new
new
event
and
let's
see
that
how
that
worked,
you
know
we
have
both
services,
the
the
workflow
service
and
the
service
that
we
just
called-
and
I
have
this-
I
don't
know
if
you
can
see-
I
don't
think
so
yeah.
This
is
just
a
a
way
to
display
to
consume
the
event
that
we
just
published.
A
A
Okay,
all
right,
we
have
like
10
minutes
and
I
would
like
to
you
know
fulfill
my
promise
that
I
have
in
this
in
the
description
of
the
of
the
talk.
I
hopefully
you
guys
are
waiting
for
that
or
not
I
don't
know,
but
yeah.
Let's
try
to
do
that
together,
you
don't
need
a
laptop
or
anything.
I
will
do
everything
here.
A
This
is
how
we're
going
to
create
our
first
workflow,
so
you
can,
you
know,
try
technology
understand
what
it
is
play
around
with
that,
even
though
you
don't
know
java,
you
don't
need
to
know
java.
You
just
need
to
you
know
play
around
with
the
with
the
with
those
tooling.
This
is
the
like.
I
said
this
is
the
first
iteration
of
the
project,
so
in
this
first
iteration
we
are
aiming
for
java
developers
much
of
the
but
developers
in
general.
A
That
can,
you
know,
use
this
technology
to
be
their
own
workflows,
but
in
the
future
that
we
are
just
planning,
you
don't
need,
you
know
to
know
any
kind
of
underneath
technology
whatsoever
is
it.
I
will
show
you
guys,
a
poc
that
we
are
preparing,
so
how
you
can
leverage
workflows
without
knowing
this
technology,
just
you
know,
drag
and
drop.
You
know
the
the
the
boxes
of
the
states
of
the
workflows,
describing
your
functions,
assessing
service
hazardry
to
retrieve
your
functions.
A
To
call
to
do
you
know
a
lot
of
things
well
for
this
stage.
What
you're
gonna
need
java
sdk,
of
course,
maven
quarkx
click
cli.
It
is
the
tooling
that
we
chose
to
build
on
top
of
this
technology
and
what
we
are
doing
right
now
to
create
a
new
project,
so
this
command
line
will
create
a
new
project
from
scratch.
So
you
don't
you
don't
need
to
do
anything.
You
just
have
to
run
this
and
let
me
run
here
no,
not
here
wrong.
A
Okay,
maybe
here,
okay,
all
right!
So
oh
gosh,
it's
terrible!
Let
me
see
if
I
can
yeah
all
right
what
what
we're
trying
to
do
here.
So
I'm
creating
like
a
skeleton
of
a
project
with
some
extensions
and
some
building
blocks
from
quarkx
and
from
cogito
to
create
this
project
and
then
the
last
line.
It
is
the
the
name
of
my
approach.
So
when
my
name
space
and
my
in
the
name
of
my
project
and
the
version,
so
I
just
said
that
whoa
all
right.
A
A
This
is
the
name
of
my
workflow,
the
name
of
my
file,
whatever
I
want,
and
then
I
have
to
you
know
describe
like
this
as
they
blue
and
yemo
file,
or
it
could
be
a
json
file.
But
I
I
think
that
this
audience
prefers
emo
file
right,
let's
go
and
copy
and
paste
the
workflow,
so
we
can
not
take
too
much
time.
A
So
you
can
have
a
big
picture,
so
you,
you
might
also
talk
with
business
persons
or
you
know
other
stakeholders
or
people
that
are
interested
in
the
work
that
they're
doing
and
what
you're
doing
and
they
can
see.
Clearly
they
don't
need
to
be.
You
know
super
technical
to
understand
this
kind
of
stuff,
so
it
has
business
value
as
well.
So
let's
try
to
understand
what
is
do
what
we
are
doing
here.
So
the
first
state
is
just
a
state
to
inject
a
data
in
our
payload.
A
So,
as
you
know,
workflows
works
like
this:
the
input
of
a
workflow.
It
is
the
output
of
the
previous
zone
right.
So
in
this
case
the
last
state
will
produce
a
a
new
payload,
because
we
have
this
state
data
filter
for
output.
So
the
output
of
this
last
state
the
print
state.
We
want
to
apply
that
jq
expression
there
all
right.
So,
let's
see
that
working
well,
we
have
we
have
time.
A
It
will
compile
build
my
project
and
again
start
in
what
we
call
in
quarkus
dev
mode.
So
you
can
access
the
application
and
play
around
with
that
so
yeah.
Let's
please
work.
Okay,
yeah,
we're
fine,
yeah,
no
yeah,
totally
fine!
I
have
time
I
have
done
okay,
yeah!
Thank
you
all
right.
So
this
is
just
a
regular
quirks
application.
If
you
go
to
the
quarkus
guides
and
create
a
new
application,
you
see,
you
know
something
like
that
and
the
interesting
part
it
is
the
swagger
ui.
So
what
kushita
does
it
is?
A
A
Okay!
So
we
generate
an
open
api
specification
for
you.
So
imagine
that
you
have
a
lot
of
workflows
and
you
want
to
call
them.
You
can
import
all
these.
You
know,
specifications
between
them
or
you
can
use
in
postman.
You
can
do
use
whatever
you
want,
and
this
is
a
in
a
sense.
A
coach
to
workflow
application
for
you,
so
greetings
is
the
name
of
a
workflow.
If
you
recall
in
the
id
of
my
workflow,
I
have
the
word
greetings.
That
would
be.
You
know
my
endpoint
here.
A
So
to
start
the
workflow
I
have
to
to
make
a
post
a
request
to
this
workflow.
Let
me
all
right,
so
I
have
to
to
do
a
post
request
to
this
workflow
with
this
json
payload.
Here
we
have
a
way
to
describe
the
input
scheme
for
for
the
workflow,
for
you
know
simplicity,
I
didn't
add
so
I
have
to
add
manually
here,
but
if
you,
if
you
add
a
json
schema
for
the
input
of
your
workflow,
it
will
be
there.
So
it
would
be
nice,
let's
say
cubecall
and
I
can
execute
all
right.
A
This
is
the
response
of
the
execution
of
my
workflow,
so
it
is
hello
cubecall
and
it's
pretty
pretty
funny
and
easy
to
do.
Let
me
know,
but
it
is
just
for
demo
purposes.
You
can
download
the
other
example.
That
is
much
more
complex,
that
a
lot
of
other
features
there,
but
the
nice
thing
is
well
what
happened.
A
So
well,
what
I
was
going
to
do
is
like
well,
while
in
dev
mode
you
can
change
whatever
you
want
in
your
project
like
instead
of
hello,
I
can
add
hi,
and
this
brings
a
lot
of
value
to
the
to
the
developer.
So
when
you
you're
creating
workflows,
you're,
trying
you're
testing,
etc.
So
you
can
live
in
that
mode
testing.
A
Whatever
change
your
workflow
anytime,
that
you
change
and
you
save
the
file,
and
you
do
you
know
another
execution
or
you
refresh
the
application,
you
you
see
the
changes
that
are
made
in
your
in
your
application.
So
in
this
case
I
changed
hello
from
hi
and
just
you
know,
has
magically
changed
the
application
as
well
all
right
last
thing:
it
is
the.
A
Oh,
where
is
okay
here
all
right,
we
did
the
dev,
and
now
you
know
about
deploying
so
what
this
quarkx
application
does.
That
is
like
we
generate
all
the
the
emo
files
that
we
need
to
have
in
order
to
deploy
any
kubernetes
resistance
that
you
have
so
in
this
case,
I
have
me
in
cube,
so
I
have
to
set
up
a
few
things,
but
first
it
is
the
yeah.
I
want
to
delete
this.
Stop
please.
Okay,
all
right.
A
So
yeah
first
thing
is
like
we're
preparing
my
mini
cube
environment,
so
I
can
push
the
image
to
the
internal
registry
easily.
That's
the
way
I
do
you
can.
You
know
do
the
way
you
want
that
doesn't
matter.
It
is
just
a
regular
java,
quarkx
application
in
the
end-
and
here
we're
going
to
view
the
image
based
on
the
project
that
we
already
have
and
generate
all
the
emo
files
to
be
able
to
push
to
a
native
environment
crystal
has
a
very
tight
integration
with
k
native.
A
So
we
have
an
adam
that
calls
kinetic
eventing
and
when
you
have
events
in
your
in
your
workflow,
we
generate
all
the
k
native
objects
like
source,
sync
bindings,
triggers
brokers,
etc.
In
order
to
you
know,
bind
the
the
the
up,
your
application
with
the
canadian
platform,
so
this
is
really
cool
in
the
example
that
I
showed
you
about
the
newsletter
subscription
we
go
into
the
github.
You
can
see
that
in
practice
all
right,
so
please
build
the
image
I
don't
know
what's
happening
today.
A
I
test
this
multiple
times
and
it
was
like
one
minute
come
on
all
right:
yeah,
the
wi-fi
yeah
yeah,
please
demo,
gods,
okay,
it's
it
is
working
so
yeah.
Since
we
have
access
to
the
mean
cube
registry,
you
can
see
our
image
that
just
pushed
to
the
to
the
to
the
hashtag
right
now
and
quarkus
and
kojitov
will
generate
the
information.
A
A
Hopefully
we
work,
please
work
yeah
and
I
can
do
something
like
this
kn
service
list
and
you
see
you
know
the
service
there.
It
is
wrapping
up
becoming
ready,
becoming
ready.
Okay,
it
is
ready
and
we
can
access
and
use
the
same
application
right.
So
yeah,
that's
the
that's
the
idea
behind
all
I
hopefully
I
could
you
know,
go
through
all
of
that.
We
have
only
one
minute,
two
questions.
If
you
have
any
questions,
if
we
do
not,
you
can
ping
me
offline,
that's
the
way
I'll
be
around.