<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Satheesh Mohandass on Medium]]></title>
        <description><![CDATA[Stories by Satheesh Mohandass on Medium]]></description>
        <link>https://medium.com/@satheesh.mohandass?source=rss-13f9daf8fc2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Satheesh Mohandass on Medium</title>
            <link>https://medium.com/@satheesh.mohandass?source=rss-13f9daf8fc2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:48:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satheesh.mohandass/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sales boost]]></title>
            <link>https://medium.com/@satheesh.mohandass/sales-boost-d695d796552d?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d695d796552d</guid>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Fri, 20 Dec 2024 00:00:55 GMT</pubDate>
            <atom:updated>2024-12-20T00:00:55.473Z</atom:updated>
            <content:encoded><![CDATA[<h2>Sales in Nintendo boosting up</h2><p>Looks like shigeru miyamoto has boosted up in sales and has been getting so much money. What is the cause for this boost in sales?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d695d796552d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting GitLab on Kubernetes using Kasten]]></title>
            <link>https://medium.com/@satheesh.mohandass/protecting-gitlab-on-kubernetes-using-kasten-e2a21adb09ba?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2a21adb09ba</guid>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Tue, 05 Dec 2023 18:26:53 GMT</pubDate>
            <atom:updated>2023-12-05T18:26:53.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbM4MOOiYpxiboolUUP9zA.png" /></figure><p>Let’s talk about protecting GitLab application running on Kubernetes using Kasten K10.</p><h3>What is GitLab?</h3><p>GitLab is a web-based DevOps tool that provides a Git repository manager with features such as source code management, continuous integration, and more. It is used to manage software development projects and provides a platform for version control, collaboration, issue tracking, and code review. Protecting GitLab is extremely critical that in the event of a disaster and the kubernetes cluster is beyond recoverable all the data including the source code is lost. This is where Kasten K10 can help.</p><h3>What is Kasten K10?</h3><p>Kasten K10 is a data management platform that was purpose-built for Kubernetes. It provides enterprise operations teams with an easy-to-use, scalable and secure system for backup, restore, disaster recovery and the mobility of Kubernetes applications.</p><p>For this use case, I use an Azure Kubernetes Service (AKS) cluster. If GitLab is not yet deployed on the AKS cluster, follow the instructions <a href="https://medium.com/@satheesh.mohandass/6a61715d72e5">here</a>.</p><p>If you are installing GitLab application for the first time, go ahead and create a sample GitLab project and upload some code. I have created a k10-dp-projectproject and uploaded two yaml files which I will protect using Kasten K10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3Kr5OVPDgl-Fkdls3uE_w.png" /></figure><h3>Installing Kasten</h3><p>To protect the Gitlab application, let’s first install Kasten K10 on the kubernetes cluster using the helm chart method.</p><pre>kubectl create namespace kasten-io<br><br>helm repo add kasten https://charts.kasten.io/<br>helm repo update<br><br># Install Kasten with Token authentication<br>helm install k10 kasten/k10 --namespace=kasten-io \<br>    --set externalGateway.create=true \<br>    --set auth.tokenAuth.enabled=true</pre><p>Get the EXTERNAL-IP of the Kasten service gateway-ext</p><pre>kubectl get svc gateway-ext -n kasten-io<br><br>NAME          TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)        AGE<br>gateway-ext   LoadBalancer   10.0.77.140   20.109.201.21   80:31671/TCP   4d2h</pre><p>Retrieve the token to log into K10 dashboard using the kubectl command</p><pre>kubectl - namespace kasten-io create token k10-k10 - duration=24h</pre><p>Open the Kasten K10 dashboard using the URL <em>http://&lt;EXTERNAL-IP&gt;/k10/#</em></p><p>Accept the EULA and login using the token retrieved above<em>.</em></p><h3>Protecting GitLab using Kasten</h3><p>In K10 dashboard, create a location profile to store the backups to an external repository. K10 supports various storage providers such as Amazon S3, Azure Storage, Google Cloud Storage, NFS File store, etc. In this example, I use an AWS S3 bucket.</p><p>In K10 dashboard, navigate to Profiles -&gt; Location -&gt; New Profile</p><ul><li>Provide a Profile Name</li><li>Select Amazon S3 as storage provider</li><li>Enter the AWS Access Key, AWS Secret, Region and Bucket Name</li><li>Click Save profile.</li></ul><p>K10 will validate the connection to the AWS S3 bucket and the status should show <em>Valid</em>.</p><p>Provide a Profile Name, and select Amazon S3 as storage provider. Specify the AWS Access Key, AWS Secret, Region, Bucket Name and click Save profile. K10 will validate the connection to the AWS S3 bucket and the status should show <em>Valid</em>.</p><p>Create a K10 policy to protect the GitLab application. In K10 dashboard, navigate to Policies -&gt; Create New Policy.</p><ul><li>Provide a Profile Name</li><li>Set the Action as “Snapshot”</li><li>Set the Backup Frequency as “On Demand”</li><li>Enable Backups via Snapshot Exports and set the Export Location Profile to the AWS S3 Profile created earlier.</li><li>Select Applications by Name and choose gitlab</li><li>Click Create Policy</li><li>Click Run Once on the policy tile and set an expiration date and click Yes, Continue to run the policy to backup the Gitlab application.</li></ul><p>You can track the status of the policy run from the K10 dashboard and when successfully complete, the output will be similar to the one below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mo9ZfEiV236pRVZMfgpV_w.png" /></figure><p>Next, I create a disaster by manually deleting the k10-dp-projectproject from the Gitlab repository.</p><h3>Recovering from backup</h3><p>Now that the sample project has been deleted from the GitLab repository, let’s restore it from backup.</p><p>In K10 dashboard,</p><ul><li>Click Applications</li><li>Select the three dots to the right of application name gitlab and click restore.</li><li>You should see two restore points available from the previous backup, one points to the local restore point and the other points to external AWS S3 bucket.</li><li>Select the AWS S3 restore point</li><li>Leave the settings unchanged and click Restore.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CD_ReS5XE-ZQtzp8ewLz2A.png" /></figure><p>Once the application is successfully restored, login to the Gitlab UI and see the project restored from backup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*st59l6hB59UaqBymPxCA9w.png" /></figure><p>Kasten K10 can also be used to restore GitLab backup on a secondary kubernetes cluster. Follow the youtube link below for more details.</p><p><a href="https://www.youtube.com/watch?v=9tizgUT-VmM">https://www.youtube.com/watch?v=9tizgUT-VmM</a></p><p>Try yourself using <a href="https://www.kasten.io/try-kasten-k10?__hstc=78384331.10dc2e9b20749d626b5fbf3543880f6c.1610478912369.1619112058603.1619545499893.25&amp;__hssc=78384331.1.1619545499893&amp;__hsfp=721764561&amp;hsutk=10dc2e9b20749d626b5fbf3543880f6c&amp;contentType=standard-page">Free Kasten K10 </a>today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2a21adb09ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Gitlab on Azure Kuberenetes Service (AKS) cluster]]></title>
            <link>https://medium.com/@satheesh.mohandass/installing-gitlab-on-azure-kuberenetes-service-aks-cluster-6a61715d72e5?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a61715d72e5</guid>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 19:29:14 GMT</pubDate>
            <atom:updated>2023-10-15T19:29:14.296Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YIC9yN38yaHcx3nIWbc8JQ.png" /></figure><p>In this article, I walk through the process of installing Gitlab application on Azure Kuberenetes Service (AKS) cluster.</p><h3>What is GitLab?</h3><p>GitLab is a web-based DevOps tool that provides a Git repository manager with features such as source code management, continuous integration, and more. It is used to manage software development projects and provides a platform for version control, collaboration, issue tracking, and code review.</p><p>There are several ways to deploy GitLab application as documented <a href="https://docs.gitlab.com/ee/install/install_methods.html">here</a>, and in this article, I choose the helm chart method.</p><pre>kubectl create namespace gitlab<br><br>helm repo add gitlab https://charts.gitlab.io/<br>helm repo update<br><br>helm install gitlab gitlab/gitlab --namespace gitlab \<br>  --set global.hosts.domain=DOMAIN \<br>  --set certmanager-issuer.email=me@example.com</pre><p>Wait for all the pods to be up and running</p><pre>kubectl get deploy<br><br>NAME                              READY   UP-TO-DATE   AVAILABLE   AGE<br>gitlab-certmanager                1/1     1            1           19m<br>gitlab-certmanager-cainjector     1/1     1            1           19m<br>gitlab-certmanager-webhook        1/1     1            1           19m<br>gitlab-gitlab-exporter            1/1     1            1           19m<br>gitlab-gitlab-runner              1/1     1            1           19m<br>gitlab-gitlab-shell               2/2     2            2           19m<br>gitlab-kas                        2/2     2            2           19m<br>gitlab-minio                      1/1     1            1           19m<br>gitlab-nginx-ingress-controller   2/2     2            2           19m<br>gitlab-prometheus-server          1/1     1            1           19m<br>gitlab-registry                   2/2     2            2           19m<br>gitlab-sidekiq-all-in-1-v2        1/1     1            1           19m<br>gitlab-toolbox                    1/1     1            1           19m<br>gitlab-webservice-default         2/2     2            2           19m</pre><p>Use kubectl to fetch the address that has been dynamically allocated by AKS to the NGINX Ingress installed and configured as a part of the GitLab helm chart.</p><pre>kubectl get ingress -lrelease=gitlab<br><br>NAME                        CLASS          HOSTS                 ADDRESS         PORTS     AGE<br>gitlab-kas                  gitlab-nginx   kas.domain.tld        52.158.169.22   80, 443   21m<br>gitlab-minio                gitlab-nginx   minio.domain.tld      52.158.169.22   80, 443   21m<br>gitlab-registry             gitlab-nginx   registry.domain.tld   52.158.169.22   80, 443   21m<br>gitlab-webservice-default   gitlab-nginx   gitlab.domain.tld     52.158.169.22   80, 443   21m</pre><p>You’ll notice that there are four entries, all with the same IP address. Take this IP address, and add it to your DNS for the domain you have chosen. You can add multiple records of type A, but for simplicity you can add one single wildcard record *.domain.tld pointing to the IP address.</p><p>Access the GitLab UI at URL <em>https://gitlab.domain.tld</em>. For example, if you set global.hosts.domain=my.domain.tld, then you would visit <em>https://gitlab.my.domain.tld</em>.</p><p>To sign in, use the root user. The password for root user is automatically generated at installation and stored in a Kubernetes Secret. Fetch the password for the user rootfrom the secret and decode it using the kubectlcommand.</p><pre>kubectl get secret gitlab-gitlab-initial-root-password -ojsonpath=&#39;{.data.password}&#39; | base64 --decode ; echo</pre><p>You can now sign in to GitLab with username root, and the retrieved password. You can change this password through the user preferences after logged in, we only generate it so that we can secure the first login on your behalf.</p><p>Now that you have successfully installed GitLab application on your AKS cluster and logged into the UI, you can proceed to creating your first project and uploading your code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a61715d72e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Kasten K10 on Openshift using OpenShift’s OAuth server]]></title>
            <link>https://medium.com/@satheesh.mohandass/installing-kasten-k10-on-openshift-using-openshifts-oauth-server-b2801cb37744?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2801cb37744</guid>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 16:11:01 GMT</pubDate>
            <atom:updated>2023-08-11T17:17:13.934Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mnl8EKMyaXCdC0vuhPeFFQ.png" /></figure><p>In this article, I discuss the steps to install Kasten K10 on Openshift Cluster using Openshift’s OAuth server.</p><p>The OpenShift Container Platform includes a built-in OAuth server. Users obtain OAuth access tokens to authenticate themselves to the API. When a user requests a new OAuth token, the OAuth server uses the configured identity provider to determine the identity of the user making the request. It then determines what user that identity maps to, creates an access token for that user, and returns the token for use.</p><h3>What is Kasten K10?</h3><p>Kasten K10 is a data management platform that was purpose-built for Kubernetes. It provides enterprise operations teams with an easy-to-use, scalable and secure system for backup, restore, disaster recovery and the mobility of Kubernetes applications.</p><h4>Installing K10</h4><p>Kasten K10 can be installed on Openshift clusters via helm chart or by using Openshift OperatorHub. In this article, I use the OperatorHub path.</p><p>Log into Openshift Console as an Administrator. On the left menu, navigate to Operators -&gt; OperatorHub and filter by the keyword kasten</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J86oqXRYF44nR4HQQL7_RQ.png" /></figure><p><strong>Kasten K10</strong> is available for free with no feature restrictions for up to 5 worker nodes. Select the <strong><em>Kasten K10 (Free)</em></strong> tile and click Install. Use the default options and click Install again. This installs the Kasten K10 operator on the kasten-io namespace. Wait for the operator install status to show — ready for use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17IOUKWERZZFgtwX8kEYSw.png" /></figure><p>You should see kasten operator pod running in kasten-io namespace.</p><pre>oc get pods -n kasten-io <br>NAME                                                           READY   STATUS    RESTARTS   AGE<br>k10-kasten-operator-rhmp-controller-manager-66f587db54-6wblw   2/2     Running   0          137m</pre><p>In the openshift console, navigate to Operators -&gt; Installed Operators. Set the project filter to kasten-io.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qkYzJVixgVVR_jFFxKr9Lg.png" /></figure><p>Click on operator name <strong><em>Kasten K10 (Free)</em></strong>. In the details tab, under Provided APIs, click <strong><em>Create instance</em></strong> on the K10 tile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQr8mozZUabKxW3JJ_kAeg.png" /></figure><p>All the options needed to install K10 with openshift’s oauth server are not available in the form view at this time, so lets switch to yaml view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9z0A_txuol7UGuWoKU9GcQ.png" /></figure><p>Before we update the details in the yaml, we need to complete a few additional steps.</p><p><strong>Step 1:</strong> Create a Service Account.</p><p>The service account represents an OAuth client to interact with OpenShift’s OAuth server. Assuming Kasten K10 is deployed with the default release name <strong><em>k10</em></strong><em> </em>and the URL for accessing K10 dashboard is <a href="https://k10-route-kasten-io.apps.cluster-name.example.com/k10">https://k10-route-kasten-io.apps.cluster-name.example.com/k10</a> , use the yaml below to create the service account k10-dex-sa.</p><pre>cat &gt; oauth-sa.yaml &lt;&lt;EOF<br>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br>  name: k10-dex-sa<br>  namespace: kasten-io<br>  annotations:<br>    serviceaccounts.openshift.io/oauth-redirecturi.dex: https://k10-route-kasten-io.apps.cluster-name.example.com/k10/dex/callback<br>EOF<br><br>oc create -f oauth-sa.yaml</pre><p><strong>Step 2: </strong>Create a Secret.</p><p>Use the yaml below to create a secret k10-dex-sa-secret that will map to k10-dex-sa service sccount with the right annotation.</p><pre>cat &gt; k10-dex-sa-secret.yaml &lt;&lt;EOF<br>apiVersion: v1<br>kind: Secret<br>type: kubernetes.io/service-account-token<br>metadata:<br>  name: k10-dex-sa-secret<br>  namespace: kasten-io<br>  annotations:<br>    kubernetes.io/service-account.name: &quot;k10-dex-sa&quot;<br>EOF<br><br>oc create -f k10-dex-sa-secret.yaml</pre><p>Retrieve the token from the k10-dex-sa-secret secret.</p><pre>secret_token=$(oc -n kasten-io get secret k10-dex-sa-secret -o jsonpath=&#39;{.data.token}&#39; | base64 -d)</pre><p><strong>Step 3:</strong> Obtain the Certificates.</p><p>Depending on the Openshift cluster configuration, there are two ways to obtain the certificate that’s used for encrypting the traffic between the client and target service.</p><p><strong>Option 1:</strong> Openshift Cluster uses a cluster wide proxy</p><p>Let’s first check if a cluster wide proxy is enabled. This can be done by running oc get proxy cluster -n openshift-config -o yaml | grep trustedCA. If there is a value defined for <strong><em>trustedCA</em></strong> then cluster wide proxy is used. If that’s the case, use the following command to retrieve the certificate.</p><pre>oc get proxy cluster -n openshift-config -o=jsonpath=‘{.spec.trustedCA.name}’  | base64 --decode &gt; custom-ca-bundle.pem</pre><p><strong>Option 2:</strong> If a cluster wide proxy is not used, then run</p><pre>oc get secret router-ca -n openshift-ingress-operator -o jsonpath=‘{.data.tls\.crt}’ | base64 --decode &gt; custom-ca-bundle.pem</pre><p><strong>Note:</strong> The name of the Root CA certificate file must be <strong>custom-ca-bundle.pem</strong></p><p>The next step is to retrieve the certificate used for secure connection to cluster’s API server.</p><p>Openshift issues a default self-signed API server certificate at the time of install. Openshift allows to update the cluster with a custom certificate so every API server requests are signed by the certificate that relates to your organization and trusted by a certificate authority.</p><p>The easiest way to obtain the API server certificate, whether it is a self-signed or a custom certificate is to open the API URL https://api.&lt;cluster-name&gt;.&lt;domain-name&gt;:6443 in a browser and export the certificate.</p><p>In the browser address bar, open the API URL</p><ul><li>Click on either <strong><em>Not secure </em></strong>or<strong><em> Secure</em></strong> button (usually a padlock)</li><li>Select <strong><em>Certificate (Valid)</em></strong> or <strong><em>Certificate is not valid</em></strong></li><li>Go to <strong><em>Details</em></strong> tab</li><li>Click <strong><em>Export</em></strong> and save the certificate in a file</li><li>Open the downloaded file using a text editor</li><li>Copy the contents of the file (including the BEGIN CERTIFICATE and END CERTIFICATE lines)</li><li>Append the copied certificate to the custom-ca-bundle.pem file created earlier.</li></ul><p><strong>Step 4: </strong>Create a configmap using the retrieved certificates</p><p>To create the configmap, run</p><pre>oc --namespace kasten-io create configmap custom-ca-bundle-store --from-file=custom-ca-bundle.pem</pre><p>Let’s switch back to the openshift console and provide the yaml file connecting all the pieces together to install k10 with Oauth authentication.</p><p>Below is an example yaml file that creates <strong><em>k10</em></strong> based on my cluster configuration. Modify the yaml as per your cluster’s configuration</p><pre>apiVersion: apik10.kasten.io/v1alpha1<br>kind: K10<br>metadata:<br>  name: k10<br>  namespace: kasten-io<br>spec:<br>  auth:<br>    openshift:<br>      enabled: true<br>      serviceAccount: &quot;k10-dex-sa&quot; # service account created in step 1<br>      clientSecret: &quot;&lt;value of secret_token from step 2&gt;&quot; # token for the secret k10-dex-sa-secret<br>      dashboardURL: &quot;https://k10-route-kasten-io.apps.cluster-name.example.com/k10&quot; # same as the k10 dashboard URL used in step 1<br>      openshiftURL: &quot;https://api.cluster-name.example.com:6443&quot; # api server URL of the openshift cluster<br>      insecureCA: false<br>  cacertconfigmap:<br>    name: &quot;custom-ca-bundle-store&quot; # name of the configmap created in step 3 <br>  global:<br>    persistence:<br>      storageClass: &quot;rook-ceph-block&quot; # storage class in openshift cluster to use for K10<br>  route:<br>    enabled: true <br>    tls:<br>      enabled: true</pre><p>Copy the modified yaml and replace the one in Openshift console (yaml view) and click create.</p><p>Wait for the k10 instance to be deployed . You can run watch -n2 oc get pods -n kasten-io and watch the pods.</p><pre>oc get pods -n kasten-io   <br><br>NAME                                                           READY   STATUS    RESTARTS   AGE<br>aggregatedapis-svc-6754465c54-qrvcf                            1/1     Running   0          19m<br>auth-svc-546df666df-tp979                                      2/2     Running   0          19m<br>catalog-svc-c65cbb77f-7lrxc                                    2/2     Running   0          19m<br>controllermanager-svc-5c8dcd8bcd-srpvc                         1/1     Running   0          19m<br>crypto-svc-59db49db77-98lfz                                    4/4     Running   0          19m<br>dashboardbff-svc-864b6454c7-7vxjn                              2/2     Running   0          19m<br>executor-svc-7898f5df87-27z75                                  2/2     Running   0          19m<br>executor-svc-7898f5df87-dkp8m                                  2/2     Running   0          19m<br>executor-svc-7898f5df87-pmpk2                                  2/2     Running   0          19m<br>frontend-svc-5ddc6cfbbb-xhsgh                                  1/1     Running   0          19m<br>gateway-7dbf4f5c6f-4wjf5                                       1/1     Running   0          19m<br>jobs-svc-5b66d867cf-9dnd5                                      1/1     Running   0          19m<br>k10-grafana-74c574b64c-d44qd                                   1/1     Running   0          18m<br>k10-kasten-operator-rhmp-controller-manager-66f587db54-6wblw   2/2     Running   0          117m<br>kanister-svc-5bcfbbf4d9-pqmg2                                  1/1     Running   0          19m<br>logging-svc-86cdbf9895-x465z                                   1/1     Running   0          19m<br>metering-svc-87f94b76f-dscgw                                   1/1     Running   0          19m<br>prometheus-server-97c99cd46-5l8w5                              2/2     Running   0          19m<br>state-svc-58648587-zk7fb                                       2/2     Running   0          19m</pre><h4>Testing Time</h4><p>Open the K10 dashboard URL <a href="https://k10-route-kasten-io.apps.kasten-sno-cluster.sbmlabs.net/k10/">https://k10-route-kasten-io.apps.cluster-name.example.com/k10/</a> (note the / at the end) it should re-direct to Openshift authentication screen. I have created a local user using htpasswd as identity provider, hence i see both kube:admin and htpasswd as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04fO-6orYnqbnXeSJ2E18A.png" /></figure><p>Select htpasswd and enter the user credentials, you should see the below screen to Authorize Access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ie9BA63-Wnlscb-90bsiXQ.png" /></figure><p>Click <strong><em>Allow selected permissions</em></strong> and it should redirect to Kasten dashboard.</p><p><strong>Note:</strong> At this time, there is no role based access assigned to the local user for K10. Even though the user is able to login to K10 dashboard, most of the actions would be restricted.</p><p>For verification purposes, let’s provide K10 administrator privileges to the user. Assuming the local user is namedk10admin, run the following oc commands</p><pre>oc create clusterrolebinding crb-k10-admin --clusterrole=k10-admin --user=k10admin<br>oc create rolebinding rb-k10-nsadmin --role=k10-ns-admin --user=k10admin --namespace=kasten-io</pre><p>Re-login to K10 dashboard as k10admin user and you should see the access level is unrestricted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*iJmz2UsKSpuf3an1bpihcg.png" /></figure><p>Now that you have successfully installed and configured Kasten K10 to openshift oauth authentication. Its time to create policies and protect your applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2801cb37744" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing rook-ceph for Persistent storage on Single Node Openshift]]></title>
            <link>https://medium.com/@satheesh.mohandass/installing-rook-ceph-for-persistent-storage-on-single-node-openshift-c1102a8ced40?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1102a8ced40</guid>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Mon, 07 Aug 2023 22:33:04 GMT</pubDate>
            <atom:updated>2025-10-01T14:42:47.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iImlHMJRADhuTzYN.png" /></figure><p>In this article, we will discuss installing rook-ceph to provide persistent storage for application workloads running on single node openshift.</p><p>In the previous <a href="https://medium.com/@satheesh.mohandass/single-node-openshift-on-vmware-vsphere-8fd858573735">article</a>, we discussed how to create a single node openshift on VMware vSphere. During the creation of the openshift cluster we added two additional hard disks, each 100 GB to configure persistent storage for application workloads.</p><p>Ceph is a distributed storage system that provides file, block and object storage designed for large scale production clusters. Rook turns distributed storage systems into self-managing services and scalable. It automates the tasks of a storage administrator such as deployment, configuration, provisioning, scaling, upgrading, monitoring, and resource management. Rook uses the power of the Kubernetes platform to deliver its services via a Kubernetes Operator for Ceph.</p><p>By default, rook ceph operator is designed to run on a minimum of three worker nodes to provide fault tolerance, however with little tweaks we can install rook-ceph operator on single node openshift.</p><p><strong>Prerequisites</strong></p><ul><li>Single Node OpenShift cluster running version 4.19.6</li><li>At least 2 additional block devices (e.g., `/dev/sdb`, `/dev/sdc`) for Ceph storage</li><li>Cluster admin access (`oc` CLI configured)</li><li>Bastion node or workstation with `git` and `oc` CLI tools</li></ul><p><strong>Version Compatibility</strong></p><p>Based on compatibility testing and conservative approach:</p><ul><li>Rook Version : v1.16.7 (Latest stable from 1.16.x series)</li><li>Ceph Version : v19.2.2 (Default with Rook 1.16.7)</li><li>OpenShift Version : 4.19.6 (Target)</li></ul><p><strong>Note</strong>: Rook 1.16.x series has proven compatibility with OpenShift 4.18+ environments. Using 1.17.x+ may cause compatibility issues with OpenShift 4.19.6.</p><p>On the bastion node, connect to the single node openshift cluster. Run oc get nodes to validate. The output will be similar to this</p><pre>oc get nodes<br>NAME               STATUS   ROLES                         AGE    VERSION<br>sno-test-cluster   Ready    control-plane,master,worker   7d6h   v1.32.8</pre><p>Clone the rook GitHub repo on to your bastion node. At the time of writing release 1.3 is the stable release.</p><pre>git clone --single-branch --branch release-1.16 https://github.com/rook/rook.git<br>cd rook/deploy/examples/</pre><p>In the examples directory, there is a yaml file cluster.yaml that contains the configuration to create a CephCluster with 3 worker nodes. Since we are using a single node cluster, lets create a new yaml with the right configuration.</p><p>Note: This yaml uses sdb and sdc as the device names for the two 100 GB disks. If this name is different on your environment, modify the yaml file accordingly.</p><pre>cat &lt;&lt; &#39;EOF&#39; &gt; sno-cluster.yaml<br>---<br># ConfigMap to override Ceph default settings for single node<br>apiVersion: v1<br>kind: ConfigMap<br>metadata:<br>  name: rook-config-override<br>  namespace: rook-ceph<br>data:<br>  config: |<br>    [global]<br>    osd_pool_default_size = 1<br>    <br>---<br>apiVersion: ceph.rook.io/v1<br>kind: CephCluster<br>metadata:<br>  name: rook-ceph<br>  namespace: rook-ceph<br>spec:<br>  cephVersion:<br>    image: quay.io/ceph/ceph:v19.2.2<br>    allowUnsupported: false<br>  dataDirHostPath: /var/lib/rook<br>  skipUpgradeChecks: false<br>  continueUpgradeAfterChecksEvenIfNotHealthy: false<br>  waitTimeoutForHealthyOSDInMinutes: 10<br>  <br>  # Monitor configuration for single node<br>  mon:<br>    count: 1<br>    allowMultiplePerNode: true<br>    <br>  # Manager configuration for single node  <br>  mgr:<br>    count: 1<br>    allowMultiplePerNode: true<br>    modules:<br>      - name: pg_autoscaler<br>        enabled: true<br>        <br>  # Dashboard configuration<br>  dashboard:<br>    enabled: true<br>    ssl: true<br>    <br>  # Monitoring disabled for single node to reduce resource usage<br>  monitoring:<br>    enabled: false<br>    <br>  # Network configuration<br>  network:<br>    connections:<br>      encryption:<br>        enabled: false<br>      compression:<br>        enabled: false<br>        <br>  # Crash collector<br>  crashCollector:<br>    disable: false<br>    <br>  # Cleanup policy<br>  cleanupPolicy:<br>    confirmation: &quot;&quot;<br>    sanitizeDisks:<br>      method: quick<br>      dataSource: zero<br>      iteration: 1<br>    allowUninstallWithVolumes: false<br>    <br>  # Resource priorities for single node<br>  priorityClassNames:<br>    mon: system-node-critical<br>    osd: system-node-critical<br>    mgr: system-cluster-critical<br>    <br>  # Storage configuration<br>  storage:<br>    useAllNodes: true<br>    useAllDevices: false<br>    devices:<br>      - name: &quot;sdb&quot;  # Modify if your device names are different<br>      - name: &quot;sdc&quot;  # Modify if your device names are different<br>    config:<br>      osdsPerDevice: &quot;1&quot;<br>      <br>  # Disruption management for single node<br>  disruptionManagement:<br>    managePodBudgets: false<br>    osdMaintenanceTimeout: 30<br>    pgHealthCheckTimeout: 0<br>    manageMachineDisruptionBudgets: false<br>    machineDisruptionBudgetNamespace: openshift-machine-api<br>    <br>  # Health check configuration<br>  healthCheck:<br>    daemonHealth:<br>      mon:<br>        disabled: false<br>        interval: 45s<br>      osd:<br>        disabled: false<br>        interval: 60s<br>      status:<br>        disabled: false<br>        interval: 60s<br>    livenessProbe:<br>      mon:<br>        disabled: false<br>      mgr:<br>        disabled: false<br>      osd:<br>        disabled: false<br>    startupProbe:<br>      mon:<br>        disabled: false<br>      mgr:<br>        disabled: false<br>      osd:<br>        disabled: false<br>EOF</pre><p>Prepare yaml files for filesystem and block based StorageClasses</p><pre>cat &lt;&lt; &#39;EOF&#39; &gt; sno-storageclass.yaml<br>---<br># CephFS Filesystem configuration<br>apiVersion: ceph.rook.io/v1<br>kind: CephFilesystem<br>metadata:<br>  name: cephfspool<br>  namespace: rook-ceph<br>spec:<br>  metadataPool:<br>    replicated:<br>      size: 1<br>      requireSafeReplicaSize: false<br>  dataPools:<br>    - name: replicated<br>      replicated:<br>        size: 1<br>        requireSafeReplicaSize: false<br>      compressionMode: none<br>  preserveFilesystemOnDelete: false<br>  metadataServer:<br>    activeCount: 1<br>    activeStandby: false<br>    <br>---<br># CephFS StorageClass<br>apiVersion: storage.k8s.io/v1<br>kind: StorageClass<br>metadata:<br>  name: rook-cephfs<br>provisioner: rook-ceph.cephfs.csi.ceph.com<br>allowVolumeExpansion: true<br>parameters:<br>  clusterID: rook-ceph<br>  fsName: cephfspool<br>  pool: cephfspool-replicated<br>  csi.storage.k8s.io/provisioner-secret-name: rook-csi-cephfs-provisioner<br>  csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph<br>  csi.storage.k8s.io/controller-expand-secret-name: rook-csi-cephfs-provisioner<br>  csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph<br>  csi.storage.k8s.io/node-stage-secret-name: rook-csi-cephfs-node<br>  csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph<br>reclaimPolicy: Delete<br><br>---<br># RBD Block Pool configuration<br>apiVersion: ceph.rook.io/v1<br>kind: CephBlockPool<br>metadata:<br>  name: cephblockpool<br>  namespace: rook-ceph<br>spec:<br>  failureDomain: host<br>  replicated:<br>    size: 1<br>    requireSafeReplicaSize: false<br>    <br>---<br># RBD Block StorageClass<br>apiVersion: storage.k8s.io/v1<br>kind: StorageClass<br>metadata:<br>  name: rook-ceph-block<br>provisioner: rook-ceph.rbd.csi.ceph.com<br>parameters:<br>  clusterID: rook-ceph<br>  pool: cephblockpool<br>  imageFormat: &quot;2&quot;<br>  imageFeatures: layering<br>  csi.storage.k8s.io/provisioner-secret-name: rook-csi-rbd-provisioner<br>  csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph<br>  csi.storage.k8s.io/controller-expand-secret-name: rook-csi-rbd-provisioner<br>  csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph<br>  csi.storage.k8s.io/node-stage-secret-name: rook-csi-rbd-node<br>  csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph<br>  csi.storage.k8s.io/fstype: ext4<br>reclaimPolicy: Delete<br>allowVolumeExpansion: true<br>EOF</pre><p>Deploy CRDs, common, and operator yaml files.</p><pre>oc create -f crds.yaml -f common.yaml<br>oc create -f operator-openshift.yaml</pre><p>You should now see rook-ceph-operator pod running on rook-ceph namespace.</p><pre>oc get pods -n rook-ceph<br>NAME                                 READY   STATUS    RESTARTS   AGE<br>rook-ceph-operator-b89dfdd94-69pxq   1/1     Running   0          74s  </pre><p>Create the CephCluster</p><pre>oc create -f sno-cluster.yaml</pre><p>You should now see the following pods running in rook-ceph namespace</p><pre>oc get pods -n rook-ceph<br>NAME                                                         READY   STATUS      RESTARTS   AGE<br>csi-cephfsplugin-jrq8r                                       2/2     Running     0          2d9h<br>csi-cephfsplugin-provisioner-754dc996bd-t5gn7                5/5     Running     0          2d9h<br>csi-rbdplugin-7wsqq                                          2/2     Running     0          2d9h<br>csi-rbdplugin-provisioner-578749b758-jfn9w                   5/5     Running     0          2d9h<br>rook-ceph-crashcollector-sno-test-cluster-69bf9d6749-vd6zm   1/1     Running     0          2d9h<br>rook-ceph-mgr-a-7d5bc7859-lc7vt                              1/1     Running     0          2d9h<br>rook-ceph-mon-a-588cb6df74-55fsq                             1/1     Running     0          2d9h<br>rook-ceph-operator-b89dfdd94-69pxq                           1/1     Running     0          2d9h<br>rook-ceph-osd-0-64587ff74c-v8p5c                             1/1     Running     0          2d9h<br>rook-ceph-osd-1-c4d7767d6-nhq97                              1/1     Running     0          2d9h<br>rook-ceph-osd-prepare-sno-test-cluster-nv7ln                 0/1     Completed   0          2d9h</pre><p>Deploy the Rook Ceph toolbox, storage class and VolumeSnapshotClass</p><pre>oc create -f toolbox.yaml<br>oc create -f sno-storageclass.yaml<br>oc create -f csi/rbd/snapshotclass.yaml<br>oc create -f csi/cephfs/snapshotclass.yaml</pre><p>Set rook-ceph-block as the default StorageClass.</p><pre>oc patch storageclass rook-ceph-block -p &#39;{&quot;metadata&quot;:<br>{&quot;annotations&quot;:{&quot;storageclass.kubernetes.io/is-default-class&quot;:&quot;true&quot;}}}&#39;</pre><p>Now that we have provisioned our storage, lets deploy a test pacman application</p><pre>helm repo add pacman https://shuguet.github.io/pacman/<br>oc create ns pacman<br>oc adm policy add-scc-to-group anyuid system:authenticated -n pacman<br>helm install pacman pacman/pacman -n pacman</pre><p>Let’s validate that the PVC’s were created successfully and all pods are running.</p><pre>oc get pvc -n pacman<br>NAME             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE<br>pacman-mongodb   Bound    pvc-904925cb-6201-4153-863a-c390cd2c83b1   8Gi        RWO            rook-ceph-block   4m28s<br><br>oc get pods -n pacman<br>NAME                              READY   STATUS    RESTARTS        AGE<br>pacman-555d9f6f5-gwqnq            1/1     Running   1 (3m57s ago)   4m32s<br>pacman-mongodb-67fffc6787-pptz2   1/1     Running   0               4m32s<br><br>oc get svc -n pacman<br>NAME             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)     AGE<br>pacman           ClusterIP   172.30.181.165   &lt;none&gt;        80/TCP      2m40s<br>pacman-mongodb   ClusterIP   172.30.196.139   &lt;none&gt;        27017/TCP   2m40s</pre><p>To access the pacman application from a browser, let’s expose the service via openshift route</p><pre>oc expose svc pacman -n pacman<br><br>oc get route -n pacman<br>NAME     HOST/PORT                                           PATH   SERVICES   PORT   TERMINATION   WILDCARD<br>pacman   pacman-pacman.apps.sno-test-cluster.example.com          pacman     http                 None</pre><p>Now the front end application of pacman should be accessible from a browser via URL <a href="http://pacman-pacman.apps.kasten-sno-cluster.sbmlabs.net/">http://pacman-pacman.apps.sno-test-cluster.example.com</a></p><p>Now that we have successfully deployed rook ceph to provide persistent storage for application workloads and deployed a pacman application, in the next article I will discuss on how the workloads can be protected using Kasten K10.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1102a8ced40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Single Node Openshift on VMware vSphere]]></title>
            <link>https://medium.com/@satheesh.mohandass/single-node-openshift-on-vmware-vsphere-8fd858573735?source=rss-13f9daf8fc2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fd858573735</guid>
            <category><![CDATA[single-node-openshift]]></category>
            <dc:creator><![CDATA[Satheesh Mohandass]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 17:24:57 GMT</pubDate>
            <atom:updated>2023-08-11T03:55:56.511Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/0*-wFYbLDMR6r-HKc-.png" /></figure><p>In this article, I will walk through the steps to create a Single Node Openshift clusters on VMware vSphere.</p><p>Red Hat OpenShift is a unified platform to build, modernize, and deploy applications at scale. It is based on Kubernetes, the open-source container orchestration platform. As of Openshift 4.9, RedHat supports running a Openshift environment on a single node.</p><p>Openshift cluster can be created in several ways (User Provisioned Infrastructure, Installed Provisioned Infrastructure, cli and web) and in this article to keep it simple, I am using the RedHat recommended Interactive web-based method.</p><p>Log into console.redhat.com using your RedHat credentials. If you don’t have one, you can register for a RedHat account.</p><p>Click Services menu on the top bar and Select Containers -&gt; Create Cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uFc2b46UqHF-8TQ_7hRog.png" /></figure><p>Here you can see there are several methods available to create an Openshift cluster depending on where you want to create them. In our scenario, we select Datacenter -&gt; vSphere. Click on the Interactive tile.</p><p>Enter the cluster details</p><ul><li>Provide a cluster name -&gt; sno-test-cluster</li><li>Specify the base domain.</li><li>Select the Openshift Version -&gt; Openshift 4.12.25</li><li>CPU Architecture -&gt; x86_64</li><li>Select the checkbox Install Single Node Openshift(SNO)</li><li>Click Next</li></ul><p>Do not select anything under Operators, click Next again.</p><ul><li>Select Add host</li><li>Select the Provisioning type to Full image file — Download a self-contained ISO</li><li>Specify SSH Public Key. Generate a public SSH key from the machine that will be used to SSH to the Openshift cluster.</li><li>Click Generate Discovery ISO and download the discovery ISO.</li></ul><p>Log into vSphere client with administrator privileges and upload the discovery ISO file to a datastore.</p><p><strong>Create a New Virtual machine</strong></p><ul><li>In vSphere client, right click the cluster where you want to host the new virtual machine and select New Virtual machine.</li><li>Provide a name for the new virtual machine. As it is a single node cluster, I name the virtual machine same as the openshift cluster name sno-test-cluster</li><li>Select the compute resource and storage for the virtual machine.</li><li>Set the compatibility to ESXi 7.0 U2 and later</li><li>Set the Guest OS Family to Linux and Guest OS Version to Red Hat Enterprise Linux 8 (64 bit)</li><li>Select how many CPUs you would like to allocate to the cluster. I set it to 16 and enable the Expose hardware assisted virtualization to the guest OS</li><li>Select how much memory you would like to allocate to the cluster. I Set the memory to 64 GB.</li><li>Set the primary Hard disk to 100 GB. Add two additional disks each with 100 GB to be used for cephblockpool that provides persistent storage for the workloads on the cluster.</li><li>Set the CD/DVD drive to the ISO file uploaded to the datastore. Select the checkbox Connect at Power on</li><li>On the VM Options tab, under Advanced -&gt; Edit Configuration -&gt; Add Configuration Params, add a new parameter disk.EnableUUID<strong> </strong>and set the value to TRUE.</li><li>Click Next and then Finish.</li><li>Right click the Virtual Machine and select Power On</li></ul><p>Once the virtual machine is powered on and ISO file is loaded, you should see the host show up in Redhat Console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GEoEssHO47agkPqveUU6Aw.png" /></figure><ul><li>Click the host name and change it to sno-test-cluster</li><li>Click Next</li><li>Leave the defaults for Networking. It might take a few minutes for the status to show Ready.</li><li>Click Next</li><li>Review the details and click Install Cluster</li></ul><p>Once the cluster is created successfully, you should see the below status in the console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QDVggDWvlBCmQTN2YDpoQ.png" /></figure><p>Now click on Not able to access the Web Console? If you have an external DNS server, follow option 1 and add the A records to the DNS server. If you do not have an external DNS server, follow the instructions from Option 2.</p><p><strong>Accessing the Openshift Environment</strong></p><p>Access the Openshift Console using the provided Web Console URL and the kubeadmin credentials provided in the Installation completion page.</p><p>To access the Openshift environment using the oc cli option,</p><ul><li>Install the oc cli using the instruction provided <a href="https://docs.openshift.com/container-platform/4.12/cli_reference/openshift_cli/getting-started-cli.html">here</a>.</li><li>Download the kubeconfig file from the Installation completion page and copy into the machine where oc cli was installed.</li><li>Set the KUBECONFIG environment variable pointing to the downloaded kubeconfig file</li></ul><p>export KUBECONFIG=&lt;/path-to-kubeconfig-file&gt;/kubeconfig</p><ul><li>Run command oc get nodes , you should see an output similar to the one below</li></ul><pre>oc get nodes<br>NAME               STATUS   ROLES                         AGE     VERSION<br>sno-test-cluster   Ready    control-plane,master,worker   2d19h   v1.25.11+1485cc9</pre><p>Now that the Single Node Openshift Cluster is successfully installed. In the next article, lets talk about configuring persistent storage using rook-ceph to deploy workloads.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fd858573735" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>