►
From YouTube: Configure team meeting 2021-03-10
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
D
E
All
right,
sorry,
for
being
a
little
bit
late,
maria
it
looks
like
you
have.
You
actually
have
the
first
item.
E
Saw
more,
there
was
yeah
that
that
was
for
monday's
meeting.
I
moved
her
issue
up
to
today.
D
Okay,
so
I
have
redesigned
the
kubernetes
experience
and
I
wanted
maybe
to
share
share
with
the
team
design
the
redesign
so
that
we
have
a
an
early
discussion.
D
Also,
I
wanted
to
bring
up
that
it's
one
of
our
okrs
and
I
wanted
to
ask
victor
because
I
don't
know
when
the
end
or
anyone
who
knows
on
the
call
when
the
end
of
the
quarter
is.
C
Yeah
it's
the
next
question
starts
on
the
first.
C
D
So
we
have
a
milestone
and
a
half
to
complete.
Basically
this
issue
and
let
me
also
add
the
shared
okr
issue.
I
saw
that
we
need
to
complete
at
least
one
issue.
D
D
D
One
part
of
the
of
the
ui
that
doesn't
work
anymore
is
when
we
enter
this
area
for
two
reasons
or
three
one
is
purely
look
and
feel
it's
very
different
from
what
we
have
from
the
rest
of
the
system.
This
doesn't
affect
the
ux,
but
it
affects
our
ui.
D
Delight
second
reason
is
we
have
introductory
text
here
for
kubernetes
cluster,
but
we're
in
the
second
level
of
navigation,
so
it's
not
relevant
anymore,
and
the
third
is
that
we
cannot
really
go
back
to
the
agents
to
the
previous
screen
without
hitting
the
back
button
or
without
hitting
kubernetes
again
to
go
back
to
the
screen.
So
this
is
one
one
of
the
issues
that
I
would
like
to
fix.
D
The
other
issue
is
in
like
information.
Our
wording
here
is
not
really
good.
It's
not
very
clear
to
the
users.
One
of
our
internal
users
commented
and
don't
know
what
this
is.
What
do
you
mean
by
clusters
connected
with
certificate
or
integrated
cluster
with
certificate?
D
The
other
thing
is
that
we
represent
the
agents
as
clusters,
which
is
not
true.
D
We
have
two
solutions
here,
but
we
don't
really
have
an
intro
or
something
that
explains
to
somebody
who
doesn't
really
know
where
they
came
to
or
what
their
solutions
are,
why
they
would
use
the
cluster
solution,
why
they
would
use
an
agent
what's
the
one,
the
first
and
what's
the
latter.
D
So
these
are
the
three
main
categories
I'm
trying
to
fix
with
the
redesign
of
this
area,
and
then
there
is
a
fourth
item
I
have
proposed
to
fix,
which
is
the
docs,
but
this
is
outside
the
scope
of
this
presentation.
D
Nicer
sequence,
so
the
first
thing
I
did
towards
fixing
the
last
issue
that
I
mentioned
was
to
add
an
introduction
up
here,
I'm
taking
an
initial
stab
with
the
text,
but
I
will
work
with
marcia,
our
copywriter
and
victor,
and
if
anyone
has
any
feedback,
obviously
it's
always
welcome.
D
So
up
here,
I'm
trying
to
explain
what
our
two
solutions
are
and
what
you
can
do
with
them
in
the
next
level.
I
renamed
the
agent
I
first
I
introduced
agents
as
the
first
tab,
at
least
for
the
premium
or
gold
users
and
rename
to
kubernetes
agents.
We
can
drop
kubernetes
and
just
have
agents
so
that
we
don't
repeat
ourselves
so
again
copy
I'm
just
trying
my
best
and
then
here
I
created
an
intro,
mentioning
copying
from
docs
some
things
and
trying
to
explain
why
you
would
use
an
agent.
D
D
C
C
D
Okay,
so
moving
on,
so
this
is
the
experience
I
haven't
worked
on.
Yet
it's
the
next
thing.
I'm
gonna
work
the
installation
instructions
so
moving
to
the
clusters.
Again,
I
try
to
enhance
the
text
here,
but
I
would
like
maybe
even
more
enhancement
from
marcia
and
then
the
other
thing
I
did
here
was
to
split
the
connect
existing
cluster
and
create
new
cluster
experience
that
we
have
currently
in
the
form
of
tabs
up.
D
D
So
I
split
it
into
two
different
buttons
so
that
it's
clear,
where
you're
going
and
what
you're
doing,
and
also
to
remove
this
weird
level
of
hierarchy
we
have
on
the
next
page.
So
when
you
click
connect
existing
cluster,
that
takes
you
to
the
content
you
had
before
for
existing
cluster
without
the
tabs.
On
top.
D
And
then,
if
you
click
on
create
new
cluster,
which
I
added
as
a
secondary
action,
because
we
don't
want
to
promote
it
either
way,
it
takes
you
to
the
current
screen.
We
have
the
two
cluster
type
selection
with
a
few
visual
changes.
Just
these
buttons
are
wider.
Actually.
C
I
would
I
I
would
change
this,
so
go
go
back
one
more,
please
it's
the
two
actions
there
until
now.
So
what
we
know
is
that
the
create
new
cluster
is
a
rather
limited
functionality.
You
can't
customize
that
cluster
et
cetera,
et
cetera.
On
the
other
hand,
if
you
have
an
existing
cluster,
we
want.
We
want
you
to
use
the
agent
and
you
probably
want
to
use
the
agent.
C
So
for
this
reason
I
would
rather
recommend
to
have
the
create
new
cluster
being
the
primary
action
and
the
connect
existing
one
being
the
secondary
one,
because
it
probably
fits
better
our
users,
like
the
advanced
users
who
have
their
own
clusters.
We
want
them
to
use
the
agent
and
they
are
probably
looking
for
the
agent.
C
F
F
Yeah
regarding
the
tab
choices
use
like
tabs
tool
that
we
see
that
people
see
it
as
a
a
or
b
like
that
you're
actually
taking
an
option
there
and
deciding,
if
you're,
going
to
with
tab
a
or
type
b.
When
I
think
about
tabs.
For
me,
it
seems
more
like
some
things
that
are
unrelated
and
yeah.
You
know
what
I
mean:
you're
like
just
showing
the
first
step,
and
the
user
does
not
is
not
aware
that
there
is
an
alternative
way
of
connecting
clusters.
A
D
Up
here
I
agree
that,
but
we
don't
have
a
better
pattern
for
so
if
it
was
up
to
me,
I
would
split
these
two
into
different
navigation
items
here,
oh,
but
I
was
advised
for
now
not
to
do
that
that
they're
both
kubernetes
solutions,
so
they
should
sit
under
the
same
egg.
My.
F
Feeling
was
that
we
would
either
do
what
you
just
said,
like
I
split
into
different
things
or
have
some
kind
of
previous
view.
I
mean
this.
This
is
too
much
work.
This
already
looks
much
better
than
what
we
already
have
and
just
brainstorming
on
what
could
be
better,
but
then
I
was
thinking
it
would
be
nice
for
the
user
to
compare
solutions.
I
think
some
somehow.
F
D
A
D
B
D
B
D
C
My
idea
would
be
to
just
have
them
on
a
single
page,
actually
in
two
tables
and
then
even
the
add
new
button.
We
can
propose
the
agent
first
and
it
just
it,
can
just
have
the
this
drop
down
extractions
to
attach
something
to
the
certificate
or
create
a
new
cluster.
D
C
B
C
We
have
a
few
outliers,
though
so
we
have
one
german
university
that
has
ten
thousand
clusters
at
the
edge
and
those
might
be
in
ten
thousand
different
projects.
I
don't
know,
but
that
was
fun
to
find
in
the
data.
B
E
Yeah
a
question
so
so
like
if
I
use
the
agent
to
connect
to
my
kubernetes
cluster,
I
I
I
guess
like
I,
I
feel
like
we're
we're
setting
up
these
two
different
paths
of
managing
kubernetes.
But
if
I
use
the
agent
I
logically
have
a
cluster
already.
Will
that
show
up
under
this
cluster
section,
or
is
this
only
if
because
I
feel
like,
then
then
that's
automatically
confusing
right,
because
in
my
head
I
have
a
kubernetes
cluster
and
I
just
connected
my
agent
to
it.
D
E
It
right
now
we
don't
I'm
saying
in
the
future,
which
is
why,
with
this
ui,
if,
if
I
have
these
kind
of
pairing
of
like
okay,
this
is
two
different
ways
of
managing
kubernetes.
I
feel
like
it
needs
to
be
somehow
more
segmented
like
and
like
I
I
mean
like
right
now.
It's
like
they
share
the
page,
but
I'm
wondering
if
that
makes
sense
it's
like.
E
Would
it
make
more
sense
to
have
to
go
up
a
level
to
say,
okay,
this
is
this
other
way
of
managing
it
and
here's
my
clusters
does
that
make
sense.
Maybe
I'm
not
communicating
myself
very
well.
E
No,
that's
it's
fine!
Basically,
what
I'm
saying
is
that,
if
I'm,
if
I'm
using
kubernetes,
they
automatically
have
clusters
right
like
if
I
and
I
can
use
the
agent
to
manage
my
or
to
interact
with
my
kubernetes
clusters
right
and
so
here
we're
talking
about
how
git
lab
is
managing
it.
But,
logically
I
have
clusters
in
both
cases,
so
for
the
user.
I
think
it's
going
to
be
it's
like
it's
like.
We
need
a
way
to
segment
how
gitlab
is
managing
it
for
the
user,
because
I
have
clusters
in
both
cases.
E
D
F
I
agree
with
with
that,
and
I
was
even
thinking
the
same.
Why
don't
we
forget
about
this
idea
of
having
clusters
in
gitlab
and
have
only
connections
to
closer?
I
think
we
discussed
this
before.
Didn't
we
yeah
so
under
kubernetes
agents
we'll
have,
we
can
even
show
a
list
of
agents
that
connects
to
kubernetes
and
this
first
description
like
when
that
you
first
got
to
the
page.
F
You
you,
maybe
you
don't
want
to
say
creator
cluster,
but
rather
you
want
to
say,
connect
gitlab
to
your
cluster
and
then
you
have
two
options:
yeah,
we
do
provision
clusters
for
you.
If
you
want
that's
the
other
thing,
but
we
are
not
tracking
your
cluster
here
we
are
still
tracking
how
gitlab
is
configured
to
to
connect
to
your
cluster.
A
C
We
discussed
actually
this
was
maria's
original
recommendation
and
at
that
time
I
was
against
it.
If
I
remember
well,
but
I
just
wanted
to
propose
the
same.
D
So
is
my
note:
correct,
have
one
a
single
list
of
connections
to
clusters
and
then
we
have
type
of
connections.
F
F
Don't
know
gitlab
can
connect
to
to
your
kubernetes
cluster,
either
through
agents,
and
then
you
we
can
print
somewhere
like
the
the
what
the
user
will
get
from
it
either
you
can
connect
a
space,
sharing
your
api
certificate
and
so
on
and
so
forth.
Kubernetes
certificate
connection
or
gitlab
can
even
help
you
provision
a
cluster
and
to
if
you
don't
have,
if
you
don't
know
how
to
to
create
a
cluster
yourself,
youth
lab
can
provision
disclosure
and
keep
the
access
the
connection
through
a
certificate.
D
I
would
like
to
have
a
type
of
connection
columns
so
that
you
could
see
whether
you'd
certificate
merged
or
agent
managed
well
185.
However,
we
might
call
them.
A
A
D
D
C
C
C
F
C
C
C
D
C
I
have
one
proposal
that
we
learned
a
few
months
ago:
let's
go
back
to
low
fidelity
ideation
because
it's
probably
much
faster
and
then
the
two
of
us
or
you
alone.
We
could
create
three
four
different
variants,
with
even
with
whole
user
flows,
to
see
what
we
mean
and
then
it
might
be
much
clearer
for
us
as
well.
D
C
That's
not
that's
not
my
concern.
On
the
other
hand,
I
tried
to
add
this
to
the
to
doc
that
okrs
are
a
success.
If
we
manage
to
ship
65
to
80
percent
of
them,
or
something
like
that,
so
we
shouldn't
aim
400
percent.
We
want
to
shift
these
things.
If
we
get
to
a
point
where
we
are
already
working
on
them
and
the
quarter
ends,
I
would
I
would
be
totally
fine
with
that.
D
Okay,
also
in
terms
of
the
other
experience,
for
example,
install
an
agent
will
be
connecting
new
cluster.
I
mean
if
you
change
the
ux.
There
are
many
other
issues
as
emily
mentioned
that
are
interconnected,
so
I
would
appreciate
yeah
I
can
go
back
to
low
fidelity,
but
we
can
all
give
it
some
thinking
about
how
we
want
the
ux
to
be
here,
because
you
are
the
users
and
just
the
means
to
design
the.
B
You
can
also
try
to
take
a
step
back
and
not
even
go
design
and
just
make
sure
that
the
workflows
from
text
based
click
this
go
to
this
go
to
this.
If
I
need
to
go
to
this,
how
do
I
get
there?
What's
that
workflow?
If
I
need
to
go
to
this,
how
do
I
then
get
there,
because
that's
what
it
sort
of
seemed
like
emily
was
getting
at
was
paths.
You
know
if
we
do
this
as
a
table,
and
you
click
on
this.
B
C
So
I'm
going
to
intervene
now
because
we
are
over
time-
and
I
don't
want
to-
I
want
to
respect
everyone's
time
here,
so
I
have
to
do
this
anyway
and
if
I
leave
and
don't
give
over
the
hosting
host
to
someone
else,
then
the
meeting
will
be
over.
So
I
joined
first
and
there's
very
overtime.
I
would
recommend
to
to
continue
this
discussion
different
way.
Sure.