On 10/30/24 14:58, Tim Holloway wrote:
Speaking abstractly, I can see 3 possible approaches.
...
2. You can create a Dockerfile based on the stock mgr but with your
extensions added. The main problem with this is that from what I can
see, the cephadm tool has the names and repositories of the
On Wednesday, October 30, 2024 2:00:56 PM EDT Darrell Enns wrote:
> Is there a simple way to deploy a custom (in-house) mgr module to an
> orchestrator managed cluster? I assume the module code would need to be
> included in the mgr container image. However, there doesn't seem to be a
> straightfor
Speaking abstractly, I can see 3 possible approaches.
1. You can create a separate container and invoke it from the mgr
container as a micro-service. As to how, I don't know. This is likely
the cleanest approach.
2. You can create a Dockerfile based on the stock mgr but with your
extensions added
Build your own Image based on the ceph container Image.
Joachim Kraftmayer
CEO
joachim.kraftma...@clyso.com
www.clyso.com
Hohenzollernstr. 27, 80801 Munich
Utting a. A. | HR: Augsburg | HRB: 25866 | USt. ID-Nr.: DE2754306
Darrell Enns schrieb am Mi., 30. Okt. 2024, 19:01:
> Is there a si
