Change Details

The paws-public tool is running these objects on the legacy kubernetes cluster: ``` $ /usr/local/bin/kubectl get deployment,rs,po,svc NAME READY STATUS RESTARTS AGE po/nbserve-t5pht 1/1 Running 2 129d po/renderer-h8f9t 1/1 Running 2 142d NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/paws-public 192.168.0.168 <none> 8000/TCP 3y svc/renderer 192.168.0.125 <none> 8000/TCP 3y ``` The tool's $HOME has no documentation or YAML files to repeat creation of these objects on the 2020 Kubernetes cluster. We need to figure out how to migrate them.

The paws-public tool is running these objects on the legacy kubernetes cluster: ``` $ /usr/local/bin/kubectl get deployment,rs,po,svc NAME READY STATUS RESTARTS AGE po/nbserve-t5pht 1/1 Running 2 129d po/renderer-h8f9t 1/1 Running 2 142d NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/paws-public 192.168.0.168 <none> 8000/TCP 3y svc/renderer 192.168.0.125 <none> 8000/TCP 3y ``` The tool's $HOME has no documentation or YAML files to repeat creation of these objects on the 2020 Kubernetes cluster. We need to figure out how to migrate them. NOTE: Interacting with the legacy Kubernetes cluster needs an older version of kubectl. Use `/data/project/paws-public/bin/kubectl`.

The paws-public tool is running these objects on the legacy kubernetes cluster: ``` $ /usr/local/bin/kubectl get deployment,rs,po,svc NAME READY STATUS RESTARTS AGE po/nbserve-t5pht 1/1 Running 2 129d po/renderer-h8f9t 1/1 Running 2 142d NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/paws-public 192.168.0.168 <none> 8000/TCP 3y svc/renderer 192.168.0.125 <none> 8000/TCP 3y ``` The tool's $HOME has no documentation or YAML files to repeat creation of these objects on the 2020 Kubernetes cluster. We need to figure out how to migrate them. NOTE: Interacting with the legacy Kubernetes cluster needs an older version of kubectl. Use `/data/project/paws-public/bin/kubectl`.