<?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 Rose Crisp on Medium]]></title>
        <description><![CDATA[Stories by Rose Crisp on Medium]]></description>
        <link>https://medium.com/@rose.crisp.info?source=rss-2a453c252a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*UJoAyCQPh8M8y4gp.jpg</url>
            <title>Stories by Rose Crisp on Medium</title>
            <link>https://medium.com/@rose.crisp.info?source=rss-2a453c252a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:29:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rose.crisp.info/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[The ABCs of installing Kubernetes Operators]]></title>
            <link>https://medium.com/@rose.crisp.info/the-abcs-of-installing-kubernetes-operators-42874d07c6ee?source=rss-2a453c252a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/42874d07c6ee</guid>
            <category><![CDATA[installation-of-operator]]></category>
            <category><![CDATA[olm]]></category>
            <category><![CDATA[operator-sdk]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[kubernetes-operator]]></category>
            <dc:creator><![CDATA[Rose Crisp]]></dc:creator>
            <pubDate>Tue, 06 Dec 2022 21:14:20 GMT</pubDate>
            <atom:updated>2022-12-07T15:25:35.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pbDcxFXVWMSLOtRt577ozg.png" /></figure><p>The most common way to install a K8s Operator is to add Custom Resource Definition, Custom Controller, and authentication/authorization to your cluster.</p><p>Some of the steps are listed here:</p><pre>oc create sa $OPERATOR_PROJECT<br>oc create -f deploy/role.yaml<br>oc create -f deploy/role_binding.yaml<br>oc create -f deploy/crds/${OPERATOR_GROUP}_${CRD_KIND,,}s_crd.yaml<br>oc create -f deploy/operator.yaml<br>oc create -f deploy/crds/${OPERATOR_GROUP}_${OPERATOR_VERSION}_${CRD_KIND,,}_cr.yaml<br>oc get deployment $OPERATOR_PROJECT<br>oc get pod -l app=example-${CRD_KIND,,}<br>oc describe ${CRD_KIND,,}s.${OPERATOR_GROUP} example-${CRD_KIND,,}</pre><p>Writing and managing these yaml files is difficult to say the least. A much easier way is to use the <a href="https://operatorframework.io/">Operator Framework</a> aid in the development, installation, and updating of the Operator.</p><p><strong>Why does the Operator Framework offer multiple ways of installing Kubernetes Operators?</strong></p><p>Because it cuts down the installation time during the development of your Operator. <strong>Operator Framework </strong>offers three installation strategies for development purposes. I’ll cover these methods, and conclude with a deep dive into using the <a href="https://olm.operatorframework.io/">Operator Lifecycle Manager</a> for installing and managing the lifecycle of your Operator in production.</p><p>Without further ado, let’s get started.</p><h4><a href="https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/#1-run-locally-outside-the-cluster">make install run</a></h4><blockquote>A super fast way to test your Custom controller code without building the container image of your operator.</blockquote><p>The Custom Controller is running on your local machine as an application without the use of Kubernetes Deployment</p><h4><a href="http://Fast way of testing the Operator Image because the Custom Controller is installed as a Kubernetes deployment.">make deploy img=&lt;operator-img&gt;</a></h4><blockquote>Fast way to test the Operator container Image</blockquote><p>The Custom Controller is running inside the cluster as a Deployment.</p><h4><a href="https://sdk.operatorframework.io/docs/cli/operator-sdk_run_bundle/"><strong>operator-sdk run bundle &lt;bundle-image&gt;</strong></a></h4><blockquote>Test the Operator bundle image without providing an index image.</blockquote><p>This method is integrated with OLM which means it uses OLM under the hood to install the Operator but without having to understand OLM. As a bonus, you can test operator upgrade by using the subcommand <strong>bundle-upgrade. </strong>For more information click <a href="https://sdk.operatorframework.io/docs/cli/operator-sdk_run_bundle-upgrade/#m-docsclioperator-sdk_run_bundle-upgrade">here</a>.</p><h4><a href="https://olm.operatorframework.io/">Operator Lifecycle Manager</a></h4><blockquote>OLM provides a way to install, manage and upgrade Operators on a cluster.</blockquote><p>In a nutshell, OLM comes with 2 operators, the Catalog operator and the OLM operator, and together they provide 5 resources working together for a seamless Operator install and upgrade experience. Low touch and a GUI way of installing your operator.</p><h3>Here are some terminologies important to the OLM</h3><p>The C<strong>atalog Operator</strong> acts on a new Subscription object created, and fetches the index image in the CatalogSource object @ certain intervals. If a new version of the Operator is available, it will generate a new InstallPlan object. The InstallPlan creates a Custom Resource Definitions and a ClusterServiceVersion(csv) object, and other dependent objects while the Catalog Operator tries to deploy dependent resources.</p><p>The <strong>OLM Operator</strong> acts on a new ClusterServiceVersion(csv) object created. It checks if the dependent resources are deployed by the Catalog Operator. Once all dependencies are installed, the OLM operator starts installing the operator.</p><p>The <strong>index image</strong> consists of one or more <strong>Operator bundles</strong>, and the Operator bundle includes the <strong>operator image and other manifest files.</strong></p><p>For an in-depth overview of the OLM operator click <a href="https://olm.operatorframework.io/docs/concepts/olm-architecture/">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/0*U0Ckft1lmovK9CCL" /></figure><h3>The best way to learn OLM is to do a step by step installation of the Operator using OLM.</h3><p>Prerequisite: Build example-operator using Operator-sdk toolkit.<br><em>Note:</em> New to OPERATOR SDK ? Have a look at this <a href="https://olm.operatorframework.io/about/">tutorial</a> to get started.</p><pre>export VERSION=0.0.1<br>export IMG=quay.io/$USERNAME/example-operator:v$VERSION<br>export BUNDLE_IMG=quay.io/$USERNAME/example-operator-bundle:v$VERSION<br>export CATALOG_IMG=quay.io/$USERNAME/example-operator-catalog:v$VERSION</pre><p>2. Generate bundle manifests and metadata, then validate generated files. More information can be found <a href="https://sdk.operatorframework.io/docs/cli/operator-sdk_generate_bundle/#synopsis">here</a>.</p><pre>make bundle</pre><p>3. Build and push the operator image.</p><pre>make docker-build docker-push</pre><p>4. Build and push the operator bundle image</p><pre>make bundle-build bundle-push</pre><p>5. Build and push the Operator index image</p><pre>make catalog-build catalog-push</pre><p>6. Make ALL images public</p><h4>Create a CatalogSource object that references the index image.</h4><p>7. Copy and paste the code below to a new yaml file named catalogsource.yaml</p><pre>apiVersion: operators.coreos.com/v1alpha1<br>kind: CatalogSource<br>metadata:<br> name: my-example-operators<br> namespace: example<br>spec:<br> sourceType: grpc<br> image: quay.io/rocrisp/example-operator-catalog:v0.0.1<br> displayName: Example Operators<br> publisher: Red Hat Partner<br> updateStrategy:<br> registryPoll:<br> interval: 5m</pre><p>8. Apply the yaml and verify CatalogSource is created and the associated pod is successfully running.</p><pre>$ oc apply -f catalogsource.yaml<br>catalogsource.operators.coreos.com/my-example-operators created<br><br>$ oc get pods<br>NAME READY STATUS RESTARTS AGE<br>my-example-operators-wd6cv 1/1 Running 0 16s<br><br>$ oc get catalogsource<br>NAME DISPLAY TYPE PUBLISHER AGE<br>my-example-operators Example Operators grpc Red Hat Partner 2m34s<br><br>$ oc get packagemanifests | grep &#39;Example Operators&#39;<br>example-operator Example Operators 7m56s</pre><h4><a href="https://docs.openshift.com/container-platform/4.11/operators/understanding/olm/olm-understanding-operatorgroups.html">OperatorGroup</a> provides multi tenant configuration to OLM-installed operators. Further readings can be found <a href="https://olm.operatorframework.io/docs/advanced-tasks/operator-scoping-with-operatorgroups/">here</a>.<br> <br>Create an OperatorGroup object.</h4><p>9. Copy and paste the code below to a new yaml file named operatorgroup.yaml.</p><pre>apiVersion: operators.coreos.com/v1<br>kind: OperatorGroup<br>metadata:<br> name: example-group<br> namespace: example</pre><p>10. Apply the yaml and verify OperatorGroup is created within the namespace example</p><pre>$ oc apply -f operatorgroup.yaml<br>operatorgroup.operators.coreos.com/example-group created<br><br>$ oc get og<br>NAME AGE<br>example-group 22s</pre><h4>Create a Subscription object.</h4><p>11. Copy and paste the code below to a new yaml file named subscription.yaml</p><pre>apiVersion: operators.coreos.com/v1alpha1<br>kind: Subscription<br>metadata:<br> name: example-subscription<br> namespace: example<br>spec:<br> channel: alpha<br> installPlanApproval: Automatic<br> name: example-operator<br> source: my-example-operators<br> sourceNamespace: example</pre><p>Apply the yaml and verify Subscription, InstallPlan, and ClusterServiceVersion(csv) objects are created</p><pre>$oc apply -f subscription.yaml<br>subscription.operators.coreos.com/example-subscription created<br><br>$oc get sub<br>NAME PACKAGE SOURCE CHANNEL<br>example-subscription example-operator my-example-operators alpha<br><br>$ oc get installplan<br>NAME CSV APPROVAL APPROVED<br>install-mz2bm example-operator.v0.0.1 Automatic true<br><br>$ oc get csv<br>NAME DISPLAY VERSION REPLACES PHASE<br>example-operator.v0.0.1 example 0.0.1 Succeeded</pre><p>Once the new ClusterServiceVersion(csv) object is created, the OLM operator will complete the operator install</p><p>12. Verify the operator is running in the example namespace:</p><pre>$ oc get pod | grep example-operator-controller<br>example-operator-controller-manager-6dc58f4996-lbzmp 2/2 Running 0 21m</pre><p>The controller pod is running so we have successfully installed example-operator v0.0.1.</p><p>Upgrading is always necessary for any Operator improvement and OLM makes it really easy to do.</p><p>Basically, we create a new version of Operator image, Operator bundle image, and Operator index image. Update the CatalogSource resource and watch for the new Operator being installed.</p><ol><li>First we bump up the version number to 0.0.2 and re-assign the parameters as exported variables.</li></ol><pre>export VERSION=0.0.2<br>export IMG=quay.io/$USERNAME/example-operator:v$VERSION<br>export BUNDLE_IMG=quay.io/$USERNAME/example-operator-bundle:v$VERSION</pre><p>2. Generate bundle manifests and metadata, then validate generated files.</p><pre>make bundle</pre><p>3. Build and push the Operator image and the Operator bundle image.</p><pre>make docker-build docker-push <br>make bundle-build bundle-push</pre><p>4. To create a new index image containing bundle images versions 0.0.1 and 0.0.2, we add a new parameter as an exported environment variable.</p><p>Under the hood, makefile uses CATALOG_BASE_IMG to add a flag “from-index” to <em>opm index add</em> which pulls operator bundle images from the base catalog index image to add to the new catalog index image.</p><pre>export CATALOG_BASE_IMG=quay.io/$USERNAME/example-operator-catalog:v0.0.1</pre><p>5. Build and push the Operator index image.</p><pre>make catalog-build catalog-push</pre><p>6. Verify operator-bundle images version 0.0.1 and 0.0.2 are copied inside the operator-index image</p><pre>$ opm index export --index=&quot;quay.io/rocrisp/example-operator-catalog:v0.0.2&quot; --package=&quot;example-operator&quot; -c=&quot;docker&quot;<br><br>$ tree downloaded/example-operator/<br>downloaded/example-operator/<br>├── 0.0.1<br>│   ├── cache.example.com_customresources.yaml<br>│   ├── example-operator-controller-manager-metrics-service_v1_service.yaml<br>│   ├── example-operator-metrics-reader_rbac.authorization.k8s.io_v1_clusterrole.yaml<br>│   └── example-operator.clusterserviceversion.yaml<br>├── 0.0.2<br>│   ├── cache.example.com_customresources.yaml<br>│   ├── example-operator-controller-manager-metrics-service_v1_service.yaml<br>│   ├── example-operator-metrics-reader_rbac.authorization.k8s.io_v1_clusterrole.yaml<br>│   └── example-operator.clusterserviceversion.yaml</pre><p>7. Update catalogsource.yaml from version v0.0.1 to v0.0.2.</p><p>Note : You can ignore this step if you choose to use latest as the version for index image. Ex. quay.io/rocrisp/example-operator-catalog:latest. Go back to Step 4 and export CATALOG_BASE_IMG=quay.io/$USERNAME/example-operator-catalog:latest</p><pre>apiVersion: operators.coreos.com/v1alpha1<br>kind: CatalogSource<br>metadata:<br>name: my-example-operators<br>namespace: example<br>spec:<br>sourceType: grpc<br>image: quay.io/rocrisp/example-operator-catalog:v0.0.2<br>displayName: Example Operators<br>publisher: Red Hat Partner<br>updateStrategy:<br> registryPoll:<br> interval: 5m</pre><p>8. Apply the yaml and verify the new pod associated with the CatalogSource comes up.</p><pre>$ oc apply -f catalogsource.yaml<br>catalogsource.operators.coreos.com/my-example-operators configured<br><br>$ oc get pod<br>NAME READY STATUS RESTARTS AGE<br>2fea47e9a5fc901db7b940da38a3cbc4028077cd5a8467ba363f6fb03c22nwz 0/1 Completed 0 87m<br>example-operator-controller-manager-6dc58f4996-lbzmp 2/2 Running 0 86m<br>my-example-operators-fv66b 0/1 Running 0 10s<br>my-example-operators-v5lqr 0/1 Running 0 10s</pre><p>9. Verify a new InstallPlan version v0.0.2 is generated by the Catalog Operator.</p><pre>$ oc get installplan<br>NAME CSV APPROVAL APPROVED<br>install-f24gx example-operator.v0.0.2 Automatic true<br>install-mz2bm example-operator.v0.0.1 Automatic true</pre><p>10. Verify a new ClusterServiceVersion(csv) object is generated by the InstallPlan resource and the OLM operator has successfully installed the Operator by checking the PHASE equals to succeeded.</p><pre>$ oc get csv<br>NAME DISPLAY VERSION REPLACES PHASE<br>example-operator.v0.0.2 example 0.0.2 example-operator.v0.0.1 Succeeded</pre><p>Now you have it. OLM makes it routine to install and upgrade your Operator.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42874d07c6ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step by step guide : How to install Open edX Platform on Red Hat Openshift Container Platform.]]></title>
            <link>https://medium.com/step-by-step-install-open-edx-platform-on-red-hat/step-by-step-guide-how-to-install-open-edx-platform-on-red-hat-openshift-container-platform-7eaca4dcd8a2?source=rss-2a453c252a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eaca4dcd8a2</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[online-learning-system]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[red-hat-openshift]]></category>
            <category><![CDATA[open-edx]]></category>
            <dc:creator><![CDATA[Rose Crisp]]></dc:creator>
            <pubDate>Mon, 16 Nov 2020 15:30:29 GMT</pubDate>
            <atom:updated>2020-11-16T15:30:29.879Z</atom:updated>
            <content:encoded><![CDATA[<h3>Step by step guide : How to install Open edX Platform on Red Hat Openshift Container Platform.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVTQsXsmCI_FqMS3_CqUzA.jpeg" /></figure><h3>Before you begin</h3><p>You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. If you do not already have a cluster, you can create one by using <a href="https://kubernetes.io/docs/tasks/tools/#minikube">minikube</a> or in my case and for this article, I’m using Openshift Cluster from <a href="https://www.openshift.com/"><strong>Red Hat</strong></a>.</p><p><strong>OpenShift</strong> is an open source <strong>container</strong> application <strong>platform</strong> based on the <strong>Kubernetes container</strong> orchestrator for enterprise app development. It is easy to install, configure and manage a kubernetes cluster than using other tools.</p><p>I installed Openshift Cluster version 4.5 on AWS by following the installation guide provided by Red Hat.</p><p><a href="https://docs.openshift.com/container-platform/4.5/installing/installing_aws/installing-aws-account.html">Configuring an AWS account</a></p><h4>1. In your terminal, set the KUBECONFIG environment variable</h4><pre>export KUBECONFIG=/path to your kubeconfig file</pre><h4>2. Managing SCCs in OpenShift</h4><p>Running Tutor in a OpenShift Cluster will fail with Permission Denied. This is because Tutor expects to start containers with root privileges.</p><p>To keep your cluster safe by default, OpenShift prevents containers from running as root (although cluster-admins can override this). Unfortunately, this means that Tutor won’t run out of the box on OpenShift today. However, the good news is that none of this prevents you from installing and managing secure (non-root) containers on OpenShift.</p><p>To fix this, we’re going to allows images to run as the root UID if no <strong>USER</strong> is specified in the <strong><em>Dockerfile</em></strong>.</p><pre>oc adm policy add-scc-to-group anyuid system:authenticated</pre><p>Some container images (examples: RabbitMQ ) require root access and have certain expectations about how volumes are owned. For these images, add the service account to the anyuid SCC.</p><pre>oc adm policy add-scc-to-user anyuid &quot;system:serviceaccount:openedx:default&quot;</pre><pre>oc adm policy add-scc-to-user anyuid &quot;system:serviceaccount:openedx:builder&quot;</pre><pre>oc adm policy add-scc-to-user anyuid &quot;system:serviceaccount:openedx:deployer&quot;</pre><h3>Next on the list</h3><p>There are a few docker-based Open edX installation packages out there, but some of the images are outdated or the documentation is hard to follow.</p><h4>Tutor however, is well maintained and easy to install.</h4><p>I suggest using pip to install Tutor because it will install the latest version of Tutor. For this article, the version I’m using is tutor-openedx 10.4.1.</p><p>Here is more information on installation of Tutor using the pip command.</p><p><a href="https://docs.tutor.overhang.io/install.html#installing-from-pypi">Install Tutor - Tutor documentation</a></p><p>Since we’re installing Open edX on an Openshift Cluster ( Openshift Cluster is based on the Kubernetes container orchestrator ), you might want to read about the installation from the official documentation from Tutor.</p><p><a href="https://docs.tutor.overhang.io/k8s.html">Kubernetes deployment - Tutor documentation</a></p><h3>Now that you have an Openshift Cluster and Tutor installed, we’re ready to get started.</h3><pre>tutor k8s quickstart</pre><p>For LMS Host, I put www.lms-openedx.apps.courses.operatortrain.me</p><ul><li>You can replace <em>lms </em>with your own<em>.</em></li><li>openedx is the namespace where tutor installs OpenedX. Leave this as is.</li><li>apps is defined by Openshift. Leave this as is.</li><li>courses.operatortrain.me is the Openshift domain. Replace this with your Openshift domain name.</li></ul><p>Answer Y to Production<br>Answer N to ACTIVATE_HTTPS</p><p>Tutor will start to install OpenedX in your Openshift Cluster.<br>Here is an example of my cluster.</p><pre>oc get all</pre><pre>NAME                                 READY   STATUS      RESTARTS   AGE</pre><pre>pod/cms-978bf6646-9jzjq              1/1     Running     0          24h</pre><pre>pod/cms-job-20201113134945-j8kh4     0/1     Completed   0          24h</pre><pre>pod/cms-worker-5c7987b78d-9gv9r      1/1     Running     0          24h</pre><pre>pod/elasticsearch-5bd96c9995-t56b6   1/1     Running     0          24h</pre><pre>pod/forum-778db5bdd4-d99jv           1/1     Running     5          24h</pre><pre>pod/forum-job-20201113135014-5kmn8   0/1     Completed   0          24h</pre><pre>pod/lms-fc7b47db4-n7g85              1/1     Running     0          24h</pre><pre>pod/lms-job-20201113134503-rf6l8     0/1     Completed   0          24h</pre><pre>pod/lms-worker-589b6b99cb-kntbx      1/1     Running     0          24h</pre><pre>pod/memcached-5f6f6cc58-4kbsp        1/1     Running     0          24h</pre><pre>pod/mongodb-5fc58c59f5-t2qvm         1/1     Running     0          24h</pre><pre>pod/mysql-7d5d7cc69d-9xdtx           1/1     Running     0          24h</pre><pre>pod/mysql-job-20201113134454-tdbpk   0/1     Completed   0          24h</pre><pre>pod/nginx-df8f747bd-h45t7            1/1     Running     0          24h</pre><pre>pod/rabbitmq-6fc689b655-zvtcs        1/1     Running     0          24h</pre><pre>pod/smtp-684879f87b-4wc6g            1/1     Running     0          24h</pre><pre>NAME                    TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE</pre><pre>service/cms             NodePort   172.30.55.21     &lt;none&gt;        8000:31568/TCP               24h</pre><pre>service/elasticsearch   NodePort   172.30.255.20    &lt;none&gt;        9200:31753/TCP               24h</pre><pre>service/forum           NodePort   172.30.218.132   &lt;none&gt;        4567:30471/TCP               24h</pre><pre>service/lms             NodePort   172.30.106.144   &lt;none&gt;        8000:31467/TCP               24h</pre><pre>service/memcached       NodePort   172.30.178.36    &lt;none&gt;        11211:31652/TCP              24h</pre><pre>service/mongodb         NodePort   172.30.239.100   &lt;none&gt;        27017:32587/TCP              24h</pre><pre>service/mysql           NodePort   172.30.146.85    &lt;none&gt;        3306:32015/TCP               24h</pre><pre>service/nginx           NodePort   172.30.191.111   &lt;none&gt;        80:30728/TCP,443:32623/TCP   24h</pre><pre>service/rabbitmq        NodePort   172.30.149.198   &lt;none&gt;        5672:31506/TCP               24h</pre><pre>service/smtp            NodePort   172.30.10.229    &lt;none&gt;        25:32436/TCP                 24h</pre><pre>NAME                            READY   UP-TO-DATE   AVAILABLE   AGE</pre><pre>deployment.apps/cms             1/1     1            1           24h</pre><pre>deployment.apps/cms-worker      1/1     1            1           24h</pre><pre>deployment.apps/elasticsearch   1/1     1            1           24h</pre><pre>deployment.apps/forum           1/1     1            1           24h</pre><pre>deployment.apps/lms             1/1     1            1           24h</pre><pre>deployment.apps/lms-worker      1/1     1            1           24h</pre><pre>deployment.apps/memcached       1/1     1            1           24h</pre><pre>deployment.apps/mongodb         1/1     1            1           24h</pre><pre>deployment.apps/mysql           1/1     1            1           24h</pre><pre>deployment.apps/nginx           1/1     1            1           24h</pre><pre>deployment.apps/rabbitmq        1/1     1            1           24h</pre><pre>deployment.apps/smtp            1/1     1            1           24h</pre><pre>NAME                                       DESIRED   CURRENT   READY   AGE</pre><pre>replicaset.apps/cms-978bf6646              1         1         1       24h</pre><pre>replicaset.apps/cms-worker-5c7987b78d      1         1         1       24h</pre><pre>replicaset.apps/elasticsearch-5bd96c9995   1         1         1       24h</pre><pre>replicaset.apps/forum-778db5bdd4           1         1         1       24h</pre><pre>replicaset.apps/lms-fc7b47db4              1         1         1       24h</pre><pre>replicaset.apps/lms-worker-589b6b99cb      1         1         1       24h</pre><pre>replicaset.apps/memcached-5f6f6cc58        1         1         1       24h</pre><pre>replicaset.apps/mongodb-5fc58c59f5         1         1         1       24h</pre><pre>replicaset.apps/mysql-7d5d7cc69d           1         1         1       24h</pre><pre>replicaset.apps/nginx-df8f747bd            1         1         1       24h</pre><pre>replicaset.apps/rabbitmq-6fc689b655        1         1         1       24h</pre><pre>replicaset.apps/smtp-684879f87b            1         1         1       24h</pre><pre>NAME                                 COMPLETIONS   DURATION   AGE</pre><pre>job.batch/cms-job-20201113134945     1/1           24s        24h</pre><pre>job.batch/forum-job-20201113135014   1/1           21s        24h</pre><pre>job.batch/lms-job-20201113134503     1/1           4m41s      24h</pre><pre>job.batch/mysql-job-20201113134454   1/1           3s         24h</pre><h3>You’re almost done !</h3><p>By default, ingress is NOT deployed to the Kubernetes cluster when running “quickstart”.</p><p>However, tutor has already created a file named ngress.yml for us, and all we have to do is run it to create the router needed to access the OpenEdx website.</p><blockquote><em>I’m on a mac so tutor installs all the files under /Users/userid/Library/Application Support/tutor.</em></blockquote><p>ingress.yml is in <strong>/Users/userid/Library/Application Support/tutor/env/k8s</strong></p><pre>oc apply -f ingress.yml<br>oc get routes</pre><pre>NAME        HOST/PORT                                               PATH   SERVICES   PORT   TERMINATION   WILDCARD</pre><pre>web-h7bbh   www.lms-openedx.apps.courses.operatortrain.me                  nginx      http                 None</pre><pre>web-qzq4g   preview.www.lms-openedx.apps.courses.operatortrain.me          nginx      http                 None</pre><pre>web-wp7jd   studio.www.lms-openedx.apps.courses.operatortrain.me           nginx      http                 None</pre><h3>Now you have setup your own LMS, Open edX on an Openshift Cluster !!!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eaca4dcd8a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/step-by-step-install-open-edx-platform-on-red-hat/step-by-step-guide-how-to-install-open-edx-platform-on-red-hat-openshift-container-platform-7eaca4dcd8a2">Step by step guide : How to install Open edX Platform on Red Hat Openshift Container Platform.</a> was originally published in <a href="https://medium.com/step-by-step-install-open-edx-platform-on-red-hat">Step by step : Install Open edX Platform on Red Hat Openshift Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>