►
From YouTube: Tekton's Hassle-free Journey with Tekton Operator - Vincent Hou, IBM & Savita Ashture, Red Hat
Description
Tekton's Hassle-free Journey with Tekton Operator - Vincent Hou, IBM & Savita Ashture, Red Hat
Speakers: Vincent Hou, Savita Ashture
Vincent and Savita will introduce what Tekton operator is, why we need it, and history of Tekton operator in Tekton community, explain how to install, configure and upgrade Tekton components, and demonstrate how Tekton experience becomes easier by leveraging Tekton operator. In addition, they will walk you through the experience on how Tekton Operator installs Tekton components on different Kubernetes services in a platform-agnostic way.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
Good
morning,
good
afternoon
and
good
evening
to
everyone,
depending
on
where
you
are
it's
a
great
honor-
to
attend
this
city
conference
virtually
in
2021.
Welcome
to
our
session
today,
my
colleague
savita,
and
I
will
co-present
this
topic
on
captain's
hassle-free
journey
with
tactile
operator.
Something
about
me.
My
name
is
vincent
ho.
I
originally
come
from
china.
I
used
to
stay
in
belgium
for
four
years
to
my
colleague.
Now
I'm
working
in
united
states.
This
is
a
hint
that
I
know
everything
I
tried,
but
unfortunately
not.
A
A
B
You
vincent
from
for
the
brief
introduction,
hello.
Everyone
hope
you
all
are
doing
good
myself
today,
I'm
based
out
of
india
bangalore.
Currently,
I'm
working
as
a
senior
software
engineer
at
red
hat.
I
have
a
working
experience
in
different
open
source
projects
like
cloud
foundry,
k
native
and
right
now
I
am
an
active
contributor
on
the
tecton.
Please
feel
free
to
reach
out
to
me
on
the
slab
twitter
linkedin.
The
details
are
given
here.
I
think
that's
all
about
me.
Thank
you.
A
You
sebasta,
I
will
go
on
with
our
agenda
for
today.
First,
we
will
explain
what
a
kubernetes
operator
is
and
why
we
use
it
then
briefly
introduce
the
tapton
projects.
After
that
we
go
deep
into
techno
operator
by
walking
through
its
functionalities
and
configurations
what
benefits
we
have
to
use
it.
How
chapter
operator
supports
multiple
humanities
platform?
A
What
is
special
on
openshift
and
how
cr
behave
differently
in
different
platforms?
We
will
have
a
demo
for
the
operator
today
and
last
but
not
least,
there
is
a
time
slot
dedicated
to
questions.
What
is
a
kubernetes
operator,
the
kubernetes
operator,
in
the
nutshell,
is
a
construct
packaging
deploying
and
managing
a
kubernetes
native
application.
A
A
Why
do
we
use
the
kubernetes
operator,
automation
he
automates
everything,
including
the
installation
management
upgrade
etc
for
container-based
services,
offload
human
operators
work
and
make
life
easier.
Based
on
the
specification,
the
operator
manages
the
application
in
a
controller
which
checks
the
cluster
to
ensure
the
ideal
states
are
fulfilled
with
the
correct
infrastructure
resources.
A
A
What
is
tactile
about
tethno
is
a
open
source
framework
for
creating
csv
systems
in
the
cloud
native
way.
It
consists
of
many
components
like
pipeline,
a
set
of
crs
to
create
csd
systems
trigger,
which
is
able
to
instantiate
pipelines
based
on
events
dashboards,
a
web-based
graphical
interface
catalog,
which
is
tactile
building
blocks
and
cli,
since
it
has
so
many
components,
installation
and
management
can
be
averted.
You
have
to
go
across
a
different
repository
to
find
the
correct
links
and
apply
them
go
to
each
correct
resource
for
configurations,
not
user
friendly.
A
Is
there
an
easier
way?
Yes,
the
operator
is
the
one
ring
to
rule
them.
All.
Captain
operator
by
far
can
manage
three
major
components
with
custom
resources.
It
is
expanding
to
manage
more
components.
Lifecycle,
management
and
configurations
of
the
type
of
components
are
done
by
crs.
The
names
of
the
custom
resources
are
very
self-explanatory.
A
Each
cluster
only
allows
one
instance
of
the
typedone
component,
so
we
define
the
cr
as
cluster
scoped
once
cluster
only
allows
one
cr
with
the
spec
in
the
crs,
you
can
configure
the
target
namespace
on
top
of
the
basic
crs
tactile
operator,
also
defined
the
cr
name.
The
technique
to
manage
all
of
them.
There
are
three
modes
available
to
be
configured
in
tactile.
Config
default
mode
is
to
install
pipeline
and
trigger
basic
mode
needs
to
install
pipeline.
Only
full
mode
means
to
install
all
of
the
three
components.
A
B
B
This
support
of
multiple
platforms
can
be
achieved
with
the
help
of
extension
mechanism,
which
is
a
feature
from
the
relative
package.
So
as
of
today
in
tecton
operator,
we
support
generic
kubernetes
and
openshift,
and
we
can.
We
also
have
a
roadmap
for
the
different
platform
to
be
supported,
but
that
depends
on
the
use
case
scenarios
like.
If
anyone
wants
tekton
operator
to
be
supported
as
a
default,
then
we
can
add
those
platform
also,
but
it
is
under.
It
is
in
roadmap.
B
B
So
in
the
today's
call
we
are
not
going
to
discuss
in-depth
technical
details
about
this
extension
mechanism,
considering
the
time
constraint
now,
let's
just
take
the
one
use
cases
of
open
shift
where
it
is
helpful
for
how
this
extension
mechanism
is
helpful.
So
you
can
see
on
openshift
we
have
a
a
different
cr
called
tecton
add-on,
which
helps
to
install
the
catalog
tasks
as
a
cluster
task
and
trigger
binding,
which
makes
the
openshift
users
a
use
case
scenario
easy
way.
It
means
like
a
customers
or
uses
an
open
shift.
B
They
don't
need
to
install
the
task
from
the
catalog
repo
instead,
when
they
install
the
operator
by
default,
those
things
will
be
installed.
So,
while
writing
the
resources
of
pipeline
or
trigger
they
can
directly
make
use
of
those
existing
inbuilt
catalog
tasks.
This
is
where
I
just
wanted
to
give
a
feature
which
is
specific
to
openshift.
B
Now,
let's
quickly
understand
how
what
are
the
different
cias
available
on
different
platforms,
so
in
kubernetes
we
have
tecton
pipeline
triggers
and
dashboard
and
on
the
openshift
we
have
pipeline
triggers
and
add-on.
So
you
can
see
pipeline
triggers
are
common
in
both
the
platform,
but
dashboard
and
add-ons
are
differ
for
these
two
platforms,
so
this
is
kind
of
difference
can
be
achieved
and
we
are
able
to
do
it
today
in
the
tecton
operator
with
the
help
of
extension
mechanism.
B
So
today
we
are
planning
to
show
how
we
can
do
installation
how
the
tecton
operate
operator
could
be
able
to
do
deployment
restoration.
Then
we
will
show
us
example
of
pipeline
deployment
with
the
help
of
trigger,
even
after
upgrade
the
example
works
seamlessly.
And
finally,
we
will
see
the
uninstallation
part,
let's
start
with
the
installation.
B
B
B
Now
we
just
the
tecton
operator
controller
is
running
which
watches
on
the
principles,
so
that
will
help
us
to
install
the
tecton
components
so
now
to
install
the
tecton
components
like
pipeline
trigger
and
dashboard.
Let's
use
the
custom
resources.
Let's
apply
this
custom
resource
called
config.
Now
we
have
applied
the
configs
here.
Let's
watch
the
status
of
different
crs
of
tecton
you
can
see.
Tecton
pipeline
is
true
and
similarly
watch
for
the
tecton
triggers
and
then
take
down
dashboard
if
it's
in
the
installation
state,
so
it
don't
show
ready
as
true.
B
B
B
Let's
apply
the
ingress
dot.
I
am
infect
on
demon
code
itself,
so
I
have
applied
the
ingress.yaml
and
meanwhile,
let's
get
the
ingress
object
in
the
tecton
pipeline
in
space.
You
can
see
this
one,
let's
execute
you
can
see
still
address
shows
shows.
Meanwhile,
let's
watch
on
that
once
you,
this
dashboard
is
up
and
running.
We
can
see
like
what
are
the
installed
version
of
the
tecton
components?
B
Okay,
so
now
the
dashboard
ingress
url
we
got
so
let's
do
quick
access
on
that.
So
you
can
see
here.
Dashboard
is
the
part
where
it
is
actually
running.
This
is
how
the
dashboard
looks
like.
So
I
don't.
I
won't
go
to
different
parts
of
the
dash
resources
instead,
I'll
just
show
like
what
are
the
installed
version
of
tecton
components.
B
The
next
step
is
like
how
we
do
the
deployment
restore
in
the
tecton
operator.
So
now,
let's
do
a
deploy
on
the
tecton
pipelining
space.
Let's
remove
one
of
the
deployment
I
will
just
remove
here,
so
you
can
see,
we
expect
to
see
the
deployment
resource
is
gone
and
re-launched.
You
can
see
here,
tecton
pipeline
got
deleted
and
then
it
started
creating
it
here.
This
is
how
the
you
can
see
our
deployment
restoration
works.
We
are.
We
are
ready
with
the
tecton
components
installed
on
the
cluster.
B
Now,
let's
understand
how
we
can
deploy
the
sample
pipeline
to
proceed
with
that.
Let's
install
the
example
as
part
of
this
demo.
What
I'm
planning
to
do
is,
I
am
planning
to
install
a
task
run
based
on
the
github
event.
So
this
way
I
can
cover
both
pipeline
concept,
as
well
as
a
trigger
concept.
This
is
my
event:
listener
yaml,
where
it
installs
the
task
run.
What
it
does
is
like
it
just
close
the
bit
repository
url
for
a
particular
revision
and
it
it
do
a
ls
iphone,
lrt
on
that
particular
current
working
directory.
B
This
is
where
the
task
run
will
be
installed,
but
when
this
task
run
will
be
installed,
that
is
somewhere
given
by
the
interceptor
where
we
are
integrating
with
the
github.
So
what
we
are
doing,
we
are
watching
on
the
event
of
the
pull
request
whenever
there
is
a
pr
open.
So
whenever
these
three
event
occurs
for
the
pull
request,
specifically,
they
are
creating
a
task
run.
This
is
a
simple
example:
let's
see
it
in
action,
so
to
do
that,
let's
install
the
example
and
watch
the
the
parts
which
will
be
created
here
under
port
section.
B
Now
you
can
see
updates
in
the
creating
state.
Now
it's
up
and
running,
let
me
do
a
tail
on
the
log.
It's
waiting
for
the
event.
Now
what
we
will
do.
The
next
step
is
to
configure
the
url
in
the
github
settings
right.
So
to
do
that,
I
should
have
a
publicly
accessible
url.
I
have
created
a
interest
which
I
kept
in
the
example
folder
itself,
and
my
interest
look
like
this.
So
this
is
how
my
ingress
look
like
and
it
is
watching
on
the.
B
As
ingress
will
help
us
to
do
a
publicly
accessible
thing,
so
let
me
get
the
ingress
id
and
do
a
call
request.
Skid
is
the
path
where
my
ingress
looks
like
now
you
can
see
a
error
occurs
like
invalid
body
format
and
you
can
see
blocks
in
the
event
listener
also.
So
this
shows
that
okay,
the
connection
is
working
fine.
Now,
let's
do
a
settings,
as
mentioned
in
the
github
repo.
So
now,
let's
go
to
savitastra
sample
go
up
right,
so
let
me
quickly
go
over.
B
Let's
add
in
the
book
here:
let
me
copy
the
url
from
here
and
just
remove
it
and
add
it
then
to
application
lesson
content
and
this
secret
is
required
to
require
for
the
authentication
purpose.
So
this
is
the
secret
I'll
copy
and
paste
it
as
seen
in
the
event
listener
yaman,
I'm
actually
watching
on
the
pull
request
event.
So
let
me
select
the
event
instead
of
push.
Let
me
just
select
the
full
request
part
so
that
I
can
get
the
events
properly.
So,
let's
add
the
web.
No
okay!
The
book
is
added.
B
You
can
see
some
logs,
which
indicates
okay,
something
is
added
something
happen
on
the
url.
Now
what
we
will
do.
As
per
this,
I
will
go
to
the
full
request
so
for
the
time
constraint,
what
I'll
do?
What
I'm
doing?
I'm
just
closing
the
existing
pull
request
and
re-opening
the
request,
so
you
can
see
event
messages
displayed.
We
can
see
a
task
run
getting
created,
so
you
can
see
15
seconds
five
seconds
ago,
so
it
is
succeeded
now
to
see
what
is
the
task
run
actually
doing.
B
B
B
B
Action
now
I
will
just
copy
the
yama.
Now
I
have
applied
it
so
meanwhile,
let's
wait
first,
wait
for
a
minute
so
that
it
start
it
start
upgrading
the.
If
I
have
it
control
c,
let
me
do
again:
cube
cpl
get
ctrl
get
for
site
final
tecton
pipelines
you
may
be
seeing
some
pods
are
in
terminating
state.
Some
pods
are
in
creating
state.
So
this
is
where
it
starts.
B
Upgrading
the
components
you
can
see
the
components
version
got
upgraded
like
13.0
23.0
16.1,
so
it
indicates
our
upgraded
success
upgrade
of
tetron
box
once
upgrade
is
done.
You
can
see
a
event.
Listener
code
is
also
got
terminated.
So
if
I
come
and
see
here
do
a
cube,
ctl
get
parts
you
can
see.
A
card
is
recreated
in
a
just
a
fraction
of
second
or
55.
So.
B
Do
a
quick,
cpr
logs
hyphen,
the
next
action
is
verify
the
example.
After
upgrade,
what
I'll
do
I
don't
do
any
changes,
I'll
resend
an
event
to
recent
event?
I
will
again
reopen
the
full
request.
You
can
see
a
event
occurs,
so
it
indicates
that,
after
upgrade,
our
example
works
perfectly.
Let
me
check
a
task
run.
You
can
see
a
new
task
when
getting
created.
B
So
now,
let's
clear
this
out,
let's
delete
the
cr
which
got
installed,
so
we
should
delete
the
cr
first
so
that
all
the
tecton
components
will
get
deleted
so
that
we
can
observe
here
here
like
we
can
refresh
the
dash
portal
after
a
few
seconds.
We
should
see
503
error,
let's
wait
for
a
second,
so
it
is
in
the
deleting
state.
So,
meanwhile,
if
we
want,
we
can
see,
we
can
version
to
see
like
okay,
what
all
things
coordinated
you
can
see.
B
B
A
A
A
B
A
A
Some
other
communities
which
I
work
with
here
as
well.
They
have
been
talked
a
lot
about
the
differences
of
these
different
installing
two
installing
toolkits.
I
actually
said
we'll
compare
them.
This
is
not
a
beauty
contest,
I
say
which
guy
which
person
wants.
Is
it
how
you
how
it
fits
your
project's
needs?
For
example,
we
talk
about
puberty
into
the
operator.
A
Sure
number
one
thing:
it
is
a
combination
application
so
for
certain
anti-dopamine
to
the
application
you
leverage
with
too
many
capabilities
it
can
create.
You
can
create
your
own
cio
leverage,
the
reconcile
loop
to
compare
between
the
desire
and
the
actual
states
and
move
them
from
the
actual
state
to
this
is
downstairs
that
yeah,
that's
how
providential
works
and
number
two
yeah
and
cr's
custom
resource
is,
I
would
say,
unique
and
that's
the
only
source
of
choice
for
you
to
conceive
your
applications
and
usually
before
you
solve
something.
Maybe
you
need
to
your
own.
A
B
So
if,
if
we
make
use
of
kubernetes
operator,
we
could
able
to
manage
data
operations
like
management,
upgradation
roll
back
those
things
easily
through
inbuilt
features
of
like
management
kind
of
functionalities.
But
with
the
help
of
helm,
we
could
able
to
do
the
deployment
and
even
to
manage
helm.
Also,
we
we
can
make
use
of
operators
so
yeah.
I
I
agree
with
you
like.
It
all
depends
on
our
project
use
cases
and
the
way
we
want
to
deploy
our
project
and
handle
it.
A
A
Everything
as
every
tools,
including
even
the
administrators,
when
lines
you
can
apply
on
top
of
your
combination,
software,
I
think
that's
also
the
benefits
you
use,
accommodation
operator
to
manage
your
applications
and
webinar
ecosystem.
I
think
have
metropolitan
user
well
released
in
the
traditional
way
by
publishing,
yaml
somewhere,
and
you
can
also
leverage,
I
think
the
operator
hub
by
wrapping
with,
I
think
csv
artifacts,
so
that's
yeah
yeah.
So
that's
the
operator,
however,
can
copy
your
repo
to
host
all
your
operators
running
managed
by
the
olm
tools
right.