It could be run as codius deployment in an iframe with requests to it including the web monetization bearer token. The dashboard can be configured to allow access via Authorization header (instead of a login screen). The Kubernetes API server's webhook authentication server (https://github.com/wilsonianb/c8s/issues/52) can accept the token and return a user bound to a role allowing CREATE of codius deployments (within the namespace). The user could also be allowed to READ to allow the dashboard to also display all running codius workloads.
There's a chance this setup would severely overcharge the user, since I imagine the dashboard defaults to making a lot of calls for various metrics to the api server, and each call would result in a payment verification spend by the auth server regardless of whether the returned user is authorized to perform the particular request.
The Kubernetes dashboard allows you to deploy resources via a web ui.
It could be run as codius deployment in an iframe with requests to it including the web monetization bearer token. The dashboard can be configured to allow access via Authorization header (instead of a login screen). The Kubernetes API server's webhook authentication server (https://github.com/wilsonianb/c8s/issues/52) can accept the token and return a user bound to a role allowing CREATE of codius deployments (within the namespace). The user could also be allowed to READ to allow the dashboard to also display all running codius workloads.
There's a chance this setup would severely overcharge the user, since I imagine the dashboard defaults to making a lot of calls for various metrics to the api server, and each call would result in a payment verification spend by the auth server regardless of whether the returned user is authorized to perform the particular request.
This would replace https://github.com/wilsonianb/c8s/issues/54 and https://github.com/wilsonianb/c8s/issues/4