Skip to content
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.

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

Support ConsoleYamlSample in bundle manifests #1615

Closed
Jamstah opened this issue Jun 30, 2020 · 6 comments · Fixed by #1616
Closed

Support ConsoleYamlSample in bundle manifests #1615

Jamstah opened this issue Jun 30, 2020 · 6 comments · Fixed by #1616
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@Jamstah
Copy link
Contributor

Jamstah commented Jun 30, 2020

Feature Request

Is your feature request related to a problem? Please describe.
I would like to add ConsoleYamlSamples to my operator, but at the moment, I have to run an init hook in my operator pod to install them into the cluster

Describe the solution you'd like
Be able to drop ConsoleYamlSamples into the bundle manifests directory and have them applied to the cluster.

I did try this, and get UnsupportedResource on the InstallPlan

    - resolving: ibm-integration-platform-navigator.v4.0.1
      resource:
        group: console.openshift.io
        kind: ConsoleYAMLSample
        manifest: >
          {"apiVersion":"console.openshift.io/v1","kind":"ConsoleYAMLSample","metadata":{"name":"pn-sample-1"},"spec":{"description":"PN
          Sample","snippet":false,"targetResource":{"apiVersion":"integration.ibm.com/v1beta1","kind":"PlatformNavigator"},"title":"Sample
          1","yaml":"---\napiVersion: integration.ibm.com/v1beta1\nkind:
          PlatformNavigator\nmetadata:\n    name: cp4i-navigator\n    namespace:
          cp4i\nspec:\n    license:\n        accept: true\n    mqDashboard:
          true\n    replicas: 3\n    version: 2020.2.1\n"}}
        name: pn-sample-1
        sourceName: pn
        sourceNamespace: openshift-marketplace
        version: v1
      status: UnsupportedResource
@exdx exdx added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 27, 2020
@exdx
Copy link
Member

exdx commented Aug 27, 2020

We are adding supporting to additional objects to the operator bundle and potentially expanding the scope to all arbitrary kube objects at some point in the future. I think this is a valid feature request and we can hopefully accommodate it in a future release of OLM.

@Jamstah
Copy link
Contributor Author

Jamstah commented Aug 27, 2020

@exdx Thanks. I've actually submitted a PR that's currently sitting waiting. What are the next steps to get that merged?

@exdx
Copy link
Member

exdx commented Aug 27, 2020

Looks like @ecordell approved it so I went ahead and gave it an lgtm so its pretty much good to go. We are currently in feature freeze, so master isn't open, but your PR will merge when master opens back up in several weeks.

@exdx
Copy link
Member

exdx commented Aug 31, 2020

@Jamstah note: your PR adds support for ConsoleYamlSample types in OLM, but we would also need to support adding this type to operator bundles, otherwise a bundle with a ConsoleYamlSample would fail validation by opm.

See https://github.com/exdx/operator-registry/blob/master/pkg/lib/bundle/supported_resources.go for the file that should be updated

@Jamstah
Copy link
Contributor Author

Jamstah commented Sep 3, 2020

Thanks for spotting that, I had seen it before and thought it was sensible to add it here first, then into opm, so that we don't end up with packages that have unsupported resources. I had since forgotten about it though :)

Have opened that PR too now:

@stale
Copy link

stale bot commented Nov 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Nov 2, 2020
@openshift-ci-robot openshift-ci-robot added the triage/unresolved Indicates an issue that can not or will not be resolved. label Nov 3, 2020
@stale stale bot removed the wontfix label Nov 3, 2020
ankitathomas pushed a commit to ankitathomas/operator-framework-olm that referenced this issue Apr 6, 2021
operator-framework/operator-lifecycle-manager#1615
(upstream operator-registry commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977)
benluddy pushed a commit to benluddy/operator-framework-olm that referenced this issue Jul 1, 2021
operator-framework/operator-lifecycle-manager#1615

Upstream-repository: operator-registry
Upstream-commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977
openshift-merge-robot pushed a commit to openshift/operator-framework-olm that referenced this issue Jul 14, 2021
operator-framework/operator-lifecycle-manager#1615

Upstream-repository: operator-registry
Upstream-commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants