If you’ve ever launched a startup, you know how hard it is to find funding. It’s a huge grind just to get from conception to execution without even worrying about profitability yet. But to attract an investor, you have to show consistent revenue growth to prove they will eventually see a return. Many, many startups fail before they reach a Series A. And the industry with the highest startup failure rate? The information industry, at 63%.

In this tutorial, we will be using Heroku to deploy our Node.js application through CircleCI using Docker. We will set up Heroku Continuous Integration and Deployment (CI/CD) pipelines using Git as a single source of truth. Containerization allows developers to create and deploy applications faster with a wide range of other benefits like increased security, efficiency, agility to integrate with DevOps pipelines, portability, and scalability.

In part one of this series on Kubernetes RBAC, we introduced authentication and authorization methods. In this article, we’ll dive a little deeper into authentication — a prerequisite for RBAC. As we saw, there are a few authentication methods including client certificates, bearer tokens, HTTP basic auth, auth proxy, and impersonation. Because HTTP basic auth and statically configured bearer tokens are considered insecure, we won’t cover them here.