You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stacks can be used to extend the functionality of Crossplane with new types of infrastructure and applications. The experience for creating and publishing a stack is very manual at this point, so we can provide some automation and user experience around this process. This will facilitate the adoption of Stacks by the community and make it easier for more people to create their own.
What does it look like when we're done?
The general user experience will be described in a design 1-pager
Users will have an automated experience around:
initializing a new repo with the scaffolding for creating a stack
building a stack
publishing a stack
kubectl plugin (e.g. bash script)
only have limited config: name; limited support for patterns; kubebuilder v2.0 projects
How could this be demonstrated?
Crossplane user reads the blog post describing this new functionality
Click through to the updated user guide
Try out the updated example(s)
For example:
building the wordpress stack
publishing the wordpress stack
init a new hello-world stack as part of example so new users can get started quickly
Relative to #572 , we are thinking that this epic is the lower priority of the two. I am planning on working on #572 first before starting this one; I am planning to only do work on this epic before finishing #572 if it seems like it will help me finish #572 faster.
Initial DevOps tooling to build Stacks, push Stacks to a registry, and init the scaffolding for new Stacks.
Part of the 0.3 release
Why? What problem are we solving with this epic?
Stacks can be used to extend the functionality of Crossplane with new types of infrastructure and applications. The experience for creating and publishing a stack is very manual at this point, so we can provide some automation and user experience around this process. This will facilitate the adoption of Stacks by the community and make it easier for more people to create their own.
What does it look like when we're done?
How could this be demonstrated?
For example:
What is dev UX, e.g. CLI commands and usage?
TBD
Related
The text was updated successfully, but these errors were encountered: