You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streampipes.apache.org by gi...@apache.org on 2020/04/18 19:46:47 UTC

[incubator-streampipes-website] branch asf-site updated: Automated deployment: Sat Apr 18 19:46:38 UTC 2020 d5501124ea5bc74af438054485e77ef5c4c495ff

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-streampipes-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 9b4b965  Automated deployment: Sat Apr 18 19:46:38 UTC 2020 d5501124ea5bc74af438054485e77ef5c4c495ff
9b4b965 is described below

commit 9b4b965ff2810a4ecf9a209bc778f8c4e0a2fb8b
Author: dominikriemer <do...@users.noreply.github.com>
AuthorDate: Sat Apr 18 19:46:38 2020 +0000

    Automated deployment: Sat Apr 18 19:46:38 UTC 2020 d5501124ea5bc74af438054485e77ef5c4c495ff
---
 docs/blog/2018/06/14/welcome.html                  |   2 +-
 docs/blog/2018/06/14/welcome/index.html            |   2 +-
 .../06/18/how-to-understand-your-machine-data.html |   2 +-
 .../how-to-understand-your-machine-data/index.html |   2 +-
 docs/blog/2018/09/17/preview-060.html              |   2 +-
 docs/blog/2018/09/17/preview-060/index.html        |   2 +-
 docs/blog/2018/11/24/container-cli.html            |   2 +-
 docs/blog/2018/11/24/container-cli/index.html      |   2 +-
 docs/blog/2019/04/04/release-0610.html             |   2 +-
 docs/blog/2019/04/04/release-0610/index.html       |   2 +-
 docs/blog/2019/05/23/release-0620.html             |   2 +-
 docs/blog/2019/05/23/release-0620/index.html       |   2 +-
 docs/blog/2019/09/05/release-0630.html             |   2 +-
 docs/blog/2019/09/05/release-0630/index.html       |   2 +-
 docs/blog/2019/09/19/release-0640.html             |   2 +-
 docs/blog/2019/09/19/release-0640/index.html       |   2 +-
 docs/blog/2019/11/23/release-0650.html             |   2 +-
 docs/blog/2019/11/23/release-0650/index.html       |   2 +-
 .../2019/11/25/moving-to-the-apache-incubator.html |   2 +-
 .../25/moving-to-the-apache-incubator/index.html   |   2 +-
 docs/blog/2020/01/23/streampipes_on_rpi.html       |  10 +-
 docs/blog/2020/01/23/streampipes_on_rpi/index.html |  10 +-
 docs/blog/2020/04/14/streampipes_on_k3s.html       | 261 +++++++++++++++++++++
 docs/blog/2020/04/14/streampipes_on_k3s/index.html | 261 +++++++++++++++++++++
 docs/blog/assets/2020-04-14/deployment.png         | Bin 0 -> 538484 bytes
 docs/blog/assets/2020-04-14/helm_k3s.png           | Bin 0 -> 405335 bytes
 docs/blog/assets/2020-04-14/k3s.png                | Bin 0 -> 189414 bytes
 .../assets/2020-04-14/streampi_installation.png    | Bin 0 -> 260362 bytes
 docs/blog/assets/2020-04-14/streampipes_k3s.png    | Bin 0 -> 2051203 bytes
 docs/blog/atom.xml                                 |  20 +-
 docs/blog/feed.xml                                 |  15 +-
 docs/blog/index.html                               |  18 +-
 docs/blog/page2/index.html                         |  10 +-
 .../0.55.2-pre-asf/dev-guide-tutorial-sources.html |   2 +-
 .../dev-guide-tutorial-sources/index.html          |   2 +-
 .../docs/0.61.0-pre-asf/dev-guide-event-model.html |   4 +-
 .../dev-guide-event-model/index.html               |   4 +-
 .../dev-guide-tutorial-processors.html             |   2 +-
 .../dev-guide-tutorial-processors/index.html       |   2 +-
 .../0.61.0-pre-asf/dev-guide-tutorial-sources.html |   2 +-
 .../dev-guide-tutorial-sources/index.html          |   2 +-
 .../docs/0.62.0-pre-asf/dev-guide-event-model.html |   4 +-
 .../dev-guide-event-model/index.html               |   4 +-
 .../dev-guide-tutorial-processors.html             |   2 +-
 .../dev-guide-tutorial-processors/index.html       |   2 +-
 .../0.62.0-pre-asf/dev-guide-tutorial-sources.html |   2 +-
 .../dev-guide-tutorial-sources/index.html          |   2 +-
 .../docs/0.63.0-pre-asf/dev-guide-event-model.html |   4 +-
 .../dev-guide-event-model/index.html               |   4 +-
 .../dev-guide-tutorial-processors.html             |   2 +-
 .../dev-guide-tutorial-processors/index.html       |   2 +-
 .../0.63.0-pre-asf/dev-guide-tutorial-sources.html |   2 +-
 .../dev-guide-tutorial-sources/index.html          |   2 +-
 .../docs/0.64.0-pre-asf/dev-guide-event-model.html |   4 +-
 .../dev-guide-event-model/index.html               |   4 +-
 .../dev-guide-tutorial-processors.html             |   2 +-
 .../dev-guide-tutorial-processors/index.html       |   2 +-
 .../0.64.0-pre-asf/dev-guide-tutorial-sources.html |   2 +-
 .../dev-guide-tutorial-sources/index.html          |   2 +-
 docs/docs/dev-guide-event-model.html               |   4 +-
 docs/docs/dev-guide-event-model/index.html         |   4 +-
 docs/docs/dev-guide-tutorial-processors.html       |   2 +-
 docs/docs/dev-guide-tutorial-processors/index.html |   2 +-
 docs/docs/dev-guide-tutorial-sources.html          |   2 +-
 docs/docs/dev-guide-tutorial-sources/index.html    |   2 +-
 .../next/dev-guide-development-environment.html    |   2 +-
 .../dev-guide-development-environment/index.html   |   2 +-
 docs/docs/next/dev-guide-event-model.html          |   4 +-
 docs/docs/next/dev-guide-event-model/index.html    |   4 +-
 docs/docs/next/dev-guide-tutorial-processors.html  |   2 +-
 .../next/dev-guide-tutorial-processors/index.html  |   2 +-
 docs/sitemap.xml                                   |   1 +
 getinvolved.html                                   |   2 +-
 73 files changed, 651 insertions(+), 97 deletions(-)

diff --git a/docs/blog/2018/06/14/welcome.html b/docs/blog/2018/06/14/welcome.html
index 7b70c2e..e92db39 100644
--- a/docs/blog/2018/06/14/welcome.html
+++ b/docs/blog/2018/06/14/welcome.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/06/14/welcome/index.html b/docs/blog/2018/06/14/welcome/index.html
index 7b70c2e..e92db39 100644
--- a/docs/blog/2018/06/14/welcome/index.html
+++ b/docs/blog/2018/06/14/welcome/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/06/18/how-to-understand-your-machine-data.html b/docs/blog/2018/06/18/how-to-understand-your-machine-data.html
index 57535da..cec8516 100644
--- a/docs/blog/2018/06/18/how-to-understand-your-machine-data.html
+++ b/docs/blog/2018/06/18/how-to-understand-your-machine-data.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/06/18/how-to-understand-your-machine-data/index.html b/docs/blog/2018/06/18/how-to-understand-your-machine-data/index.html
index 57535da..cec8516 100644
--- a/docs/blog/2018/06/18/how-to-understand-your-machine-data/index.html
+++ b/docs/blog/2018/06/18/how-to-understand-your-machine-data/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/09/17/preview-060.html b/docs/blog/2018/09/17/preview-060.html
index 598bbb1..97ee850 100644
--- a/docs/blog/2018/09/17/preview-060.html
+++ b/docs/blog/2018/09/17/preview-060.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/09/17/preview-060/index.html b/docs/blog/2018/09/17/preview-060/index.html
index 598bbb1..97ee850 100644
--- a/docs/blog/2018/09/17/preview-060/index.html
+++ b/docs/blog/2018/09/17/preview-060/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/11/24/container-cli.html b/docs/blog/2018/11/24/container-cli.html
index 5926c33..2a1ed56 100644
--- a/docs/blog/2018/11/24/container-cli.html
+++ b/docs/blog/2018/11/24/container-cli.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2018/11/24/container-cli/index.html b/docs/blog/2018/11/24/container-cli/index.html
index 5926c33..2a1ed56 100644
--- a/docs/blog/2018/11/24/container-cli/index.html
+++ b/docs/blog/2018/11/24/container-cli/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/04/04/release-0610.html b/docs/blog/2019/04/04/release-0610.html
index 031c5e0..79d0faa 100644
--- a/docs/blog/2019/04/04/release-0610.html
+++ b/docs/blog/2019/04/04/release-0610.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/04/04/release-0610/index.html b/docs/blog/2019/04/04/release-0610/index.html
index 031c5e0..79d0faa 100644
--- a/docs/blog/2019/04/04/release-0610/index.html
+++ b/docs/blog/2019/04/04/release-0610/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/05/23/release-0620.html b/docs/blog/2019/05/23/release-0620.html
index 64ec122..30d20d1 100644
--- a/docs/blog/2019/05/23/release-0620.html
+++ b/docs/blog/2019/05/23/release-0620.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/05/23/release-0620/index.html b/docs/blog/2019/05/23/release-0620/index.html
index 64ec122..30d20d1 100644
--- a/docs/blog/2019/05/23/release-0620/index.html
+++ b/docs/blog/2019/05/23/release-0620/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/09/05/release-0630.html b/docs/blog/2019/09/05/release-0630.html
index 9da5612..bf5c0af 100644
--- a/docs/blog/2019/09/05/release-0630.html
+++ b/docs/blog/2019/09/05/release-0630.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/09/05/release-0630/index.html b/docs/blog/2019/09/05/release-0630/index.html
index 9da5612..bf5c0af 100644
--- a/docs/blog/2019/09/05/release-0630/index.html
+++ b/docs/blog/2019/09/05/release-0630/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/09/19/release-0640.html b/docs/blog/2019/09/19/release-0640.html
index 3317cc7..5fd8539 100644
--- a/docs/blog/2019/09/19/release-0640.html
+++ b/docs/blog/2019/09/19/release-0640.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/09/19/release-0640/index.html b/docs/blog/2019/09/19/release-0640/index.html
index 3317cc7..5fd8539 100644
--- a/docs/blog/2019/09/19/release-0640/index.html
+++ b/docs/blog/2019/09/19/release-0640/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/11/23/release-0650.html b/docs/blog/2019/11/23/release-0650.html
index fd1b35c..baf6ebc 100644
--- a/docs/blog/2019/11/23/release-0650.html
+++ b/docs/blog/2019/11/23/release-0650.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/11/23/release-0650/index.html b/docs/blog/2019/11/23/release-0650/index.html
index fd1b35c..baf6ebc 100644
--- a/docs/blog/2019/11/23/release-0650/index.html
+++ b/docs/blog/2019/11/23/release-0650/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/11/25/moving-to-the-apache-incubator.html b/docs/blog/2019/11/25/moving-to-the-apache-incubator.html
index 097a540..2334b51 100644
--- a/docs/blog/2019/11/25/moving-to-the-apache-incubator.html
+++ b/docs/blog/2019/11/25/moving-to-the-apache-incubator.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2019/11/25/moving-to-the-apache-incubator/index.html b/docs/blog/2019/11/25/moving-to-the-apache-incubator/index.html
index 097a540..2334b51 100644
--- a/docs/blog/2019/11/25/moving-to-the-apache-incubator/index.html
+++ b/docs/blog/2019/11/25/moving-to-the-apache-incubator/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
diff --git a/docs/blog/2020/01/23/streampipes_on_rpi.html b/docs/blog/2020/01/23/streampipes_on_rpi.html
index 35e0ea2..09362ce 100644
--- a/docs/blog/2020/01/23/streampipes_on_rpi.html
+++ b/docs/blog/2020/01/23/streampipes_on_rpi.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
@@ -62,7 +62,7 @@
         </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="lonePost"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/01/23/streampipes_on_rpi">StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></h1><p class="post-meta">January 23, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer no [...]
 <strong><div style="float: left; padding-right: 40px;">5 minutes to read</div></strong>
 <br></p>
-<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The first part describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the the second part further covers how to deploy StreamPipes over a two-node Raspberry Pi cluster managed via k3s using our StreamPipes helm chart.</p>
+<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via K3s using our StreamPipes helm chart.</p>
 <!--truncate-->
 <p>&lt;TL;DR&gt;</p>
 <p><em>With new advancements that came in the last StreamPipes release, we managed to reduce the required resources (mainly memory) drastically. To this extent, we cross-compiled StreamPipes Docker images for ARM support and deployed our lite version on a Raspberry Pi (Model 4). We showcase, that it is feasible to run analytical pipelines with ease and operate StreamPipes at moderate load.</em></p>
@@ -84,16 +84,16 @@
 <p>After saving and starting the pipeline, we built our dashboard based on the results of the pipeline, only showing values above 65°C. Additionally, we receive a notification for every event, that exceeds this temperature threshold.</p>
 <p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-01-23/04_dashboard.png" alt="Dashboard"></p>
 <h3><a class="anchor" aria-hidden="true" id="so-what-s-next"></a><a href="#so-what-s-next" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
-<p>Starting out as a simple hack session on a late afternoon, trying to test where we could potentially run StreamPipes on and push it to it's limits, we gained valueable insights on how to build and run it on various architectures. Even though we do not recommend deploying StreamPipes in it's full glory on single low-resourced devices such as Raspberry Pi's, we aim to bring certain algorithms closer to where data is generated - on the edge. Consequently - apart from x86 images - we plan [...]
+<p>Starting out as a simple hack session on a late afternoon, trying to test where we could potentially run StreamPipes on and push it to it's limits, we gained valueable insights on how to build and run it on various architectures. Even though we do not recommend deploying StreamPipes in it's full glory on single low-resourced devices such as Raspberry Pi's, we aim to bring certain algorithms closer to where data is generated - on the edge. Consequently - apart from x86 images - we plan [...]
 <ul>
 <li><strong><a href="/docs/blog/2020/01/23/streampipes_on_rpi">Part 1: StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></strong></li>
-<li>Part 2: StreamPipes goes edge - Running StreamPipes on k3s</li>
+<li><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Part 2: Running StreamPipes the Kubernetes-Way using K3s</a></li>
 </ul>
 <h3><a class="anchor" aria-hidden="true" id="useful-links"></a><a href="#useful-links" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
 <ul>
 <li>[1] <a href="https://docs.docker.com/engine/reference/commandline/manifest/">Docker manifest docs</a></li>
 <li>[2] <a href="https://ownyourbits.com/2018/06/27/running-and-building-arm-docker-containers-in-x86/">Running and Building ARM Docker containers in x86</a></li>
