►
From YouTube: Distribution Team Demo - Dec 10, 2020
Description
The Distribution team demos using gitlab pages with a in-progress MR deployed within the gitlab-helm chart. With self-signed certificates.
A
A
A
So
this
is
my
basic
self
sign
and
we're
going
to
install
this
without
pages
support,
and
while
that
runs
so,
let's
just
say,
I'm
a
customer
and
what
I'm
gonna
assume
is.
I
have
no
idea,
I'm
using
the
charts,
because
someone
said
kubernetes
kind
of
like
the
the
good
old
cartoon
right,
the
dilbert
cartoon,
so
once
they're
too
ready,
so
I'm
gonna
try
it.
So,
according
to
this
documentation,
I
need
to
bring
a
wildcard
certificate
and
I
saw
that
in.
A
A
A
A
A
A
B
A
A
E
B
A
A
A
D
A
D
A
A
E
A
A
A
A
A
E
A
Yes,
I
do,
I
did
it
the
first
time
I
typed
it
in
the
wrong
path,
brains,
all
right,
so
that
running
you
now
see
the
pods
are
running
so
just
to
recap,
where
we're
at
we
have
modified
and
adapted
the
generate
certificates,
wild
card
service
from
what
I
know
to
be
from
the
getaway
service,
but
what
someone
would
use
to
if
they
were
just
coming
into
this
new.
We
have
built
our
wild
card,
self-signed
secret
and
added
it
to
kubernetes,
and
now
we
are
trying
to
install
pages.
E
A
A
A
A
D
E
E
A
A
That
is
a
deep
should.
I
saw
something
similar
the
other
night
that
I
noted
when
testing
the
upgraded
engine
and
ingress
going
from
version
0.20
to
0.41.2,
where,
if
there's
a
deep,
if
there's
enough
of
the
change,
all
the
pause
for
the
web
service
will
just
stop
responding
as
opposed
to
rolling
over
like
I
would
have
expected.
E
E
E
F
B
E
A
D
A
A
A
B
D
G
G
A
A
A
G
G
E
A
E
E
G
A
A
B
E
E
E
E
E
E
E
H
H
F
A
E
E
F
A
B
A
B
E
A
E
E
F
F
A
A
A
So
I
think
that
overall
I'll
declare
this
in
working
most
of
the
issues
encountered
were
just
typical,
systematic
I'll
think
on
whether
or
not
that
would
be
something
that
we
could
translate
to
think
about,
whether
to
translate
back
to
things
that
we
can
document.
That
would
be
a
follower
to
this,
not
part
of
this
overall,
though
quite
successful
stuff
went
in.
Is
there
anything
else
you
want
to
kick
the
tires
on?
E
A
A
A
A
E
A
E
C
E
E
E
E
E
E
E
F
E
E
E
E
E
E
Why
does
this
matter?
You
might
ask
architecturally
speaking.
The
way
pages
used
to
work
is
that
you
would
actually
write
this
into
the
file
system
somewhere
and
then
pages
would
serve
from
the
file
system.
Hence
pages
couldn't
work
in
cloud
native
due
to
the
nfs
requirement
when
they
moved
to
doing
this
through
artifact
storage,
they
initially
took
it
and
instead
of
literally
taking
the
output,
bundle
sticking
in
artifacts
and
then
sidekicks
comes
along.
It
pulls
the
artifact
down,
extracts
it
and
writes
it
to
the
file
system.
A
E
E
G
E
E
It
doesn't,
we
don't
have
a
way
to
load
extra
tls
certificates
into
it
and
it
would
actually
turn
around
and
go.
I
can't
serve
https
on
this
because
I
don't
have
a
certificate
for
it
and
it
would
go
back
to
its
default
one
and
then
you'd
get
a
complaint
like
self-signed,
nginx,
ingress
or
kubernetes
ingress
doesn't
match
the
hostname,
so
we
actually
have
to
do
that
in
the
next
stages
to
actually
make
it
possible
to
serve
https.