Open ssolerg opened 7 months ago
Hey @ssolerg do you think this is necessary?
Hi guy.
Yes, I do. I think is really necessary because using a custom namespace for the operator, yo can reduce errors as accidentally deletion or any other actions that could affect the operator deployment.
Using a custom namespace, you can segregate the operator resources.
I have deployed my typesense instances with both PR applied.
Regards
On Fri, Dec 8, 2023, 11:30 AM Sai Prasanth R @.***> wrote:
Hey @ssolerg https://github.com/ssolerg do you think this is necessary?
— Reply to this email directly, view it on GitHub https://github.com/sai3010/Typesense-Kubernetes-Operator/pull/6#issuecomment-1847484872, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2WR74XYKTSHL4YXNZM3SN3YIM6BDAVCNFSM6AAAAAA7FEYKMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGQ4DIOBXGI . You are receiving this because you were mentioned.Message ID: @.***>
All operator resources were moved from default namespace to typesense-operator namespace.