-<li>[3] <a href="https://k3s.io/">k3s - lightweight Kubernetes distro</a></li>
+<li>[3] <a href="https://k3s.io/">K3s - lightweight Kubernetes distro</a></li>
 </ul>
 </span></div></div><div class="blogSocialSection"></div></div><div class="blog-recent"><a class="button" href="/docs/blog">Recent Posts</a></div></div></div><nav class="onPageNav"></nav></div><div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/docs/" class="nav-home"><img src="/docs/img/sp-logo-color.png" alt="StreamPipes" width="66"/></a><div><h5>Docs</h5><a href="/docs/docs/user-guide-introduction">User Guide</a><a href="/docs/docs/dev-guide-introduction">Dev [...]
                 document.addEventListener('keyup', function(e) {
diff --git a/docs/blog/2020/01/23/streampipes_on_rpi/index.html b/docs/blog/2020/01/23/streampipes_on_rpi/index.html
index 35e0ea2..09362ce 100644
--- a/docs/blog/2020/01/23/streampipes_on_rpi/index.html
+++ b/docs/blog/2020/01/23/streampipes_on_rpi/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
@@ -62,7 +62,7 @@
         </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="lonePost"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/01/23/streampipes_on_rpi">StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></h1><p class="post-meta">January 23, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer no [...]
 <strong><div style="float: left; padding-right: 40px;">5 minutes to read</div></strong>
 <br></p>
-<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The first part describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the the second part further covers how to deploy StreamPipes over a two-node Raspberry Pi cluster managed via k3s using our StreamPipes helm chart.</p>
+<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via K3s using our StreamPipes helm chart.</p>
 <!--truncate-->
 <p>&lt;TL;DR&gt;</p>
 <p><em>With new advancements that came in the last StreamPipes release, we managed to reduce the required resources (mainly memory) drastically. To this extent, we cross-compiled StreamPipes Docker images for ARM support and deployed our lite version on a Raspberry Pi (Model 4). We showcase, that it is feasible to run analytical pipelines with ease and operate StreamPipes at moderate load.</em></p>
@@ -84,16 +84,16 @@
 <p>After saving and starting the pipeline, we built our dashboard based on the results of the pipeline, only showing values above 65°C. Additionally, we receive a notification for every event, that exceeds this temperature threshold.</p>
 <p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-01-23/04_dashboard.png" alt="Dashboard"></p>
 <h3><a class="anchor" aria-hidden="true" id="so-what-s-next"></a><a href="#so-what-s-next" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
-<p>Starting out as a simple hack session on a late afternoon, trying to test where we could potentially run StreamPipes on and push it to it's limits, we gained valueable insights on how to build and run it on various architectures. Even though we do not recommend deploying StreamPipes in it's full glory on single low-resourced devices such as Raspberry Pi's, we aim to bring certain algorithms closer to where data is generated - on the edge. Consequently - apart from x86 images - we plan [...]
+<p>Starting out as a simple hack session on a late afternoon, trying to test where we could potentially run StreamPipes on and push it to it's limits, we gained valueable insights on how to build and run it on various architectures. Even though we do not recommend deploying StreamPipes in it's full glory on single low-resourced devices such as Raspberry Pi's, we aim to bring certain algorithms closer to where data is generated - on the edge. Consequently - apart from x86 images - we plan [...]
 <ul>
 <li><strong><a href="/docs/blog/2020/01/23/streampipes_on_rpi">Part 1: StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></strong></li>
-<li>Part 2: StreamPipes goes edge - Running StreamPipes on k3s</li>
+<li><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Part 2: Running StreamPipes the Kubernetes-Way using K3s</a></li>
 </ul>
 <h3><a class="anchor" aria-hidden="true" id="useful-links"></a><a href="#useful-links" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
 <ul>
 <li>[1] <a href="https://docs.docker.com/engine/reference/commandline/manifest/">Docker manifest docs</a></li>
 <li>[2] <a href="https://ownyourbits.com/2018/06/27/running-and-building-arm-docker-containers-in-x86/">Running and Building ARM Docker containers in x86</a></li>
-<li>[3] <a href="https://k3s.io/">k3s - lightweight Kubernetes distro</a></li>
+<li>[3] <a href="https://k3s.io/">K3s - lightweight Kubernetes distro</a></li>
 </ul>
 </span></div></div><div class="blogSocialSection"></div></div><div class="blog-recent"><a class="button" href="/docs/blog">Recent Posts</a></div></div></div><nav class="onPageNav"></nav></div><div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/docs/" class="nav-home"><img src="/docs/img/sp-logo-color.png" alt="StreamPipes" width="66"/></a><div><h5>Docs</h5><a href="/docs/docs/user-guide-introduction">User Guide</a><a href="/docs/docs/dev-guide-introduction">Dev [...]
                 document.addEventListener('keyup', function(e) {
diff --git a/docs/blog/2020/04/14/streampipes_on_k3s.html b/docs/blog/2020/04/14/streampipes_on_k3s.html
new file mode 100644
index 0000000..bec5a4c
--- /dev/null
+++ b/docs/blog/2020/04/14/streampipes_on_k3s.html
@@ -0,0 +1,261 @@
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Running StreamPipes the Kubernetes-Way using k3s · StreamPipes</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="&lt;img class=&quot;blog-image&quot; style=&quot;max-width:100%;&quot; src=&quot;/docs/blog/assets/2020-04-14/streampipes_k3s.png&quot; alt=&quot;StreamPipes on k3s&quot; [...]
+              window.dataLayer = window.dataLayer || [];
+              function gtag(){dataLayer.push(arguments); }
+              gtag('js', new Date());
+              gtag('config', 'UA-154181944-1');
+            </script><link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons"/><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css"/><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css"/><link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto"/><link rel="stylesheet" href="/docs/css/admonition.css"/><link rel="stylesheet" href="/docs [...]
+        document.addEventListener('DOMContentLoaded', function() {
+          addBackToTop(
+            {"zIndex":100}
+          )
+        });
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+            var coll = document.getElementsByClassName('collapsible');
+            var checkActiveCategory = true;
+            for (var i = 0; i < coll.length; i++) {
+              var links = coll[i].nextElementSibling.getElementsByTagName('*');
+              if (checkActiveCategory){
+                for (var j = 0; j < links.length; j++) {
+                  if (links[j].classList.contains('navListItemActive')){
+                    coll[i].nextElementSibling.classList.toggle('hide');
+                    coll[i].childNodes[1].classList.toggle('rotate');
+                    checkActiveCategory = false;
+                    break;
+                  }
+                }
+              }
+
+              coll[i].addEventListener('click', function() {
+                var arrow = this.childNodes[1];
+                arrow.classList.toggle('rotate');
+                var content = this.nextElementSibling;
+                content.classList.toggle('hide');
+              });
+            }
+
+            document.addEventListener('DOMContentLoaded', function() {
+              createToggler('#navToggler', '#docsNav', 'docsSliderActive');
+              createToggler('#tocToggler', 'body', 'tocActive');
+
+              const headings = document.querySelector('.toc-headings');
+              headings && headings.addEventListener('click', function(event) {
+                if (event.target.tagName === 'A') {
+                  document.body.classList.remove('tocActive');
+                }
+              }, false);
+
+              function createToggler(togglerSelector, targetSelector, className) {
+                var toggler = document.querySelector(togglerSelector);
+                var target = document.querySelector(targetSelector);
+
+                if (!toggler) {
+                  return;
+                }
+
+                toggler.onclick = function(event) {
+                  event.preventDefault();
+
+                  target.classList.toggle(className);
+                };
+              }
+            });
+        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="lonePost"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Running StreamPipes the Kubernetes-Way using k3s</a></h1><p class="post-meta">April 14, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer noopene [...]
+<strong><div style="float: left; padding-right: 40px;">15 minutes to read</div></strong>
+<br></p>
+<p>This blog post is the second part of a series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via k3s using our StreamPipes helm chart.</p>
+<!--truncate-->
+<p><strong>&lt;TL;DR&gt;</strong></p>
+<p><strong>With new advancements that came in the last StreamPipes release, we managed to reduce the required resources (mainly memory) drastically. To this extent, we cross-compiled StreamPipes Docker images for ARM support and deployed our lite version on a Raspberry Pi (Model 4). We showcase, that it is feasible to run analytical pipelines with ease and operate StreamPipes at moderate load. Additionally, we demonstrate how to deploy StreamPipes over a two-node k3s cluster using our St [...]
+<p><img class="blog-image" style="max-width:80%;" src="/docs/blog/assets/2020-04-14/k3s.png" alt="K3s"></p>
+<h2><a class="anchor" aria-hidden="true" id="introduction"></a><a href="#introduction" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
+<p>While it is easy to get started with StreamPipes in no time using our single-node deployment <a href="/docs/docs/user-guide-installation">instructions</a> using Docker and Docker-Compose, StreamPipes naturally is designed to run in a distributed cluster setup through its microservice architecture.</p>
+<p>This architectural design paired with the advancements of multi-architecture StreamPipes images as described in the previous blog post allows us to run certain analytical pipeline element containers with ease on various target nodes as well as target hardware architecture wether it is X86, ARM32v7, or ARM64v8. This becomes more valuable, as we shift the focus away from centralized cloud or data center only deployments where we generally are provided with a homogenous compute landscape [...]
+<p>Thereby, having multi-architecture images in your repertoire is key to deal with the challenge of heterogeneity in compute resources along the edge-cloud continuum. However, there are other challenges that occur when dealing with distributed container deployments such as automating deployments itself, scaling them, managing the containerized applications, taking care of networking between services, or realizing fault-tolerance by comparing the desired state against the current one. If [...]
+<h2><a class="anchor" aria-hidden="true" id="well-which-k-to-use-kubernetes-k3s"></a><a href="#well-which-k-to-use-kubernetes-k3s" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5 [...]
+<p>Fortunately, there exists a few solutions in the container ecosystem with the open source container orchestrator <a href="https://kubernetes.io">Kubernetes</a> (K8s) being the defacto standard, thereby incorporating the best ideas of Google's internal large-scale container cluster management system <a href="https://kubernetes.io/blog/2015/04/borg-predecessor-to-kubernetes/">Borg</a> (see academic paper about the details published at <a href="https://research.google/pubs/pub43438/">Eur [...]
+<p>On the other hand, there exists <a href="https://k3s.io/">K3s</a>, a lightweight Kubernetes distro by Rancher that was introduced early 2019 and has since then gained huge popularity. As it is stated on their website:</p>
+<ul>
+<li><strong>Perfect for Edge</strong>: <em>K3s is a highly available, certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances</em></li>
+<li><strong>Simplified &amp; Secure</strong>: <em>K3s is packaged as a single &lt;40MB binary that reduces the dependencies and steps needed to install, run and auto-update a production Kubernetes cluster.</em></li>
+<li><strong>Optimized for ARM</strong>: <em>Both ARM64 and ARMv7 are supported with binaries and multiarch images available for both. K3s works great from something as small as a Raspberry Pi to an AWS a1.4xlarge 32GiB server.</em></li>
+</ul>
+<p>Thus, this lead us to the point to say, hey why not use K3s to manage StreamPipes in all its glory. The containerized microservice design in addition to the newly available multiarch images are a great fit.</p>
+<h2><a class="anchor" aria-hidden="true" id="streampipes-helm-chart"></a><a href="#streampipes-helm-chart" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
+<p>While you can easily write an deploy K8s YAML-based manifests for your deployments and services and so on the standard way, it is way more convenient to leverage  <a href="https://helm.sh/">Helm</a>, the package manager for K8s. Helm describes complex, distributed deployments using <strong>charts</strong> in order to provide repeatable application installation, easy updates, rollbacks etc.</p>
+<p>To this extent, we wrote a Helm chart for StreamPipes that can be found on our Github <a href="https://github.com/apache/incubator-streampipes-installer/tree/dev/helm-chart">incubator-streampipes-installer</a> repository. This allows to deploy StreamPipes as one liner as shown later. Helm charts follow a certain directory structure as depicted in the following:</p>
+<pre><code class="hljs">helm-chart/
+  <span class="hljs-module-access"><span class="hljs-module"><span class="hljs-identifier">Chart</span>.</span></span>yaml
+  values.yaml
+  templates/<span class="hljs-operator">
+  ...
+</span></code></pre>
+<p>The <code>Chart.yaml</code> file contains a description of the chart, e.g., metadata such as chart name, version, maintainers etc.</p>
+<p>The <code>values.yaml</code> file contains default values for all charts and in our case serves the purpose to provide a central place to store all variable/values, e.g., <code>streampipes.registry: &quot;apachestreampipes&quot;</code>, that replace chart templates such as the registry and version of the StreamPipes backend image:</p>
+<pre><code class="hljs css language-yaml"><span class="hljs-string">...</span>
+<span class="hljs-attr">image:</span> <span class="hljs-string">{{</span> <span class="hljs-string">.Values.streampipes.registry</span> <span class="hljs-string">}}/backend:{{</span> <span class="hljs-string">.Values.streampipes.version</span> <span class="hljs-string">}}</span>
+<span class="hljs-string">...</span>
+</code></pre>
+<p>Lastly, the <code>template/</code> directory is for template files. When Helm evaluates a chart, it sends all of the files in this directory through the template rendering engine before collecting the results and finally forwarding them to K8s. If interested, you can read more on this in the <a href="https://helm.sh/docs/">official Helm documentation</a>.</p>
+<h2><a class="anchor" aria-hidden="true" id="the-almighty-streampi-k3s-cluster"></a><a href="#the-almighty-streampi-k3s-cluster" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S1 [...]
+<p>As pointed out in the first part of the series, we have gained valueable insights on how to run and deploy StreamPipes on a Raspberry Pi. This worked out so greatly, that we thought, why not step up the game, use another Pi and built the <strong>almighty StreamPi cluster</strong> by leveraging K3s for orchestration and management.</p>
+<p><strong>Note</strong>: We are aware that this is far off from a production-grade setup, especially running StreamPipes core services such as the central pipeline management backend, or the UI in a two-node cluster. However, it provides a solid starting point for more elaborate deployments along the edge-cloud continuum.</p>
+<p>As shown in the following figure, starting from the multiarch images hosted on <a href="https://hub.docker.com/search?q=apachestreampipes&amp;type=image">Dockerhub</a>, we first provisioned the two Pi's with Docker, install and setup K3s and finally deploy our StreamPipes helm chart in order for users to connect, analyze and exploit their IIoT data with StreamPipes.</p>
+<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/deployment.png" alt="Deployment"></p>
+<p>In the remainder, we cover how we installed Helm and K3s to form our almighty StreamPi K3s cluster. At the time of writing, we tested our deployment using the latest version of the Docker, Helm as well as K3s in the following setup</p>
+<ul>
+<li>2x Raspberry Pi Model 4 (4GiB RAM): <code>streampi-01</code>, <code>streampi-02</code></li>
+<li>Raspbian Buster 10</li>
+<li>Docker 19.03.8</li>
+<li>Helm 3.1.2</li>
+<li>K3s v1.17.4+k3s1</li>
+</ul>
+<h3><a class="anchor" aria-hidden="true" id="1-install-docker"></a><a href="#1-install-docker" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
+<p>SSH into your Raspberry Pi's and run the following command:</p>
+<pre><code class="hljs css language-bash">curl -sSL https://get.docker.com | sh
+</code></pre>
+<h3><a class="anchor" aria-hidden="true" id="2-install-k3s"></a><a href="#2-install-k3s" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
+<p>Now that we got Helm installed, we can proceed and install K3s. Thus, we must check wether we fulfill all the requirements. These are mainly network related, such that specific ports (server on <code>6443</code>) are accessible. You should carefully read about this in their <a href="https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/">official documentation</a>.</p>
+<p>Other than that, lean back and enjoy - the installation happens so fast, you might miss it if you get a coffee :)</p>
+<h4><a class="anchor" aria-hidden="true" id="ssh-into-k3s-server-streampi-01"></a><a href="#ssh-into-k3s-server-streampi-01" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
+<p>On the server node, run the following command:</p>
+<pre><code class="hljs css language-bash">sudo curl -sfL https://get.k3s.io | sh -
+</code></pre>
+<p>A kubeconfig file is written to <code>/etc/rancher/k3s/k3s.yaml</code> and the service is automatically started or restarted. The install script will install k3s and additional utilities, such as <code>kubectl</code>, <code>crictl</code>, <code>k3s-killall.sh</code>, and <code>k3s-uninstall.sh</code>.</p>
+<p>The K3s installer creates a systemd service which can be used to <code>stop</code>, <code>start</code>, <code>restart</code> and check the <code>status</code> of the K3s server.</p>
+<pre><code class="hljs css language-bash">sudo systemctl status k3s.service
+
+● k3s.service - Lightweight Kubernetes
+   Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
+   Active: active (running) since Sat 2020-04-11 15:54:07 BST; 3 days ago
+     Docs: https://k3s.io
+  Process: 10193 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
+  Process: 10194 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
+ Main PID: 10195 (k3s-server)
+ (...)
+</code></pre>
+<p>Next, copy the server node token in order to connect additional agent nodes to the cluster.</p>
+<pre><code class="hljs css language-bash">sudo cat /var/lib/rancher/k3s/server/node-token
+</code></pre>
+<h4><a class="anchor" aria-hidden="true" id="ssh-into-k3s-agent-streampi-02"></a><a href="#ssh-into-k3s-agent-streampi-02" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
+<p>Now, open a new terminal session and SSH into your agent and run the following command, thereby adding the copied <code>K3S_TOKEN</code> to connect to the server, that is specified using <code>K3S_URL</code>.</p>
+<pre><code class="hljs css language-bash">sudo curl -sfL https://get.k3s.io | K3S_URL=https://streampi-01:6443 \
+K3S_TOKEN=&lt;NODE_TOKEN&gt; sh -
+</code></pre>
+<p>The K3s installer creates a systemd service which can be used to <code>stop</code>, <code>start</code>, <code>restart</code> and check the <code>status</code> of the K3s agent.</p>
+<pre><code class="hljs css language-bash">sudo systemctl status k3s-agent.service
+
+● k3s-agent.service - Lightweight Kubernetes
+   Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
+   Active: active (running) since Sat 2020-04-11 16:05:37 BST; 3 days ago
+     Docs: https://k3s.io
+  Process: 24469 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
+  Process: 24470 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
+ Main PID: 24471 (k3s-agent)
+ (...)
+</code></pre>
+<p>That's it ... that's all!</p>
+<p>When you go back to the terminal session on the K3s server you can list all nodes in the cluster using standard <code>kubectl</code> commands.</p>
+<pre><code class="hljs css language-bash">kubectl get nodes
+NAME              STATUS   ROLES    AGE   VERSION
+streampi-02   Ready    &lt;none&gt;   3d    v1.17.4+k3s1
+streampi-01   Ready    master   3d    v1.17.4+k3s1
+</code></pre>
+<p>Hmmm - but wait. We did only add one agent node to the cluster right? Well, that's true, however when installing K3s using the script the server automatically installs and runs an agent on the same node.</p>
+<h3><a class="anchor" aria-hidden="true" id="3-install-helm"></a><a href="#3-install-helm" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
+<p>SSH into the RPi that should act as the K3s server later on - in our case this is <code>streampi-01</code> and install Helm. Since we are using Helm 3 there is no need to install tiller. Thus, installing helm is as simple as running the following command:</p>
+<pre><code class="hljs css language-bash">curl -sSL https://get.helm.sh/helm-v3.1.2-linux-arm.tar.gz | sudo tar -xzf - -C /usr/<span class="hljs-built_in">local</span>/bin/ linux-arm/helm --strip-components=1
+</code></pre>
+<p>This command downloads the Helm binary release from Github, extracts only the binary and puts it in <code>/usr/local/bin</code>. Try go check <code>helm version</code> to see if it worked.</p>
+<pre><code class="hljs css language-bash">version.BuildInfo{Version:<span class="hljs-string">"v3.1.2"</span>, GitCommit:<span class="hljs-string">"d878d4d45863e42fd5cff6743294a11d28a9abce"</span>, GitTreeState:<span class="hljs-string">"clean"</span>, GoVersion:<span class="hljs-string">"go1.13.8"</span>}
+</code></pre>
+<p>To use Helm, we can set and export <code>KUBECONFIG</code> environment variable to point to the kubeconfig under <code>/etc/rancher/k3s/k3s.yaml</code>.</p>
+<pre><code class="hljs css language-bash"><span class="hljs-built_in">export</span> KUBECONFIG=/etc/rancher/k3s/k3s.yaml
+</code></pre>
+<p>Alternatively, if you want this permanently you can either add it to your <code>.bashrc</code>/<code>.zshrc</code>, or create a <code>.kube</code> directory in your home directory and symlink the <code>k3s.yaml</code>.</p>
+<pre><code class="hljs css language-bash">mkdir <span class="hljs-variable">$HOME</span>/.kube
+ln -s /etc/rancher/k3s/k3s.yaml <span class="hljs-variable">$HOME</span>/.kube/config
+</code></pre>
+<h2><a class="anchor" aria-hidden="true" id="deploy-streampipes-on-k3s-using-helm"></a><a href="#deploy-streampipes-on-k3s-using-helm" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 [...]
+<p>Now, that we have all set up, we can go ahead and deploy StreamPipes using our Helm chart. Therefore, we go to the server node (<code>streampi-01</code>), where we installed Helm. Next, we clone our StreamPipes installer repository (<code>dev</code> branch) and navigate to the helm-chart directory.</p>
+<p><strong>Note</strong>: At the point of writing, the helm chart is <strong>only</strong> available in the <code>dev</code> branch. This will change in the future as we update the repository.</p>
+<pre><code class="hljs css language-bash">git <span class="hljs-built_in">clone</span> -b dev --single-branch https://github.com/apache/incubator-streampipes-installer.git
+<span class="hljs-built_in">cd</span> incubator-streampipes-installer
+</code></pre>
+<p>At this point, we can leverage Helm's <code>install</code> command in order to install the StreamPipes Helm chart. Since Helm reads the K3s kubeconfig, it forwards the deployment request to K3s. As per default, we deploy StreamPipes <code>lite</code> version, where we only start standalone Java-based pipeline elements and disregard the ones building on top of our Flink wrapper.</p>
+<pre><code class="hljs css language-bash">helm install streampipes helm-chart
+
+NAME: streampipes
+LAST DEPLOYED: Tue Apr 14 18:13:19 2020
+NAMESPACE: default
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+</code></pre>
+<p>Next, K3s receives this requests and goes ahead and downloads the corresponding Docker images and starts the deployments in the right order according to the specified dependencies, creates services as well as persistent volume claims when needed. This step takes some time depending on your internet connection and the hardware when starting the containers. You can check the status of the StreamPipes Helm installation using <code>kubectl get pods -o wide</code> (when adding <code>-w</co [...]
+<pre><code class="hljs css language-bash">kubectl get pods -o=custom-columns=NAME:.metadata.name,STATUS:.status.phase,NODE:.spec.nodeName
+
+NAME                                           STATUS    NODE
+activemq-66d58f47cf-b88nb                      Running   streampi-01
+zookeeper-5d9947686f-7vpjb                     Running   streampi-02
+couchdb-77db98cf7b-6nn99                       Running   streampi-02
+consul-55965f966b-tjcfb                        Running   streampi-02
+influxdb-b95b6479-mvgbg                        Running   streampi-02
+backend-6cdfb7bbf9-b4vgh                       Running   streampi-02
+pipeline-elements-all-jvm-64795974-g2xhv       Running   streampi-02
+kafka-657b5fb77-xtw8p                          Running   streampi-01
+connect-master-56f5f947d-n2t5b                 Running   streampi-01
+sources-watertank-simulator-6958f7844c-2jv78   Running   streampi-01
+connect-worker-fdbd6f464-m6vm8                 Running   streampi-01
+nginx-5d4498d4f5-fcccq                         Running   streampi-02
+</code></pre>
+<p>As can be seen, a fair amount of StreamPipes containers aka pods were deployed on <code>streampi-01</code> and <code>streampi-02</code>. When everything goes well, you should see all containers in the status <code>RUNNING</code> after a couple of minutes. To access K8s cluster UI pod a <code>NodePort</code> was created. The <code>NodePort</code> publishes the UI (nginx) service on every node using using its public IP and a port. Then you can access the service using any of the cluster [...]
+<pre><code class="hljs css language-yaml"><span class="hljs-attr">apiVersion:</span> <span class="hljs-string">v1</span>
+<span class="hljs-attr">kind:</span> <span class="hljs-string">Service</span>
+<span class="hljs-attr">metadata:</span>
+  <span class="hljs-attr">name:</span> <span class="hljs-string">nginx</span>
+<span class="hljs-attr">spec:</span>
+  <span class="hljs-attr">selector:</span>
+    <span class="hljs-attr">app:</span> <span class="hljs-string">nginx</span>
+  <span class="hljs-attr">type:</span> <span class="hljs-string">NodePort</span>
+  <span class="hljs-attr">ports:</span>
+    <span class="hljs-bullet">-</span> <span class="hljs-attr">name:</span> <span class="hljs-string">main</span>
+      <span class="hljs-attr">protocol:</span> <span class="hljs-string">TCP</span>
+      <span class="hljs-attr">port:</span> <span class="hljs-number">80</span> <span class="hljs-comment"># container port</span>
+      <span class="hljs-attr">targetPort:</span> <span class="hljs-number">80</span> <span class="hljs-comment"># node port</span>
+</code></pre>
+<p>That means, you can go and check the StreamPipes UI either on <code>http://streampi-01/</code> or <code>http://streampi-02/</code> - K8s service handles the routing to the nginx pod containing the UI - just to name one nice feature.</p>
+<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/streampi_installation.png" alt="Installation"></p>
+<h2><a class="anchor" aria-hidden="true" id="sum-up-where-to-go-from-here"></a><a href="#sum-up-where-to-go-from-here" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
+<p>Starting out as a simple hack session on a late afternoon, we build multi-archicture StreamPipes Docker images and deployed them on a Raspberry Pi in the first part of the series. Though, this is was feasible StreamPipes architectural microservice design provides a natural fit for a distributed cluster deployment. To this extent, we provide a StreamPipes Helm chart that lets you easily deploy StreamPipes in a one-liner in a Kubernetes cluster as showcased using a testbed of two Raspbe [...]
+<p>As of now, we let K8s handle the scheduling of containers for us in a random fashion. From here, we can further explore K8s feature such as <code>nodeSelector</code> or <code>nodeAffinity</code> that helps you use labels (<code>key=value</code> pairs) for pod to node assignment.</p>
+<p><img class="blog-image" style="max-width:60%;" src="/docs/blog/assets/2020-04-14/helm_k3s.png" alt="HelmK3s"></p>
+<ul>
+<li><a href="/docs/blog/2020/01/23/streampipes_on_rpi">Part 1: StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></li>
+<li><strong><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Part 2: Running StreamPipes the Kubernetes-Way using K3s</a></strong></li>
+</ul>
+<h3><a class="anchor" aria-hidden="true" id="useful-links"></a><a href="#useful-links" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
+<ul>
+<li>[1] <a href="https://k3s.io/">K3s - lightweight Kubernetes distro</a></li>
+<li>[2] <a href="https://helm.sh/">Helm - the package manager for Kubernetes</a></li>
+<li>[3] <a href="https://github.com/apache/incubator-streampipes-installer/tree/dev/helm-chart">Github: StreamPipes Helm chart</a></li>
+</ul>
+</span></div></div><div class="blogSocialSection"></div></div><div class="blog-recent"><a class="button" href="/docs/blog">Recent Posts</a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#well-which-k-to-use-kubernetes-k3s">Well, which K to use? Kubernetes, K3s</a></li><li><a href="#streampipes-helm-chart">StreamPipes Helm Chart</a></li><li><a href="#the-almighty-streampi-k3s-cluster">The almighty StreamPi K3 [...]
+                document.addEventListener('keyup', function(e) {
+                  if (e.target !== document.body) {
+                    return;
+                  }
+                  // keyCode for '/' (slash)
+                  if (e.keyCode === 191) {
+                    const search = document.getElementById('search_input_react');
+                    search && search.focus();
+                  }
+                });
+              </script><script>
+              var search = docsearch({
+                
+                apiKey: '0fedc89dddf2810657708b178e56ef02',
+                indexName: 'streampipes',
+                inputSelector: '#search_input_react',
+                algoliaOptions: {}
+              });
+            </script></body></html>
\ No newline at end of file
diff --git a/docs/blog/2020/04/14/streampipes_on_k3s/index.html b/docs/blog/2020/04/14/streampipes_on_k3s/index.html
new file mode 100644
index 0000000..bec5a4c
--- /dev/null
+++ b/docs/blog/2020/04/14/streampipes_on_k3s/index.html
@@ -0,0 +1,261 @@
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Running StreamPipes the Kubernetes-Way using k3s · StreamPipes</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="&lt;img class=&quot;blog-image&quot; style=&quot;max-width:100%;&quot; src=&quot;/docs/blog/assets/2020-04-14/streampipes_k3s.png&quot; alt=&quot;StreamPipes on k3s&quot; [...]
+              window.dataLayer = window.dataLayer || [];
+              function gtag(){dataLayer.push(arguments); }
+              gtag('js', new Date());
+              gtag('config', 'UA-154181944-1');
+            </script><link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons"/><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css"/><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css"/><link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto"/><link rel="stylesheet" href="/docs/css/admonition.css"/><link rel="stylesheet" href="/docs [...]
+        document.addEventListener('DOMContentLoaded', function() {
+          addBackToTop(
+            {"zIndex":100}
+          )
+        });
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="sideNavVisible separateOnPageNav"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><n [...]
+            var coll = document.getElementsByClassName('collapsible');
+            var checkActiveCategory = true;
+            for (var i = 0; i < coll.length; i++) {
+              var links = coll[i].nextElementSibling.getElementsByTagName('*');
+              if (checkActiveCategory){
+                for (var j = 0; j < links.length; j++) {
+                  if (links[j].classList.contains('navListItemActive')){
+                    coll[i].nextElementSibling.classList.toggle('hide');
+                    coll[i].childNodes[1].classList.toggle('rotate');
+                    checkActiveCategory = false;
+                    break;
+                  }
+                }
+              }
+
+              coll[i].addEventListener('click', function() {
+                var arrow = this.childNodes[1];
+                arrow.classList.toggle('rotate');
+                var content = this.nextElementSibling;
+                content.classList.toggle('hide');
+              });
+            }
+
+            document.addEventListener('DOMContentLoaded', function() {
+              createToggler('#navToggler', '#docsNav', 'docsSliderActive');
+              createToggler('#tocToggler', 'body', 'tocActive');
+
+              const headings = document.querySelector('.toc-headings');
+              headings && headings.addEventListener('click', function(event) {
+                if (event.target.tagName === 'A') {
+                  document.body.classList.remove('tocActive');
+                }
+              }, false);
+
+              function createToggler(togglerSelector, targetSelector, className) {
+                var toggler = document.querySelector(togglerSelector);
+                var target = document.querySelector(targetSelector);
+
+                if (!toggler) {
+                  return;
+                }
+
+                toggler.onclick = function(event) {
+                  event.preventDefault();
+
+                  target.classList.toggle(className);
+                };
+              }
+            });
+        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="lonePost"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Running StreamPipes the Kubernetes-Way using k3s</a></h1><p class="post-meta">April 14, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer noopene [...]
+<strong><div style="float: left; padding-right: 40px;">15 minutes to read</div></strong>
+<br></p>
+<p>This blog post is the second part of a series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via k3s using our StreamPipes helm chart.</p>
+<!--truncate-->
+<p><strong>&lt;TL;DR&gt;</strong></p>
+<p><strong>With new advancements that came in the last StreamPipes release, we managed to reduce the required resources (mainly memory) drastically. To this extent, we cross-compiled StreamPipes Docker images for ARM support and deployed our lite version on a Raspberry Pi (Model 4). We showcase, that it is feasible to run analytical pipelines with ease and operate StreamPipes at moderate load. Additionally, we demonstrate how to deploy StreamPipes over a two-node k3s cluster using our St [...]
+<p><img class="blog-image" style="max-width:80%;" src="/docs/blog/assets/2020-04-14/k3s.png" alt="K3s"></p>
+<h2><a class="anchor" aria-hidden="true" id="introduction"></a><a href="#introduction" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
+<p>While it is easy to get started with StreamPipes in no time using our single-node deployment <a href="/docs/docs/user-guide-installation">instructions</a> using Docker and Docker-Compose, StreamPipes naturally is designed to run in a distributed cluster setup through its microservice architecture.</p>
+<p>This architectural design paired with the advancements of multi-architecture StreamPipes images as described in the previous blog post allows us to run certain analytical pipeline element containers with ease on various target nodes as well as target hardware architecture wether it is X86, ARM32v7, or ARM64v8. This becomes more valuable, as we shift the focus away from centralized cloud or data center only deployments where we generally are provided with a homogenous compute landscape [...]
+<p>Thereby, having multi-architecture images in your repertoire is key to deal with the challenge of heterogeneity in compute resources along the edge-cloud continuum. However, there are other challenges that occur when dealing with distributed container deployments such as automating deployments itself, scaling them, managing the containerized applications, taking care of networking between services, or realizing fault-tolerance by comparing the desired state against the current one. If [...]
+<h2><a class="anchor" aria-hidden="true" id="well-which-k-to-use-kubernetes-k3s"></a><a href="#well-which-k-to-use-kubernetes-k3s" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5 [...]
+<p>Fortunately, there exists a few solutions in the container ecosystem with the open source container orchestrator <a href="https://kubernetes.io">Kubernetes</a> (K8s) being the defacto standard, thereby incorporating the best ideas of Google's internal large-scale container cluster management system <a href="https://kubernetes.io/blog/2015/04/borg-predecessor-to-kubernetes/">Borg</a> (see academic paper about the details published at <a href="https://research.google/pubs/pub43438/">Eur [...]
+<p>On the other hand, there exists <a href="https://k3s.io/">K3s</a>, a lightweight Kubernetes distro by Rancher that was introduced early 2019 and has since then gained huge popularity. As it is stated on their website:</p>
+<ul>
+<li><strong>Perfect for Edge</strong>: <em>K3s is a highly available, certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances</em></li>
+<li><strong>Simplified &amp; Secure</strong>: <em>K3s is packaged as a single &lt;40MB binary that reduces the dependencies and steps needed to install, run and auto-update a production Kubernetes cluster.</em></li>
+<li><strong>Optimized for ARM</strong>: <em>Both ARM64 and ARMv7 are supported with binaries and multiarch images available for both. K3s works great from something as small as a Raspberry Pi to an AWS a1.4xlarge 32GiB server.</em></li>
+</ul>
+<p>Thus, this lead us to the point to say, hey why not use K3s to manage StreamPipes in all its glory. The containerized microservice design in addition to the newly available multiarch images are a great fit.</p>
+<h2><a class="anchor" aria-hidden="true" id="streampipes-helm-chart"></a><a href="#streampipes-helm-chart" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
+<p>While you can easily write an deploy K8s YAML-based manifests for your deployments and services and so on the standard way, it is way more convenient to leverage  <a href="https://helm.sh/">Helm</a>, the package manager for K8s. Helm describes complex, distributed deployments using <strong>charts</strong> in order to provide repeatable application installation, easy updates, rollbacks etc.</p>
+<p>To this extent, we wrote a Helm chart for StreamPipes that can be found on our Github <a href="https://github.com/apache/incubator-streampipes-installer/tree/dev/helm-chart">incubator-streampipes-installer</a> repository. This allows to deploy StreamPipes as one liner as shown later. Helm charts follow a certain directory structure as depicted in the following:</p>
+<pre><code class="hljs">helm-chart/
+  <span class="hljs-module-access"><span class="hljs-module"><span class="hljs-identifier">Chart</span>.</span></span>yaml
+  values.yaml
+  templates/<span class="hljs-operator">
+  ...
+</span></code></pre>
+<p>The <code>Chart.yaml</code> file contains a description of the chart, e.g., metadata such as chart name, version, maintainers etc.</p>
+<p>The <code>values.yaml</code> file contains default values for all charts and in our case serves the purpose to provide a central place to store all variable/values, e.g., <code>streampipes.registry: &quot;apachestreampipes&quot;</code>, that replace chart templates such as the registry and version of the StreamPipes backend image:</p>
+<pre><code class="hljs css language-yaml"><span class="hljs-string">...</span>
+<span class="hljs-attr">image:</span> <span class="hljs-string">{{</span> <span class="hljs-string">.Values.streampipes.registry</span> <span class="hljs-string">}}/backend:{{</span> <span class="hljs-string">.Values.streampipes.version</span> <span class="hljs-string">}}</span>
+<span class="hljs-string">...</span>
+</code></pre>
+<p>Lastly, the <code>template/</code> directory is for template files. When Helm evaluates a chart, it sends all of the files in this directory through the template rendering engine before collecting the results and finally forwarding them to K8s. If interested, you can read more on this in the <a href="https://helm.sh/docs/">official Helm documentation</a>.</p>
+<h2><a class="anchor" aria-hidden="true" id="the-almighty-streampi-k3s-cluster"></a><a href="#the-almighty-streampi-k3s-cluster" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S1 [...]
+<p>As pointed out in the first part of the series, we have gained valueable insights on how to run and deploy StreamPipes on a Raspberry Pi. This worked out so greatly, that we thought, why not step up the game, use another Pi and built the <strong>almighty StreamPi cluster</strong> by leveraging K3s for orchestration and management.</p>
+<p><strong>Note</strong>: We are aware that this is far off from a production-grade setup, especially running StreamPipes core services such as the central pipeline management backend, or the UI in a two-node cluster. However, it provides a solid starting point for more elaborate deployments along the edge-cloud continuum.</p>
+<p>As shown in the following figure, starting from the multiarch images hosted on <a href="https://hub.docker.com/search?q=apachestreampipes&amp;type=image">Dockerhub</a>, we first provisioned the two Pi's with Docker, install and setup K3s and finally deploy our StreamPipes helm chart in order for users to connect, analyze and exploit their IIoT data with StreamPipes.</p>
+<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/deployment.png" alt="Deployment"></p>
+<p>In the remainder, we cover how we installed Helm and K3s to form our almighty StreamPi K3s cluster. At the time of writing, we tested our deployment using the latest version of the Docker, Helm as well as K3s in the following setup</p>
+<ul>
+<li>2x Raspberry Pi Model 4 (4GiB RAM): <code>streampi-01</code>, <code>streampi-02</code></li>
+<li>Raspbian Buster 10</li>
+<li>Docker 19.03.8</li>
+<li>Helm 3.1.2</li>
+<li>K3s v1.17.4+k3s1</li>
+</ul>
+<h3><a class="anchor" aria-hidden="true" id="1-install-docker"></a><a href="#1-install-docker" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
+<p>SSH into your Raspberry Pi's and run the following command:</p>
+<pre><code class="hljs css language-bash">curl -sSL https://get.docker.com | sh
+</code></pre>
+<h3><a class="anchor" aria-hidden="true" id="2-install-k3s"></a><a href="#2-install-k3s" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
+<p>Now that we got Helm installed, we can proceed and install K3s. Thus, we must check wether we fulfill all the requirements. These are mainly network related, such that specific ports (server on <code>6443</code>) are accessible. You should carefully read about this in their <a href="https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/">official documentation</a>.</p>
+<p>Other than that, lean back and enjoy - the installation happens so fast, you might miss it if you get a coffee :)</p>
+<h4><a class="anchor" aria-hidden="true" id="ssh-into-k3s-server-streampi-01"></a><a href="#ssh-into-k3s-server-streampi-01" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
+<p>On the server node, run the following command:</p>
+<pre><code class="hljs css language-bash">sudo curl -sfL https://get.k3s.io | sh -
+</code></pre>
+<p>A kubeconfig file is written to <code>/etc/rancher/k3s/k3s.yaml</code> and the service is automatically started or restarted. The install script will install k3s and additional utilities, such as <code>kubectl</code>, <code>crictl</code>, <code>k3s-killall.sh</code>, and <code>k3s-uninstall.sh</code>.</p>
+<p>The K3s installer creates a systemd service which can be used to <code>stop</code>, <code>start</code>, <code>restart</code> and check the <code>status</code> of the K3s server.</p>
+<pre><code class="hljs css language-bash">sudo systemctl status k3s.service
+
+● k3s.service - Lightweight Kubernetes
+   Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
+   Active: active (running) since Sat 2020-04-11 15:54:07 BST; 3 days ago
+     Docs: https://k3s.io
+  Process: 10193 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
+  Process: 10194 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
+ Main PID: 10195 (k3s-server)
+ (...)
+</code></pre>
+<p>Next, copy the server node token in order to connect additional agent nodes to the cluster.</p>
+<pre><code class="hljs css language-bash">sudo cat /var/lib/rancher/k3s/server/node-token
+</code></pre>
+<h4><a class="anchor" aria-hidden="true" id="ssh-into-k3s-agent-streampi-02"></a><a href="#ssh-into-k3s-agent-streampi-02" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
+<p>Now, open a new terminal session and SSH into your agent and run the following command, thereby adding the copied <code>K3S_TOKEN</code> to connect to the server, that is specified using <code>K3S_URL</code>.</p>
+<pre><code class="hljs css language-bash">sudo curl -sfL https://get.k3s.io | K3S_URL=https://streampi-01:6443 \
+K3S_TOKEN=&lt;NODE_TOKEN&gt; sh -
+</code></pre>
+<p>The K3s installer creates a systemd service which can be used to <code>stop</code>, <code>start</code>, <code>restart</code> and check the <code>status</code> of the K3s agent.</p>
+<pre><code class="hljs css language-bash">sudo systemctl status k3s-agent.service
+
+● k3s-agent.service - Lightweight Kubernetes
+   Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
+   Active: active (running) since Sat 2020-04-11 16:05:37 BST; 3 days ago
+     Docs: https://k3s.io
+  Process: 24469 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
+  Process: 24470 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
+ Main PID: 24471 (k3s-agent)
+ (...)
+</code></pre>
+<p>That's it ... that's all!</p>
+<p>When you go back to the terminal session on the K3s server you can list all nodes in the cluster using standard <code>kubectl</code> commands.</p>
+<pre><code class="hljs css language-bash">kubectl get nodes
+NAME              STATUS   ROLES    AGE   VERSION
+streampi-02   Ready    &lt;none&gt;   3d    v1.17.4+k3s1
+streampi-01   Ready    master   3d    v1.17.4+k3s1
+</code></pre>
+<p>Hmmm - but wait. We did only add one agent node to the cluster right? Well, that's true, however when installing K3s using the script the server automatically installs and runs an agent on the same node.</p>
+<h3><a class="anchor" aria-hidden="true" id="3-install-helm"></a><a href="#3-install-helm" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
+<p>SSH into the RPi that should act as the K3s server later on - in our case this is <code>streampi-01</code> and install Helm. Since we are using Helm 3 there is no need to install tiller. Thus, installing helm is as simple as running the following command:</p>
+<pre><code class="hljs css language-bash">curl -sSL https://get.helm.sh/helm-v3.1.2-linux-arm.tar.gz | sudo tar -xzf - -C /usr/<span class="hljs-built_in">local</span>/bin/ linux-arm/helm --strip-components=1
+</code></pre>
+<p>This command downloads the Helm binary release from Github, extracts only the binary and puts it in <code>/usr/local/bin</code>. Try go check <code>helm version</code> to see if it worked.</p>
+<pre><code class="hljs css language-bash">version.BuildInfo{Version:<span class="hljs-string">"v3.1.2"</span>, GitCommit:<span class="hljs-string">"d878d4d45863e42fd5cff6743294a11d28a9abce"</span>, GitTreeState:<span class="hljs-string">"clean"</span>, GoVersion:<span class="hljs-string">"go1.13.8"</span>}
+</code></pre>
+<p>To use Helm, we can set and export <code>KUBECONFIG</code> environment variable to point to the kubeconfig under <code>/etc/rancher/k3s/k3s.yaml</code>.</p>
+<pre><code class="hljs css language-bash"><span class="hljs-built_in">export</span> KUBECONFIG=/etc/rancher/k3s/k3s.yaml
+</code></pre>
+<p>Alternatively, if you want this permanently you can either add it to your <code>.bashrc</code>/<code>.zshrc</code>, or create a <code>.kube</code> directory in your home directory and symlink the <code>k3s.yaml</code>.</p>
+<pre><code class="hljs css language-bash">mkdir <span class="hljs-variable">$HOME</span>/.kube
+ln -s /etc/rancher/k3s/k3s.yaml <span class="hljs-variable">$HOME</span>/.kube/config
+</code></pre>
+<h2><a class="anchor" aria-hidden="true" id="deploy-streampipes-on-k3s-using-helm"></a><a href="#deploy-streampipes-on-k3s-using-helm" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 [...]
+<p>Now, that we have all set up, we can go ahead and deploy StreamPipes using our Helm chart. Therefore, we go to the server node (<code>streampi-01</code>), where we installed Helm. Next, we clone our StreamPipes installer repository (<code>dev</code> branch) and navigate to the helm-chart directory.</p>
+<p><strong>Note</strong>: At the point of writing, the helm chart is <strong>only</strong> available in the <code>dev</code> branch. This will change in the future as we update the repository.</p>
+<pre><code class="hljs css language-bash">git <span class="hljs-built_in">clone</span> -b dev --single-branch https://github.com/apache/incubator-streampipes-installer.git
+<span class="hljs-built_in">cd</span> incubator-streampipes-installer
+</code></pre>
+<p>At this point, we can leverage Helm's <code>install</code> command in order to install the StreamPipes Helm chart. Since Helm reads the K3s kubeconfig, it forwards the deployment request to K3s. As per default, we deploy StreamPipes <code>lite</code> version, where we only start standalone Java-based pipeline elements and disregard the ones building on top of our Flink wrapper.</p>
+<pre><code class="hljs css language-bash">helm install streampipes helm-chart
+
+NAME: streampipes
+LAST DEPLOYED: Tue Apr 14 18:13:19 2020
+NAMESPACE: default
+STATUS: deployed
+REVISION: 1
+TEST SUITE: None
+</code></pre>
+<p>Next, K3s receives this requests and goes ahead and downloads the corresponding Docker images and starts the deployments in the right order according to the specified dependencies, creates services as well as persistent volume claims when needed. This step takes some time depending on your internet connection and the hardware when starting the containers. You can check the status of the StreamPipes Helm installation using <code>kubectl get pods -o wide</code> (when adding <code>-w</co [...]
+<pre><code class="hljs css language-bash">kubectl get pods -o=custom-columns=NAME:.metadata.name,STATUS:.status.phase,NODE:.spec.nodeName
+
+NAME                                           STATUS    NODE
+activemq-66d58f47cf-b88nb                      Running   streampi-01
+zookeeper-5d9947686f-7vpjb                     Running   streampi-02
+couchdb-77db98cf7b-6nn99                       Running   streampi-02
+consul-55965f966b-tjcfb                        Running   streampi-02
+influxdb-b95b6479-mvgbg                        Running   streampi-02
+backend-6cdfb7bbf9-b4vgh                       Running   streampi-02
+pipeline-elements-all-jvm-64795974-g2xhv       Running   streampi-02
+kafka-657b5fb77-xtw8p                          Running   streampi-01
+connect-master-56f5f947d-n2t5b                 Running   streampi-01
+sources-watertank-simulator-6958f7844c-2jv78   Running   streampi-01
+connect-worker-fdbd6f464-m6vm8                 Running   streampi-01
+nginx-5d4498d4f5-fcccq                         Running   streampi-02
+</code></pre>
+<p>As can be seen, a fair amount of StreamPipes containers aka pods were deployed on <code>streampi-01</code> and <code>streampi-02</code>. When everything goes well, you should see all containers in the status <code>RUNNING</code> after a couple of minutes. To access K8s cluster UI pod a <code>NodePort</code> was created. The <code>NodePort</code> publishes the UI (nginx) service on every node using using its public IP and a port. Then you can access the service using any of the cluster [...]
+<pre><code class="hljs css language-yaml"><span class="hljs-attr">apiVersion:</span> <span class="hljs-string">v1</span>
+<span class="hljs-attr">kind:</span> <span class="hljs-string">Service</span>
+<span class="hljs-attr">metadata:</span>
+  <span class="hljs-attr">name:</span> <span class="hljs-string">nginx</span>
+<span class="hljs-attr">spec:</span>
+  <span class="hljs-attr">selector:</span>
+    <span class="hljs-attr">app:</span> <span class="hljs-string">nginx</span>
+  <span class="hljs-attr">type:</span> <span class="hljs-string">NodePort</span>
+  <span class="hljs-attr">ports:</span>
+    <span class="hljs-bullet">-</span> <span class="hljs-attr">name:</span> <span class="hljs-string">main</span>
+      <span class="hljs-attr">protocol:</span> <span class="hljs-string">TCP</span>
+      <span class="hljs-attr">port:</span> <span class="hljs-number">80</span> <span class="hljs-comment"># container port</span>
+      <span class="hljs-attr">targetPort:</span> <span class="hljs-number">80</span> <span class="hljs-comment"># node port</span>
+</code></pre>
+<p>That means, you can go and check the StreamPipes UI either on <code>http://streampi-01/</code> or <code>http://streampi-02/</code> - K8s service handles the routing to the nginx pod containing the UI - just to name one nice feature.</p>
+<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/streampi_installation.png" alt="Installation"></p>
+<h2><a class="anchor" aria-hidden="true" id="sum-up-where-to-go-from-here"></a><a href="#sum-up-where-to-go-from-here" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
+<p>Starting out as a simple hack session on a late afternoon, we build multi-archicture StreamPipes Docker images and deployed them on a Raspberry Pi in the first part of the series. Though, this is was feasible StreamPipes architectural microservice design provides a natural fit for a distributed cluster deployment. To this extent, we provide a StreamPipes Helm chart that lets you easily deploy StreamPipes in a one-liner in a Kubernetes cluster as showcased using a testbed of two Raspbe [...]
+<p>As of now, we let K8s handle the scheduling of containers for us in a random fashion. From here, we can further explore K8s feature such as <code>nodeSelector</code> or <code>nodeAffinity</code> that helps you use labels (<code>key=value</code> pairs) for pod to node assignment.</p>
+<p><img class="blog-image" style="max-width:60%;" src="/docs/blog/assets/2020-04-14/helm_k3s.png" alt="HelmK3s"></p>
+<ul>
+<li><a href="/docs/blog/2020/01/23/streampipes_on_rpi">Part 1: StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></li>
+<li><strong><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Part 2: Running StreamPipes the Kubernetes-Way using K3s</a></strong></li>
+</ul>
+<h3><a class="anchor" aria-hidden="true" id="useful-links"></a><a href="#useful-links" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
+<ul>
+<li>[1] <a href="https://k3s.io/">K3s - lightweight Kubernetes distro</a></li>
+<li>[2] <a href="https://helm.sh/">Helm - the package manager for Kubernetes</a></li>
+<li>[3] <a href="https://github.com/apache/incubator-streampipes-installer/tree/dev/helm-chart">Github: StreamPipes Helm chart</a></li>
+</ul>
+</span></div></div><div class="blogSocialSection"></div></div><div class="blog-recent"><a class="button" href="/docs/blog">Recent Posts</a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#well-which-k-to-use-kubernetes-k3s">Well, which K to use? Kubernetes, K3s</a></li><li><a href="#streampipes-helm-chart">StreamPipes Helm Chart</a></li><li><a href="#the-almighty-streampi-k3s-cluster">The almighty StreamPi K3 [...]
+                document.addEventListener('keyup', function(e) {
+                  if (e.target !== document.body) {
+                    return;
+                  }
+                  // keyCode for '/' (slash)
+                  if (e.keyCode === 191) {
+                    const search = document.getElementById('search_input_react');
+                    search && search.focus();
+                  }
+                });
+              </script><script>
+              var search = docsearch({
+                
+                apiKey: '0fedc89dddf2810657708b178e56ef02',
+                indexName: 'streampipes',
+                inputSelector: '#search_input_react',
+                algoliaOptions: {}
+              });
+            </script></body></html>
\ No newline at end of file
diff --git a/docs/blog/assets/2020-04-14/deployment.png b/docs/blog/assets/2020-04-14/deployment.png
new file mode 100644
index 0000000..de608a8
Binary files /dev/null and b/docs/blog/assets/2020-04-14/deployment.png differ
diff --git a/docs/blog/assets/2020-04-14/helm_k3s.png b/docs/blog/assets/2020-04-14/helm_k3s.png
new file mode 100644
index 0000000..700367b
Binary files /dev/null and b/docs/blog/assets/2020-04-14/helm_k3s.png differ
diff --git a/docs/blog/assets/2020-04-14/k3s.png b/docs/blog/assets/2020-04-14/k3s.png
new file mode 100644
index 0000000..72092be
Binary files /dev/null and b/docs/blog/assets/2020-04-14/k3s.png differ
diff --git a/docs/blog/assets/2020-04-14/streampi_installation.png b/docs/blog/assets/2020-04-14/streampi_installation.png
new file mode 100644
index 0000000..77187df
Binary files /dev/null and b/docs/blog/assets/2020-04-14/streampi_installation.png differ
diff --git a/docs/blog/assets/2020-04-14/streampipes_k3s.png b/docs/blog/assets/2020-04-14/streampipes_k3s.png
new file mode 100644
index 0000000..7bbcec0
Binary files /dev/null and b/docs/blog/assets/2020-04-14/streampipes_k3s.png differ
diff --git a/docs/blog/atom.xml b/docs/blog/atom.xml
index 53896d2..bdb2aa7 100644
--- a/docs/blog/atom.xml
+++ b/docs/blog/atom.xml
@@ -2,13 +2,29 @@
 <feed xmlns="http://www.w3.org/2005/Atom">
     <id>https://docs.streampipes.org/docs/blog</id>
     <title>StreamPipes Blog</title>
-    <updated>2020-01-23T06:00:00Z</updated>
+    <updated>2020-04-14T06:00:00Z</updated>
     <generator>Feed for Node.js</generator>
     <link rel="alternate" href="https://docs.streampipes.org/docs/blog"/>
     <subtitle>The best place to stay up-to-date with the latest StreamPipes news and events.</subtitle>
     <logo>https://docs.streampipes.org/docs/img/sp-logo-color-docs.png</logo>
     <rights>Copyright © 2020 The Apache Software Foundation</rights>
     <entry>
+        <title type="html"><![CDATA[Running StreamPipes the Kubernetes-Way using k3s]]></title>
+        <id>https://docs.streampipes.org/docs/blog/2020/04/14/streampipes_on_k3s.html</id>
+        <link href="https://docs.streampipes.org/docs/blog/2020/04/14/streampipes_on_k3s.html">
+        </link>
+        <updated>2020-04-14T06:00:00Z</updated>
+        <summary type="html"><![CDATA[<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/streampipes_k3s.png" alt="StreamPipes on k3s">
+<strong><div style="float: left; padding-right: 40px;">15 minutes to read</div></strong>
+<br></p>
+<p>This blog post is the second part of a series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via k3s using our StreamPipes helm chart.</p>
+]]></summary>
+        <author>
+            <name>Patrick Wiener</name>
+            <uri>https://twitter.com/patrickwiener</uri>
+        </author>
+    </entry>
+    <entry>
         <title type="html"><![CDATA[StreamPi(pes) - Running StreamPipes on Raspberry Pi]]></title>
         <id>https://docs.streampipes.org/docs/blog/2020/01/23/streampipes_on_rpi.html</id>
         <link href="https://docs.streampipes.org/docs/blog/2020/01/23/streampipes_on_rpi.html">
@@ -17,7 +33,7 @@
         <summary type="html"><![CDATA[<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-01-23/streampipes_raspberrypi.png" alt="StreamPipes on Raspberry Pi">
 <strong><div style="float: left; padding-right: 40px;">5 minutes to read</div></strong>
 <br></p>
-<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The first part describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the the second part further covers how to deploy StreamPipes over a two-node Raspberry Pi cluster managed via k3s using our StreamPipes helm chart.</p>
+<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via K3s using our StreamPipes helm chart.</p>
 ]]></summary>
         <author>
             <name>Patrick Wiener</name>
diff --git a/docs/blog/feed.xml b/docs/blog/feed.xml
index 30b6607..d5b8788 100644
--- a/docs/blog/feed.xml
+++ b/docs/blog/feed.xml
@@ -4,7 +4,7 @@
         <title>StreamPipes Blog</title>
         <link>https://docs.streampipes.org/docs/blog</link>
         <description>The best place to stay up-to-date with the latest StreamPipes news and events.</description>
-        <lastBuildDate>Thu, 23 Jan 2020 06:00:00 GMT</lastBuildDate>
+        <lastBuildDate>Tue, 14 Apr 2020 06:00:00 GMT</lastBuildDate>
         <docs>http://blogs.law.harvard.edu/tech/rss</docs>
         <generator>Feed for Node.js</generator>
         <image>
@@ -14,6 +14,17 @@
         </image>
         <copyright>Copyright © 2020 The Apache Software Foundation</copyright>
         <item>
+            <title><![CDATA[Running StreamPipes the Kubernetes-Way using k3s]]></title>
+            <link>https://docs.streampipes.org/docs/blog/2020/04/14/streampipes_on_k3s.html</link>
+            <guid>https://docs.streampipes.org/docs/blog/2020/04/14/streampipes_on_k3s.html</guid>
+            <pubDate>Tue, 14 Apr 2020 06:00:00 GMT</pubDate>
+            <description><![CDATA[<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-04-14/streampipes_k3s.png" alt="StreamPipes on k3s">
+<strong><div style="float: left; padding-right: 40px;">15 minutes to read</div></strong>
+<br></p>
+<p>This blog post is the second part of a series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via k3s using our StreamPipes helm chart.</p>
+]]></description>
+        </item>
+        <item>
             <title><![CDATA[StreamPi(pes) - Running StreamPipes on Raspberry Pi]]></title>
             <link>https://docs.streampipes.org/docs/blog/2020/01/23/streampipes_on_rpi.html</link>
             <guid>https://docs.streampipes.org/docs/blog/2020/01/23/streampipes_on_rpi.html</guid>
@@ -21,7 +32,7 @@
             <description><![CDATA[<p><img class="blog-image" style="max-width:100%;" src="/docs/blog/assets/2020-01-23/streampipes_raspberrypi.png" alt="StreamPipes on Raspberry Pi">
 <strong><div style="float: left; padding-right: 40px;">5 minutes to read</div></strong>
 <br></p>
-<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The first part describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the the second part further covers how to deploy StreamPipes over a two-node Raspberry Pi cluster managed via k3s using our StreamPipes helm chart.</p>
+<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via K3s using our StreamPipes helm chart.</p>
 ]]></description>
         </item>
         <item>
diff --git a/docs/blog/index.html b/docs/blog/index.html
index 51ba443..661881c 100644
--- a/docs/blog/index.html
+++ b/docs/blog/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="blog"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><nav class="slidingNav"><ul cl [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="blog"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><nav class="slidingNav"><ul cl [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
@@ -59,10 +59,14 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="posts"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/01/23/streampipes_on_rpi">StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></h1><p class="post-meta">January 23, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer noope [...]
+        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="posts"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/04/14/streampipes_on_k3s">Running StreamPipes the Kubernetes-Way using k3s</a></h1><p class="post-meta">April 14, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer noopener"> [...]
+<strong><div style="float: left; padding-right: 40px;">15 minutes to read</div></strong>
+<br></p>
+<p>This blog post is the second part of a series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via k3s using our StreamPipes helm chart.</p>
+</span></div><div class="read-more"><a class="button" href="/docs/blog/2020/04/14/streampipes_on_k3s">Read More</a></div></article></div><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2020/01/23/streampipes_on_rpi">StreamPi(pes) - Running StreamPipes on Raspberry Pi</a></h1><p class="post-meta">January 23, 2020</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/patrickwiener" target="_blank" rel="noreferrer no [...]
 <strong><div style="float: left; padding-right: 40px;">5 minutes to read</div></strong>
 <br></p>
-<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The first part describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the the second part further covers how to deploy StreamPipes over a two-node Raspberry Pi cluster managed via k3s using our StreamPipes helm chart.</p>
+<p>This is the start of a two part series on how we want to bring StreamPipes closer to the edge. The <a href="/docs/blog/2020/01/23/streampipes_on_rpi">first part</a> describes how we managed to build and deploy StreamPipes on one Raspberry Pi (Model 4), while the <a href="/docs/blog/2020/04/14/streampipes_on_k3s">second part</a> further covers how to deploy StreamPipes over a Kubernetes cluster of two Raspberry Pi's via K3s using our StreamPipes helm chart.</p>
 </span></div><div class="read-more"><a class="button" href="/docs/blog/2020/01/23/streampipes_on_rpi">Read More</a></div></article></div><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2019/11/25/moving-to-the-apache-incubator">Moving to the Apache Incubator</a></h1><p class="post-meta">November 25, 2019</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/dominikjriemer" target="_blank" rel="noreferrer noopener" [...]
 <br>
 Great news: StreamPipes is moving to the Apache Incubator!</p>
@@ -94,13 +98,7 @@ All you need is a working docker-compose.yml file.</p>
 <br></p>
 <p>It's been a while since our last blog post. However, in the background we are working hard to release the next version of StreamPipes which is currently in the final phase.
 In this post, we'd like to give you a preview of the upcoming StreamPipes version 0.60.0, which brings many new features and improvements.</p>
-</span></div><div class="read-more"><a class="button" href="/docs/blog/2018/09/17/preview-060">Read More</a></div></article></div><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2018/06/18/how-to-understand-your-machine-data">How to understand your machine data?</a></h1><p class="post-meta">June 18, 2018</p><div class="authorBlock"><p class="post-authorName"><a href="http://twitter.com/philipp10der" target="_blank" rel="noreferrer noopener">Ph [...]
-<br></p>
-<p>Data is the new oil. Probably everybody of you has heard or read this sentence before.
-It is often stated how important data and data understanding is for companies today.
-But what does this actually mean?  How does the data look like that is produced by your machines and systems?
-And how can we solve the big challenge to turn this raw data into insights that can be understood by humans?</p>
-</span></div><div class="read-more"><a class="button" href="/docs/blog/2018/06/18/how-to-understand-your-machine-data">Read More</a></div></article></div><div class="docs-prevnext"><a class="docs-next" href="/docs/blog/page2/">Next →</a></div></div></div></div></div><div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/docs/" class="nav-home"><img src="/docs/img/sp-logo-color.png" alt="StreamPipes" width="66"/></a><div><h5>Docs</h5><a href="/docs/docs/user-guide- [...]
+</span></div><div class="read-more"><a class="button" href="/docs/blog/2018/09/17/preview-060">Read More</a></div></article></div><div class="docs-prevnext"><a class="docs-next" href="/docs/blog/page2/">Next →</a></div></div></div></div></div><div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/docs/" class="nav-home"><img src="/docs/img/sp-logo-color.png" alt="StreamPipes" width="66"/></a><div><h5>Docs</h5><a href="/docs/docs/user-guide-introduction">User Guide [...]
                 document.addEventListener('keyup', function(e) {
                   if (e.target !== document.body) {
                     return;
diff --git a/docs/blog/page2/index.html b/docs/blog/page2/index.html
index a96e778..31f401f 100644
--- a/docs/blog/page2/index.html
+++ b/docs/blog/page2/index.html
@@ -9,7 +9,7 @@
             {"zIndex":100}
           )
         });
-        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="blog"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><nav class="slidingNav"><ul cl [...]
+        </script><link rel="stylesheet" href="/docs/css/prism.css"/><link rel="stylesheet" href="/docs/css/main.css"/><script src="/docs/js/codetabs.js"></script></head><body class="blog"><div class="fixedHeaderContainer"><div class="headerWrapper wrapper"><header><a href="/docs/"><img class="logo" src="/docs/img/sp-logo-color-docs.png" alt="StreamPipes"/></a><a href="/docs/versions"><h3>0.65.0-pre-asf</h3></a><div class="navigationWrapper navigationSlider"><nav class="slidingNav"><ul cl [...]
             var coll = document.getElementsByClassName('collapsible');
             var checkActiveCategory = true;
             for (var i = 0; i < coll.length; i++) {
@@ -59,7 +59,13 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="posts"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2018/06/14/welcome">Welcome to StreamPipes!</a></h1><p class="post-meta">June 14, 2018</p><div class="authorBlock"><p class="post-authorName"><a href="http://twitter.com/dominikjriemer" target="_blank" rel="noreferrer noopener">Dominik Riemer</a></p><div class="aut [...]
+        </script></nav></div><div class="container mainContainer postContainer blogContainer"><div class="wrapper"><div class="posts"><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2018/06/18/how-to-understand-your-machine-data">How to understand your machine data?</a></h1><p class="post-meta">June 18, 2018</p><div class="authorBlock"><p class="post-authorName"><a href="http://twitter.com/philipp10der" target="_blank" rel="noreferrer noopener [...]
+<br></p>
+<p>Data is the new oil. Probably everybody of you has heard or read this sentence before.
+It is often stated how important data and data understanding is for companies today.
+But what does this actually mean?  How does the data look like that is produced by your machines and systems?
+And how can we solve the big challenge to turn this raw data into insights that can be understood by humans?</p>
+</span></div><div class="read-more"><a class="button" href="/docs/blog/2018/06/18/how-to-understand-your-machine-data">Read More</a></div></article></div><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/docs/blog/2018/06/14/welcome">Welcome to StreamPipes!</a></h1><p class="post-meta">June 14, 2018</p><div class="authorBlock"><p class="post-authorName"><a href="http://twitter.com/dominikjriemer" target="_blank" rel="noreferrer noopener">Dominik Riemer</a [...]
 <p>Stay tuned!</p>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev" href="/docs/blog/">← Prev</a></div></div></div></div></div><div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/docs/" class="nav-home"><img src="/docs/img/sp-logo-color.png" alt="StreamPipes" width="66"/></a><div><h5>Docs</h5><a href="/docs/docs/user-guide-introduction">User Guide</a><a href="/docs/docs/dev-guide-introduction">Developer Guide</a><a href="/docs/docs/faq-common-problems" [...]
                 document.addEventListener('keyup', function(e) {
diff --git a/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources.html b/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources.html
index 4018927..a10de5b 100644
--- a/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources.html
+++ b/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources.html
@@ -111,7 +111,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAlreadyExistingStream</code>. This class indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).
 In contrast, if you'd plan to define a stream that produces data (e.g., simulates vehicle positions directly from this module), you could extend the class <code>AbstractAdapterIncludedStream</code>.</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"vehicle-position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources/index.html b/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources/index.html
index 4018927..a10de5b 100644
--- a/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/0.55.2-pre-asf/dev-guide-tutorial-sources/index.html
@@ -111,7 +111,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAlreadyExistingStream</code>. This class indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).
 In contrast, if you'd plan to define a stream that produces data (e.g., simulates vehicle positions directly from this module), you could extend the class <code>AbstractAdapterIncludedStream</code>.</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"vehicle-position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-event-model.html b/docs/docs/0.61.0-pre-asf/dev-guide-event-model.html
index cef4b6a..9569882 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-event-model.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.61.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.61.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.61.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.61.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.61.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.61.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-event-model/index.html b/docs/docs/0.61.0-pre-asf/dev-guide-event-model/index.html
index cef4b6a..9569882 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-event-model/index.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.61.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.61.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.61.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.61.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.61.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.61.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors.html b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors.html
index a0598c5..a341136 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors.html
@@ -256,7 +256,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors/index.html b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors/index.html
index a0598c5..a341136 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-processors/index.html
@@ -256,7 +256,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources.html b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources.html
index 2a39b66..d316037 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources/index.html b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources/index.html
index 2a39b66..d316037 100644
--- a/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/0.61.0-pre-asf/dev-guide-tutorial-sources/index.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-event-model.html b/docs/docs/0.62.0-pre-asf/dev-guide-event-model.html
index 33018c6..8bba494 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-event-model.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.62.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.62.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.62.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.62.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.62.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.62.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-event-model/index.html b/docs/docs/0.62.0-pre-asf/dev-guide-event-model/index.html
index 33018c6..8bba494 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-event-model/index.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.62.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.62.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.62.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.62.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.62.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.62.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors.html b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors.html
index be12d70..d547786 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors.html
@@ -256,7 +256,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors/index.html b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors/index.html
index be12d70..d547786 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-processors/index.html
@@ -256,7 +256,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources.html b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources.html
index 4a958fb..361522d 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources/index.html b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources/index.html
index 4a958fb..361522d 100644
--- a/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/0.62.0-pre-asf/dev-guide-tutorial-sources/index.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-event-model.html b/docs/docs/0.63.0-pre-asf/dev-guide-event-model.html
index 8f198e0..191c79f 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-event-model.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.63.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.63.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.63.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.63.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.63.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.63.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-event-model/index.html b/docs/docs/0.63.0-pre-asf/dev-guide-event-model/index.html
index 8f198e0..191c79f 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-event-model/index.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.63.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.63.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.63.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.63.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.63.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.63.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors.html b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors.html
index 6165bdf..53a6f21 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors/index.html b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors/index.html
index 6165bdf..53a6f21 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-processors/index.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources.html b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources.html
index d694f28..6614296 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources/index.html b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources/index.html
index d694f28..6614296 100644
--- a/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/0.63.0-pre-asf/dev-guide-tutorial-sources/index.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-event-model.html b/docs/docs/0.64.0-pre-asf/dev-guide-event-model.html
index 7f21dca..8562ebc 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-event-model.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.64.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.64.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.64.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.64.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.64.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.64.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-event-model/index.html b/docs/docs/0.64.0-pre-asf/dev-guide-event-model/index.html
index 7f21dca..8562ebc 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-event-model/index.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/0.64.0-pre-asf/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/0.64.0-pre-asf/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.64.0-pre-asf/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/0.64.0-pre-asf/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/0.64.0-pre-asf/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/0.64.0-pre-asf/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Refere [...]
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors.html b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors.html
index bc921a3..4e083d9 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors.html
@@ -262,7 +262,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors/index.html b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors/index.html
index bc921a3..4e083d9 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-processors/index.html
@@ -262,7 +262,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources.html b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources.html
index e566302..6fc21d0 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources/index.html b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources/index.html
index e566302..6fc21d0 100644
--- a/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/0.64.0-pre-asf/dev-guide-tutorial-sources/index.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/dev-guide-event-model.html b/docs/docs/dev-guide-event-model.html
index 62b891a..d21a778 100644
--- a/docs/docs/dev-guide-event-model.html
+++ b/docs/docs/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Reference</a><ul class="toc-headings [...]
diff --git a/docs/docs/dev-guide-event-model/index.html b/docs/docs/dev-guide-event-model/index.html
index 62b891a..d21a778 100644
--- a/docs/docs/dev-guide-event-model/index.html
+++ b/docs/docs/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Reference</a><ul class="toc-headings [...]
diff --git a/docs/docs/dev-guide-tutorial-processors.html b/docs/docs/dev-guide-tutorial-processors.html
index e523aec..e0c91ee 100644
--- a/docs/docs/dev-guide-tutorial-processors.html
+++ b/docs/docs/dev-guide-tutorial-processors.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/dev-guide-tutorial-processors/index.html b/docs/docs/dev-guide-tutorial-processors/index.html
index e523aec..e0c91ee 100644
--- a/docs/docs/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/dev-guide-tutorial-processors/index.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/dev-guide-tutorial-sources.html b/docs/docs/dev-guide-tutorial-sources.html
index 2c9d1a3..85dc7a0 100644
--- a/docs/docs/dev-guide-tutorial-sources.html
+++ b/docs/docs/dev-guide-tutorial-sources.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/dev-guide-tutorial-sources/index.html b/docs/docs/dev-guide-tutorial-sources/index.html
index 2c9d1a3..85dc7a0 100644
--- a/docs/docs/dev-guide-tutorial-sources/index.html
+++ b/docs/docs/dev-guide-tutorial-sources/index.html
@@ -130,7 +130,7 @@ First, open the class <code>VehicleStream</code> which should look as follows:</
 </code></pre>
 <p>This class extends the class <code>AbstractAdapterIncludedStream</code>, which indicates that this source continuously produces data (configured in the <code>executeStream()</code> method.
 In contrast, the class <code>AbstractAlreadyExistingStream</code> indicates that we only want to describe an already existing stream (e.g., a stream that already sends data to an existing Kafka broker).</p>
-<p>No we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
+<p>Now we will add the definition of the data stream. Add the following code inside of the <code>declareModel</code> method:</p>
 <pre><code class="hljs css language-java"><span class="hljs-keyword">return</span> DataStreamBuilder.create(<span class="hljs-string">"org.streampipes.tutorial.vehicle.position"</span>, <span class="hljs-string">"Vehicle Position"</span>, <span class="hljs-string">"An event stream "</span> +
           <span class="hljs-string">"that produces current vehicle positions"</span>)
 </code></pre>
diff --git a/docs/docs/next/dev-guide-development-environment.html b/docs/docs/next/dev-guide-development-environment.html
index a147c4f..c0cc281 100644
--- a/docs/docs/next/dev-guide-development-environment.html
+++ b/docs/docs/next/dev-guide-development-environment.html
@@ -73,7 +73,7 @@ The CLI tool allows to switch to several templates (based on docker-compose) dep
 <p>Now, once you've started the development instance, you are ready to develop your very first pipeline element.
 Instead of starting from scratch, we recommend using our provided maven archetypes:</p>
 <h3><a class="anchor" aria-hidden="true" id="maven-archetypes"></a><a href="#maven-archetypes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
-<p>Create the Maven archetype as described in the <a href="dev-guide-archetype">Getting Started</a> guide.</p>
+<p>Create the Maven archetype as described in the <a href="/docs/dev-guide-archetype">Getting Started</a> guide.</p>
 <h3><a class="anchor" aria-hidden="true" id="starting-from-scratch"></a><a href="#starting-from-scratch" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2 [...]
 <p>In order to develop a new pipeline element from scratch, you need to create a new Maven project and import the following dependencies:</p>
 <p><details class="info">
diff --git a/docs/docs/next/dev-guide-development-environment/index.html b/docs/docs/next/dev-guide-development-environment/index.html
index a147c4f..c0cc281 100644
--- a/docs/docs/next/dev-guide-development-environment/index.html
+++ b/docs/docs/next/dev-guide-development-environment/index.html
@@ -73,7 +73,7 @@ The CLI tool allows to switch to several templates (based on docker-compose) dep
 <p>Now, once you've started the development instance, you are ready to develop your very first pipeline element.
 Instead of starting from scratch, we recommend using our provided maven archetypes:</p>
 <h3><a class="anchor" aria-hidden="true" id="maven-archetypes"></a><a href="#maven-archetypes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
-<p>Create the Maven archetype as described in the <a href="dev-guide-archetype">Getting Started</a> guide.</p>
+<p>Create the Maven archetype as described in the <a href="/docs/dev-guide-archetype">Getting Started</a> guide.</p>
 <h3><a class="anchor" aria-hidden="true" id="starting-from-scratch"></a><a href="#starting-from-scratch" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2 [...]
 <p>In order to develop a new pipeline element from scratch, you need to create a new Maven project and import the following dependencies:</p>
 <p><details class="info">
diff --git a/docs/docs/next/dev-guide-event-model.html b/docs/docs/next/dev-guide-event-model.html
index b1fd6a2..c148564 100644
--- a/docs/docs/next/dev-guide-event-model.html
+++ b/docs/docs/next/dev-guide-event-model.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/next/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/next/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/next/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/next/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/next/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/next/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Reference</a><ul class="to [...]
diff --git a/docs/docs/next/dev-guide-event-model/index.html b/docs/docs/next/dev-guide-event-model/index.html
index b1fd6a2..c148564 100644
--- a/docs/docs/next/dev-guide-event-model/index.html
+++ b/docs/docs/next/dev-guide-event-model/index.html
@@ -66,7 +66,7 @@
 <h2><a class="anchor" aria-hidden="true" id="reference"></a><a href="#reference" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
 <p>This guide assumes that you are already familiar with the basic setup of <a href="/docs/docs/next/dev-guide-sdk-guide-processors">data processors</a> and <a href="/docs/docs/next/dev-guide-sdk-guide-sinks">data sinks</a>.</p>
 <h3><a class="anchor" aria-hidden="true" id="property-selectors"></a><a href="#property-selectors" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/next/dev-guide-static-properties">static properties</a>.</p>
+<p>In most cases, fields that are subject to be transformed by pipeline elements are provided by the assigned <code>MappingProperty</code> (see the guide on <a href="/docs/docs/next/dev-guide-static-properties">static properties</a>).</p>
 <p>Mapping properties return a <code>PropertySelector</code> that identifies a field based on (i) the <strong>streamIndex</strong> and (ii) the runtime name of the field.
 Let's assume we have an event with the following structure:</p>
 <pre><code class="hljs css language-json">{
@@ -151,7 +151,7 @@ List&lt;Integer&gt; lastValues = event.getFieldBySelector(lastValueSelector).get
     <span class="hljs-comment">// remove the field "temperature" from the event</span>
     event.removeFieldBySelector(temperatureSelector);
 
-    <span class="hljs-comment">// add a new field </span>
+    <span class="hljs-comment">// add a new field</span>
     event.addField(<span class="hljs-string">"fahrenheit"</span>, <span class="hljs-number">48</span>);
 </code></pre>
 </span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/docs/next/dev-guide-output-strategies"><span class="arrow-prev">← </span><span>Output Strategies</span></a><a class="docs-next button" href="/docs/docs/next/dev-guide-ssl"><span>Use SSL</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#introduction">Introduction</a></li><li><a href="#reference">Reference</a><ul class="to [...]
diff --git a/docs/docs/next/dev-guide-tutorial-processors.html b/docs/docs/next/dev-guide-tutorial-processors.html
index dbe2066..adfa12f 100644
--- a/docs/docs/next/dev-guide-tutorial-processors.html
+++ b/docs/docs/next/dev-guide-tutorial-processors.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/docs/next/dev-guide-tutorial-processors/index.html b/docs/docs/next/dev-guide-tutorial-processors/index.html
index dbe2066..adfa12f 100644
--- a/docs/docs/next/dev-guide-tutorial-processors/index.html
+++ b/docs/docs/next/dev-guide-tutorial-processors/index.html
@@ -254,7 +254,7 @@ Open the file <code>GeofencingParameters</code> and modify it as follows:</p>
 </code></pre>
 <p>This simple Pojo class will later serve to store user-defined parameters in a single object.</p>
 <p>Now we go back to the controller class and extract these values from the invocation object.</p>
-<p>The <code>ProessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
+<p>The <code>ProcessingElementParameterExtractor</code>  provides convenience methods to extract the relevant information from the <code>DataProcessorInvocation</code> object.</p>
 <p>Next, we are interested in the fields of the input event stream that contains the latitude and longitude value we would like to compute against the geofence center location as follows:</p>
 <pre><code class="hljs css language-java">String latitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"latitude-field"</span>);
 String longitudeFieldName = extractor.mappingPropertyValue(<span class="hljs-string">"longitude-field"</span>);
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index 211e8d2..dc6ee50 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -2,6 +2,7 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:news="http://www.google.com/schemas/sitemap-news/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:mobile="http://www.google.com/schemas/sitemap-mobile/1.0" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1" xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
 <url> <loc>https://docs.streampipes.org/docs/index</loc> <changefreq>weekly</changefreq> <priority>0.5</priority> <xhtml:link rel="alternate" hreflang="en" href="https://docs.streampipes.org/docs/en/index" /> </url>
 <url> <loc>https://docs.streampipes.org/docs/versions</loc> <changefreq>weekly</changefreq> <priority>0.5</priority> <xhtml:link rel="alternate" hreflang="en" href="https://docs.streampipes.org/docs/en/versions" /> </url>
+<url> <loc>https://docs.streampipes.org/docs/blog/2020/04/14/streampipes_on_k3s</loc> <changefreq>weekly</changefreq> <priority>0.3</priority> </url>
 <url> <loc>https://docs.streampipes.org/docs/blog/2020/01/23/streampipes_on_rpi</loc> <changefreq>weekly</changefreq> <priority>0.3</priority> </url>
 <url> <loc>https://docs.streampipes.org/docs/blog/2019/11/25/moving-to-the-apache-incubator</loc> <changefreq>weekly</changefreq> <priority>0.3</priority> </url>
 <url> <loc>https://docs.streampipes.org/docs/blog/2019/11/23/release-0650</loc> <changefreq>weekly</changefreq> <priority>0.3</priority> </url>
diff --git a/getinvolved.html b/getinvolved.html
index ebdab7b..418fe9a 100644
--- a/getinvolved.html
+++ b/getinvolved.html
@@ -161,7 +161,7 @@
                     <p>There are many ways to help. Become part of a highly motivated community and help growing
                         StreamPipes:</p>
                     <ul>
-                        <li><i class="fas fa-check sp-color-green"></i> Submit a bug report in our <a href="">JIRA</a></li>
+                        <li><i class="fas fa-check sp-color-green"></i> Submit a bug report in our <a href="https://issues.apache.org/jira/browse/STREAMPIPES">JIRA</a></li>
                         <li><i class="fas fa-check sp-color-green"></i> Subscribe to our <a href="/mailinglists.html">mailing lists</a></li>
                         <li><i class="fas fa-check sp-color-green"></i> Create a pull request on Github</li>
                     </ul>