Skip to content

Clarify use case of operator-sdk run bundle(-upgrade) in documentation #6610

@everettraven

Description

@everettraven

Recently, in various communication channels, there have been questions around using the operator-sdk run bundle(-upgrade) command for non-testing purposes. I think this has to do with some pretty strong suggestions in our documentation that operator-sdk run bundle(-upgrade) is useful for deploying operators with OLM but lacking the caveat that this if for local dev / testing purposes only and should not be used for deploying operators in production. We do call this out in https://sdk.operatorframework.io/docs/olm-integration/testing-deployment/#caveats but I have a feeling this is being overlooked and should revise our docs to better reflect this caveat everywhere operator-sdk run bundle(-upgrade) is referenced / suggested.

Metadata

Metadata

Labels

good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions