jarrpa
commented
3 years ago Sorry I'm just getting around to this, but please open a Jira issue instead. GitHub issues are not very well tracked.
Open mmgaggle opened 3 years ago
jarrpa
commented
3 years ago Sorry I'm just getting around to this, but please open a Jira issue instead. GitHub issues are not very well tracked.
openshift-bot
commented
3 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
mmgaggle
commented
3 years ago /remove-lifecycle stale
On Tue, Apr 13, 2021 at 11:58 OpenShift Bot @.***> wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openshift/ocs-operator/issues/960#issuecomment-818979407, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFKIG5YGYDC4S7ARKKJFOLTISH4BANCNFSM4U5BCBHQ .
openshift-bot
commented
3 years ago Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
openshift-bot
commented
3 years ago Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
In the spirit of embracing alternative outcomes for the OCS experience, we discussed providing a means to disable or ignore the platform detection logic that currently prevents CephObjectStore deployments in the public cloud. The reconcileStrategy functionality that was introduced to lend more control over which OCS components are deployed, seems like a natural way to do this, even if we decide we should continue to not install a CephObjectStore by default.
The intent of course is not that this be some hidden flag for folks at Red Hat to use, but rather a choice that customers can make and that the result would be a fully supported configuration.