Follow-up: Create Operator Framework Quay images Is this the name we want? Do we want to split the apiserver and controllers into separate repos? Is this something we want to do as part of the alpha release/implementation process? Transfer ownership of anik120/rukpak-packageserver to Operator Framework GitHub Organization (?) We should probably try to use kustomize to make this process as automated as possible (i.e just have to run a `make` target) Currently there are a lot of manual changes that need to be made with the manifests (mostly related to RBAC) as the controller and API implementations are modified. Explore configuring the manifests generation to be a bit better automated release on tag push using goreleaser go fmt/vet & git diff checks on PR/merge Can probably break this down into smaller chunks Update the Operator Registry or OF/api types to include the appropriate functions to be used in multiple different scenarios (i.e library usage and CR field type usage) Ensure ownership is set properly on child resources for easy resource cleanup on CatalogSource deletion Refactor CatalogSource controller to follow a similar format to that of rukpak or oria controllers (keeps controller implementations across OLM v1 components consistent) Update CatalogSource controller to properly handle various error states Update CatalogSource CR to communicate state via `.Status.Conditions` Refine the CatalogSource controller to be more production-like I was thinking it might be nice to go ahead and create tickets for things we *know* we are going to have to do regardless of the route we take after the PoC so this is a stab at that: Is this something we want to do as part of the PoC? Test the viability of this new API approach early by creating some form of integration Extend the current Operator Controller prototypes to use the new CatalogSource V1 API surface (?) (might be best to do this on a new branch/fork to have some degree of separation between approaches) Update the current CatalogSource V1 PoC to run the GraphQL PoC as a sidecar for storing/serving bundle/catalog data. Update the GraphQL PoC to have functionality to add bundle/catalog data The purpose of this is to evaluate a method that reduces the number of CREATE requests sent to the apiserver in anticipation that this *could* be a concern GraphQL sidecar container for serving bundle data (replaces `BundleMetadata` CR) Explore options for configuring Package and BundleMetadata CR admission criteria on the apiserver See how to open and use custom libraries in diagrams.A scratchpad for potential new Jira stories/epics/tasks to be created for various things xml file extension by default - then click Download, or click on the location where you want to save the file. Enter a filename - your custom shape library will be saved with the.Click the edit pencil to edit the scratchpad, then click Export.By default, shapes added to the scratchpad are untitled.Ĭlick Save when you have finished editing the scratchpad to return to the drawing canvas.Įxport the scratchpad as a custom shape library Click on the text field underneath a shape and enter a name.Click on the small cross in the top-right of a shape to delete it from the scratchpad.Click and drag shapes into new positions in the scratchpad.You can connect this to an existing shape on the drawing canvas by hovering over the target shape and then dropping it on one of the direction arrows that appear.Ĭlick the edit pencil icon to open the scratchpad ‘library’ and edit the shapes you have stored there. Alternatively, once you have selected the shapes, click on the little + (plus) icon in the heading of the Scratchpad library to add the shapes.Īdd shapes from the scratchpad to the drawing canvasĬlick on one of the shapes or groups of shapes you have saved to the scratchpad to add another copy to the drawing canvas.ĭrag the shapes from the scratchpad.Select one or more shapes, then drag them from the drawing canvas and drop them onto the scratchpad.See how to get started with the editor Add shapes to the scratchpad Select View > Scratchpad to display or hide the scratchpad.The scratchpad is usually found at the top of the left panel, above the shape libraries and below the Search Shapes field. You can drag a shape/group of shapes from the drawing canvas onto your scratchpad, and then drag new copies from the scratchpad back onto the drawing canvas whenever you need them. The scratchpad is your personal shape library where you can add the styled shapes or groups of shapes that you use the most often. Modified on: Wed, 16 Dec, 2020 at 6:27 PM
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |