Closed varshaprasad96 closed 4 years ago
@jmrodri @estroz @joelanford @dmesser - I have moved the PR (https://github.com/operator-framework/operator-sdk/pull/2834) from Operator SDK to this repo. Please provide your inputs.
Updated the PR with man page for commands.
/lgtm
/approve
Updated the doc based on reviews.
This PR has been updated to a full EP.
/cc @varshaprasad96 @jmrodri
@estroz: GitHub didn't allow me to request PR reviews from the following users: varshaprasad96.
Note that only operator-framework members and repo collaborators can review this PR, and authors cannot review their own PRs.
In https://github.com/operator-framework/operator-sdk/pull/2860 I changed init
behavior so that it scaffolds config/bundle/kustomization.yaml
instead of generate bundle --kustomize
, which I haven't yet added to this EP.
My reasoning for this change: why would you use operator-sdk
if you did not want bundle/packagemanifests features? Just use vanilla kubebuilder
instead. Thoughts on this?
@camilamacedo86 @shawn-hurley @joelanford @hasbro17 I removed the manifests
recipe modification and changed packagemanifests -> package
.
is the convention normally "operator-sdk
@jmccormick2001 when talking about the binary, I try to use operator-sdk
. When talking about the general Operator SDK project I try to use SDK or Operator SDK. Is that the discrepancy you're referring to?
New changes are detected. LGTM label has been removed.
This PR provides documentation explaining the workflows for proposed OLM commands with Operator SDK and a README describing the deployment of operator by following the suggested workflows.