This repository has been archived by the owner on Sep 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Investigate if we can get rid of the addons version #60
Labels
area/service-management
Issues or PRs related to service management
Comments
mszostok
added
the
area/service-management
Issues or PRs related to service management
label
Dec 4, 2019
mszostok
changed the title
Investigation if we can get rid of the addons version
Investigate if we can get rid of the addons version
Dec 4, 2019
Consider if we need versioning for this issue: #61 |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to the lack of recent activity. |
Three times stale, closing it. @mszostok please reopen if you want to keep it, but make sure to un-stale that every month. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Currently, we have 3 layers for versioning:
From the beginning, an addon was considered as an abstraction layer over a Helm chart which provides all information required to convert the chart into a Service Class. We added the bundle versions which are a new layer and directly not supported in Service Catalog.
The most problematic part is that the version of the addon is not used anywhere from the beginning and it's confusing for our users who need to create and maintain the addons repository.
We need to have a clear vision if we need the bundle version at all. If we cannot find any purpose for this versioning then we should deprecate that and remove it in the next version.
AC:
The text was updated successfully, but these errors were encountered: