-
Notifications
You must be signed in to change notification settings - Fork 552
Support ConsoleYamlSample in bundle manifests #1615
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
Comments
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. |
@exdx Thanks. I've actually submitted a PR that's currently sitting waiting. What are the next steps to get that merged? |
Looks like @ecordell approved it so I went ahead and gave it an |
@Jamstah note: your PR adds support for See https://github.com/exdx/operator-registry/blob/master/pkg/lib/bundle/supported_resources.go for the file that should be updated |
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:
|
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. |
operator-framework/operator-lifecycle-manager#1615 (upstream operator-registry commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977)
operator-framework/operator-lifecycle-manager#1615 Upstream-repository: operator-registry Upstream-commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977
operator-framework/operator-lifecycle-manager#1615 Upstream-repository: operator-registry Upstream-commit: 2c2dec85b09ae30ddfbdfb81b69b84e82796d977
Feature Request
Is your feature request related to a problem? Please describe.
I would like to add
ConsoleYamlSample
s to my operator, but at the moment, I have to run an init hook in my operator pod to install them into the clusterDescribe the solution you'd like
Be able to drop
ConsoleYamlSample
s into the bundlemanifests
directory and have them applied to the cluster.I did try this, and get
UnsupportedResource
on the InstallPlanThe text was updated successfully, but these errors were encountered: