Update website

This commit is contained in:
Tomasz Sęk
2019-09-05 10:23:13 +02:00
parent 5e213b2f4b
commit 1c080c531d
58 changed files with 1953 additions and 1948 deletions
+50 -50
View File
@@ -1,17 +1,17 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Jenkins Operator – Documentation</title>
<link>/docs/</link>
<link>/kubernetes-operator/docs/</link>
<description>Recent Hugo news from gohugo.io</description>
<generator>Hugo -- gohugo.io</generator>
<lastBuildDate>Tue, 03 Sep 2019 00:00:00 +0000</lastBuildDate>
<image>
<url>/img/hugo.png</url>
<url>/kubernetes-operator/img/hugo.png</url>
<title>GoHugo.io</title>
<link>/docs/</link>
<link>/kubernetes-operator/docs/</link>
</image>
<atom:link href="/docs/index.xml" rel="self" type="application/rss+xml" />
<atom:link href="/kubernetes-operator/docs/index.xml" rel="self" type="application/rss+xml" />
@@ -21,10 +21,10 @@
<item>
<title>Docs: Architecture and design</title>
<link>/docs/how-it-works/architecture-and-design/</link>
<link>/kubernetes-operator/docs/how-it-works/architecture-and-design/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/how-it-works/architecture-and-design/</guid>
<guid>/kubernetes-operator/docs/how-it-works/architecture-and-design/</guid>
<description>
@@ -34,7 +34,7 @@
- watches any changes of manifests and maintain the desired state according to deployed custom resource manifest
- implements the main reconciliation loop which consists of two smaller reconciliation loops - base and user&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/reconcile.png&#34; alt=&#34;reconcile&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/reconcile.png&#34; alt=&#34;reconcile&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Base&lt;/strong&gt; reconciliation loop takes care of reconciling base Jenkins configuration, which consists of:
- Ensure Manifests - monitors any changes in manifests
@@ -48,7 +48,7 @@
- Ensure User Configuration - executed user provided configuration, like groovy scripts, configuration as code or plugins
- Ensure Backup Job - creates Backup job and ensures that backup has been successfully performed&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/phases.png&#34; alt=&#34;reconcile&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/phases.png&#34; alt=&#34;reconcile&#34; /&gt;&lt;/p&gt;
&lt;h2 id=&#34;operator-state&#34;&gt;Operator State&lt;/h2&gt;
@@ -60,10 +60,10 @@ It helps to maintain or recover desired state even after operator or Jenkins res
<item>
<title>Docs: Deploy Jenkins</title>
<link>/docs/getting-started/v0.1.1/deploy-jenkins/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/deploy-jenkins/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/deploy-jenkins/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/deploy-jenkins/</guid>
<description>
@@ -128,17 +128,17 @@ kubectl get secret jenkins-operator-credentials-&amp;lt;cr_name&amp;gt; -o &lt;s
&lt;p&gt;Connect to Jenkins (actual Kubernetes cluster):&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;kubectl port-forward jenkins-&amp;lt;cr_name&amp;gt; &lt;span style=&#34;color:#0000cf;font-weight:bold&#34;&gt;8080&lt;/span&gt;:8080&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;Then open browser with address &lt;code&gt;http://localhost:8080&lt;/code&gt;.
&lt;img src=&#34;/img/jenkins.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;img src=&#34;/kubernetes-operator/img/jenkins.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
</description>
</item>
<item>
<title>Docs: Deploy Jenkins</title>
<link>/docs/getting-started/v0.2.0/deploy-jenkins/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/deploy-jenkins/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/deploy-jenkins/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/deploy-jenkins/</guid>
<description>
@@ -199,17 +199,17 @@ kubectl get secret jenkins-operator-credentials-&amp;lt;cr_name&amp;gt; -o &lt;s
&lt;p&gt;Connect to Jenkins (actual Kubernetes cluster):&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;kubectl port-forward jenkins-&amp;lt;cr_name&amp;gt; &lt;span style=&#34;color:#0000cf;font-weight:bold&#34;&gt;8080&lt;/span&gt;:8080&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;Then open browser with address &lt;code&gt;http://localhost:8080&lt;/code&gt;.
&lt;img src=&#34;/img/jenkins.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;img src=&#34;/kubernetes-operator/img/jenkins.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
</description>
</item>
<item>
<title>Docs: Configuration</title>
<link>/docs/getting-started/v0.1.1/configuration/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/configuration/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/configuration/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/configuration/</guid>
<description>
@@ -326,11 +326,11 @@ spec:
&lt;p&gt;You can verify if deploy keys were successfully configured in Jenkins &lt;strong&gt;Credentials&lt;/strong&gt; tab.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/jenkins-credentials.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/jenkins-credentials.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;You can verify if your pipelines were successfully configured in Jenkins Seed Job console output.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/jenkins-seed.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/jenkins-seed.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;If your GitHub repository is &lt;strong&gt;private&lt;/strong&gt; you have to configure SSH or username/password authentication.&lt;/p&gt;
@@ -455,10 +455,10 @@ The &lt;code&gt;/sbin/tini -s -- /usr/local/bin/jenkins.sh&lt;/code&gt; command
<item>
<title>Docs: Configuration</title>
<link>/docs/getting-started/v0.2.0/configuration/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/configuration/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/configuration/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/configuration/</guid>
<description>
@@ -577,11 +577,11 @@ spec:
&lt;p&gt;You can verify if deploy keys were successfully configured in Jenkins &lt;strong&gt;Credentials&lt;/strong&gt; tab.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/jenkins-credentials.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/jenkins-credentials.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;You can verify if your pipelines were successfully configured in Jenkins Seed Job console output.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/img/jenkins-seed.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;/kubernetes-operator/img/jenkins-seed.png&#34; alt=&#34;jenkins&#34; /&gt;&lt;/p&gt;
&lt;p&gt;If your GitHub repository is &lt;strong&gt;private&lt;/strong&gt; you have to configure SSH or username/password authentication.&lt;/p&gt;
@@ -745,10 +745,10 @@ stringData:
<item>
<title>Docs: Customization</title>
<link>/docs/getting-started/v0.1.1/customization/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/customization/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/customization/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/customization/</guid>
<description>
@@ -860,10 +860,10 @@ spec:
<item>
<title>Docs: Customization</title>
<link>/docs/getting-started/v0.2.0/customization/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/customization/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/customization/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/customization/</guid>
<description>
@@ -1026,10 +1026,10 @@ spec:
<item>
<title>Docs: AKS</title>
<link>/docs/getting-started/v0.1.1/aks/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/aks/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/aks/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/aks/</guid>
<description>
@@ -1050,10 +1050,10 @@ restart Jenkins pod over and over again.&lt;/p&gt;
<item>
<title>Docs: AKS</title>
<link>/docs/getting-started/v0.2.0/aks/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/aks/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/aks/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/aks/</guid>
<description>
@@ -1074,10 +1074,10 @@ restart Jenkins pod over and over again.&lt;/p&gt;
<item>
<title>Docs: Configure backup and restore</title>
<link>/docs/getting-started/v0.1.1/configure-backup-and-restore/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/configure-backup-and-restore/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/configure-backup-and-restore/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/configure-backup-and-restore/</guid>
<description>
@@ -1154,10 +1154,10 @@ restart Jenkins pod over and over again.&lt;/p&gt;
<item>
<title>Docs: Configure backup and restore</title>
<link>/docs/getting-started/v0.2.0/configure-backup-and-restore/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/configure-backup-and-restore/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/configure-backup-and-restore/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/configure-backup-and-restore/</guid>
<description>
@@ -1236,10 +1236,10 @@ restart Jenkins pod over and over again.&lt;/p&gt;
<item>
<title>Docs: Jenkins Docker Images</title>
<link>/docs/how-it-works/jenkins-docker-images/</link>
<link>/kubernetes-operator/docs/how-it-works/jenkins-docker-images/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/how-it-works/jenkins-docker-images/</guid>
<guid>/kubernetes-operator/docs/how-it-works/jenkins-docker-images/</guid>
<description>
@@ -1251,10 +1251,10 @@ If needed, the docker image can easily be changed in custom resource manifest as
<item>
<title>Docs: Migration from v0.1.1</title>
<link>/docs/getting-started/v0.2.0/migration/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/migration/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/migration/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/migration/</guid>
<description>
@@ -1291,10 +1291,10 @@ Now, when Jenkins configuration jobs are removed, you must use this command to s
<item>
<title>Docs: Tools</title>
<link>/docs/developer-guide/tools/</link>
<link>/kubernetes-operator/docs/developer-guide/tools/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/developer-guide/tools/</guid>
<guid>/kubernetes-operator/docs/developer-guide/tools/</guid>
<description>
@@ -1351,10 +1351,10 @@ go install
<item>
<title>Docs: Diagnostics</title>
<link>/docs/getting-started/v0.1.1/diagnostics/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/diagnostics/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/diagnostics/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/diagnostics/</guid>
<description>
@@ -1378,10 +1378,10 @@ kubectl apply -f deploy/operator.yaml&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
<item>
<title>Docs: Diagnostics</title>
<link>/docs/getting-started/v0.2.0/diagnostics/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/diagnostics/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/diagnostics/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/diagnostics/</guid>
<description>
@@ -1405,10 +1405,10 @@ kubectl apply -f deploy/operator.yaml&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
<item>
<title>Docs: Scheme</title>
<link>/docs/getting-started/v0.1.1/scheme/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/scheme/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/scheme/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/scheme/</guid>
<description>
@@ -2857,10 +2857,10 @@ on git commit &lt;code&gt;37e531a&lt;/code&gt;.
<item>
<title>Docs: Scheme</title>
<link>/docs/getting-started/v0.2.0/scheme/</link>
<link>/kubernetes-operator/docs/getting-started/v0.2.0/scheme/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.2.0/scheme/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.2.0/scheme/</guid>
<description>
@@ -4309,10 +4309,10 @@ on git commit &lt;code&gt;37e531a&lt;/code&gt;.
<item>
<title>Docs: Migration guide from v1alpha1 to v1alpha2</title>
<link>/docs/getting-started/v0.1.1/migration-guide-v1alpha1-to-v1alpha2/</link>
<link>/kubernetes-operator/docs/getting-started/v0.1.1/migration-guide-v1alpha1-to-v1alpha2/</link>
<pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
<guid>/docs/getting-started/v0.1.1/migration-guide-v1alpha1-to-v1alpha2/</guid>
<guid>/kubernetes-operator/docs/getting-started/v0.1.1/migration-guide-v1alpha1-to-v1alpha2/</guid>
<description>