►
From YouTube: SIG Apps Biweekly meeting 20200629
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
Welcome
everyone
to
kubernetes
igg
apps
for
Monday
June,
29th
2020
ma
che
thanks
for
dropping
the
link
into
chat
to
the
agenda.
You
beat
me
to
it.
We
only
have
one
thing
on
the
agenda
today
and
that's
a
demo
if
somebody
else
has
another
thing
that
they
want
to
add
to
the
discussion
for
today.
Please
go
ahead
and
add
it
into
the
open
discussion
area
and
we'll
get
to
it
after
the
demo,
Remis
I
see
you
online
I.
Take
it
you're
the
one
whose
demo
this
is
yes,.
A
C
A
B
Okay,
then
chat
Center.
Let
me
start
from
am
UI
first,
because
I
know
it.
Some
part
is
more
interesting
part
as
well.
So,
as
you
know,
don't
shut
the
up
very
missed.
One
thing:
you
can
use
a
central
repository,
you
still
you
can
search
and
devorah
will
do
many
things,
but
you
cannot
point
some
client
and
use
almost
200,
whatever
+.
B
How
many
positive
is
hacker,
so
a
gift
for
community
become
for
last
5
months.
Your
building
chart
Center
because
I'd
recommend
before,
but
now
we
became
chart
Center
and
okay.
First,
it's
a
Central
Depository.
You
can
point
it
chart.
Center
and
all
200
plus
upholstery
are
available.
So
what
we
do
we
check
for
repo
llamo
on
home
hub,
pull,
Idris
upholsteries
and
if
our
new
ones,
you
add
them
as
well
and
as
always,
to
support
adding
pulled
across
as
well
directly
to
chart
Center.
So
let
me
share
their
a
sorry
how
it
works.
B
B
B
So
it
found
two
charts,
so
we
can
pull
them
one
chart.
Of
course.
Now
it
will
pull
Postgres
one
cold.
So
that's
basically
just
taxing
in
space.
We
have
we
still
keeping
the
repository
name
and
the
chart
name
and
that's
basically
from
a
client
side.
The
index
file
is
a
bit
modified
and
it
took
some
keywords.
Material
sources
so
make
it
smaller,
because
the
rise
is
too
big
to
handle
children,
plots
of
all
the
trees
and
I
think
we
have
almost
39,000
charts.
B
B
Well,
information
of
a
chart
to
behavior
chin
up
version,
Oh,
dr.
feyten
good,
now
loud
humming,
the
love
to
God
how
to
set
up
at
the
center
next
interesting
thing
get
chucked
in
for
used
by
if,
okay,
let
me
change
think
I'll
be
using
this
one
so
use
by.
So
there
are
couple
sharks
which
are
using
that
both
great
so
dependencies.
Yes,
we
see
Susan
docker
image
and
the
chef
is
triangle
hi,
so
basically
sharing
critical
issues
as
well.
Dr.
images
when
I
go
deeply,
you
can
go
to
security.
B
You
get
series.
The
list
you
can
cut
a
graph
part
is
impacted
that,
like
that
and
see,
hi
is
not
shown
because
this
chart
doesn't
have
oh
yeah,
so
we
added
a
new
thing:
security
mitigations.
So
basically
you
can
write
a
notes
or
for
SAV
and
explain
why,
how
what's
happening
and
when
you
don't
share
Affairs,
it's
a
good
medication.
Jemelle
file,
including
a
chart
they
are
high,
is
disabled.
B
So
let
me
go
back
to
used
a
sheet
credit
their
demo
chart
for
that
you,
it's
using
cruel,
aggressive
girl,
so
dependence
again,
so
we
CHF
Postgres
have
go
application
showing
some
go
long.
112
point
was
the
mystical
issues
and
if
I
go
to
security,
now
again,
it's
I
see
series
AC
highly
because
I
did
add
to
communication
notes
like
here
and
applies
to
that
city
below
equals
to
a
tradition
too
high
acute
issue
and
AG.
You
can
explain
what
exactly
is
variation.
B
I
think
I
said
it's
just
simple:
nice
UI
protection
which
feature
charts.
Will
you
like
to
share
them
yeah,
so
to
add
a
chart
just
hope.
We
just
go
to
our
chart
Center
or
J
frog
on
github.
You
can
open
your
pull
request
very
similar
to
home
hub
llamo
file.
You
are
the
repository
and
you
like
the
post.
It
will
be
accepted
small
checks
to
catch
a
roadmap.
B
Public
road
map,
the
only
one
thing
we
have
week,
because
the
limits
are
some
client
to
or
treaters
model
doesn't
count
package
doesn't
support
extra
namespace.
So
you
can
cannot
reference
dependency,
charts
in
a
chart
center,
but
the
plug-in
listing
networks.
So
the
plug-in
will
be
able
to
pull
that
dependency
charts
for
the
chart
center
and
especially
shown
to
will
tell
me
the
plugin,
even
if
they
do
compare
to
get
fixed
for
country
but
come
to
doesn't
suck
two
things
though
the
plugins
can
be
used
by
from
two
guys.
Think.
That's
it
from
my
side.
A
B
So
all
our
process
explained
here
so
basically
yeah.
We
have
an
example
here.
So
basically
the
other
file
colloquy
is
called
security,
McGee
medication
like
llamo
and
you
against,
play
our
CD
East.
It
could
be
doctor
level,
chart
level,
medication
notes
and
I
created
security
example
chart
basically
to
learn
where
things
community.
B
We
really
happy
to
be
getting
communicate
involved.
It's
a
communication
because
that's
very
important
show
security
issues
and
again
it
will
depend
on
the
chart.
Making
your
given
act,
explain
X,
high
secret
issues
or
not
how
I?
Just
you
don't
explain,
only
media
months
will
be
shown
or
less
Soho
transportation
so
stuff
like
that.
B
B
B
Up
to
you
that
we
kind
of
control
that,
but
at
least
whatever
comes
through
the
chart,
we
show
you
can
because
they're
using
called
a
broker
products
at
the
factory
x-ray
to
host
two
Jewish
security
issues.
So
it's
a
as
well
we're
not
hiding
our
issues
for
our
products
or
we
totally
transparent
the
hope
committee.
We
transport
as
well,
that
you
have
Prada,
because
even
if
you're
looking
to
progress
from
the
geometry
have
load
of
issues
and
their
love
that
many
child
doing
that,
so.
A
B
Really
it's
J
for
thing
basically
just
drink.
It's
not
different!
If
you
are
be
that
part
of
a
UFO
story,
chart
in
this
case
will
be
processed
the
chart
Center,
we
hope
community
my
adopted,
because
it's
not
really
for
j4e
working
for
community
I'm.
Talking
me
I
mean
community
team
you're,
not
making
money
for
it's
totally
free,
probably
no.
A
B
E
D
E
Like
to
add
few
things
so,
which
is
where
we
kept
the
format,
a
very
generic
like
affected
package,
URI
or
cloud
native
to
begin
with,
we
are
starting
with
Whitaker
and
helm,
and-
and
this
is
something
which
we
saw,
which
is
lacking
the
camry.
There
is
no
way
to
easily
exchange
security,
information
between
producers
and
consumers,
and
and
and
and-
and
this
is
something
that
we
are
not
only
collecting,
but
it's
something
that
we
allow
others
to
proxy
as
well.
E
A
C
If
it's
definitely
I'm
not
gonna
happen
that
fast,
but
I'm,
hoping
within
the
next
couple
of
weeks,
we'll
be
able
to
put
together
a
PR
and
set
it
out
to
the
sig
ass
mailing
list
for
general,
with
you
sweet
so
that
you're,
targeting
like
maybe
120
yeah
120,
is
definitely
something
that
we
want
to
go
for,
at
least
as
the
at
the
alpha
I'm
pretty
sure
that
there
will
be
some
positional
things
that
will
come
up
as
we
go.
But
I
would
like
to
get
the
initial
version
for
120
on.
D
F
I,
don't
need
to
check
with
him
to
see
was
his
point
is
I.
Think
and
currently
his
PR
is
being
blocked
by
some
API
reviews.
D
C
C
Yeah
for
cron
job
yeah,
okay,
even
for
even
from
what
I
was
looking
at
the
time
frames
and
based
on
the
discussion
that
we
had
in
the
past.
We
will
still
have
to
move
the
clock
for
all
four
cron
jobs
through
making
V
1
beta
2,
and
the
reason
for
that
is.
If
I
remember
correctly,
the
clock
is
set
to
expire
in
1:20
to
be
to
remove
in
122,
which,
given
that
we
will
be
doing
the
alpha
beta
and
only
after
g8,
we
might
run
out
of
time.
C
D
Plan
that
you
might
consider
is
this
if
you're
gonna.
So
if
your
plan
is
to
start
with
an
alpha
version
for
the
new
controller
and
then
promote
that
through
beta,
you
could
just
do
a
V
1
beta
2
for
that
promotion
anyway,
and
then
deprecated
b---one,
b---two
1
and
promote
V
1
beta
2.
Did
you
hear
that
might
not
be
as
people.
C
D
Will
get
interesting,
the
ideal
path
would
be
to
go
up
through
the
API.
Maybe
evolutions
for
B
1,
B,
2
1
and
then
like
basically
have
the
new
controller
ready
migrate.
The
J,
without
requiring
two
steps,
I
mean
I.
Think
if
we
were
asking
for
a
variance,
if
we're
very
close,
did
you
say
look?
Can
we
not
make
all
users
have
to
upgrade
through
a
deprecated
API
to
get
the
GA.
G
C
C
Yeah
but
then
still
that
means
that
well
so
within
119
you
are
basically
using
a
deprecated
API.
C
D
C
D
Going
to
say
that,
like
you
know
the
forcing
function
so
I
would
say
from
from
the
from
the
perspective
of
having
a
portion
function
to
make
his
GA.
They
can
call
that
a
success
because
we
moved
towards
GA
and
also
we
can
take
the
best
interest
of
users
into
account.
So
that
I
mean
that
feels
like
something
that
can.
You
did
even
probably
get
by
and
I.
C
The
interaction
with
the
in
farmers
not
from
the
rest
of
the
functionality,
and
we
will
definitely
not
be
addressing
any
future
development
within
that
time
frame,
because
that's
not
what
I
want
to
do.
I
want
to
g8
what
we
have
currently
and
only
one.
We
have
a
stable
GA.
All
we
can
think
about
adding
additional
stuff
that
people
and
a
half
there
yeah
it'll
be
just
simpler
and.
A
That
makes
sense,
I
was
just
gonna,
say
the
going
from
the
the
beta
one
cron
job
straight
to
GA
from
an
end
user
interface
right,
because
all
this
other
stuff
with
scaling
and
informers-
that's
that
is
targeting
a
more
of
a
niche
market.
A
lot
of
people
use
cron
jobs
today,
the
way
they
are
and
if
they
have
to
jump
to
another
beta
and
then
GA
that
adds
more
work
to
them.
A
D
D
The
other
thing
there
is
a
top
of
the
thing
for
next
week.
Do
we
want
to
discuss
this
Bluegreen
strategy
for
deployment.
D
D
D
Forget
the
name
of
it
but
flux
also
had
a
product,
a
bit
advanced
rollout
strategies
with
the
greens
and
Canaries
the
the
requestor
is
asking
us
to
consider.
Taking
that
functionality,
that's
been
prevalent
in
the
community
and
kind
of
standardizing
it
because
and
I
think
the
their
thesis
is
it
like.
You
know
there
are
third
part,
a
lot
of
third
parties
and
controllers
that
do
it.
Maybe
it
should
be
done
in
a
standard
way.
D
It's
like
a
native
serving
has.
Some
of
this
functionality
are
garou,
like
rollout,
has
some
of
it
they're
they're
tools
that
perform
canary
updates,
including
analysis.
Some
of
the
spinnaker
functionality
tries
form
Canaries.
My
actual
thought
is
kind
of.
Like
you
know,
I,
don't
see
why
we
would
need
to
take
that
into
the
built-in
types,
but
I
think
it's
worth
at
least
a
broader
discussion.
C
And
that's
definitely
one
tier
discussion
and
+12
to
have
it
a
further
discussion,
but
I
would
like
to
really
eat
down
the
future
request.
First,
before
stating
anything.
A
C
D
I'd
like
to
schedule
scrub
for
next
or
next
time
as
well,
all.