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
I think perhaps we should adjust the deployer command used in the existing github workflow to determine if we are a AWS based cluster, and if so, deploy the cost attribution dashboard as well after deploying the jupyterhub/grafana-dashboards.
Definition of done
We have automation to deploy the cost attribution dashboard to all AWS clusters
consideRatio
changed the title
AWS cost attribution (3b/n): automate deployment of the grafana dashboard definitions
AWS cost attribution (3c/n): automate deployment of the grafana dashboard definitions
Sep 24, 2024
consideRatio
changed the title
AWS cost attribution (3c/n): automate deployment of the grafana dashboard definitions
AWS cost attribution (2d/n): automate deployment of the grafana dashboard definitions
Sep 25, 2024
consideRatio
changed the title
AWS cost attribution (2d/n): automate deployment of the grafana dashboard definitions
AWS cost attribution (2d/4): automate deployment of the grafana dashboard definitions
Sep 25, 2024
Technical context
We have a github workflow to deploy grafana dashboards already, but what we deploy are the standardized dashboards in jupyterhub/grafana-dashboards.
I think perhaps we should adjust the deployer command used in the existing github workflow to determine if we are a AWS based cluster, and if so, deploy the cost attribution dashboard as well after deploying the jupyterhub/grafana-dashboards.
Definition of done
Especially consider updates to docs written in AWS cost attribution (1/4): write documentation on how to deploy the system to another community #4873 as that was written before automation to deploy dashboards were around.
The text was updated successfully, but these errors were encountered: