►
From YouTube: Easy notifications for Kubernetes - Alexander Matyushentsev, Intuit & Remington Breeze, Akuity
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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.
Easy notifications for Kubernetes - Alexander Matyushentsev, Intuit & Remington Breeze, Akuity
Kubernetes provides powerful features and empowers developers to solve lots of use-cases. Do you want to do GitOps, Progressive Delivery, batch processing? Easy - there is a tool that provides an effective way of solving each problem. The email that notifies the team about successful deployment is the cherry on the cake and should not be hard to do, right? Well, the notifications support is not as straightforward as it sounds. Does your team prefer Slack, Telegram, or all of the above? Do you want to fine-tune notifications criteria and avoid spamming your team about each and every change? Do you need customized notification messages that include details specific to your environment? We have solved this problem for Argo by introducing a generic Notification Engine that powers a notification experience for Argo projects. You will learn how to leverage the engine to configure notifications for Argo projects as well as how to use it for any other Kubernetes-native application.
A
All
right,
hi
everyone
today
we're
going
to
be
speaking
about
a
project
that
we
created
to
enable
notifications
features
for
the
argo
project,
all
right,
so
my
name
is
remington
brees
and
I'm
one
of
the
maintainers
of
the
argo
project
along
with
alex
here
and
I'm
also,
a
software
engineer
at
a
company
called
acuity
which
we
launched
this
week
and
acuity,
provides
vendor
supported.
Distribution
of
argo,
in
addition
to
support
and
services
that
are
around
the
argo
project,
all
right.
B
Don't
try
to
pronounce
my
last
name,
I'm
I'm
a
principal
software
engineer
at
a
company
called
intuit
and
I'm
also
a
long
time.
Maintainer
of
argo.
I've
been
with
argo
for,
like
maybe
five
six
years
already
worked
on.
Argo
workflows,
rollouts
and
currently
my
focus
is
argo.
Cd,
all
right
and
few
words
about
a
company
I
work
for
so
intuit
is
a
us-based
fintech
company
and
intuit
to
the
product
maker
of
financial
products
such
as
turbotax,
mint
and
quickbooks.
B
So,
and
we
serve
10
million
customers
in
all
segments
and
I'm
happy
to
say
that
intuit
is
a
gold
member
of
cncf
all
right
enough
introductions.
Now
we
can
get
to
a
topic.
So,
as
limited
mentioned,
we
want
to
speak
about
notifications
and
kubernetes
and
argo.
I
want
to
start
with
argo,
and
you
might
know
already
that
argo
is
not
a
single
product,
it's
a
family
of
products
projects,
and
so
we
have
four
currently
and
it's
really
important
for
us-
that
every
project
is
focused
on
a
single
use
case.
B
At
the
same
time,
it's
hard
to
argue
that
notifications
is
a
very
important
feature
for
the
good
end
user
experience
and,
as
you
might
notice,
a
notification
was
not
mentioned
in
as
a
focus
when
I
described
any
of
these
projects,
and
so
it's
a
it's
a
it's
kind
of
it's
a
problem
and
we've
heard
a
lot
from
our
end
users.
That
notifications
feature
is
needed,
and
the
next
slide
is
to
kind
of
just
to
prove
that
it's
not
just
our
imagination.
B
We've
got
a
bug
report,
a
feature
request
about
notifications,
pretty
much
in
each
and
every
project
of
argo
organization,
github
organization,
and
so
it
was
just
clear
that
it's
no
longer
okay
to
just
keep
ignoring
them
and
we
had
to
do
something,
and
so
we
did.
We
decided
to
try
to
investigate
and
see
what
is
it
we
can
do
so
we
can
deliver
a
great
user
experience,
enable
notifications,
but
do
not
sacrifice
the
quality
and
keep
projects
light
as
as
they
currently
are
all
right.
B
So
and
in
this
talk
I
will
walk
you
through
our
journey
that
we
did
like
last
year.
I
will
explain
to
you
which
options
we
tried,
which
worked,
which
didn't
work,
and
you
will
see
an
action,
the
solution
that
we
are
pretty
happy
about
all
right,
so
I'm
going
to
start
from
step
number
one.
So
before
we
even
consider
building
anything.
We
just
decided
to
see
if
there
is
anything
in
the
kubernetes
system
that
already
works
and
probably
can
be
used
by
argo
users,
and
we
can
see
we
checked
a
lot
of
projects.
B
I
just
highlighted
three
of
them
here,
the
first
one,
you
probably
already
know,
I'm
probably
using
it's
a
cube
watch
project
by
bitnamilabs
and
we
really
enjoyed
when
we
tried
this
project
for
the
first
time.
It
was
extremely
easy
to
get
started
and
get
notifications
for
built-in
kubernetes
resources.
B
Next,
the
simplicity
is
great,
but
we
had
we
heard
a
lot
from
our
users
that
customization
is
also
very
important
and
we
could
not
find
it
in
cube
watch.
So
we
decided
to
check
another
one,
and
the
next
project
was
primitives
and
alert
manager
and
it
felt
like
a
good
solution.
Probably
at
least
you
cannot
complain
about
a
lack
of
customization,
it's
possible
to
configure
a
load
using
primitives
and
alert
manager,
but
we
got
some
pushback
from
end
users.
B
B
Why
didn't
it
work
and
why
didn't
we
just
use
this
project
and
so,
as
opposed
to
cube
watch
cargo
cube
native
fire
is
extremely
flexible,
but
according
to
feedback
from
users,
flexibility
doesn't
mean
you
know,
ease
of
use,
and
so
it
was
just
too
difficult
to
use
it.
Each
and
every
user
was
supposed
to
come
up
with.
B
You
know
thousands
of
years
of
configuration,
and
so
we
decided
to
maybe
you
know,
take
it
into
account
and
I
make
sure
it
won't
be
repeated
in
in
the
final
solution
and
so
yeah.
It
was
kind
of
clear,
we'll
have
to
build
something
and
one
more
step
back
and
we
decided
to
do
a
deep
dive
and
you
know,
speak
with
our
user
analyze,
all
the
bugs
that
were
filed
in
github
repo,
and
this
is
how
we
felt
you
know
like
after
day
or
two
of
of
this
exercise.
B
There
are
a
lot
of
things
we
learn.
One
of
them
was
apparently,
notifications
are
not
just
slack
and
email.
A
lot
of
people,
apparently
don't
use
slack
a
lot
use
ms
teams,
some
some
use
telegram.
Google
chat,
rocket
chat
and
actually
I
can
continue
a
lot
and
it
would
be
just
the
first
type
of
notification
providers
text-based,
but
for
some
people
notification
means
jury,
issue,
pager
duty.
Maybe
it's
a
comment
in
pull
request
and
some
users
said
we
just
want
to
call
an
api
server
when
vis
and
custom
do
a
custom.
B
B
It
was
just
the
beginning.
The
next
set
of
challenges,
no
problems
was
that
every
user
has
opinion
about
when
the
notification
should
be
sent.
Some
wants
to
get
notified
about
everything.
Some
only
wants
to
know
about
important
events.
Important
means
like
different
for
for
everyone,
and
absolutely
everyone
wants
to
be
able
to
customize
the
notification
text.
B
So
that
was
another
kind
of
challenge
we
had
to
take
into
account
because
at
best
we
probably
can
go
through
most
common
use
cases,
but
it
would
take
us
like
forever
to
iterate
and
codify
all
of
them.
But
it
was
not.
It
was
not
a
waste
of
time.
We
kind
of
we
analyzed
all
of
that,
and
we
noticed
that
we
have
different
set
of
repeated
requirements
from
two
personas
of
user
who
users
who
use
argo.
B
B
We
have
application
developers
who
value
simplicity
a
lot
and
they
are
less
opinionated,
which
means
they
do
not
want
to
invest
a
lot
of
time
because
they're
writing,
you
know
end
user
applications
plus
they
are
usually
fine
with
what
platform
operators
wants
them
to
use,
and
it
feels
like
a
very
good
feed
and
the
only
additional
requirement
from
application
developers
was
that
they
do
not
want
to
file
a
jury
ticket.
This
is
just
not
okay,
they
want
some
simple
way
to.
B
You
know
enable
the
notification
feature
for
themselves
and
they
don't
mind
to
write
a
little
bit
of
yammer
as
well,
and
that
really
helped
us
and
eventually,
after
some
brainstorming,
we
come
up
with
a
set
of
more
or
less
clear
requirements.
We
understood
what
is
it
we
want,
and
on
high
level
like,
we
basically
realized
that
we
want
flexible
solution,
which
means
it's
driven
by
configuration
and
we
expected
platform
operators
to
spend
some
time
writing
the
configuration
the
project
maintainers
can
help
operators
as
much
as
possible
and
deliver
good,
getting
started
set
of
configurations.
B
Of
course
we
wanted
to
support
a
lot
of
notification
services
and
we
just
which
is
very
important.
We
knew
we
are
going
to
add
more
and
more
and
more,
and
we
wanted
to
kind
of
introduce
some
interface
that
encapsulates
complexity
of
magic,
different
notification
providers
and
second,
set
of
requirements
related
to
end
users.
B
So
notification
engine
is
a
go
link
based
library,
which
is
already
used
by
argo,
workflows,
argo,
cd
and
work.
Sorry,
argo,
cd
and
algorithms
workflows
support
is
coming,
hopefully
soon
and
so
notification
engine
already
supports
all
these
notification
services,
which
you
see
on
the
screen,
and
this
is
not
a
full
list.
There
is
a
new
release
coming
soon
and
the
final
version
of
current
version
of
notification
engine
supports
more
than
a
dozen
of
such
services
and
what
is
also
very
important
notification.
B
B
It
would
feel
exactly
the
same,
and
basically
we
don't
expect
that
any
additional
education
would
be
needed
to
consume
our
robot
notifications,
and
here
is
the
repo.
So
if
you
interested
in
learning
about
the
engine
feel
free
to
open
this
url
don't
hesitate
to
give
it
a
start.
It
needs
stars,
and
I
guess
that's
it
now.
I
can
go
a
little
bit
deep
into
and
explain
how
it
works
before
we
start
the
real
demo.
B
Okay,
so
here
you
are
seeing
a
high
level
diagram
that
demonstrates
components
of
a
modification
engine
notification.
Controller
is
central
power,
part
of
it.
What
it
does.
It
consume
the
configuration
provided
by
the
operator
and
stored
in
a
config
map
and
some
authentication
information
stored
in
secret,
and
it
continuously
watches
custom
resources
and
what
it
does
it.
Basically
as
soon
as
it
realized
that,
according
to
configuration,
an
important
event
happened.
B
It
would
send
the
notification
and
the
information
about
who
is
interested
in
the
notification
is
stored
in
a
kubernetes
annotation,
which
is
managed
by
application
developer
and,
as
I
mentioned,
engine
supports
a
bunch
of
notification
providers
out
of
the
box.
I
realize
it's,
maybe
not
so
easy
to
understand.
So
I
have
a
few
pml.
B
For
you,
which
hopefully,
will
make
it
more
clear,
so
what
you
are
seeing
now
is
a
real
life
example
of
a
configuration
for
argo,
cd
application,
notifications,
argo
cd
notifications,
so
the
operator
supposed
to
pretty
much
configure
the
following
to
enable
notifications.
So,
first
of
all,
engine
needs
to
know
when
to
send
the
notification
and
we
introduce
something
we
call
a
notification
trigger,
and
so
notification
trigger
is
just
a
function
that
has
a
name
and
this
expression
that
returns
that
consume
custom,
kubernetes
resource
and
returns
true
or
false
as
soon
as
function
is
a
result.
B
Value
changes
from
false
to
true.
This
is
when
a
notification
engine
sends
a
message
and
it
needs
to
so.
The
next
step
is,
it
needs
to
somehow
produce
the
content
for
that
notification
and
to
do
so,
it
uses
another
configurable
part
which
we
call
notification.
Template
and
name
is
self-explanatory.
Basically,
it's
another
function
that
consume
a
kubernetes
resource
and
produce
a
message,
and
example.
B
Here
is
pretty
simple:
it
just
produces
a
string
that
has
some
information
about
application,
including
name
including
status
yeah,
so
nothing
complex
here
so
far
and
then
final
step
is
to
simply
provide
credentials
that
are
required
to
talk
to
the
notification
provider.
In
this
particular
case
we
are
configuring,
slack
and
the
real
token
is
stored
in
a
secret
that
can
be
referenced
in
a
config
map,
and
so
I
promised
some
encapsulation
so
here
it
is
the
notification
template
not
necessary,
defines
just
a
boring
text.
B
B
So
hopefully
it
makes
more
clear
what
operator
has
to
do
to
configure
the
notifications.
So
the
next
step
is
what
does
end
user
application
developer
has
to
do
to
start
using
it,
and
this
is
not
much.
Basically,
the
end
user
just
have
to
apply
an
annotation
and
in
that
annotation
user
have
to
specify
the
trigger
name.
That
knows
about
when
notification
should
be
sent
at
the
end,
explain
where
we
want
to
get
notification
to
be
delivered.
So
in
this
case
a
user
wants
to
be
notified
about
successful
application,
things
which
is
the
trigger
part.
B
A
So
there
are
three
things
that
we
need
to
configure
notifications
for
rollouts.
So
the
first
is
the
latest
version
of
argo
robots
version.
1.1
includes
support
for
argo
notifications
through
the
notifications
engine.
So
to
install
that
it's
a
it's
pretty
simple,
you
go
to
our
github
download
the
installation
manifest
and
it's
a
simple
cube.
Ctl
apply.
A
The
second
thing
that
we
need
is,
as
alex
mentioned,
there
are
two
personas
and
the
first
is
from
an
operator
perspective.
So
what
you
need
to
do
as
an
operator
is
configure
argo,
rollouts
notifications,
config
map,
and
then
the
third
thing
that
we
need
to
do
is
configure
as
a
developer.
We
need
to
configure
our
rollout
with
an
annotation
that
alex
demonstrated
to
set
up
notifications
for
that
specific
rollout.
A
A
Next,
let's
take
a
look
at
the
config
map
that
we
have
to
set
up
so,
like
I
said
you
have
to
name
it.
Argo
rolex
notification,
config
map
for
it
to
be
detected
by
the
rolex
controller.
So,
let's
start
from
the
bottom.
So
we
have
this
service
dot
email.
So
that's
what
we're
going
to
be
setting
up
today,
an
email
notification
and
it's
pretty
straightforward,
so
we
have
a
username,
password,
etc.
A
So
that's
always
all
there
is
to
it
there.
Okay!
So,
let's
move
on
to
the
template,
so
you
can
see
here
we
have
an
email
stanza,
and
this
contains
email,
specific
notification
configuration.
So
in
this
case
it's
a
subject,
and
we
also
have
the
message
stanza
and
this
is
going
to
be
shared
across
many
different
notification
services.
A
So
this
allows
you
to
basically
add
say
a
slack
stanza
hero,
a
telegram
stanza
that
has
slack
or
telegram
specific
configuration,
but
you
have
a
common
message:
that's
shared
amongst
them,
and
another
interesting
thing
to
note
here
is
this
piece
between
the
curly
braces,
which
is
injecting
information
from
our
rollout
spec
or
our
rollout
metadata.
Excuse
me,
and
it's
just
going
to
inject
the
name
of
the
rollout.
You
can
get
a
little
fancier
with
this,
but
we'll
keep
it
simple
for
this
demo
and
then
finally,
we
have
the
trigger.
A
So
this
is
a
trigger
called
on
purple
and
it's
going
to
be
sending
this
on
per
my
the
my
purple
template
that
we
just
configured
and
that
is
under
the
send
field
and
that's
going
to
be
sent
when
the
first
container
in
the
rollout
spec
template
is
set
to
a
rolex
demo.
Purple
image
so
like
alex
said
as
soon
as
that
statement
is
set
to
true
that's
when
that
notification
is
going
to
be
sent
so
yeah,
that's
all
there
is
to
it
there.
A
You
can
set
up
again
other
services
like
slack
or
telegram,
or
what
have
you
and
then
finally,
the
last
portion.
That's
important
is
this
email,
which
is
going
to
be
the
recipient
of
the
notification
all
right?
So
that's
all
we
have
to
do
to
configure
notifications
for
a
rollout.
It's
pretty
simple,
you
would
just
cube.
Ctl
apply
those
resources
or,
however
else
you
apply
manifest
to
your
cluster
and
you're
good
to
go.
So
let's
see
that
working
all
right.
A
A
B
A
B
We
wrap
up
the
demo
move
into
questions.
I
did
want
to
share
with
you
some
additional
information
and
I
will
use
slides
to
do
so.
All
right,
you
can
see
my
screen
so
awesome.
Basically
one
important
thing
about
argo
notification
engine
I
already
mentioned
it
before,
but
I
will
repeat
that
again.
So
the
engine
is
not
just
for
argo.
B
We
build
it
for
us
for
ourselves
and
we
consume
it,
but
it
has
pretty
much
nothing,
argo,
cd
or
argo,
rollout,
specific
or
workflows,
and
so
it's
perfectly
fine
to
use
it
to
enable
notification
and
get
the
integration
with
a
bunch
of
services
out
of
the
box
for
any
other
custom
resource,
and
here
are
a
few
links
that
you
can
use
to
to
try
it.
So,
of
course
you
will
need
it.
It
will
be
useful
to
navigate
to
our
quantification
engine
repository
and
read
the
documentation
and
as
soon
as
maybe
you're
interested
to
build
something.
B
You
can
check
this
example
that
supports
notifications
for
a
certificate
crd
of
search
manager
and
it.
Basically,
there
is
one
goldlink
file
that
has
pretty
much
everything
you
need
to
to
get
it
working,
and
so,
if
you
want
to
do
one
step
further,
then
just
go
get
github
argo
personification
engine
and
work
on
your
project,
and
this
is
it
thanks
for
listening
and
please
ask
questions.