How to organize users, teams and applications in IBM Cloud
Ever wondered how you would organize your users, teams, applications, build pipelines if you had to manage a large project deploying to multiple environments?
When building an application, it is very common to define multiple environments reflecting the development lifecycle of a project from a developer committing code to an update being made available to the end-users. Sandbox, test, staging, UAT (user acceptance testing), pre-production, production are typical names for these environments.
Isolating the underlying resources, implementing governance and access policies, protecting a production workload, validating changes before pushing them to production, are some of the reasons why you would want to create these separate environments. There is no one size fits all but understanding the concepts at your disposal to achieve your goals is one step in the right direction.
We have added a new tutorial to the IBM Cloud documentation where we look at concepts such as Identity and Access Management, Resources, Policies, Roles, DevOps pipelines, Kubernetes clusters and how to apply the concepts to a sample project scenario.
The tutorials section has a feedback form on the side where you can comment on the content. If you have suggestions on the existing tutorials or ideas for future additions, please submit your feedback.
