Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add intro blog post #13

Merged
merged 4 commits into from
Jan 26, 2024
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added _images/skodjob_intro.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed _images/tealc.jpg
Binary file not shown.
16 changes: 0 additions & 16 deletions posts/general/hello-world.md

This file was deleted.

51 changes: 51 additions & 0 deletions posts/general/new-boy-in-town.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---

title: Welcome this little boy to the town
menu_order: 1
post_status: publish
post_excerpt: An introduction about us, our work and what we want to do in scope of Skodjob.io
featured_image: _images/skodjob.jpg
author: jstejskal
taxonomy:
category:
- general

---

# Welcome this little boy to the town
The whole idea started a few years back. Our main work consists of testing system, that are running on top of Kubernetes.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
That itself is quite a challenge if we consider that systems like that could be distributed systems, integration of several different components, or even integration of several systems together.
Our experience was mostly about spinning up Kubernetes cluster, deploy our project, in our case [Strimzi](https://strimzi.io/), play with it a little bit on test level, and then evaluate the state with some result.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
That was enough for testing most of the features we introduced. However, at some point it started to be a little bit boring so we were thinking about some new challenge.
Frawless marked this conversation as resolved.
Show resolved Hide resolved

## Codename Teal'c
During Covid-19 pandemic we spent a lot of time home and during that time one of the best TV series was online - Stargate SG-1.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
No worries, I am not going to promote the series or spoils the plot to you!
Frawless marked this conversation as resolved.
Show resolved Hide resolved
However, within our team we liked Teal'c character, and then it started - let's start to work on something and le'ts called it Teal'c!
Frawless marked this conversation as resolved.
Show resolved Hide resolved

We started with an initiative that's goal was to test our projects more like customers.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
Our existing approach was fine for verifying features, but it was usually done in small scale.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
A lot of questions suddenly comes to our minds like:
Frawless marked this conversation as resolved.
Show resolved Hide resolved
- how the software be behave when it will running for several weeks/months?
Frawless marked this conversation as resolved.
Show resolved Hide resolved
- how we can easily automate the deployment and upgrade process?
- how upgrades of underlying architecture influences it?
- actually, how users are using it? :O
- what about monitoring?
- collecting logs?
- chaos?!

So we took that road and during free time we moved from regular verification to customer simulation with a lot of unknown.
Frawless marked this conversation as resolved.
Show resolved Hide resolved

## Teal'c is dead, long live Skodjob
It took some time, but we started to reap the fruits of our labor.
From quite complex (but still simple) testing we moved to continuous verification of several projects that were deployed for months!
Issues were found, motivation enlarged, and experience? Marvelous.

During the years we did several talks, write some blog posts about our work, and learn a lot of cool stuff.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
However, we were still missing something.
The freedom of sharing our knowledge quickly and easily somewhere, where we could manage it on our own.
We wanted to write down our ideas and experience after a couple of years of experience without any limitations.

And here we are, on `skodjob.io`.
It is good feeling, and we all hope, that you will enjoy our posts where we will try to provide as much information as we may, and also information that we were missing in other posts that we came across in the past.
Frawless marked this conversation as resolved.
Show resolved Hide resolved
Happy reading!