This repository has been archived by the owner on Jul 30, 2021. It is now read-only.
Service and ConfigMap specification in ClusterServiceVersion #569
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Comments
|
@sunsingerus I have the same question as well, Have not found any solution. |
|
@houshengbo no, I still do not know correct way how to bundle Services and ConfigMaps. Just had to make ugly workaround to live without pre-shipped configuration |
|
This issue is stale because it has been open for 30 days with no activity. |
openshift-ci-robot
added
lifecycle/stale
|
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there!
Is there a way to bundle Service(s) and ConfigMap(s) into ClusterServiceVersion?
What would be the correct way to distribute operator via operatorhub if it (operator) requires Service(s) and ConfigMap(s) with configuration files and templates? As far as I see ClusterServiceVersion provides specification for
Deploymentonly, is it so?This question is relative to this in operator lifecycle manager
The text was updated successfully, but these errors were encountered: