From 9ce54e2b4a251ec69da8a5742bd6f016d560d8b7 Mon Sep 17 00:00:00 2001 From: Quarto GHA Workflow Runner Date: Fri, 25 Oct 2024 23:58:09 +0000 Subject: [PATCH] Built site for gh-pages --- .nojekyll | 2 +- admins/cicd-github-actions.html | 6 +- admins/index.html | 12 +-- hubs.html | 18 ++--- incidents/index.html | 38 +++++----- search.json | 2 +- sitemap.xml | 130 ++++++++++++++++---------------- 7 files changed, 104 insertions(+), 104 deletions(-) diff --git a/.nojekyll b/.nojekyll index 18a94bf94..6fbbcde61 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -3187b28e \ No newline at end of file +b254c817 \ No newline at end of file diff --git a/admins/cicd-github-actions.html b/admins/cicd-github-actions.html index f327aaa69..547b5fbec 100644 --- a/admins/cicd-github-actions.html +++ b/admins/cicd-github-actions.html @@ -527,7 +527,7 @@

Singl stateDiagram-v2 image_repo: github.com/berkeley-dsep-infra/hubname-user-image - forked_repo: github.com/github username/hubname-user-image + user_repo: github.com/username/hubname-user-image image_test_build: Image is built and tested image_push_build: Image is built and pushed to registry pr_created: A pull request is automatically<br/>created in the Datahub repo @@ -535,8 +535,8 @@

Singl contributor_tests: The contributor logs into the<br/>staging hub and tests the image. deploy_to_prod: Hub is deployed to prod - image_repo --> forked_repo: Contributor forks the image repo. - forked_repo --> image_repo: Contributor creates a PR. + image_repo --> user_repo: Contributor forks the image repo. + user_repo --> image_repo: Contributor creates a PR. image_repo --> image_test_build image_test_build --> image_push_build: Test build passes and Datahub staff merge pull request image_push_build --> pr_created diff --git a/admins/index.html b/admins/index.html index 5d2bdec89..f42b9b3e9 100644 --- a/admins/index.html +++ b/admins/index.html @@ -447,7 +447,7 @@

Architecture and Contribution Overview

-
+

 
@@ -469,7 +469,7 @@

-
+

 
@@ -491,7 +491,7 @@

-
+

 
@@ -513,7 +513,7 @@

-
+

 
@@ -535,7 +535,7 @@

-
+

 
@@ -557,7 +557,7 @@

-
+

 
diff --git a/hubs.html b/hubs.html index e1ee47920..975d1a318 100644 --- a/hubs.html +++ b/hubs.html @@ -449,7 +449,7 @@

JupyterHub Deployments

-
+

 
@@ -485,7 +485,7 @@

-
+

 
@@ -521,7 +521,7 @@

-
+

 
@@ -551,7 +551,7 @@

-
+

 
@@ -584,7 +584,7 @@

-
+

 
@@ -617,7 +617,7 @@

-
+

 
@@ -653,7 +653,7 @@

-
+

 
@@ -686,7 +686,7 @@

-
+

 
@@ -725,7 +725,7 @@

-
+

 
diff --git a/incidents/index.html b/incidents/index.html index 3ec394859..ac14e83f7 100644 --- a/incidents/index.html +++ b/incidents/index.html @@ -481,7 +481,7 @@

Incident Reports

- + Feb 9, 2017 @@ -489,7 +489,7 @@

Incident Reports

JupyterHub db manual overwrite - + Feb 24, 2017 @@ -497,7 +497,7 @@

Incident Reports

Custom Autoscaler gonee haywire - + Feb 24, 2017 @@ -505,7 +505,7 @@

Incident Reports

Proxy eviction strands user - + Mar 6, 2017 @@ -513,7 +513,7 @@

Incident Reports

Non-matching hub image tags cause downtime - + Mar 20, 2017 @@ -521,7 +521,7 @@

Incident Reports

Too many volumes per disk leave students stuck - + Mar 23, 2017 @@ -529,7 +529,7 @@

Incident Reports

Weird upstream ipython bug kills kernels - + Apr 3, 2017 @@ -537,7 +537,7 @@

Incident Reports

Custom autoscaler does not scale up when it should - + May 9, 2017 @@ -545,7 +545,7 @@

Incident Reports

Oops we forgot to pay the bill - + Oct 10, 2017 @@ -553,7 +553,7 @@

Incident Reports

Docker dies on a few Azure nodes - + Oct 19, 2017 @@ -561,7 +561,7 @@

Incident Reports

Billing confusion with Azure portal causes summer hub to be lost - + Jan 25, 2018 @@ -569,7 +569,7 @@

Incident Reports

Accidental merge to prod brings things down - + Jan 26, 2018 @@ -577,7 +577,7 @@

Incident Reports

Hub starts up very slow, causing outage for users - + Feb 6, 2018 @@ -585,7 +585,7 @@

Incident Reports

Azure PD refuses to detach, causing downtime for data100 - + Feb 28, 2018 @@ -593,7 +593,7 @@

Incident Reports

A node hangs, causing a subset of users to report issues - + Jun 11, 2018 @@ -601,7 +601,7 @@

Incident Reports

Azure billing issue causes downtime - + Feb 25, 2019 @@ -609,7 +609,7 @@

Incident Reports

Azure Kubernetes API Server outage causes downtime - + May 1, 2019 @@ -617,7 +617,7 @@

Incident Reports

Service Account key leak incident - + Jan 20, 2022 @@ -625,7 +625,7 @@

Incident Reports

Hubs throwing 505 errors - + Feb 1, 2024 diff --git a/search.json b/search.json index 65e933253..395e5005e 100644 --- a/search.json +++ b/search.json @@ -2081,7 +2081,7 @@ "href": "admins/cicd-github-actions.html#github-actions-architecture", "title": "Continuous Integration and Deployment", "section": "Github Actions Architecture", - "text": "Github Actions Architecture\n\nSecrets and Variables\nAll of these workflows depend on a few Actions secrets and variables, with some at the organization level, and others at the repository level.\n\nOrganization secrets and variables\nGitHub Actions settings contain all of the organizational secrets and variables.\n\nOrganization Secrets\n\nDATAHUB_CREATE_PR\n\nThis secret is a fine-grained personal access token, and has the following permissions defined:\n\n\n\nSelect repositories (only berkeley-dsep-infra/datahub)\nRepository permissions: Contents (read/write), Metadata (read only), Pull requests (read/write)\n\nWhen adding a new image repository in the berkeley-dsep-infra org, you must edit this secret and manually add this repository to the access list.\n\n\n\n\n\n\nImportant\n\n\n\nThis PAT has an lifetime of 366 days, and should be rotated at the beginning of every maintenance window.\n\n\n\nGAR_SECRET_KEY and GAR_SECRET_KEY_EDX\n\nThese secrets are for the GCP IAM roles for each GCP project given roles/storage.admin permissions. This allows us to push the built images to the Artifact Registry.\n\n\nWhen adding a new image repository in the berkeley-dsep-infra org, you must edit this secret and manually add this repository to the access list.\n\n\nOrganization Variables\n\nIMAGE_BUILDER_BOT_EMAIL and IMAGE_BUILDER_BOT_NAME\n\nThese are used to set the git identity in the image build workflow step that pushes a commit and creates a PR in the datahub repo.\n\n\n\nDataHub repository secrets\n\nGCP_PROJECT_ID\n\nThis is the name of our GCP project.\n\nGKE_KEY\n\nThis key is used in the workflows that deploy the support and node-placeholder namespaces. It’s attached to the hubploy service account, and has the assigned roles of roles/container.clusterViewer and roles/container.developer.\n\nSOPS_KEY\n\nThis key is used to decrypt our secrets using sops, and is attached to the sopsaccount service account and provides KMS access.\n\n\n\n\n\nUser Image Repository Variables\nEach image repository contains two variables, which are used to identify the name of the hub, and the path within the Artifact Registry that it’s published to.\n\nHUB\n\nThe name of the hub, natch! datahub, data100, etc.\n\nIMAGE\n\nThe path within the artifact registry: ucb-datahub-2018/user-images/<hubname>-user-image\n\n\n\n\n\n\nSingle user server image modification workflow\nEach hub’s user image is located in the berkeley-dsep-infra’s organization. When a pull request is submitted, there are two workflows that run:\n\nYAML lint\nBuild and test the image\n\nWhen both tests pass, and the pull request is merged in to the main branch, a third and final workflow is run:\n\nBuild push and create PR\n\nThis builds the image again, and when successful pushes it to our Google Artifact Registry and creates a pull request in the datahub repository with the updated image tag for that hub’s deployment.\n\n\nUpdating the datahub repository\n\nSingle user server image tag updates\nWhen a pull request is opened to update one or more image tags for deployments, the labeler will apply the hub: <hubname> label upon creation. When this pull request is merged, the deploy-hubs workflow is triggered.\nThis workflow will then grab the labels from the merged pull request, see if any hubs need to be deployed and if so, execute a python script that checks the environment variables within that workflow for hubs, and emits a list of what’s to be deployed.\nThat list is iterated over, and hubploy is used to deploy only the flagged hubs.\n\n\n\n\n\n%% State diagram documentation at\n%% https://mermaid.js.org/syntax/stateDiagram.html\n\nstateDiagram-v2\n image_repo: github.com/berkeley-dsep-infra/hubname-user-image\n forked_repo: github.com/github username/hubname-user-image\n image_test_build: Image is built and tested\n image_push_build: Image is built and pushed to registry\n pr_created: A pull request is automatically<br/>created in the Datahub repo\n deploy_to_staging: Hub is deployed to staging\n contributor_tests: The contributor logs into the<br/>staging hub and tests the image.\n deploy_to_prod: Hub is deployed to prod\n\n image_repo --> forked_repo: Contributor forks the image repo.\n forked_repo --> image_repo: Contributor creates a PR.\n image_repo --> image_test_build\n image_test_build --> image_push_build: Test build passes and Datahub staff merge pull request\n image_push_build --> pr_created\n pr_created --> deploy_to_staging: Datahub staff review and merge to staging\n deploy_to_staging --> contributor_tests\n contributor_tests --> deploy_to_prod: Datahub staff create a PR to merge to prod\n\n\n\n\n\n\n\n\nSupport and node-placeholder charts\nEach of these deployments has their own workflow, which only runs on pushes to staging:\n\ndeploy-support.yaml\ndeploy-node-placeholder.yaml\n\nIf the correct labels are found, it will use the GKE_KEY secret to run helm upgrade for the necessary deployments.\n\n\nMiscellaneous workflows\nThere are also a couple of other workflows in the datahub repository:\n\nprevent-prod-merges.yml\n\nThis workflow will only allow us to merge to prod from staging.\n\nquarto-docs.yml\n\nThis builds, renders and pushes our docs to Github Pages.\n\n\n\n\n\nDocumentation’s Workflow\nThis documentation is also deployed by GitHub Actions.", + "text": "Github Actions Architecture\n\nSecrets and Variables\nAll of these workflows depend on a few Actions secrets and variables, with some at the organization level, and others at the repository level.\n\nOrganization secrets and variables\nGitHub Actions settings contain all of the organizational secrets and variables.\n\nOrganization Secrets\n\nDATAHUB_CREATE_PR\n\nThis secret is a fine-grained personal access token, and has the following permissions defined:\n\n\n\nSelect repositories (only berkeley-dsep-infra/datahub)\nRepository permissions: Contents (read/write), Metadata (read only), Pull requests (read/write)\n\nWhen adding a new image repository in the berkeley-dsep-infra org, you must edit this secret and manually add this repository to the access list.\n\n\n\n\n\n\nImportant\n\n\n\nThis PAT has an lifetime of 366 days, and should be rotated at the beginning of every maintenance window.\n\n\n\nGAR_SECRET_KEY and GAR_SECRET_KEY_EDX\n\nThese secrets are for the GCP IAM roles for each GCP project given roles/storage.admin permissions. This allows us to push the built images to the Artifact Registry.\n\n\nWhen adding a new image repository in the berkeley-dsep-infra org, you must edit this secret and manually add this repository to the access list.\n\n\nOrganization Variables\n\nIMAGE_BUILDER_BOT_EMAIL and IMAGE_BUILDER_BOT_NAME\n\nThese are used to set the git identity in the image build workflow step that pushes a commit and creates a PR in the datahub repo.\n\n\n\nDataHub repository secrets\n\nGCP_PROJECT_ID\n\nThis is the name of our GCP project.\n\nGKE_KEY\n\nThis key is used in the workflows that deploy the support and node-placeholder namespaces. It’s attached to the hubploy service account, and has the assigned roles of roles/container.clusterViewer and roles/container.developer.\n\nSOPS_KEY\n\nThis key is used to decrypt our secrets using sops, and is attached to the sopsaccount service account and provides KMS access.\n\n\n\n\n\nUser Image Repository Variables\nEach image repository contains two variables, which are used to identify the name of the hub, and the path within the Artifact Registry that it’s published to.\n\nHUB\n\nThe name of the hub, natch! datahub, data100, etc.\n\nIMAGE\n\nThe path within the artifact registry: ucb-datahub-2018/user-images/<hubname>-user-image\n\n\n\n\n\n\nSingle user server image modification workflow\nEach hub’s user image is located in the berkeley-dsep-infra’s organization. When a pull request is submitted, there are two workflows that run:\n\nYAML lint\nBuild and test the image\n\nWhen both tests pass, and the pull request is merged in to the main branch, a third and final workflow is run:\n\nBuild push and create PR\n\nThis builds the image again, and when successful pushes it to our Google Artifact Registry and creates a pull request in the datahub repository with the updated image tag for that hub’s deployment.\n\n\nUpdating the datahub repository\n\nSingle user server image tag updates\nWhen a pull request is opened to update one or more image tags for deployments, the labeler will apply the hub: <hubname> label upon creation. When this pull request is merged, the deploy-hubs workflow is triggered.\nThis workflow will then grab the labels from the merged pull request, see if any hubs need to be deployed and if so, execute a python script that checks the environment variables within that workflow for hubs, and emits a list of what’s to be deployed.\nThat list is iterated over, and hubploy is used to deploy only the flagged hubs.\n\n\n\n\n\n%% State diagram documentation at\n%% https://mermaid.js.org/syntax/stateDiagram.html\n\nstateDiagram-v2\n image_repo: github.com/berkeley-dsep-infra/hubname-user-image\n user_repo: github.com/username/hubname-user-image\n image_test_build: Image is built and tested\n image_push_build: Image is built and pushed to registry\n pr_created: A pull request is automatically<br/>created in the Datahub repo\n deploy_to_staging: Hub is deployed to staging\n contributor_tests: The contributor logs into the<br/>staging hub and tests the image.\n deploy_to_prod: Hub is deployed to prod\n\n image_repo --> user_repo: Contributor forks the image repo.\n user_repo --> image_repo: Contributor creates a PR.\n image_repo --> image_test_build\n image_test_build --> image_push_build: Test build passes and Datahub staff merge pull request\n image_push_build --> pr_created\n pr_created --> deploy_to_staging: Datahub staff review and merge to staging\n deploy_to_staging --> contributor_tests\n contributor_tests --> deploy_to_prod: Datahub staff create a PR to merge to prod\n\n\n\n\n\n\n\n\nSupport and node-placeholder charts\nEach of these deployments has their own workflow, which only runs on pushes to staging:\n\ndeploy-support.yaml\ndeploy-node-placeholder.yaml\n\nIf the correct labels are found, it will use the GKE_KEY secret to run helm upgrade for the necessary deployments.\n\n\nMiscellaneous workflows\nThere are also a couple of other workflows in the datahub repository:\n\nprevent-prod-merges.yml\n\nThis workflow will only allow us to merge to prod from staging.\n\nquarto-docs.yml\n\nThis builds, renders and pushes our docs to Github Pages.\n\n\n\n\n\nDocumentation’s Workflow\nThis documentation is also deployed by GitHub Actions.", "crumbs": [ "Architecture and contributing", "Architecture and Contribution Overview", diff --git a/sitemap.xml b/sitemap.xml index 7d5a62ad6..a71c4153b 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,262 +2,262 @@ https://docs.datahub.berkeley.edu/admins/cluster-config.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/index.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/credentials.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/storage.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/storage-retention.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/policy_create_hubs.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/policy_deploy_mainhubs.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-04-03-cluster-full-incident.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2019-05-01-service-account-leak.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2018-01-25-helm-chart-upgrade.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2018-01-26-hub-slow-startup.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-03-23-kernel-deaths-incident.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-02-09-datahub-db-outage.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2024-core-node-incidents.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2018-06-11-course-subscription-canceled.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-10-19-course-subscription-canceled.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-02-09-datahub-db-outage-pvc-recreate-script.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/prometheus-grafana.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/index.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/documentation.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/remove-users-orm.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/dns.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/google-sheets.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/new-packages.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/rebuild-hub-image.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/new-image.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/course-config.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/datahub.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/stat159.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/edx.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/stat20.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/data102.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/data100.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/r.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/prob140.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/hubs/shiny.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/new-hub.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/managing-multiple-user-image-repos.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/core-pool.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/delete-hub.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/calendar-scaler.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/rebuild-postgres-image.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/clusterswitch.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/cheatsheet.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/github-token.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/tasks/transition-image.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2019-02-25-k8s-api-server-down.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2022-01-20-package-dependency-upgrade-incident.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-05-09-gce-billing.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2018-02-06-hub-db-dir.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2018-02-28-hung-node.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-02-24-autoscaler-incident.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-10-10-hung-nodes.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-03-20-too-many-volumes.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/index.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-03-06-helm-config-image-mismatch.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/incidents/2017-02-24-proxy-death-incident.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/index.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/principles.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/index.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/policy/create_policy.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/cicd-github-actions.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/pre-reqs.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z https://docs.datahub.berkeley.edu/admins/structure.html - 2024-10-25T23:38:28.207Z + 2024-10-25T23:57:28.578Z