►
Description
This is the weekly update for the Server Runtime SEG for the week of the 12th of December 2022
This week I've continued on the new technical path of using GA4K. Updates include:
1. Rails UI Updates
POC to start thinking about what the UI could look like
2. Authentication Sidecar Injection
A forked version OAuth2-Proxy is being injected that is responsible for both authentication and authorization
3. Repository Cloning
Able to clone the workspace with the oauth2 token and refresh the token when it expires
Chapters
0:00 Overview
1:23 Demo - New Workspaces Page
2:05 Demo - Workspace updates from agentk
2:42 Demo - Authentication and Authorisation
3:14 Demo - Repository Cloning
4:06 Whats next
A
Hi,
everyone
welcome
to
another
update
from
server
runtime
site
for
the
week
of
the
12th
of
December
2022.,
so
for
this
week,
I've
been
working
on
the
new
version
of
server
runtime.
So,
as
I
mentioned
last
time,
we've
been
a
change
in
technical
Direction,
I'm,
now
incorporating
all
of
server
runtime
into
gitlab
agent
for
kubernetes,
and
so
the
new
name
is
server
runtime
for
gitlab
agent
for
kubernetes.
That's
because
you
can't
have
enough
force
in
the
name.
A
You
know
I'm,
now
able
to
incorporate
all
the
spots
into
gitlab
itself
and
that
could
be
potentially
pretty
cool.
The
other
thing
is
I'm
automatically,
adding
the
sidecar
for
authentication
and
authorization,
so
that's
automatically
injected
into
the
workspace,
and
so
as
I
log
into
my
workspace.
If
I
don't
have
access
to
the
workspace,
I
won't
be
able
to
see
the
workspace.
The
other
aspect
that
I
Incorporated
this
week
is
repository
cloning,
so
automatically
any
private
repository
or
public
repository
would
be
cloned
with
your
credentials.
A
And
so,
when
you
push
up
that
repository,
it
will
be
automatically
pushed
up,
because
we
have
a
what
token
and,
as
you
log
in
again,
we'll
refresh
that
token
automatically.
So
that's
also
been
Incorporated.
So
with
that
I'll
go
straight
to
the
demo.
So
here
I've
got
a
workspace
with
sorry,
a
repository
with
a
def
file
and
now
I've,
already
sort
of
configured.
A
The
agents
and
things
like
that
to
the
agents
already
set
up
now
in
order
to
create
a
workspace
I
can
either
click
on
the
open
workspace
button,
which
will
take
me
to
the
new
workspace
screen
or
I,
could
go
to
the
workspace
screen.
I,
don't
have
any
workspaces
at
the
moment,
but
I
can
go
ahead
and
create
a
workspace.
A
Now,
when
I
get
to
the
screen,
automatically
I
can
select
a
ref,
so
I
can
go
ahead
and
select
a
ref
where
I
want
to
create
my
workspace
from
now.
There'll
be
other
fields
added
here
as
well
in
the
near
future,
but
I'm
going
to
go
ahead
and
just
say:
I'm
going
to
create
a
ref
from
the
sample
range
and
I
can
go
ahead
and
create
a
workspace,
and
that
should
start
provisioning.
Now,
one
of
the
things
you'll
notice
is
that
the
provisioning
status
directly
now
updates
here.
A
So
as
the
workspace
is
being
created
and
picked
up
by
Cass
and
gitlab
agent
for
kubernetes,
it
is
automatically
getting
processed.
So
now
you
could
see
the
workspace
is
running
so,
as
you
can
see
the
the
status
automatically
updates
now,
so
we
are
actually
sending
events
back
all
the
way.
When
you
create
a
workspace,
all
those
events
are
flowing
directly
back
and
you
can
see
the
status
whether
it
be
running
or
error
or
whatever,
so
that
you
can
see
straight
away.
A
So
now,
I
also
have
this
open
button
here
to
open
up
the
workspace
right
away
for
me,
so
I
can
go
ahead
and
click
that,
and
you
can
see
it
takes
me
to
oauth
proxy.
Now
this
we're
going
to
get
rid
of
the
screen
in
the
near
future.
I'm
going
to
go
ahead
and
sign
in
and
because
I
am
authorized
to
use
this
workspace
I
can
actually
sign
in
now.
A
If
I
were
to
actually
take
the
same
URL
and
you
know
open
it
and
log
in
with
an
unauthorized
user,
I
would
get
an
error
back
segment.
Hey
you
don't
have
access
right.
So
so
that's
basically
the
authorization
part
of
it
now
in
terms
of
the
workspace
itself,
I
can
go
ahead
because
we
are
doing
Auto
cloning.
Now
I
can
go
ahead
and
actually
open
up.
My
my
Repository
now
you
have
it
so.
My
repositories,
open
I,
have
access
to
the
files
in
the
repository
and
things
like
that.
A
You
can
see
them
automatically
logged
in
right,
so
the
or
token
then
next
time,
I
log
in
it
will
refresh
the
token
automatically.
In
addition,
I
also
am
on
that
particular
ref,
so
I'm
on
that
broad,
so
I
can
actually
see
code
specific
to
the
branch.
So
that's
it
for
this
week
for
next
week,
what
I'm
going
to
do
is
I'm,
going
to
primarily
work
on
how
to
start
stop
workspaces
more
interactions
from
the
UI.
So
that's
that's
the
plan
for
next
week.
Thank
you
for
listening.