►
From YouTube: UX Showcase: Configure Scorecard for Kubernetes agents
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Hi
everyone,
my
name
is
ali
and
I'm
a
product
designer
on
the
configure
team
and
today
I'll
be
talking
about
a
ux
scorecard
that
I
did
for
configure
and
the
journey
that
I
had
and
some
of
the
lessons
that
I
learned
along
the
way
so
I'll
be
talking
about
the
tasks
that
were
involved
the
scorecard
itself
and
why
I
gave
the
experience
a
ac,
some
of
the
things
I
learned
about
kubernetes
and
that
I
felt
I
should
share
and
also
while
I
was
interacting
with
you
know,
information
about
jobs
to
be
done.
A
I
also
came
across
something
about
strategy
and
it
led
to
a
conversation
with
my
pm.
I
wanted
to
share
a
bit
about
that,
and
also
some
of
the
learnings
that
I
had
how
I
learned
about
jobs
to
be
done
just
having
joined
git
lab
and
also
how
I
got
to
learn
about
kubernetes.
A
Cool,
so
the
jobs
to
be
done
that
I
had
was
relates
to
priyanka
and
it's
it's
on
our
it's
on
our
direction,
page
for
kubernetes
management,
and
essentially
you
know
I'll
read
it
here.
It
says
I
have
a
new
version
when
I
have
a
new
version
of
my
of
my
application,
I
want
to
deploy
it
into
production
following
my
preferred
deployment
strategy,
so
that
I
can
reap
the
fruits
of
my
work
and
can
celebrate
success.
A
I
know
it
sounds
weird
as
a
job
to
be
done
and
it's
something
that
I'll
I'll
touch
on
later,
but
essentially
this
this
scenario,
a
typical
scenario
would
be
and
the
the
persona
that
would
be
where
that
I
was
working
with
was
priyanka
and
that's
the
platform
engineer
and
whenever
she-
and
in
this
scenario
she
is
managing
application
and
configuration
deployments
using
kubernetes
and
essentially
she
she
wants
a
way
to
manage
these
deployments
and
typically
they
are
across
multiple
projects.
A
So
an
agent
is
something
that
you
know
brings
in
efficiency.
A
The
tasks
that
I
had
to
do
and
in
preparation
for
this
evaluation.
Firstly,
I
had
to
create
a
cluster
and
which
involved
having
a
google
cloud
account,
and
I
mean
today,
enterprises
use
different
cloud
providers,
I'm
not
yet
at
the
stage
where
I
can
do
multi-cloud
deployment,
but
it's
something
that
that
I
would
love
to
do
quite
soon,
so
that
I
can
work
in
the
customer's
shoes.
A
And
the
next
thing
that
I
had
to
do
was
go
into
gitlab,
create
a
project
and
then
connect
an
agent,
the
agent
that
I
created
to
the
cluster
and
then.
Thirdly,
I
had
to
deploy
and
scale
a
demo
demo
application.
A
So
typically,
you
can
use
two
methods,
there's
git
ops
and
the
cicd
method.
But
for
this
evaluation
I
used
the
githubs
method,
which
is
something
that
a
lot
of
organizations
are
exploring.
So
I
I
wanted
to
try
that
first
so,
which
resulted
in
the
scorecard
that
we
have
in
front,
so
I've
always
wanted
to
make
a
scorecard.
I
was,
I
was
envious
of
my
teachers
whenever
they
would
make
scorecards
so
I've.
A
I
felt
a
little
bit
like
that
when
I
was
making
this
card,
and
essentially
I
took
the
heuristics
that
we
have
in
our
in
our
handbook
and
the
the
three
men.
A
They
are
divided
into
three
main
areas,
which
is
usability,
desired
characteristics
and
onboarding,
and
I
took
each
heuristic
and
and
and
gave
it
a
score,
and
when
I
contrasted
this
with
the
map
that
I
had
made
in
mural,
the
same
areas
that
I
gave
a
low
score
were
the
same
ones
that
had
a
negative
experience
on
on
my
map,
which,
which
visibility
of
the
systems
the
system
status.
So,
as
you
can
see
from
the
tasks
that
I
had
to
do,
I
was
working
across
multiple
systems.
A
So
when
I
did
a
deployment
in
when
I
did
a
deployment
in
my
in
my
project
in
my
repo,
I
was
not
able
to
see
what's
happening
inside
my
cluster,
which
is
on
google
cloud.
I
had
to
use
a
third-party
tool,
so
that
was
one
of
the
things
that
immediately
stood
out
for
me.
So
any
mistake
or
anything
that
I
had
to
do.
I
had
to
leverage
a
third-party
tool
in
between
and
then
one
of
the
other
problems
that
I
ran
into
sorry
about.
A
That
was
the
documentation,
so
the
documentation
was
not
up
to
date
with
what
is
on
the
ui
to
what
is
on
the
user
interface
today,
and
also
some
of
the
instructions
where,
where
were
hard
to
follow,
and
they
also
referenced
an
an
old
version
of
the
ui.
So
those
were
the
two
immediate
areas,
and
so
my
ra,
the
recommendations
that
I
arrived
at
were
mainly
based
on
these
on
on
these
three
areas.
So
one
of
the
recommendations
was
of
improving
the
docs.
A
The
second
one
was
providing
something
around
visibility
of
the
process.
So
when
I
make
a
change,
when
I
connect
my
agent,
how
how
can
I
see
that
that's
actually
happening
in
my
cluster,
whether
I'm
using
any
any
any
cloud
provider
and
also
the
third
recommendation,
was
around
something
that
I
had
seen
in
in
the
google
cloud
docs.
A
So
in
the
google
cloud
docs,
if
they
give
you
like
a
a
code
snippet
that
you
need
to
paste
somewhere,
they
will
actually
show
you
that
the
part
that
you
can
edit
and
you
can
edit
it
in
their
docs
before
you
paste
it
on
your
ide
or
or
or
terminal
so,
which
I
thought
was
a
cool
feature
that
could
speed
up
installation.
So,
though,
my
recommendations
were
around
those
those
three
main
areas.
A
However,
you
know
I
do
use
this
scorecard
as
a
way
to
know
some
of
the
shortfalls
that
we
have
in
configure,
and
there
are
some
issues
that
are
related
to
improving
some
of
these,
but
yeah.
We
will
be
revisiting
this
experience
soon.
So
what
did
I
learn
about
kubernetes?
A
So
I
learned
that
you
know:
kubernetes
is
quite
complex,
so
being
someone
who
studied
supply
chain,
I
use
issue
trees
to
you,
know,
simplify
complex
information,
and
you
know
the
first
time
I
came
across
kubernetes.
I
knew
that
this
is
something
that
was
complex
but
after
having
learnt.
A
A
lot
of
things
about
it,
I
was
able
to
distill
it
into
this
issue
tree
and
the
the
the
three
main
areas
that
constitute
kubernetes
management,
orchestration
monitoring
and
thirdly,
security,
and
you
can
see
within
each
one.
A
There
are
also
many
things
to
consider
and
what
what
helps
me
with
this
issue
and
why
I
I
I
I
wanted
to
utilize
it
is
that
you
know
it
also
helps
me
as
the
basis
to
know
which
teams
I
can
also
collaborate
with,
especially
on
some
of
the
things
that
are
important
for
kubernetes
management.
How
how
can
we
make
make
you
know
some
of
the
jobs
to
be
done
more
more
seamless
by
leveraging
what
we
have
inside
the
gitlab.
A
So
you
know
back
to
the
jobs
to
be
done
that
I
spoke
about
in
the
in
the
in
the
in
the
beginning.
You
know,
after
speaking
with
by
pm,
you
know
we
both
agreed
that
our
jobs
be
done
and
need
some
work
and
obviously,
with
the
vision
we
have
for
kubernetes
was
still
at
the
very
beginning.
A
You
know
one
thing:
I
realized
that
the
agent
itself
is
just
a
small
part
of
the
of
of
the
whole
picture,
and
I
mean
there's
two
pieces
that
we
want
to
research
about
and
and
and
solutions
that
we
want
to
validate
for
a
lot
of
these
overlapping
areas,
and
you
know
there
are
many
point
solutions
for
a
lot
of
the
problems
that
are
seemingly
there
about
kubernetes.
A
But
I
was
asking
my
manager,
you
know
how
well
do
we
want
to
do
kubernetes
management
like
do
we
want
to
be
the
the
number
one
tool?
Those
were
some
of
the
things
that
I
was
probing
him
with,
and
you
know
he
he
said.
Definitely
we
you
know
we.
A
We
want
to
be
the
number
one
tool,
and
then
I
I
showed
him
this
article
that
I
came
across
by
tony
alweg
and
hit
he
talks
about
how
the
degree
to
which
you
perform
a
certain
job
determines
well.
He
makes
the
assumption
rather
that
the
degree
to
which
you
perform
a
job
determines
your
product
positioning
and
therefore
your
product
strategy,
and
knowing
that
we
want
to
do
the
kubernetes
management
job
to
be
done.
A
Well,
I
assumed
that
you
know
before
I
rather
proposition
to
my
manager
that
we
fall
within
the
dominant
strategy,
which
is
a
situation
where
you
want
to
win
underserved
and
oversame
overserved
customers,
so
people
who
are
just
at
the
beginning
of
their
kubernetes
journey
and
people
who
you
know
have
been
using
kubernetes
for
years
so
which
is
a
something
that
is
hard.
But
then
it
also
you
know,
made
us
to
think
about.
You
know,
instead
of
trying
to
do
all
these
things.
A
Well,
how
could
we
also
leverage
integrations
and
still
get
the
job
to
be
done
well,
but
to
use
gitlab
as
the
con
as
the
converging
point
so
yeah?
A
It
was
really
interesting
to
see
how
jobs
to
be
done,
can
influence
strategy,
so
an
understanding
jobs
to
be
done.
I
want
to
thank
andy
for
recommending
that
I
read
the
job
to
be
done.
Playbook.
I
think
I
it's
something
I
can't
recommend
enough
for
all
of
us
as
designers
yeah
it.
It
really
leveled
me
up
as
a
designer
and
yeah
just
a
recommendation
there
and
then
in
terms
of
learning
kubernetes.
A
It's
something
that
I
struggled
with.
You
know
when
I
talk
to
some
of
my
friends
who
are
who
are
developers,
some
of
them
don't
even
know
about
kubernetes,
so
it's
really
like
high
high
order
stuff
and
it
led
me
down
a
journey
to
try
and
tackle
some
of
my
learning
difficulties
and
I
came
across
something
called
bloom's
taxonomy
and
I
I'd
like
to
recommend
it
for
anyone
who's
a
designer
that
needs
to
learn
hard
stuff
really
quickly.
It's
a
it's.
A
A
great
way
to
you
know,
approach
hard,
hard
problems,
I'm
still
filling
in
the
gaps,
and
I
hope
to
make
it
more
more
issues
that
I
that
I
can
share
with.
You
know
the
research
that
I'm
I'll
be
doing
as
as
part
of
my
next
steps,
so
as
part
of
the
next
steps
will
be
we're
currently
conducting
jobs.
We've
done
research
around
kubernetes
management
and
yeah.
That
is
my
journey.
In
a
nutshell.