Building a Developer Portal
One of the more popular concepts in recent years of DevOps and automation is to provide an Internal Developer Portal (IDP). The purpose of this portal is to provide a single point of service for your developers and infrastructure team to be able to access architectural services without having to send an email to “your guy” in IT. This is often the promise of cloud-based services, though it requires considerable custom development to achieve. It also provides the foundation for creating the guardrails needed to develop a manageable architecture.
This chapter is going to combine the theory we walked through in Chapter 18, Provisioning a Multitenant Platform, along with most of the concepts and technologies we’ve learned throughout this book to create an IDP. Once you’ve completed this chapter, you’ll have an idea of how to build an IDP for your infrastructure, as well as context for how the various technologies we have built and integrated into Kubernetes through this book should come together.
This chapter will cover the following topics:
- Technical requirements
- Deploying our IDP
- Onboarding a tenant
- Deploying an application
- Expanding our platform
Finally, before we dive into the chapter, we’d like to say thank you! This book has been quite the journey for us. It’s amazing to see how much has changed in our industry since we wrote the second edition, and how far we have come. Thank you for joining us on our quest to build out enterprise Kubernetes, and explore the different technologies and how the enterprise world impacts how we create that technology.
