Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Tickets

Solving Real World Problems of Running CMS on Kubernetes using Operators

Submitted by Adheip Singh (@adheipsingh) on Wednesday, 18 September 2019

Section: Full talk (40 mins) Category: Containers Status: Rejected

Abstract

How at SRIJAN we solved the real world problems of running CMS (Drupal) on kubernetes by writing an Operator. How can operators help in running stateful applications on kubernetes. What are the various approaches on writing operators, SRIJAN’s journey in writing an operators covering our pitfalls and learnings. A live demo of our operator which will be opensourced soon.

Outline

CMS are not microservices, so running on kubernetes can be painful. Sameway a lot of monolith stacks when tried to be broken into microservices result in ending up having decoupled/macro services. Running such kind of stacks can be tough, using operators in kubernetes we are able to solve issues such as scalibility, backups, realibilty and having a full application management lifecycle around our services. Operators help us run kubernetes more intelligently since our operator(which is a custom controller) has full knowledge of application lifecycle.Describing SRIJAN’s journey in writing operators, our learning and pitfalls. A live demo of our operator.

Requirements

Kubernetes knowledge, GoLang knowledge preferred.

Speaker bio

Adheip Singh, Senior DevOps at SRIJAN. Have been a distributed system enthusiast and OpenSource Lover. A GoLang Developer at heart currently handling SRIJAN’s OpenSource initiatives which include Kubernetes and ServiceMesh.

Links

Slides

https://www.slideshare.net/SrijanOne/srijan-wednesday-webinar-how-to-run-stateless-and-stateful-services-on-k8s-operator

Preview video

https://www.youtube.com/watch?v=A0YM-S1Ob20&t=2691s

Comments

  •   Zainab Bawa (@zainabbawa) Reviewer 5 months ago

    Thank you for the submission, Adhiep. There are two direct concerns:

    1. It’s unclear why participants should learn about Srujan’s open source solution. Right now, the proposal comes across as a pitch for Srujan’s solution.
    2. Since the solution isn’t open sourced, either you modify your proposal to explain what was the (business/tech) problem that Srujan was trying to solve and therefore why you built this solution. Or, we will only consider the solution once it is open sourced and links for the open source repo are submitted here.

    Look forward to your response.

    •   Zainab Bawa (@zainabbawa) Reviewer 4 months ago

      Hello Adhiep. Since there is no response to these comments and the proposal looks more like advocacy for Srujan’s solution, we are unable to accept it for the conference.
      All the best for this work. We look forward to your participation at the conference, and proposals for future editions.

Login with Twitter or Google to leave a comment