Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forge Role Definitions and User Scenarios #193

plombardi89 opened this issue May 7, 2018 · 0 comments

Forge Role Definitions and User Scenarios #193

plombardi89 opened this issue May 7, 2018 · 0 comments


Copy link

plombardi89 commented May 7, 2018

Last week @rhs and I spent some time trying to come up with the various user roles that Forge might be of interest to and the user scenarios that Forge functionality currently serves or in the future should serves.


These are not necessarily a single person. A person may inherit multiple of these, for example, a software engineer might be both an Operator and Developer.


Expectation: Person who gets paged / notified first and is the first to handle the alert.


Expectation: Build new product features or fix known product defects.


Expectation: Build tooling to optimize product development and operational lifecycle.


Unify operator, developer and platform role goals.


When wearing the Platform Engineer hat:

  • How can I modify the manifest before apply so I can override certain settings set by the developer for safety or stability reasons.
  • How can I share best practices for projects in my organization?
  • How can I validate manifests before they are applied to the Kubernetes cluster to ensure compliance with various things.
  • How can I ensure I am always deploying "stable" well-tested things that do not have drift between test and promotion to stable.

When wearing the Operator hat:

When wearing the Developer hat:

When wearing the Manager hat:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant