You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we fork it in opendevstack organization as a new repository we could use it for maintenance tasks in ODS projects and also in ODS central namespace, specially for PVC data migrations, and could be used in dockerplain quickstarters for maintenance tasks in ODS projects. this wouldn't take so much time to implement.
Why fork instead of using an image tag provided by https://hub.docker.com/r/jorgeandrada/ocp-utils? I think you can just launch a pod with this image ... (provided the cluster policies / regulations allow it)
I think this docker image is interesting because it can be used for data migrations and it can provide a lot of utilites that could be very helpful in a lot of situations (oc, kubectl, rsync, etc)
I mean this image could be used from any Dockerfile using the command: "FROM" (but it also can be used the original image jorgeandrada/ocp-utils)
@michaelsauter
Well, thats true, we can use the image directly in a pod .yaml and it would work with no problems.
But having enterprise/organization contexts, if this image is cloned inside opendevstack organization I think
this would add more trust to every company that would use that image specially companies that have internal validation processes.
Hi
I think this Docker image is really interesting and could be very usefull for namespace maintenance task:
https://github.com/jandradap/ocp-utils
If we fork it in opendevstack organization as a new repository we could use it for maintenance tasks in ODS projects and also in ODS central namespace, specially for PVC data migrations, and could be used in dockerplain quickstarters for maintenance tasks in ODS projects. this wouldn't take so much time to implement.
Then, what I suggest exactly is the following:
The text was updated successfully, but these errors were encountered: