Hi! Could you please transfer the owner of velero-integrator to Kubeflow Charmers? Thanks.
Hi Dario,
LP teams are being deprecated. We are encouraging adding collaborators and / or creating a store account linked to your team. You should be able to manage package collaborators yourself once you make a release for this charm. If you make a store account linked to your team and want us to transfer ownership to that account we can. Please reach out if you have any questions.
Hi @colin-c
We have created a store account connected to the KF team. The store account is called Charmed Kubeflow with username ckfbot .
I see that the migration and deprecation of LP teams has not been rolled out yet, so I have also added this account to the list of store accounts for the Kubeflow Charms LP group. But while we are at it, we could probably also transfer the ownership of various charms currently belonging to “Kubeflow Charmers” (LP group) to this account. Here is the list I would like to transition:
``` kfp-ui
istio-pilot
kfp-persistence
metacontroller-operator
kfp-api
training-operator
istio-gateway
jupyter-ui
tfjob-operator
kfp-schedwf
kfp-viz
tensorboards-web-app
tensorboard-controller
kfp-profile-controller
argo-server
kubeflow-roles
dex-auth
jupyter-controller
kfp-viewer
argo-ui
kubeflow-trainer
metadata-api
github-profiles-automator
metadata-ui
seldon-controller-manager
metadata-grpc
pipelines-scheduledworkflow
katib-controller
kfserving
mlmd
mlflow-server
kubeflow-profiles
kserve-web-app
katib-db-manager
kubeflow-volumes
katib-ui
minio
pipelines-api
pipelines-visualization
oidc-gatekeeper
kserve-controller
kubeflow-dashboard
metadata-envoy
pipelines-persistence
katib-manager
envoy
seldon-core
knative-eventing
pipelines-viewer
knative-operator
argo-controller
feast-integrator
pvcviewer-operator
feast-ui
pipelines-ui
kfp-metadata-writer
metacontroller
knative-serving
velero-operator
ngc-integrator
jupyter-web
resource-dispatcher
tf-job-operator
namespace-node-affinity
admission-webhook
mlflow
kubeflow
kubeflow-pipelines ```
1 Like
Note that the ownership transfer to this new account would mean that all existing collaborators will lose access to all of these packages (unless the kubeflow team already took care of adding each collaborator needed to each package).
You will need to check the list of store usernames under the kubeflow-charmers team in the teams deprecation form (from the announcement) and add all of them as collaborators to each one of the packages @deusebio mentioned when you’re doing the ownership transfer.
No, no, we haven’t as we were assuming that this would have been done as part of the migration out of LP teams. So, yes, we would need to transfer the ownership AND also add the store accounts as collaborators, otherwise the single developers would indeed loose access
1 Like