Skip to content

Addon pko doc #14

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.

Sign up for GitHub

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

Open
venkateshsredhat wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Addon pko doc #14

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f055533
Tenant onboarding
Jun 26, 2023
cc06542
Update addon-package.md
venkateshsredhat Jun 26, 2023
1afeb70
Update addon-package.md
venkateshsredhat Jun 26, 2023
89c775b
updated the doc
Jun 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions content/en/docs/creating-addons/top-level-operator/addon-package.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,19 @@ respectively. *To have these values inject you must maintain the default naming
All the values in `.spec.config.addonsv1` can be injected into the objects contained in your packageImage. See the
[package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#go-templates) to see
how to do this.

## Tenants Onboarding Steps

Teams can generate the packageImage themselves using the [package operator documentation](https://package-operator.run/docs/guides/packaging-an-application/#build--validate) although we recommend teams to use Managed Tenants Bundles (MTB) facilities.

Below are the Steps for generating the packageImage using MTB flow for reference-addon packageImage:

In MTB, a team just has to create a "package" directory:
https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon/package and add the manifests there, alongside the manifests.yaml[PackageManifest] .

MTB CI will create the packageImage (in addition to the OLM Index Image which is also part of the Team's addon folder https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/reference-addon) .

Then MTB CI raises a MR to [managed-tenants repository](https://gitlab.cee.redhat.com/service/managed-tenants/-/blob/main/addons/reference-addon/addonimagesets/stage/reference-addon.v0.10.1.yaml#L24) , adding a new AddonImageSet with those images.

@Ankit152 Ankit152 Jun 28, 2023

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can write something like, Once the MTB Pr is merged and builds are successful a MR is generated...