►
From YouTube: Workshop: Create DevOps Self-Serve from Slack
Description
Join Shaked Askayo the CTO of Kubiya to learn how to create an efficient and secure DevOps Self-serve experience directly from Slack that will free your team from repetitive request and keep the Devs happy.
Learn how to easily create workflows and automation using generative AI and make them accessible to your team in seconds.
- Create an efficient and secure DevOps self-serve experience directly from Slack
- Use generative AI to easily create workflows and automation
- Use conversational AI to give Devs the operational access they need without context switching or a steep learning curve
- Free your Ops team from repetitive request and keep Devs happy
A
A
A
So,
let's
get
right
to
it.
So
I
start
off
with
my
personal
Journey
I
bet
that
it
sounds
familiar
to
you.
So
I
used
to
be
a
devops
engineer.
For
a
few
years
later
stages,
I
managed
the
devops
necessary
teams.
So
I
got
to
see
all
of
the
problems
and
the
obstacles
managing
devops
pipelines
in
in
both
small
and
large
organizations.
A
A
Essentially
that's
what
led
me
to
create
Kubiak
I
wanted
to
solve
this
pain
for
a
lot
of
organizations
and
find
a
way
to
totally
self-serve
the
devops
functions
that
are
available
in
organizations.
So
the
devops
team
would
really
focus
on
what
really
matters,
so,
let's
jump
back
to
them
of
the
cubia
platform
and
how
it
can
help
with
this
topic.
A
So
I'll
start
off
with
sharing
the
documentation
that
could
be
ahead.
I'll
explain
a
second.
Why
I'm
doing
that?
But
essentially,
as
you
can
see,
we
have
a
documentation,
page,
a
documentation
site
with
a
lot
of
topics,
so
as
organizations
have
already
a
Confluence
notion
in
many
types
of
knowledge
bases,
it
all
starts
from
there.
A
A
A
It
would
also
be
installed
on
other
platforms
such
as
metal,
Muslim
teams
and,
as
you
can
see,
it
managed
to
give
me
the
accurate
so
to
my
question
straight
from
the
documentation.
So
we
can
see
that
I
could
run.
It
could
be
a
workflow
upload
command,
which
is
documented
in
the
site,
and
the
platform
is
able
to
also
add
reference
link.
So
if
I
want
to
drill
down
into
more
detail
and
understand
about
the
cells
from
where
this
knowledge
came
from,
I
could
jump
to
the
links
right
away.
So
it's
very
easy
to
use.
A
So
here
I
can
see
how
I
can
do
that
straight
from
the
documentation.
So
the
reason
why
it's
very
powerful
is
that
Google
is
able
to
integrate
with
a
different
knowledge
bases.
An
organization
might
have.
This
might
include
a
Confluence
notion,
even
a
PDF
Google
Drive.
Anything
that
includes
a
source
of
information,
basically
empower
the
developers
by
giving
them
a
platform.
They
could
just
ask
and
using
the
powerful,
loud
language
model
behind
the
scenes
that
could
be
able
to
evacuate
the
effort
to
as
well
to
the
questions
that
users
might
have.
A
A
So
what
happens
when
the
knowledge
source
is
not
really
a
documentation,
but
rather
a
workflow
that
the
platform
can
execute
for
me
in
such
cases,
besides
the
traditional
as
well,
which
could
come
from
the
knowledge
base,
the
platform
is
also
able
to
sell
the
relevant
workflow
as
I
can
see.
As
you
can
see
here,
it
found
the
kubernetes
deployment
rollout
workflow,
which
is
capable
of
following
a
deployment
in
kubernetes
I'll,
explain
about
workflows
that
how
would
they
work
as
we
go?
A
So
let's
go
ahead
and
just
click
on
go
which
will
execute
this
workflow
for
me,
so
kubia
workflows
are
really
easy
to
use.
Unlike
traditional
workflow
automation
tools,
the
special
thing
about
could
be
our
workflows
is
that
the
condensation
are,
they
are
very
easy
to
consume
and
they
can
involve
different
types
of
actions
across
the
technology
stack.
The
organization
might
have
so
in
the
case
of
falling
out.
The
deployment
in
kubernetes
I
need
to
answer
some
questions
right.
A
So,
even
if
devops
on
the
manual
way
on
the
other
side
will
get
asked
by
a
developer,
hey
I
want
to
hold
out
the
my
deployment
in
kubernetes,
usually
what
the
devops
will
say:
okay,
what
is
the
namespace
which
environment
and
so
and
so,
and
you
can
actually
build
these
questions
and
the
battles
as
could
be
a
workflows,
so
you
could
automate
the
process
of
context
gathering
in
a
human
manner.
So
it's
very
easy
to
use.
So,
let's
go
ahead
and
for
this
question,
I
think,
as
you
can
see,
I
can
see
here.
A
All
of
the
name
faces
that
I
have
in
my
kubernetes
cluster:
let's
go
ahead
and
pick
Argo
City
as
soon
as
the
platform
has
the
context
of
which
namespace.
The
second
question
is:
okay,
I
got
the
namespace.
What
is
the
deployment
that
you
want
to
roll
out
inside
the
namespace,
so
here
I
can
see
all
of
the
deployments
inside
the
Argo
City
namespace.
A
A
A
So
the
system
will
continue
with
me
that
that's
totally
what
I
want
to
do
all
out.
I'll
go
City
the
Excel
there
in
the
angle,
City
namespace
and
if
I
want
to
continue.
I
can
jump
to
the
previous
step
if
I
regret
something
at
any
time.
So
it's
really
easy
to
use.
If
you
regret
something,
what's
what's
initially
not
happening
in
traditional
workflow
automation
tools,
because
as
it
goes,
you
cannot
really
have
the
feedback
from
the
user
on
the
other
side
to
hold
back
or
decide
something
else.
A
So
let's
go
ahead
and
say:
yes,
so
that's
it
I
just
turned
out
the
algo
City
back
seller
named
this
I'll
go
CD
in
less
than
10
seconds.
But
what,
if
I,
have
the
context
and
I
know
the
namespace
and
I
know
they
sell
that
in
advance?
I
wouldn't
want
to
go
over
these
questions
all
over
again,
so
what
I
can
do
is
basically
say
roll
out.
The
kubernetes
deployment
tell
me
is
the
namespace
is
August
and
the
deployment
is.
A
So
again,
the
system
will
suggest
the
relevant
workflow
I'll
go
ahead
and
click
on
it
and
now
what
happens?
There
could
be
a
platform
analyzes.
My
query
against
the
resources
and
the
workflow
runs
that
already
related
to
rolling
out
the
deployment
recubernetes
and
basically
suggests
the
best
parameters
to
fit
into
the
workflow.
So
I,
don't
think
so.
I
don't
need
to
go
over
the
questions
again.
A
A
So,
as
you
can
see,
it
skips
the
questions
and
go
straight
to
the
validation
type
in
yes
and
amazing.
I
just
sold
out
that
deployment
kubernetes
once
again
this
time
without
answering
the
questions.
So
that's.
How
could
be
a
workflow
that
embedded
into
slack
and
how
you
can
consume
it
really
easily?
A
A
The
first
action
is
getting
the
namespace
from
kubernetes
presenting
buttons
on
selecting
the
relevant
namespace
as
soon
as
it
got
the
relevant
to
name
space
as
a
result
of
the
bottom
and
click
from
the
user,
showing
the
deployment
in
the
namespace
selecting
deployment
and
eventually
starting
the
deployment
so
before,
showing
you
the
actual
logic
and
how
you
can
empower
the
notebook
interface
to
create
all
kinds
of
workflows
for
wide
range
of
use.
Cases
I'll
show
you
the
generative
AI
capabilities,
which
is
one
of
the
way
we
could
use
to
create
a
workflow.
A
A
So
I'll
go
ahead
and
say,
create
a
workflow
which
triggers
a
Lambda
function
on
AWS
and
returns
its
outputs,
pretty
how
the
workflow
to
create
using
generative
AI.
Let's
try
it
out.
I,
just
click
on
generate
it
takes
a
few
seconds
could
be
I
will
analyze
the
point
that
I
just
gave
and
match
it
with
my
technology
staff
to
understand
which
actions
it
will
really
do
and
generate
the
workflow.
So,
as
you
can
see,
the
workflow
is
generated.
A
Let's
go
over
it
really
quick
and
then
I'll
show
you
about
the
different
hotels
that
you
could
use.
So
it
is
a
workflow
that
basically
gets
all
of
the
Lambda
functions
from
AWS
extracting
their
names,
showing
patterns
and
upon
user
clicking
on
a
button
which
is
essentially
a
Lambda
function.
It
triggers
it
and
shares
the
response
with
the
user
as
a
Json
object.
A
Sorry
about
that
and
Lambda
function
on
AWS
publish
it
in
the
second,
you
publish
a
workflow.
The
workflow
is
already
a
able
to
be
consumed
by
your
end
users.
You
didn't
play
English
the
active,
since
we
have
a
model
that
trains
and
understands
the
inner
aspects
of
what
the
workflow
does
and
is
able
to
give
the
user
the
ability
to
just
ask
for
it.
So
let's
go
ahead
and
say:
hey:
can
you
trigger
a
Lambda?
A
A
A
So
let's
go
ahead
and
understand
how
I
can
fine
tune
the
workflow
if
the
generative
I
didn't
match
my
use
case
in
most
of
the
cases
70
to
80
percent
of
the
actual
intention
on
what
you
want.
The
workflow
to
do
is
covered
by
AI,
but
sometimes
you
want
to
cover
more
or
adjust
it
to
your
use
case.
So,
as
you
can
see,
the
workflow
Builder
has
actions
and
steps
actions
are
basically
integrated
actions
across
your
Tech
stack.
A
So
in
this
example,
in
this
environment,
I
have
many
actions
relating
to
different
kind
of
Technologies.
You
can
see
Gila
kubernetes
GitHub
and
basically
you
can
use
the
copies
SDK,
which
elaborate
about
in
a
little
bit
to
create
more
and
more
actions
and
integrate
more
solutions
across
your
Tech
stock.
So
you
can
create
a
really
amazing
data
pipeline
of
integrating
different
tools
to
serve
a
specific
use
case
and
in
the
second
that's
you
know.
Basically,
in
the
workflow
editor,
you
can
choose
the
different
triggers
for
the
workflow.
A
A
Each
step
basically
does
something
for
the
user.
On
the
other
side,
there
are
many
types
of
steps:
I
won't
be
able
to
cover
them
all,
but
essentially
I'll
focus
on
the
relevant
ones
for
the
presentation
today.
So,
in
order
to
get
along
the
functions
from
AWS
I'm
using
core
AWS
integration,
which
is
available
as
a
public
action,
but
I
could
also
integrate
it
in
my
own
infrastructure
using
a
concept,
we
call
local
runners
if
we'll
get
the
chance
to
present
about
it
today
as
well.
A
I
could
decide
if
to
want
it
in
an
async
way,
which
means
it's
something
that
takes
more
than
a
few
seconds,
and
the
filtering
system
is
able
to
do
that
in
the
background
and
get
back
to
the
user
as
soon
as
the
action
is
done,
I
could
actually
ask
even
to
run
it
later
and
pop
the
user
hey.
Well,
when
do
you
want
one?
Do
you
want
to
do
it
in
a
few
hours?
A
You
want
to
do
it
tomorrow,
so
everything
is
pretty
straight
forward
and
I
could
actually
play
the
action
here
in
the
web
UI
as
I'm
building
the
workflow
to
see
that
it
totally
sells
the
use
case
that
I
wanted
it
to
do
so.
Here
is
the
response
from
AWS.
As
you
can
see,
I
see
the
full
response
here
in
the
web.
Ui
I
could
actually
save
it,
and
I
could
use
the
steps
panel
that
you
think
here
to
use
a
wide
range
of
integrated
steps
that
could
serve
use
cases
to
define
a
conversation.
A
So
if
you
edit,
the
workflow,
you
could
basically
take
a
lot
of
them
just
type.
It
here
say
going
to
learn
that
maybe
and
the
system
is
able
to
autocomplete
based
on
the
context
of
the
previous
executed
steps
in
the
workflow,
so
you
could
really
use
it
and,
as
you
create
the
workflow
and
understand
that
you're
creating
the
workflow
that
you
are
intending
intending
to
without
publishing
it
and
testing
it
on
slack
or
teams
all
over
again,
you
also
don't
need
to
understand
Json
or
you
know,
objects.
A
Since
the
platform
is
able
to
extract
the
relevant
parameter
from
Nestor
Json
object
and
give
me
the
ability
to
just
select
what
is
it
that
I
want,
so
it's
very
easy
to
use
and
I
could
also
create
the
textile
of
the
workflow
here
in
the
web.
Ui
end
to
end
before
doing
the
actual
publish
to
make
sure
that
everything
works
as
I
expected.
So
let's
go
ahead
and
click
on
test
run
and
see
the
color
workflow
that
we
saw
and
select
together
in
Excel.
A
So
it's
getting
the
Lambda
function
functions
from
AWS,
it's
pulsing
it
and
extracting
only
the
function
names
it
displays
buttons,
which
is
essentially
the
Lambda
functions
that
have
in
my
AWS
account.
I
can
pick
the
relevant
Lambda
function.
It
triggers
it
and
confirms
that
everything
worked
as
I
expected.
So
it's
very
easy
to
use.
A
A
A
So
moving
forward
to
how
you
can
extend
the
copia
platform
with
more
and
more
actions
and
basically
execute
these
sections
on
your
own
infrastructure.
So
let's
go
back
to
the
main
screen.
As
you
can
see,
every
remote
channels
and
remote
Runners
is
basically
an
easy
way
for
you
to
deploy
a
such
a
orchestrator
that
could
be
defined
on
your
own
infrastructure.
A
We
support
kubernetes
and
playing
Docker
images,
so
you
could
actually
execute
the
different
actions
that
you
saw
today
even
from
your
local
computer,
going
to
ec2
instances
and
our
kubernetes
operator,
so
you
could
spread
the
different
actions
across
multiple
accounts,
multiple
clusters
and
each
other
basically
can
use
the
action
stores
capability
in
order
to
execute
the
actions
on
your
own
infrastructure.
So
you
don't
need
to
share
Network
air
access
of
credentials
of
any
kind.
So
creating
a
runner
is
super
easy.
A
If
you
choose
the
kubernetes
way,
it
will
just
generate
kubernetes
manifest
for
you
to
deploy
the
runner
on
your
kubernetes
cluster.
If
you
use
the
docker
one,
it
will
just
share
with
you,
the
installation
state
which
is
kind
of
easy
and
as
soon
as
you
do
that
you
and
deploy
what
we
call
Action
stuff.
A
So
action
stores
is
the
actions
that
you
saw
on
the
action.
The
actions
panel
and
basically
each
action
store,
includes
the
relevant
actions
as
part
of
this
category
in
your
technology
stack.
So
today
we
execute
the
some
actions
in
the
kubernetes
action
store
that
you
could
see
here.
So
these
are
all
of
the
actions
that
are
available
in
the
kubernetes
action
store
and
you
can
basically
extend
it.
A
Based
on
your
use
cases,
you
can
even
create
your
own
action
stores
if
you
have
your
own
internal
developer
platform
or
your
own
way
of
defining
such
actions
and
behind
the
scenes
how
it
works,
it's
really
easy.
So
we
have
the
kubi
SDK
right
now.
We're
supported
for
python
coming
next
is
for
Golan,
and
essentially
these
sections.
Those
are
tiny
python
programs,
package
and
software
containers
which
you
could
use
in
combination
with
the
cubia
SDK,
so
I'll
show
you
an
example
of
some
of
the
examples
we
did
together
today.
A
A
There
could
be
I
SDK
and
as
soon
as
the
gsdk
is
imported,
you
could
just
annotate
the
generic
python
function
as
an
action
store
using
decorator,
as
you
could
see
here
and
as
soon
as
the
function
is
annotated,
and
you
do
when
you
deploy
it
to
a
local
Runner,
you're
able
to
see
it
in
the
web
UI
and
integrate
it
with
your
cubia
workflow.
So
we
took
very
easy.
A
A
The
platform
will
be
able
to
generate
the
boilerplate
for
you,
so
you
don't
need
to
rethink
how
the
application
structure
should
look
like,
and
you
can
see
here
that
the
generator
the
single
Python
program
and
initiated
it
as
an
action
install
and
here
you
can
see
that
it
has
some
actions,
simple
action
and
simple
action
with
model.
Essentially
actions
with
models
are
embedded
by
the
web
uy.
So
the
parameters
will
not
make
the
doing
runtime.
A
The
web
UI
will
be
able
to
generate
those
on
the
fly,
so
it's
very
easy
to
use
the
platform
in
this
way,
click
and
click
on.
Next.
You
need
to
provide
some
ways
to
URL,
where
you
want
to
build
the
action,
store
and
publish
it
all
so,
I'll
go
ahead
with
etn.sh,
which
is
a
temporary
Doki
registry,
for
the
testing
demonstration
and
I'll,
give
it
and
I
will
I
want
to
deploy
to
the
demo
owner.
A
Takes
a
few
seconds
behind
the
scenes,
I
was
able
to
package
the
action
Stone
reference
as
a
Docker
container
and
deploy
it
to
the
local
runner.
In
my
case,
I
have
the
demolo
Colorado,
which
is
which
was
deployed
on
kubernetes.
So,
as
you
can
see,
I
can
see
the
docker
build
log.
You
don't
need
token,
you
don't
need
anything
like
that,
and
I
can
see
a
success
message
coming
from
the
runner
that
the
action
store
was
totally
deployed
so
upon
clicking
on
done,
I
should
see
it
right
away.
A
A
A
That's
how
the
DSL
looks
like,
as
you
can
see
it's
even
simpler
than
GitHub
actions.
You
can
see
the
relevant
steps
in
the
workflow
and
for
each
step
which
Runner
executes
it
and
for
a
regular
step
like
built-in
functionality.
You
can
have
all
of
the
tools
that
you
could
use
and
the
power
to
create
a
perfect
workflow,
including,
of
course,
conditional
logic,
just
as
you
saw
in
the
workflow
editor.
A
A
So,
if
you're,
using
an
identity
provider
such
as
OCTA
or
Google
workspace,
basically,
the
platform
is
able
to
connect
to
it
and
based
on
that,
we
grab
and
understand
the
mapping
between
users
and
walls.
So
as
soon
as
some
user
executes
an
action
form
kubia,
we
try
to
understand
using
policies
that
you
will
Define
on.
If
the
user
can
do
that.
If
that's
not
the
case,
the
user
is
not
getting
lost.
It's
entering
what
we
call
an
app
overflow
and
the
Overflow
is
able
to
find
the
person
on
the
other
side
in
the
organization.
A
A
So
even
on
this
example,
I'm
connected
to
slack
since
I,
don't
have
an
I
didn't
enable
an
identity
provider
such
as
octal,
Google
workspaces
and
we're
able
to
use
like
user
groups
as
an
IPP
as
well.
So
here
I
could
see
the
relevant
policies
that
are
available
in
my
organization,
so
I
could
see
that
I
have
some
users
that
are
developed,
that
are
able
to
execute
different
workflows
and
they
could
even
create
a
policy
right
here
from
Slack
so
and
the
main
policy
and
the
workflow
that
I
want
to
allow.
A
Let's
go
with
the
kubernetes
Fallout
that
we
saw
together
with
the
multiple
if
I
want
to
and
the
all
that
I
want
to
give
permissions
to
I.
Simply
click
on
apply
and
could
be
add,
updated.
The
policy
for
me
and
now
now
the
wall
is
able
to
execute
the
actions
associated
with
the
specific
workflow
that
I
chose.
A
Besides
everything
that
I
showed
you
guys
today,
there
is
a
CLI
and
API.
So
all
of
the
actions
that
you
saw
in
the
web
interface
can
be
done
using
the
could
be
a
command
line,
interface
and,
of
course,
using
the
API.
So
you
could
even
integrate
could
be
a
workflows
as
part
of
your
existing
pipelines
without
completely
replacing
those.
So
it's
really
easy
to
integrate
kubia
all
across
the
technology
stack.
A
A
Is
asking
if
it
is
supported
on
Microsoft
teams
so
yeah
as
initial
support
for
Microsoft
teams?
It's
not
as
extended
as
you
can
see
here
on
slack,
but
we're
actively
working
on
extending
it
to
Microsoft
teams
and
in
upcoming
releases
I
was
going
to
make
the
integration
more
and
more
stable
and
and
Powerful.
So
yeah.
A
So
another
question
is:
what
happens
if
an
end
user
doesn't
have
access
and
tries
to
trigger
a
workflow?
So
it's
a
good
question.
In
case
a
user
tries
to
execute
the
workflow
and
it
doesn't
have
the
portal
permission.
Even
an
action
is
part
of
a
workflow.
The
platform
is
able
to
basically
tell
him
that
he
doesn't
get
that
he
doesn't
have
the
appreciate
permission
and
also
share
with
him
this
list
of
owner
in
the
organization
to
approve
this
specific
requests
based
on
the
policies
engine
that
the
platform
has
you
can
Define,
who
can
own?
A
What
or
basically,
who
owns
what
and
create
some
kind
of
an
approval
flow.
Well,
there
could
be
about
is
able
to
approach
the
whole
on
the
other
side,
show
him
the
relevant
context
and
up
over
the
request,
using
a
shared
channel
that
could
be
a
created
on
the
Fly,
where
you
can
discuss
culture
about
the
requirements.
Why
you
want
to
execute
such
action
so
about
that.
A
Okay,
another
question
here:
what
are
some
other
clothing
tool
that
you
can
integrate
with
kubia?
So
it's
a
good
question.
Essentially
almost
anything
can
be
integrated
with
kubia.
To
be
honest,
anything
that
is
supported
from
a
programming
language
can
be
done
from
ubia.
Some
of
the
use
cases
we've
seen
that
spokes
up
to
my
head
is
I'll,
go
CD,
kubernetes,
AWS,
gcp,
Azure,
Jenkins
and
many
others,
so
the
use
cases
are
endless.
A
Basically,
yeah
Vishal
is
asking,
if
it's
possible
to
add
up
overflow
to
email,
so
yeah,
that's
a
feature
that
a
lot
of
organizations
has
been
asking
for
so
yeah
it
is
able
it
is
possible
to
send
the
approval
flow
to
email,
in
addition
to
Fleck
over
the
chat
platform,
yeah
and
based
on
email
replies,
the
platform
is
able
to
continue
the
workflow
right
away
and
also
reply
to
your
email.
So
it's
pretty
powerful.
A
Okay,
another
question
that
I'm
seeing
here
is
it
could
be
open,
source
or
paid.
So
first
of
all,
the
ubisdk
is
open
source,
but
it
can
be
used
only
from
within
the
kubia
platform,
we're
planning
to
at
least
very
soon,
a
free
forever
plan.
Well,
you
could
use
the
kubia
platform
for
many
types
of
use
cases
and
it's
going
to
be
limited
for
some
of
those,
since
there
are
also
commercial
use
cases
in
the
Korean
platform.
A
A
Another
question
I'm,
seeing
how
I
can
control
who
does
what
in
the
platform,
so
basically
you
could
use
the
policies
I
discussed
on.
You
can
manage
such
policies
from
the
web
interface
and
from
the
cubia
CLI,
and
we
also
plan
on
releasing
the
telephone
provider
really
soon.
So
you
could
manage
this,
provide
this
policies
as
code
as
you're
doing
for
the
rest
of
uiac
stock
same
for
configuration
basically
and
workflow.
So
it's
going
to
be
very
powerful.
A
A
Another
question
I'm
seeing
here,
can
we
automatically
trigger
it
could
be
a
workflow
based
on
agility,
created
by
all
our
monitoring
system
and
do
the
required
updates
back
to
the
ticket
if
results?
Yes,
you
can
actually
do
that
using
the
webbooks
feature,
so
you
can
actually
send
the
web
okay
from
the
monitoring
system
took
bi
in
addition
to
the
create
a
ticket.
You
can
also
query,
for
instance,
using
the
gel
action
store
to
get
the
ticket
reference
and
using
the
install
integration
yeah.
A
A
A
So
I
think
we
covered
the
most
of
the
questions
I'm
seeing
here.
If
there
are
any
demo
sites
available,
so
pretty
soon
we're
going
to
release
the
kubia
playground
where
you'll
be
able
to
test
out
the
kubia
platform
on
a
select
workspace
I
will
share.
So
it's
going
to
be
a
pretty
easy
to
test
it
yourself,
foreign.
A
Use
cases
coming
from
prospects
about
this
particular
use
case.
You
can
even
generate
a
dynamic
model
based
on
inputs,
let's
say
from
telephone
Cloud
let
the
user
feel
all
of
the
variables
right
on
flag
click
on
submit
and
behind
the
scenes.
The
workflow
will
actually
get
it
and
run
it
ethically,
since
there
are
from
applying
plan
will
take
more
time.