►
Description
Google Summer of Code (GSoC) is a global, online program focused on bringing new contributors into open source software development. GSoC contributors work with an open source organization on a summer programming project under the guidance of mentors. GSoC contributors accepted into the program work on projects to improve or enhance the Keptn project and its ecosystem.
1) Entity CRDs for Keptn GitOps, by Eric Y. Kim. This project implements the remaining Keptn entities as Kubernetes Custom Resource Definitions to shift more of Keptn's components towards a GitOps workflow. As a result, users will be able to configure these entities via PRs to a configuration repository or manage them directly using the Kubernetes APIs.
2) New documentation Site Engine, by Rajiv Singh. This project is about a New Documentation Site Engine for Keptn which can handle a large number of documentation projects of Keptn. The new Documentation Site engine will be based on Docusaurus. Two major things which are needed in the documentation engine are the ability to build the documentation from the source located in multiple repositories and support for document versioning.
More about Keptn in GSoC and the projects: https://github.com/keptn/community/tree/main/mentorship/gsoc
B
B
E
C
C
C
C
So
just
quickly
get
started,
and-
and
I
don't
and
again
I
I
don't
really
want
to
like
go
super
in
depth
to
any
of
these.
I
guess
like
core
concepts
just
because
I'm
I'm
not
I'm
definitely
not
an
expert,
but
I
do
think
it's
worth
going
over
just
because
it
is
very
relevant
to
to
what
I'm
building
so
just
to
start
with,
like
kubernetes
custom
resource
definitions.
C
I
mean
I
say,
custom
resource
definitions,
but,
like
I'm,
showing
kind
of
three
different
things
here
on
the
left
is
the
custom
resource
definition
on
the
right
top
right.
You
can
kind
of
see
a
custom
resource
as
well
as
the
bottom
right
is
a
controller
that
reconciles
the
state
based
on
the
customer's
voice.
So
really
we're
talking
about
at
least
for
my
project
and
and
for
the
current
poc.
C
Another
really
important
component
obviously
is
get
ops
once
again.
I
this
is
not
a
meme
that
I
made.
This
is
one
that
I
found
online.
I
thought
it
was
funny,
so
I
included
it
here,
but
essentially
I
guess
some
important
components
of
git
ops
is
like
these
principles,
and
this
is
kind
of
taken
from
weave
the
source
on
the
bottom
right.
C
So
here
we
can
see
that,
like
for
principles
of
git
ops,
the
entire
system
is
described
declaratively
and,
as
you
saw
in
like
the
kubernetes
resources,
that's
also
the
case
with,
like
our
custom
resources
and
the
definitions,
we
have
a
canonical
desired
system,
state
versioned
in
git,
that's
obviously
very
important,
approved
changes
can
be
automatically
applied
to
the
system.
That's
where
the
controllers
come
in,
to
like
reconcile
the
state
versus
what
we
want
to
see.
C
C
C
Which
brings
us
to
the
kept
and
get
ops
operator,
and
this
is
the
prototype
that
was
built
by
thomas
there's,
a
lot
of
documentation
and
discussion
on
these
caps
as
well.
I've
linked
the
operator
itself,
and
this
is
actually
where
I'm
building
on
top
of
for
my
project
as
well.
There's
some
resources
on
on
like
specific
videos
and
developer
talks
that
thomas
gave
that
are
linked
here
as
well,
so
based
on
kind
of
what
I
just
went
over
with
regards
to
like
git
ops,
as
well
as
custom
resource
definitions.
C
C
We
see
the
captain
operator
here,
as
well
as
the
git
ops
operator,
just
like
in
the
diagram.
So
most
of
my
work
is
and
will
be
within
this
component,
so
some
so
one.
One
part
that
I've
already
well
partially
implemented
is
the
the
kept
in
service
level,
indicators
and
the
api
here,
as
you
can
see,
there's
it
defines
sort
of
the
project
stage
and
service,
as
well
as
the
provider
and
the
specific
indicators
for
the
provider.
C
C
So
this
is
currently
very
much
a
work
in
progress,
but
I
think,
as
soon
as
I
can
as
soon
as
I
become
comfortable
with
and
and
sort
of
complete
this
component,
I
think
the
rest
of
it
will
be
very
similar,
which
is
why
I
think,
which
is
why
it's
exciting,
that
that
I
think
I
can
kind
of
go
beyond
just
implementing
the
the
resources
to
kind
of
elevate
and
try
to
think
of
other
use
cases
as
well,
but
yeah.
So
there
is
currently
a
pr
for
that.
C
Something
I
learned
from
that
is
like
communicating
early
is
very
important,
as
well
as
having
great
mentors
like
everyone
was
super,
flexible
and
and
super
happy
to
grab
me
like
an
extension
based
on
which
which
really
helped
a
lot.
I
think,
with
regards
to
being
able
to
keep
along
with
the
timeline,
I
think
another
thing
I
can
do
better
is
like
leveraging
other
community
members.
In
addition
to
my
mentors,
another
thing
that
was
a
bit
of
a
challenge
is
is
setting
up
the
dev
environment.
C
I
think
the
actually
setting
up
the
get
ops
operator
so
that
it
runs
as
well
as
kept
in
that
took
up
way
more
time
than
actually
like
understanding
like
the
kept
in
client
modules
or
or
the
apis,
which
is
kind
of
just
going
into
the
code,
but
also
as
a
result.
I
learned
a
lot
more
about
like
kubernetes.
A
C
B
A
B
A
B
So,
for
me
the
biggest
question
is:
how
do
you
plan
to
make
it
available
to
others,
so
we
have
a
prototype
of
github
separator
published
by
thomas
and
the
team
and
yeah.
The
question
is
how
whether
you
plan
to
integrate
the
entity
crts
part
right
in
this
prototype
or
whether
you
want
to
have
it
separately.
D
I
think
I
I
mentioned
this
during
the
last
cheesehawk
call
when
we
had
presentations
as
well.
I
think
eric
just
moved
from
canada
to
united
states
and
I
think
a
couple
of
weeks
were
quite
hectic
for
him,
so
we
have
we
gave
an
extension,
but
otherwise,
I
think
eric
is
very
good
at
communicating
and
reaching
out
and
asking
right
the
right
questions
and
I'm
hoping
the
I'm
looking
forward
to
the
controller.
Basically.
A
F
F
Yes,
yes
yeah!
So
let's
start
with
the
ppt
okay,
so
hello,
everyone!
This
is
rajiv
and
more.
The
midterm
evaluation
and
my
project
is
on
creating
a
new
action
engine
for
kptn,
and
I
want
to
like
thanks
to
captain
organization,
to
giving
me
this
this
chance
and
to
my
mentors
who
review
my
peers
and
give
me
feedback
on
what
I
did
in
facebook,
mag,
suraj,
oleg
and
other
things,
and
all
so
I'm
going
to
like
so
like
the
this
is.
F
F
It's
open
source,
statics
generator.
The
best
thing
about
docker
service
is
like
a
very
fast
creation
of
application
like
like
it's,
because
it's
based
on
react
framework,
so
we
moved
to
we
decided
to
move
forward
with
docuseries,
so
so
I'm
going
to
showcase
the
work,
what
we
did
in
so
okay,
so
we
move
it
as
a
document
and
it's
the
starting.
The
starting
point
was
to
initialize
hosting
on
netlife
and
adding
the
accordingly.
F
So
we
have
this
repo
here,
the
sandbox
repo,
and
when
we
go
to
that,
we
see
this.
So
this
is
a
new
ux,
the
new
design
for
the
and
okay.
So
this
is
the
new.
So
next
next
was
adding
the
so
we
added
a
search
functionality
in
this
dock
site.
Earlier
in
hookah
side,
we
don't
have
a
search
some
functionality,
but
we
have
for
a
new
docker
server
side.
So
I'm
going
to
showcase
the
search.
F
Let
me
search
the
something
it's
going
to
the
all
the
cli
stuff
here
and
the
best
thing
that
is
showing
the
current
isolated
from
it's,
showing
the
latest
version,
not
from
like
different
different
versions
of
the
docs
but
showing
that
the
latest
one,
maybe
in
future
you
wanted
to
showcase
like
this
is
the
latest
version
and
you
want
to
showcase,
not
17
but
say
do
do
this
using
like
you
can
go
through
that
code
and
just
change
I'll
just
exclude
the
routes
for
that.
Like.
F
Okay,
what
about
the
I'll
be
added
in
docusaurus
next
on
the
versioning
support,
so
the
okay?
I
said
you
earlier
like
in
the
hugo
side,
we
don't
have
a
version
so
manually,
we
have
to
add
in
different
folders
and
like
it's,
it
takes
for
it.
So
we
have
a
version
support
dock
side,
so
you
can
see
the
different
versions.
As
of
now,
we
have
three
I've
added
three
versions
to
showcase
the
like
the
concept,
so
we
have
15
point
x
and
it
shows
that
this
is
not
a
latest
version.
It
shows
at
the
above.
F
F
F
F
F
So
when
we
put
this
link
here,
we
are
going
to
get
the
meta
image
or
description.
We
can
change
and
all
the
like,
all
the
metadata
of
it
and
how
we
are
getting
it
and
things
in
front
matter,
our
meta
data
tags
or
anything
related
to
like
meta
stuff
matter,
and
it's
going
to
render
it
even
image.
We
can
change
the
image
for
a
particular
docs,
the
meta
image
for
it
and
the
current
docs.
F
F
So
so,
okay,
the
problem
I
faced
during
this
phase,
one
so
at
the
starting
when
the
ui
exchanges
was
done.
I
went
with
the
tailwind
css
and
all
for
the
for
the
like
making
the
components
for
the
dock
side
and
after
like
doing
it
when
in
between,
I
stuck
there
and
have
to
re-what
the
changes.
So
one
thing
I
learned
it
like
before
anything
to
move
on.
We
have
to
showcase
one
poc
of
it
like
something
like
to.
We
shouldn't
go
directly
little
bit.
F
F
F
So
that
something
like
you
want
to
write
something
like
this
script,
so
this
is
what
it
does
it
like
going
to
clone
all
that
from
that
some
repo,
I'm
going
to
put
it
on
some
other
repo,
but
we
wanted
some
robust
thing
like
we
can't
pull
all
the
like.
We
wanted
some.
We
wanted
some
market
and
we
wanted.
F
F
That
is
in
hugo,
so
in
mobile
view
you
can,
you
can
see
here
like
it's
not
proper,
like
I
could
sniff
it
overlap
with
the,
and
this
is
one
example
of
like
like
problems
if
you're
seeing
hugo
site-
and
there
are
like
something
the
course
snippets
are
getting
out
of
the
box
in
the
hugo,
the
docusora
site.
So
when
we
go
to
mobile
view
of
docker
solas.
F
So
you
can
see
here
even
even
the
course
snippets
we
have
in
the
mobile
view.
We
can
find
automation,
format
like
and
like
I
want
to
showcase.
We
have
tabs
like
if
you
want
to
showcase
some
some
core
snippets
in
different
different
languages.
So
we
have
tab
sections
of
like
very
like
think
what,
if,
like
it's,
okay,
something
something
like
to
want
to
focus
on
something
in
different
languages.
So
that
is
more
easy,
and
if
component,
that
is
the
big
thing
about
docker
sorry,
we
can
like.
F
We
can
write
javascript
in
markdown
support
for
mdx
mobile.
It
will
look
like
this.
I'm
I'm
going
to
search
something
and
see
how
it
looks
so,
it's
more
clear,
well,
the
even
sidebars
and
our
buttons,
so
that
is
like
overview
of
mobile
view.
Okay,
now,
let's
talk
about
the
face
to
walk.
What
I
will
I
will
on
so
mostly
first
two
will
be
the
that
is
more
important
and
some
miscellaneous
topic
which
will
enhance
the
like
oxide,
like
we
wanted
a
whale
linter.
F
Linda
ptr
for
run
files,
so
when
we
do
the
current
or
docs
the
markdown
files
have
some
indentation
and
all
we
don't
have
a
proper
to
check
whether
the
markdown
files
are
structured
well
or
something
like.
So
we
will
having
a
prettier
with
a
prettier
like
peter
github
action
with
rules.
We
also
have
a
lighthouse
house
integration,
so
whenever
the
new
changes
is
done
in
the
dark
side
going
to
showcase
the
lighthouse
score,
so
lighter
score
is
like
something
it
gives.
F
The
score
of
seo
changes
how
much
js,
which
has
been
pushed
and
all
the
data
and
all
yeah,
so
adding
the
github
action
for
check,
broken
links
and
all
so
we
are
facing
like
references
links
and
all
we
can.
I
wanna
we
have
to
check
manually,
but
we
wanted
to
have
a
github
access
for
it
to
check
stuff
and
all
also
like
whatever
I'm
adding
the
feature
where
I'm
go,
I'm
documenting
documenting
it
here
and
contributing
to
md
file.
F
B
A
F
Title
is
missing
or
not,
if
somebody
adding
a
docs
and
if
they
miss
the
title,
so
it
will
going
to
give
a
message
like
give
a
a
lot
like
you
miss
a
type
field.
You
have
to
add
it
so
like
that
we
are
going
to
solve
the
quality
of
dogs,
and
one
thing
was
more
like
prettier
formatting,
so
it's
going
to
whenever
the
push
is
done
in
the
most
branches.
F
B
Yeah
personally,
I
think
that
captain
is
probably
not
the
best
tool.
For
that
I
mean.
Of
course
you
can
do
some
verification
with
captain,
but
if
you
already
have
a
bit
of
action,
if
you
have
a
standard
framework
and
static
website,
so
static
website
actually
allows
to
do
a
lot
of
regulations
without
relying
on
preview
environments
and
other
things
that
captain
supports
so.
A
B
Well,
there
still
can
be
some
opportunity
specification
with
captain,
for
example,
if
you
managing
delivery
on
our
own,
but
we
don't.
We
just
rely
on
nutley
pi
with
its
cdn,
so
it
could
make
some
sense
to
verify
some
metrics,
but
if
necessary,
I
guess
we
have.
We
don't
have
any
opportunities
to
fix
it.
A
E
Yeah
we
have
I'm
I'm
looking
forward.
We've
got
more
work,
we
you
know
to
define
exactly
what
we
want
this
to
look
like
and
and
then
get
everything
over
there.
We
need
scripts,
so
we
can
do
it
quickly
and
then
we're
going
to
want
everybody
to
chime
in
and
see
what
they
like,
how
it
should
look
and
how
it
should
behave.
E
E
D
A
C
B
So
I
think
that
it's
a
really
good
improvement
and
we
need
to
keep
investing
in
the
new
documentation
side.
We
need
to
move
more
content
tutorials
there
and
actually,
if
there
is
opportunity
to
create
a
generic
engine
based
on
the
gaza,
some
github
actions
combine
everything
in
a
single
distributable
package.
It
would
be
super
useful
for
open
source
community
too,
because
there
are
other
examples.
For
example,
see
the
events
project
is
about
building
a
documentation
site
based
on
the
kosarus
continuously.
The
foundation
wants
to
build
a
new
documentation,
engine
for
community
materials,
etc,
etc.
B
So
if
there
was
an
engine
for
that
fitting
documentations
code,
best
practices
etc,
it
would
be
super
useful
because
currently
we
don't
have
anything
between
hugo,
which
is
super
basic
for
documentation
and
enteral,
which
is
super
powerful,
but
also
quite
difficult
to
manage.
So
this
engine
as
a
small
project,
could
fit
really
well
in
the
middle.
D
Yes,
you
are,
I'm
personally
very
excited
about
both
the
projects,
because
one
project
really
solves
a
big
problem
for
a
normal
captain.
User
I'd
be
very
happy
to
operate.
Are
you
ready
the
documentation
engine
with
all
the
new,
exciting
features,
and
I'm
also
very
excited
about
the
custom
resources
that
eric
would
be
developing?
B
Read:
okay,
so
looking
forward
to
what's
next-
and
here
we
have
another
phase
of
coding,
so
by
the
end
of
august,
most
of
the
projects
will
be
slowly
wrapping
up
so
for
eric.
I
believe
we
agreed
on
longer
term
for
the
project
the
system
was
updated
and
for
the
rest
of
the
mentees.
If
you
want
to
extend
your
projects,
there
is
still
an
opportunity,
but
yes,
so
far,
we're
heading
for
revelations
in
september
for
all
of
them.
I
believe
except
serious
and
yeah.
Thanks
to
everyone
for
working
on
that
again.
B
I
believe
all
mentors
have
submitted
them
by
now
and
the
same
for
contributors
make
sure
to
submit
the
revelations
before
the
deadline,
so
that,
once
everything
is
over,
there
will
be
an
opportunity
for
the
teams
to
meet
to
do
retrospectives
and
discuss
the
feedback.
We
had
a
quick
discussion
with
brett
mccoy.