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
Is your feature request related to a problem? Please describe?
As a developer/operator I should be able to see the status/phases of all vjailbreak APIs when I use kubectl CLI
Detailed Description
Currently the vjailbreak APIs with kubectl apprear without any additional information, you need to go and do -oyaml to see the state of each resource, which is tedious and time consuming.
Example:
$ kubectl get migrationplans,migrations,migrationtemplates,networkmappings,openstackcreds,storagemappings,vmwarecreds -n migration-system
NAME AGE
migrationplan.vjailbreak.k8s.pf9.io/9ae3dda8-4df4-49a2-853a-177a711a3772 2d17h
NAME AGE
migration.vjailbreak.k8s.pf9.io/migration-centos-scale-test-10 2d17h
NAME AGE
migrationtemplate.vjailbreak.k8s.pf9.io/c3605ba8-6894-4f4e-975f-76c9853fd7d7 2d17h
NAME AGE
networkmapping.vjailbreak.k8s.pf9.io/99127ea3-5d4b-4b4c-a76d-60f43f683113 2d17h
NAME AGE
openstackcreds.vjailbreak.k8s.pf9.io/04c8ff52-735e-44aa-a35b-deac0b667338 2d17h
NAME AGE
storagemapping.vjailbreak.k8s.pf9.io/9bfbff8e-2f92-48c1-bb07-763e3a768604 2d17h
NAME AGE
vmwarecreds.vjailbreak.k8s.pf9.io/c190f3d7-ea79-4a23-96bf-c1d368d8e760 2d17h
root@jailer:/home/ubuntu#
It does not provide any additional information
Anything else you would like to add?
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe?
As a developer/operator I should be able to see the status/phases of all vjailbreak APIs when I use kubectl CLI
Detailed Description
Currently the vjailbreak APIs with kubectl apprear without any additional information, you need to go and do
-oyaml
to see the state of each resource, which is tedious and time consuming.Example:
It does not provide any additional information
Anything else you would like to add?
No response
The text was updated successfully, but these errors were encountered: