►
From YouTube: License Secret Name, backup/restore, xtail 2020-07-30
Description
Docs feedback: License Secret Name: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2231
backup/restore of Git LFS objects broken: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2072
Proposal - state of the art logging: https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2098
A
A
The
second
is
going
over
an
issue
that
we
didn't
prioritize
enough,
but
we
have
now
jumped
and
immediately
fixed
and
released.
The
patch
4
on
the
latest
container
sets
we'll
probably
confirm
back
port
of
that
to
previous
versions
very
soon,
and
also
one
proposal
from
the
community
to
have
a
json,
structured
logging
format
from
all
of
our
containers,
through
essentially
a
extail-like
wrapper
program.
A
A
A
A
A
A
A
By
default,
the
setting
is
also
paired
with
the
license
secret
key,
but
that
is
set
to
license
when
not
provided
now
our
documentation
on
creating.
That
does
actually
say
that
you're
expected
to
do
from
file
equals,
license
equals
file
bath,
and
what
that
does
is
specifically
create
that
specific
key
with
that
specific
content,
if
you
were
to
skip
the
equals
license,
equals
just
go
with
equals
file
path.
A
So
I'm
going
to
come
up
here
and
I'm
going
to
install
421
in
particular,
it's
a
release
version,
but
now
I
don't
have
to
reinstall
twice
to
go
on
the
next
item.
So
I
have
I'm
installing
four
two
one.
I
have
my
base
configuration,
I'm
including
the
thing
for
the
next
issue.
We're
going
to
review
and
then
I've
got
a
configuration
file
for
my
license
itself.
A
A
A
A
A
A
A
A
A
A
A
A
A
So
it
looks
like
the
documentation
works
as
described
unless
this
particular
person
ran
into
an
issue
where
they
didn't
create
the
secret,
with
the
key
name
being
licensed
or
and
thus
need
to
actually
specify
key.
But
it
doesn't
quite
line
up
to
what
they've
said
where,
as
soon
as
they
renamed
it
to
get
lab
git
lab
license.
It
worked
fine.
A
A
A
A
A
A
A
A
A
This
was
filed
some
time
ago
back
in
may
and
we
did
not
specifically
test
all
the
way
down
to
the
root
of
it.
We
actually
asked
that
another
team
take
it
up
after
seeing
multiple
folks
come
along
and
say,
I'm
seeing
this
too.
I
went
ahead
and
jumped
it
to
find
out
what
was
going
on.
My
investigation
can
be
found
inside
of
the
issue.
A
A
As
long
as
you
have
a
single
item,
you
won't
run
into
an
issue,
but
when
it's
a
directory
it
will
take
the
contents
under
that
directory
and
place
it
into
the
destination.
If
that
too
is
a
directory,
so
we
actually
have
to
tell
it
the
door
name.
That
is
the
content
into
because
of
the
nature
of
how
we're
making
this
call
to
upload
to
object.
Storage.
A
A
A
I
say
this
in
such
a
way
because
for
those
in
which
we're
using
exhale,
primarily
site
kick
and
web
service
at
this
time
you
get
this
giant
flood
of
all
their
content.
Some
of
them
are
structured,
some
of
them
are
not,
and
it's
essentially
unparcelable
by
some
of
the
upstream
consumers
of
those,
even
our
own
production,
has
a
couple
issues
once
in
a
while
and
dealing
with
that.
So
I'm
going
to
jump
into
one
of
these
containers
jump
into
the
web
service,
so
the
rails
web
server
itself
and
I'm
going
to
download
the
file.
A
A
What
I'm
saying
is
this:
is
such
a
small
and
effectively
self-contained
drop-in
replacement
for
tail
or
exhale.
We
can
do
this.
This
is
a
stopgap
methodology
towards
structured
logging
that
helps
both
our
consumers,
as
well
as
our
own
infrastructure,
as
well
as
allows
us
to
put
the
exact
same
functionality
inside
of
the
ubi,
because
that's
one
thing
we
don't
actually
quite
have
in
the
ebi
is
because
extail
is
not
natively
present
within
the
repositories
there.