Commit Graph

5 Commits

Author SHA1 Message Date
Kimonas Sotirchos ca44b1c4ee Manifests for Tensorboard controller (kubeflow/kubeflow#5730)
Signed-off-by: Kimonas Sotirchos <kimwnasptd@arrikto.com>
2021-03-21 14:28:17 -07:00
Rui Fang 7f9c309586 Tesorboard-Controller: use updateStatus instead of update (kubeflow/kubeflow#5644) 2021-03-10 07:46:24 -08:00
Konstantinos Andriopoulos 254c3f7bfc Add roles for Tensorboard controller pod (kubeflow/kubeflow#5262)
* Add Tensorboard controller permissions for managing resources

The pod running the Tensorboard controller didn't have permissions
to manage the deployments, services, and VirtualServices needed
so that the Tensorboard servers would function properly.

In order for the deployed Tensorboard controller to run properly,
permissions to 'get', 'list', 'watch', 'create' and 'update'
are given to the Tensorboard controller pod so that the necessary
deployments, services and VirtualServices are created and managed
as expected. Also, permissions to 'get', 'list', 'watch' PVCs and
pods were added.

* Add namespace of Tensorboard CR to VirtualService prefix

In order to avoid creating 2 virtual services that have the same
prefix in different namespaces, the namespace of the corresponding
Tensorboard CR was added in the prefix of the generated Virtual
Service.

* Fix directory bug in Makefile

* Add README.md
2020-08-30 06:56:20 -07:00
Konstantinos Andriopoulos e32222032c Tensorboard web-app: Add functionality to inform TWA frontend about the status of Tensorboard servers (kubeflow/kubeflow#5259)
* Extend Tensorboard CRD with status.readyReplicas field

The Tensorboard CRD didn't contain any information about the
Tensorboard server being ready or not. So, the status of the
Tensorboard resource is extended so that it contains a
readyReplicas field, similar to the status.readyReplicas of
the deployment of the Tensorboard server.

* Extend Tensorboard controller to update status of Tensorboard CR

The frontend of the Tensorboard web-app will need information
about whether the Tensorboard servers are ready to connect or not.
As a result, the Tensorboard controller now copies the value of the
status.readyReplicas field of the Tensorboard deployment to the
status.readyReplicas of the Tensorboard CR.

Also, a Deployment() function was added for applying and updating
Tensorboard server deployments.

* Update tensorboard.status.phase of TWA backend response

The frontend of the TWA will need information about the status
of the Tensorboard server, so that it can inform the user about
the server being ready being ready to connect or not.

As a result, the backend sets the status.phase field of the response
to "ready", if tensorboard.status.readyReplicas == 1. Otherwise, the
status.phase field of the response is set to "unavailable".

Also, the getPVCName() function was added, which extracts the name
of a given PVC object.

* Add GET route for PVCs

The Tensorboard web-app frontend will be using an autocomplete
drop-bar to show user the PVCs that live in a specific namespace.
These PVCs could be used as log storages for the Tensorboard server.

So, a PVC GET route was added to the Tensorboard web-app backend.

* Add message to Tensorboard response object in TWA backend

The frontend of the TWA will need to output a response message for
every Tensorboard object. This response message will inform the
user about the current state of the Tensorboard server.

* Use status.STATUS_PHASE for backend response

* Add requirements.txt to TWA backend

* Use status.create_status() for backend response
2020-08-30 05:08:20 -07:00
Quanjie Lin 1236c5e6d7 initial checkin of tensorboard controller (kubeflow/kubeflow#4312)
* initial checkin of tensorboard controller

* initial checkin of tensorboard controller

* typo

* typo

* fix typo

* support local path

* add status

* conflict

* remove binary
2019-10-29 09:12:44 -07:00