And so, you've been tasked to build a private cloud platform
Once upon a while, there was a datacenter that needed to go through a renewal to be in sync with the company's cloud adoption.
Self-service tools were lacking and created frustration for projects that didn't "move to the cloud".
Top management declared that creating a "private cloud platform" was now a strategic case for the entity.
We'll share our early journey testimony with many questions still unanswered. In this session, do not expect a reference implementation.
Plan:
• Birth of the project
○ Multiple issues with legacy suppliers
○ Technological debt and issues with providing a cloud-native experience onpremise.
○ From Namespace as a Service to Platform development
○ Why kubernetes ?
• Identifying your customers
○ How to find them ?
○ Wich usecases ?
• From PaaS to PlatformOfPaaS to PaaP & IDP
• Reviewing technologies
○ App delivery
○ Databases (Postgresql)
○ POC & First demo
• Identifying related projects to help you
○ Platform WG
○ BestPractices / Implementation ?
"The Walking Pods" Cluster horde is invading the company
What happens when you switch from a few kubernetes projects to a multi-entity service line strategy and then it becomes popular in your company (150+ clusters !).
Lets try to share some solutions, tips and self reflections ?
Our feedbacks on technical/organizational issues when our fleet doubles (number of clusters and projects) every year .
Themes:
- support and organizational issues & clarifying users technical responsibilities.
- limits of the technical maintenance in operational condition & lifecycle constraints
- cloud providers promises & alternative architectures;
From vision of heaven to hell on earth, a realistic and pragmatic middle ground, when our choices are confronted with reallity.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top