Rootconf Delhi edition

Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Rootconf is a platform to discuss real-world problems around Site Reliability Engineering (SRE), DevOps for data engineering platforms, evaluating and adopting technologies such as Kubernetes and containers, and DevSecOps.

Rootconf Delhi edition will be held on 18 January 2020 at the India International Centre (IIC).

Speakers from Flipkart, Hotstar, MindTickle, Red Hat and will discuss the following topics:

  1. Scaling and engineering challenges from Hotstar’s and Flipkart’s experiences.
  2. Data store choices.
  3. Kubernetes and K8s – when to choose what and why?
  4. DevSecOps

Who should attend Rootconf:

  1. Operations engineers
  2. DevOps programmers
  3. Software developers
  4. SRE
  5. Tech leads

To know more about Rootconf, check the following resources:



Click here to view the Sponsorship Deck.
Email for bulk ticket purchases, and sponsoring the above Rootconf Series.

Rootconf Delhi sponsors:

Silver Sponsor


Bronze Sponsors

upcloud SumoLogic

Community Partner

IFF Null Delhi

For information about the event, tickets (bulk discounts automatically apply on 5+ and 10+ tickets) and speaking, call Rootconf on 7676332020 or write to

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Vijay Dharap


The good, the bad and the ugly of Kubernetes - A Practitioners View!

Submitted Oct 20, 2019

Kubernetes continues to take the world by the storm every passing day. But at the same time, it continues to be fairly complex beast to tame, manage and be beneficial to the businesses.

In this talk, I would like to quickly look at:

  • why I like Kubernetes and what benefits does a k8s based infrastructure can offer (the good),
  • what challanges did I face when I implemented my k8s cluster and how did I overcome them. What are the typical gotchas to look out for when you implement Kubernetes (the bad)
  • And last but not the least – What part of kubernetes perplexes me and what am I doing about it (the ugly)

I hope that I can take the crowd on the journey filled with practical experiences – accompanied by small code snippets – and give them an insight on how they can watch for some pitfalls and have a successful kubernetes implementation.


  • Small overview kubernetes exposure
  • The Ugly Some of the decision which backfired upon me
    • Choices of EKS as Kubernetes service (replaced it with KOPS later)
    • Grafana based Alerting (Replaced with Prometheus Alerting)
    • kubeadm install - etcd failure in master nodes
  • The Bad – Some issues faced which became apparent little later but were resolved:
    • certificate length and cloudfront
    • Access log monitoring and analysis – ELK / EG
    • EFS starvation issues - separate your monitoring infrastructure from your application infrastructure
  • The Good – What I loved during my journey
    • helm charts - why is it awesome, how can it be even more easier with below tips
      • why to use
      • Install vs upgrade –install
      • configmap gotcha
      • locking down the version
    • Resource limit and health of your worker nodes
    • IaC and terraform – a lifesaver… (oh… and also a pain to deal with)
    • KOPS – a lifesaver
    • Prometheus – a highly extensible monitoring tool – ephemeral storage, etcd health, certificates, and other OOTB tools like jmx_exporter, blackbox, etc
    • Nginx-Ingress and automatic ELB vs ALB-nginx-ingress
  • Tips and Tricks
    • K8s specific Productivity enahancements: kube-ps1, kubens, aliases, etc
    • General linux productivity enahancements: git ps1, byobu, putty default values for timeout resolution, dealing with corporate CA issued certificates
    • Secrets are namespace specific. How to copy secret from one namespace to another
    • Ensuring you don’t lose your home directories in IaC
  • There is no silver bullet
    • IaC where to draw the line between terraform vs scripted application
    • Reflection on what should NOT be in kubernetes

Speaker bio

I am a Principal Technology Architect at Infosys in India with broad ranging experience from architecting large enterprise web applications to cloud infrastructure design and deployment in DevOps mode.

I am very passionate about Open Source and am a Developer Advocate within Infosys. I have spoken at conferences in India like GIDS, JSFoo, ReactFoo, etc. I organize technical conferences within Infosys. I enjoy keeping up-to-date with trends in UI and UX world and love discussing technical topics on twitter at my handle @dharapvj



{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more