diff --git a/src/current/_includes/v23.1/essential-metrics.md b/src/current/_includes/v23.1/essential-metrics.md
index 83bbc469c57..7a05c06e1dc 100644
--- a/src/current/_includes/v23.1/essential-metrics.md
+++ b/src/current/_includes/v23.1/essential-metrics.md
@@ -181,4 +181,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Events to alert on]({% link {{ page.version.version }}/monitoring-and-alerting.md %}#events-to-alert-on)
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
\ No newline at end of file
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
\ No newline at end of file
diff --git a/src/current/_includes/v23.2/essential-metrics.md b/src/current/_includes/v23.2/essential-metrics.md
index 83bbc469c57..7a05c06e1dc 100644
--- a/src/current/_includes/v23.2/essential-metrics.md
+++ b/src/current/_includes/v23.2/essential-metrics.md
@@ -181,4 +181,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Events to alert on]({% link {{ page.version.version }}/monitoring-and-alerting.md %}#events-to-alert-on)
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
\ No newline at end of file
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
\ No newline at end of file
diff --git a/src/current/_includes/v24.1/essential-metrics.md b/src/current/_includes/v24.1/essential-metrics.md
index 5f5754d17a9..011f8c8d37e 100644
--- a/src/current/_includes/v24.1/essential-metrics.md
+++ b/src/current/_includes/v24.1/essential-metrics.md
@@ -201,4 +201,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Essential Alerts]({% link {{ page.version.version }}/essential-alerts-{{ include.deployment}}.md %})
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
diff --git a/src/current/_includes/v24.2/essential-metrics.md b/src/current/_includes/v24.2/essential-metrics.md
index 0c1cc00a2d9..95a4f7a38a2 100644
--- a/src/current/_includes/v24.2/essential-metrics.md
+++ b/src/current/_includes/v24.2/essential-metrics.md
@@ -194,4 +194,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Essential Alerts]({% link {{ page.version.version }}/essential-alerts-{{ include.deployment}}.md %})
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
diff --git a/src/current/_includes/v24.3/essential-metrics.md b/src/current/_includes/v24.3/essential-metrics.md
index 1b0aac55a0b..630f403573a 100644
--- a/src/current/_includes/v24.3/essential-metrics.md
+++ b/src/current/_includes/v24.3/essential-metrics.md
@@ -201,4 +201,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Essential Alerts]({% link {{ page.version.version }}/essential-alerts-{{ include.deployment}}.md %})
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
diff --git a/src/current/_includes/v25.1/essential-metrics.md b/src/current/_includes/v25.1/essential-metrics.md
index d3acb380d44..58f88d9ca87 100644
--- a/src/current/_includes/v25.1/essential-metrics.md
+++ b/src/current/_includes/v25.1/essential-metrics.md
@@ -201,4 +201,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Essential Alerts]({% link {{ page.version.version }}/essential-alerts-{{ include.deployment}}.md %})
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
diff --git a/src/current/_includes/v25.2/essential-metrics.md b/src/current/_includes/v25.2/essential-metrics.md
index 7c958db3f50..4ffccd96275 100644
--- a/src/current/_includes/v25.2/essential-metrics.md
+++ b/src/current/_includes/v25.2/essential-metrics.md
@@ -201,4 +201,4 @@ If [Row-Level TTL]({% link {{ page.version.version }}/row-level-ttl.md %}) is co
- [Custom Chart Debug Page]({% link {{ page.version.version }}/ui-custom-chart-debug-page.md %})
- [Cluster API]({% link {{ page.version.version }}/cluster-api.md %})
- [Essential Alerts]({% link {{ page.version.version }}/essential-alerts-{{ include.deployment}}.md %})
-- [CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)](https://github.com/cockroachdb/cockroach/tree/master/pkg/ui/workspaces/db-console/src/views/cluster/containers/nodeGraphs/dashboards)
+- CockroachDB Source Code - DB Console metrics to graphs mappings (in *.tsx files)
diff --git a/src/current/v23.1/admission-control.md b/src/current/v23.1/admission-control.md
index f7c36afea13..c80b3f91157 100644
--- a/src/current/v23.1/admission-control.md
+++ b/src/current/v23.1/admission-control.md
@@ -97,6 +97,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
-The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+The [technical note for admission control](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
{% include {{page.version.version}}/sql/server-side-connection-limit.md %} This may be useful in addition to your admission control settings.
diff --git a/src/current/v23.1/architecture/sql-layer.md b/src/current/v23.1/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v23.1/architecture/sql-layer.md
+++ b/src/current/v23.1/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v23.1/fips.md b/src/current/v23.1/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v23.1/fips.md
+++ b/src/current/v23.1/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v23.1/kubernetes-performance.md b/src/current/v23.1/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v23.1/kubernetes-performance.md
+++ b/src/current/v23.1/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v23.1/migrate-from-avro.md b/src/current/v23.1/migrate-from-avro.md
index 0ff5cc230bc..82e6e8cd09f 100644
--- a/src/current/v23.1/migrate-from-avro.md
+++ b/src/current/v23.1/migrate-from-avro.md
@@ -163,7 +163,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/ccl/importccl/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v23.1/monitoring-and-alerting.md b/src/current/v23.1/monitoring-and-alerting.md
index 43f2ae9b4a7..908e7048b65 100644
--- a/src/current/v23.1/monitoring-and-alerting.md
+++ b/src/current/v23.1/monitoring-and-alerting.md
@@ -969,7 +969,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -978,7 +978,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -986,7 +986,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -994,7 +994,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1010,7 +1010,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1018,7 +1018,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v23.1/restore.md b/src/current/v23.1/restore.md
index f78885b94eb..8904c466ed5 100644
--- a/src/current/v23.1/restore.md
+++ b/src/current/v23.1/restore.md
@@ -219,11 +219,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
@@ -588,7 +588,7 @@ For more detail on using this option with `BACKUP`, see [Incremental backups wit
## Known limitations
-- To successfully [restore a table into a multi-region database](#restoring-to-multi-region-databases), it is necessary for the order and regions to match between the source and destination database. See the [Known Limitations]({% link {{ page.version.version }}/known-limitations.md %}#using-restore-with-multi-region-table-localities) page for detail on ordering and matching regions. [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/71071)
+- To successfully [restore a table into a multi-region database](#restoring-to-multi-region-databases), it is necessary for the order and regions to match between the source and destination database. See the [Known Limitations]({% link {{ page.version.version }}/known-limitations.md %}#using-restore-with-multi-region-table-localities) page for detail on ordering and matching regions. Tracking GitHub Issue
- {% include {{ page.version.version }}/known-limitations/restore-tables-non-multi-reg.md %}
- {% include {{ page.version.version }}/known-limitations/restore-udf.md %}
diff --git a/src/current/v23.1/schedule-cockroachdb-kubernetes.md b/src/current/v23.1/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v23.1/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v23.1/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v23.2/admission-control.md b/src/current/v23.2/admission-control.md
index c311b4ad7e4..2cac2ba4484 100644
--- a/src/current/v23.2/admission-control.md
+++ b/src/current/v23.2/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -149,6 +149,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v23.2/architecture/sql-layer.md b/src/current/v23.2/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v23.2/architecture/sql-layer.md
+++ b/src/current/v23.2/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v23.2/fips.md b/src/current/v23.2/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v23.2/fips.md
+++ b/src/current/v23.2/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v23.2/kubernetes-performance.md b/src/current/v23.2/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v23.2/kubernetes-performance.md
+++ b/src/current/v23.2/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v23.2/migrate-from-avro.md b/src/current/v23.2/migrate-from-avro.md
index 676f5274bff..82e6e8cd09f 100644
--- a/src/current/v23.2/migrate-from-avro.md
+++ b/src/current/v23.2/migrate-from-avro.md
@@ -163,7 +163,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v23.2/monitoring-and-alerting.md b/src/current/v23.2/monitoring-and-alerting.md
index f80cc618eb3..126b6e1aa6c 100644
--- a/src/current/v23.2/monitoring-and-alerting.md
+++ b/src/current/v23.2/monitoring-and-alerting.md
@@ -1075,7 +1075,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1084,7 +1084,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1092,7 +1092,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1100,7 +1100,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1116,7 +1116,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1124,7 +1124,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v23.2/read-committed.md b/src/current/v23.2/read-committed.md
index 94c697270f2..fea46dbbcf2 100644
--- a/src/current/v23.2/read-committed.md
+++ b/src/current/v23.2/read-committed.md
@@ -22,7 +22,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -941,5 +941,5 @@ The following affect the performance of `READ COMMITTED` transactions:
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v23.2/restore.md b/src/current/v23.2/restore.md
index 035a2fad37b..ca5fabde732 100644
--- a/src/current/v23.2/restore.md
+++ b/src/current/v23.2/restore.md
@@ -219,11 +219,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
@@ -586,7 +586,7 @@ For more detail on using this option with `BACKUP`, see [Incremental backups wit
## Known limitations
-- To successfully [restore a table into a multi-region database](#restoring-to-multi-region-databases), it is necessary for the order and regions to match between the source and destination database. See the [Known Limitations]({% link {{ page.version.version }}/known-limitations.md %}#using-restore-with-multi-region-table-localities) page for detail on ordering and matching regions. [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/71071)
+- To successfully [restore a table into a multi-region database](#restoring-to-multi-region-databases), it is necessary for the order and regions to match between the source and destination database. See the [Known Limitations]({% link {{ page.version.version }}/known-limitations.md %}#using-restore-with-multi-region-table-localities) page for detail on ordering and matching regions. Tracking GitHub Issue
- {% include {{ page.version.version }}/known-limitations/restore-tables-non-multi-reg.md %}
- {% include {{ page.version.version }}/known-limitations/restore-udf.md %}
diff --git a/src/current/v23.2/schedule-cockroachdb-kubernetes.md b/src/current/v23.2/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v23.2/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v23.2/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v24.1/admission-control.md b/src/current/v24.1/admission-control.md
index e57a49b142a..d21572c0e3b 100644
--- a/src/current/v24.1/admission-control.md
+++ b/src/current/v24.1/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -148,6 +148,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v24.1/architecture/sql-layer.md b/src/current/v24.1/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v24.1/architecture/sql-layer.md
+++ b/src/current/v24.1/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v24.1/fips.md b/src/current/v24.1/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v24.1/fips.md
+++ b/src/current/v24.1/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v24.1/kubernetes-performance.md b/src/current/v24.1/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v24.1/kubernetes-performance.md
+++ b/src/current/v24.1/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v24.1/migrate-from-avro.md b/src/current/v24.1/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v24.1/migrate-from-avro.md
+++ b/src/current/v24.1/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v24.1/monitoring-and-alerting.md b/src/current/v24.1/monitoring-and-alerting.md
index 53224596aec..5132ea9a5d0 100644
--- a/src/current/v24.1/monitoring-and-alerting.md
+++ b/src/current/v24.1/monitoring-and-alerting.md
@@ -1116,7 +1116,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1125,7 +1125,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1133,7 +1133,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1141,7 +1141,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1157,7 +1157,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1165,7 +1165,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v24.1/read-committed.md b/src/current/v24.1/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v24.1/read-committed.md
+++ b/src/current/v24.1/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v24.1/restore.md b/src/current/v24.1/restore.md
index 38833aed511..a5ae1c8ceea 100644
--- a/src/current/v24.1/restore.md
+++ b/src/current/v24.1/restore.md
@@ -219,11 +219,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v24.1/schedule-cockroachdb-kubernetes.md b/src/current/v24.1/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v24.1/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v24.1/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v24.2/admission-control.md b/src/current/v24.2/admission-control.md
index b68517a11f2..fe6e27ce737 100644
--- a/src/current/v24.2/admission-control.md
+++ b/src/current/v24.2/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -145,6 +145,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v24.2/architecture/sql-layer.md b/src/current/v24.2/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v24.2/architecture/sql-layer.md
+++ b/src/current/v24.2/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v24.2/fips.md b/src/current/v24.2/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v24.2/fips.md
+++ b/src/current/v24.2/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v24.2/kubernetes-performance.md b/src/current/v24.2/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v24.2/kubernetes-performance.md
+++ b/src/current/v24.2/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v24.2/migrate-from-avro.md b/src/current/v24.2/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v24.2/migrate-from-avro.md
+++ b/src/current/v24.2/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v24.2/monitoring-and-alerting.md b/src/current/v24.2/monitoring-and-alerting.md
index 7e6db953257..ef75d9bdb97 100644
--- a/src/current/v24.2/monitoring-and-alerting.md
+++ b/src/current/v24.2/monitoring-and-alerting.md
@@ -1122,7 +1122,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1131,7 +1131,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1139,7 +1139,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1147,7 +1147,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1163,7 +1163,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1171,7 +1171,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v24.2/read-committed.md b/src/current/v24.2/read-committed.md
index bcf0a5d9f92..e797812f832 100644
--- a/src/current/v24.2/read-committed.md
+++ b/src/current/v24.2/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v24.2/restore.md b/src/current/v24.2/restore.md
index 2be5b2b3140..4ecb693e90b 100644
--- a/src/current/v24.2/restore.md
+++ b/src/current/v24.2/restore.md
@@ -219,11 +219,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v24.2/schedule-cockroachdb-kubernetes.md b/src/current/v24.2/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v24.2/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v24.2/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v24.3/admission-control.md b/src/current/v24.3/admission-control.md
index 2b1c1f25abc..5fc915c9a84 100644
--- a/src/current/v24.3/admission-control.md
+++ b/src/current/v24.3/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -150,6 +150,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v24.3/architecture/sql-layer.md b/src/current/v24.3/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v24.3/architecture/sql-layer.md
+++ b/src/current/v24.3/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v24.3/fips.md b/src/current/v24.3/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v24.3/fips.md
+++ b/src/current/v24.3/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v24.3/kubernetes-performance.md b/src/current/v24.3/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v24.3/kubernetes-performance.md
+++ b/src/current/v24.3/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v24.3/migrate-from-avro.md b/src/current/v24.3/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v24.3/migrate-from-avro.md
+++ b/src/current/v24.3/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v24.3/monitoring-and-alerting.md b/src/current/v24.3/monitoring-and-alerting.md
index 126ea495e7e..f9285b8e419 100644
--- a/src/current/v24.3/monitoring-and-alerting.md
+++ b/src/current/v24.3/monitoring-and-alerting.md
@@ -1116,7 +1116,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1125,7 +1125,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1133,7 +1133,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1141,7 +1141,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1157,7 +1157,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1165,7 +1165,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v24.3/read-committed.md b/src/current/v24.3/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v24.3/read-committed.md
+++ b/src/current/v24.3/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v24.3/restore.md b/src/current/v24.3/restore.md
index dbd4512c271..5a2c1f5bc0f 100644
--- a/src/current/v24.3/restore.md
+++ b/src/current/v24.3/restore.md
@@ -219,11 +219,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v24.3/schedule-cockroachdb-kubernetes.md b/src/current/v24.3/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v24.3/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v24.3/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v25.1/admission-control.md b/src/current/v25.1/admission-control.md
index 83a7f42d689..2bb16075f5c 100644
--- a/src/current/v25.1/admission-control.md
+++ b/src/current/v25.1/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -167,6 +167,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v25.1/architecture/sql-layer.md b/src/current/v25.1/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v25.1/architecture/sql-layer.md
+++ b/src/current/v25.1/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v25.1/fips.md b/src/current/v25.1/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v25.1/fips.md
+++ b/src/current/v25.1/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v25.1/kubernetes-performance.md b/src/current/v25.1/kubernetes-performance.md
index 47aef82797d..356ecb6e2fb 100644
--- a/src/current/v25.1/kubernetes-performance.md
+++ b/src/current/v25.1/kubernetes-performance.md
@@ -20,9 +20,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -332,7 +332,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v25.1/migrate-from-avro.md b/src/current/v25.1/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v25.1/migrate-from-avro.md
+++ b/src/current/v25.1/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v25.1/monitoring-and-alerting.md b/src/current/v25.1/monitoring-and-alerting.md
index 8fbd199dbbd..2ad61fadac2 100644
--- a/src/current/v25.1/monitoring-and-alerting.md
+++ b/src/current/v25.1/monitoring-and-alerting.md
@@ -145,7 +145,7 @@ The `/_status/vars` metrics endpoint is in Prometheus format and is not deprecat
Several endpoints return raw status meta information in JSON at `http://:/#/debug`. You can investigate and use these endpoints, but note that they are subject to change.
-
+
### Node status command
@@ -1122,7 +1122,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1131,7 +1131,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1139,7 +1139,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1147,7 +1147,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1163,7 +1163,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1171,7 +1171,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v25.1/read-committed.md b/src/current/v25.1/read-committed.md
index bcf0a5d9f92..e797812f832 100644
--- a/src/current/v25.1/read-committed.md
+++ b/src/current/v25.1/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v25.1/restore.md b/src/current/v25.1/restore.md
index 162b6787a56..e65de2898e7 100644
--- a/src/current/v25.1/restore.md
+++ b/src/current/v25.1/restore.md
@@ -217,11 +217,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v25.1/schedule-cockroachdb-kubernetes.md b/src/current/v25.1/schedule-cockroachdb-kubernetes.md
index 973d234ffa9..de53f7c8449 100644
--- a/src/current/v25.1/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v25.1/schedule-cockroachdb-kubernetes.md
@@ -108,7 +108,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the Operator's custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v25.2/admission-control.md b/src/current/v25.2/admission-control.md
index 4870fb94728..2d8806767fb 100644
--- a/src/current/v25.2/admission-control.md
+++ b/src/current/v25.2/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -168,6 +168,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v25.2/architecture/sql-layer.md b/src/current/v25.2/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v25.2/architecture/sql-layer.md
+++ b/src/current/v25.2/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v25.2/fips.md b/src/current/v25.2/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v25.2/fips.md
+++ b/src/current/v25.2/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v25.2/kubernetes-performance.md b/src/current/v25.2/kubernetes-performance.md
index 6fa4d534442..cfe4aec6725 100644
--- a/src/current/v25.2/kubernetes-performance.md
+++ b/src/current/v25.2/kubernetes-performance.md
@@ -24,9 +24,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -336,7 +336,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v25.2/migrate-from-avro.md b/src/current/v25.2/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v25.2/migrate-from-avro.md
+++ b/src/current/v25.2/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v25.2/monitoring-and-alerting.md b/src/current/v25.2/monitoring-and-alerting.md
index 5a5816fb1b3..33a1476d280 100644
--- a/src/current/v25.2/monitoring-and-alerting.md
+++ b/src/current/v25.2/monitoring-and-alerting.md
@@ -143,7 +143,7 @@ The `/_status/vars` metrics endpoint is in Prometheus format and is not deprecat
Several endpoints return raw status meta information in JSON at `http://:/#/debug`. You can investigate and use these endpoints, but note that they are subject to change.
-
+
### Node status command
@@ -1113,7 +1113,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1122,7 +1122,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its `_status/vars` endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1130,7 +1130,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's `_status/vars` output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1138,7 +1138,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1154,7 +1154,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1162,7 +1162,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's `_status/vars` output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v25.2/read-committed.md b/src/current/v25.2/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v25.2/read-committed.md
+++ b/src/current/v25.2/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v25.2/restore.md b/src/current/v25.2/restore.md
index 794b3a338d2..8348ae9adb7 100644
--- a/src/current/v25.2/restore.md
+++ b/src/current/v25.2/restore.md
@@ -217,11 +217,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v25.2/schedule-cockroachdb-kubernetes.md b/src/current/v25.2/schedule-cockroachdb-kubernetes.md
index dd67d369c5e..5972aa3012e 100644
--- a/src/current/v25.2/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v25.2/schedule-cockroachdb-kubernetes.md
@@ -118,7 +118,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the {{ site.data.products.public-operator }}'s custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v25.2/schedule-cockroachdb-operator.md b/src/current/v25.2/schedule-cockroachdb-operator.md
index 4630ea6d9d1..25f040d1a91 100644
--- a/src/current/v25.2/schedule-cockroachdb-operator.md
+++ b/src/current/v25.2/schedule-cockroachdb-operator.md
@@ -88,7 +88,7 @@ Specify pod affinities and node anti-affinities in `cockroachdb.crdbCluster.podT
The {{ site.data.products.cockroachdb-operator }} hard-codes the pod template to only allow one pod per Kubernetes node. If you need to override this value, you can [override the pod template]({% link {{ page.version.version }}/override-templates-cockroachdb-operator.md %}#override-the-default-pod).
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
~~~ yaml
cockroachdb:
diff --git a/src/current/v25.3/admission-control.md b/src/current/v25.3/admission-control.md
index dd72fb6dcd4..eee14c739fe 100644
--- a/src/current/v25.3/admission-control.md
+++ b/src/current/v25.3/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -166,6 +166,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v25.3/architecture/sql-layer.md b/src/current/v25.3/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v25.3/architecture/sql-layer.md
+++ b/src/current/v25.3/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v25.3/fips.md b/src/current/v25.3/fips.md
index e490ddcd296..1ca62a6fa8e 100644
--- a/src/current/v25.3/fips.md
+++ b/src/current/v25.3/fips.md
@@ -58,7 +58,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v25.3/kubernetes-performance.md b/src/current/v25.3/kubernetes-performance.md
index 6fa4d534442..cfe4aec6725 100644
--- a/src/current/v25.3/kubernetes-performance.md
+++ b/src/current/v25.3/kubernetes-performance.md
@@ -24,9 +24,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -336,7 +336,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v25.3/migrate-from-avro.md b/src/current/v25.3/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v25.3/migrate-from-avro.md
+++ b/src/current/v25.3/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v25.3/monitoring-and-alerting.md b/src/current/v25.3/monitoring-and-alerting.md
index fb1a926937d..64c91a24e87 100644
--- a/src/current/v25.3/monitoring-and-alerting.md
+++ b/src/current/v25.3/monitoring-and-alerting.md
@@ -143,7 +143,7 @@ The `/_status/vars` metrics endpoint is in Prometheus format and is not deprecat
Several endpoints return raw status meta information in JSON at `http://:/#/debug`. You can investigate and use these endpoints, but note that they are subject to change.
-
+
### Node status command
@@ -1090,7 +1090,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1099,7 +1099,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its Prometheus endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1107,7 +1107,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's Prometheus endpoint output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1115,7 +1115,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1131,7 +1131,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1139,7 +1139,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v25.3/read-committed.md b/src/current/v25.3/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v25.3/read-committed.md
+++ b/src/current/v25.3/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v25.3/restore.md b/src/current/v25.3/restore.md
index 794b3a338d2..8348ae9adb7 100644
--- a/src/current/v25.3/restore.md
+++ b/src/current/v25.3/restore.md
@@ -217,11 +217,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v25.3/schedule-cockroachdb-kubernetes.md b/src/current/v25.3/schedule-cockroachdb-kubernetes.md
index dd67d369c5e..5972aa3012e 100644
--- a/src/current/v25.3/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v25.3/schedule-cockroachdb-kubernetes.md
@@ -118,7 +118,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the {{ site.data.products.public-operator }}'s custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v25.3/schedule-cockroachdb-operator.md b/src/current/v25.3/schedule-cockroachdb-operator.md
index 4630ea6d9d1..25f040d1a91 100644
--- a/src/current/v25.3/schedule-cockroachdb-operator.md
+++ b/src/current/v25.3/schedule-cockroachdb-operator.md
@@ -88,7 +88,7 @@ Specify pod affinities and node anti-affinities in `cockroachdb.crdbCluster.podT
The {{ site.data.products.cockroachdb-operator }} hard-codes the pod template to only allow one pod per Kubernetes node. If you need to override this value, you can [override the pod template]({% link {{ page.version.version }}/override-templates-cockroachdb-operator.md %}#override-the-default-pod).
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
~~~ yaml
cockroachdb:
diff --git a/src/current/v25.4/admission-control.md b/src/current/v25.4/admission-control.md
index dd72fb6dcd4..eee14c739fe 100644
--- a/src/current/v25.4/admission-control.md
+++ b/src/current/v25.4/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -166,6 +166,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v25.4/architecture/sql-layer.md b/src/current/v25.4/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v25.4/architecture/sql-layer.md
+++ b/src/current/v25.4/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v25.4/fips.md b/src/current/v25.4/fips.md
index f82d1f995a3..1b5b42dddb5 100644
--- a/src/current/v25.4/fips.md
+++ b/src/current/v25.4/fips.md
@@ -76,7 +76,7 @@ A system must have FIPS mode enabled in the kernel before it can run the FIPS-re
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 8 Docker image](https://catalog.redhat.com/software/containers/ubi8/ubi/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- Your Dockerfile must install OpenSSL before it starts the `cockroach` binary.
- You must enable FIPS mode on the Docker host kernel before it can run containers with FIPS mode enabled. The FIPS-ready CockroachDB Docker image must run with FIPS mode enabled. To enable FIPS mode in the Docker host kernel, refer to [Enable FIPS mode](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/assembly_installing-a-rhel-8-system-with-fips-mode-enabled_security-hardening) in Red Hat's documentation. To verify that FIPS mode is enabled, refer to [Verify that the kernel enforces FIPS mode](#verify-that-the-kernel-enforces-fips-mode).
diff --git a/src/current/v25.4/kubernetes-performance.md b/src/current/v25.4/kubernetes-performance.md
index 6fa4d534442..cfe4aec6725 100644
--- a/src/current/v25.4/kubernetes-performance.md
+++ b/src/current/v25.4/kubernetes-performance.md
@@ -24,9 +24,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -336,7 +336,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v25.4/migrate-from-avro.md b/src/current/v25.4/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v25.4/migrate-from-avro.md
+++ b/src/current/v25.4/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v25.4/monitoring-and-alerting.md b/src/current/v25.4/monitoring-and-alerting.md
index cc29283cd40..a3353b745a3 100644
--- a/src/current/v25.4/monitoring-and-alerting.md
+++ b/src/current/v25.4/monitoring-and-alerting.md
@@ -1090,7 +1090,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1099,7 +1099,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its Prometheus endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1107,7 +1107,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's Prometheus endpoint output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1115,7 +1115,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1131,7 +1131,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1139,7 +1139,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v25.4/read-committed.md b/src/current/v25.4/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v25.4/read-committed.md
+++ b/src/current/v25.4/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v25.4/restore.md b/src/current/v25.4/restore.md
index 794b3a338d2..8348ae9adb7 100644
--- a/src/current/v25.4/restore.md
+++ b/src/current/v25.4/restore.md
@@ -217,11 +217,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v25.4/schedule-cockroachdb-kubernetes.md b/src/current/v25.4/schedule-cockroachdb-kubernetes.md
index dd67d369c5e..5972aa3012e 100644
--- a/src/current/v25.4/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v25.4/schedule-cockroachdb-kubernetes.md
@@ -118,7 +118,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the {{ site.data.products.public-operator }}'s custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v25.4/schedule-cockroachdb-operator.md b/src/current/v25.4/schedule-cockroachdb-operator.md
index 4630ea6d9d1..25f040d1a91 100644
--- a/src/current/v25.4/schedule-cockroachdb-operator.md
+++ b/src/current/v25.4/schedule-cockroachdb-operator.md
@@ -88,7 +88,7 @@ Specify pod affinities and node anti-affinities in `cockroachdb.crdbCluster.podT
The {{ site.data.products.cockroachdb-operator }} hard-codes the pod template to only allow one pod per Kubernetes node. If you need to override this value, you can [override the pod template]({% link {{ page.version.version }}/override-templates-cockroachdb-operator.md %}#override-the-default-pod).
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
~~~ yaml
cockroachdb:
diff --git a/src/current/v26.1/admission-control.md b/src/current/v26.1/admission-control.md
index e29f44ffc21..3c07c649c81 100644
--- a/src/current/v26.1/admission-control.md
+++ b/src/current/v26.1/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -166,6 +166,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v26.1/architecture/sql-layer.md b/src/current/v26.1/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v26.1/architecture/sql-layer.md
+++ b/src/current/v26.1/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v26.1/fips.md b/src/current/v26.1/fips.md
index f1d6cf8c51d..9b5b26f2576 100644
--- a/src/current/v26.1/fips.md
+++ b/src/current/v26.1/fips.md
@@ -84,7 +84,7 @@ The FIPS-ready CockroachDB Docker images are based on [Red Hat's Universal Base
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 10](https://catalog.redhat.com/software/containers/ubi10/ubi-minimal/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- The FIPS-ready binary includes the FIPS 140-3 Go Cryptographic Module and does not require additional system libraries to be installed.
diff --git a/src/current/v26.1/kubernetes-performance.md b/src/current/v26.1/kubernetes-performance.md
index 6fa4d534442..cfe4aec6725 100644
--- a/src/current/v26.1/kubernetes-performance.md
+++ b/src/current/v26.1/kubernetes-performance.md
@@ -24,9 +24,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -336,7 +336,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v26.1/migrate-from-avro.md b/src/current/v26.1/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v26.1/migrate-from-avro.md
+++ b/src/current/v26.1/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v26.1/monitoring-and-alerting.md b/src/current/v26.1/monitoring-and-alerting.md
index 46dfaf780ea..3a285c2115b 100644
--- a/src/current/v26.1/monitoring-and-alerting.md
+++ b/src/current/v26.1/monitoring-and-alerting.md
@@ -1090,7 +1090,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1099,7 +1099,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its Prometheus endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1107,7 +1107,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's Prometheus endpoint output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1115,7 +1115,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1131,7 +1131,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1139,7 +1139,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v26.1/read-committed.md b/src/current/v26.1/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v26.1/read-committed.md
+++ b/src/current/v26.1/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v26.1/restore.md b/src/current/v26.1/restore.md
index 32943361078..b9ae28cea2a 100644
--- a/src/current/v26.1/restore.md
+++ b/src/current/v26.1/restore.md
@@ -215,11 +215,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v26.1/schedule-cockroachdb-kubernetes.md b/src/current/v26.1/schedule-cockroachdb-kubernetes.md
index dd67d369c5e..5972aa3012e 100644
--- a/src/current/v26.1/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v26.1/schedule-cockroachdb-kubernetes.md
@@ -118,7 +118,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the {{ site.data.products.public-operator }}'s custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v26.1/schedule-cockroachdb-operator.md b/src/current/v26.1/schedule-cockroachdb-operator.md
index 4630ea6d9d1..25f040d1a91 100644
--- a/src/current/v26.1/schedule-cockroachdb-operator.md
+++ b/src/current/v26.1/schedule-cockroachdb-operator.md
@@ -88,7 +88,7 @@ Specify pod affinities and node anti-affinities in `cockroachdb.crdbCluster.podT
The {{ site.data.products.cockroachdb-operator }} hard-codes the pod template to only allow one pod per Kubernetes node. If you need to override this value, you can [override the pod template]({% link {{ page.version.version }}/override-templates-cockroachdb-operator.md %}#override-the-default-pod).
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
~~~ yaml
cockroachdb:
diff --git a/src/current/v26.2/admission-control.md b/src/current/v26.2/admission-control.md
index 345df652f91..755cbd51f1c 100644
--- a/src/current/v26.2/admission-control.md
+++ b/src/current/v26.2/admission-control.md
@@ -22,7 +22,7 @@ Admission control works on a per-[node]({% link {{ page.version.version }}/archi
For more details about how the admission control system works, see:
-- The [Admission Control tech note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md).
+- [The Admission Control tech note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/admission_control.md).
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
## Use cases for admission control
@@ -167,6 +167,6 @@ The [DB Console Overload dashboard]({% link {{ page.version.version }}/ui-overlo
## See also
- The [Overload Dashboard]({% link {{ page.version.version }}/ui-overload-dashboard.md %}) in the [DB Console]({% link {{ page.version.version }}/ui-overview.md %}).
-- The [technical note for admission control](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/admission_control.md) for details on the design of the admission control system.
+- The technical note for admission control for details on the design of the admission control system.
- The blog post [Here's how CockroachDB keeps your database from collapsing under load](https://www.cockroachlabs.com/blog/admission-control-in-cockroachdb/).
- The blog post [Rubbing Control Theory on the Go scheduler](https://www.cockroachlabs.com/blog/rubbing-control-theory/).
diff --git a/src/current/v26.2/architecture/sql-layer.md b/src/current/v26.2/architecture/sql-layer.md
index bfb67a48c05..2605879b93d 100644
--- a/src/current/v26.2/architecture/sql-layer.md
+++ b/src/current/v26.2/architecture/sql-layer.md
@@ -117,7 +117,7 @@ It's also important––for indexed columns––that this byte encoding preser
However, for non-indexed columns (e.g., non-`PRIMARY KEY` columns), CockroachDB instead uses an encoding (known as "value encoding") which consumes less space but does not preserve ordering.
-You can find more exhaustive detail in the [Encoding Tech Note](https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md).
+You can find more exhaustive detail in [the Encoding Tech Note](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/tech-notes/encoding.md).
### DistSQL
@@ -134,7 +134,7 @@ To run SQL statements in a distributed fashion, we introduce a couple of concept
- **Logical plan**: Similar to the AST/`planNode` tree described above, it represents the abstract (non-distributed) data flow through computation stages.
- **Physical plan**: A physical plan is conceptually a mapping of the logical plan nodes to physical machines running `cockroach`. Logical plan nodes are replicated and specialized depending on the cluster topology. Like `planNodes` above, these components of the physical plan are scheduled and run on the cluster.
-You can find much greater detail in the [DistSQL RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160421_distributed_sql.md).
+You can find much greater detail in [the DistSQL RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160421_distributed_sql.md).
## Schema changes
diff --git a/src/current/v26.2/fips.md b/src/current/v26.2/fips.md
index f1d6cf8c51d..9b5b26f2576 100644
--- a/src/current/v26.2/fips.md
+++ b/src/current/v26.2/fips.md
@@ -84,7 +84,7 @@ The FIPS-ready CockroachDB Docker images are based on [Red Hat's Universal Base
If you do not want to use the FIPS-ready CockroachDB Docker image directly, you can create a custom Docker image based on [Red Hat's Universal Base Image 10](https://catalog.redhat.com/software/containers/ubi10/ubi-minimal/):
-- You can model your Dockerfile on the one that Cockroach Labs uses to produce the [FIPS-ready Docker image](https://github.com/cockroachdb/cockroach/blob/master/build/deploy/Dockerfile) for CockroachDB.
+- You can model your Dockerfile on the one that Cockroach Labs uses to produce the FIPS-ready Docker image for CockroachDB.
- The FIPS-ready binary includes the FIPS 140-3 Go Cryptographic Module and does not require additional system libraries to be installed.
diff --git a/src/current/v26.2/kubernetes-performance.md b/src/current/v26.2/kubernetes-performance.md
index 6fa4d534442..cfe4aec6725 100644
--- a/src/current/v26.2/kubernetes-performance.md
+++ b/src/current/v26.2/kubernetes-performance.md
@@ -24,9 +24,9 @@ Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:
A number of independent factors affect performance when running CockroachDB on Kubernetes. Most are easiest to change before you create your CockroachDB cluster. If you need to modify a CockroachDB cluster that is already running on Kubernetes, extra care and testing is strongly recommended.
-The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml).
+The following sections show how to modify excerpts from our provided Kubernetes configuration YAML files. You can find the most up-to-date versions of these files on GitHub: [one for running CockroachDB in secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) and one for [running CockroachDB in insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/cockroachdb-statefulset.yaml).
-You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
+You can also use a [performance-optimized configuration file for secure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-secure.yaml) or [insecure mode](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml). Be sure to modify the file wherever there is a `TODO` comment.
### Version of CockroachDB
@@ -336,7 +336,7 @@ If for some reason setting appropriate resource requests still isn't getting you
#### Client applications on the same machines as CockroachDB
-Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/cockroach/blob/98c506c48f3517d1ac1aadb6a09e1b23ad672c37/cloud/kubernetes/example-app.yaml#L11-L12):
+Running client applications such as benchmarking applications on the same machines as CockroachDB can be even worse than just having Kubernetes system pods on the same machines. They are very likely to end up competing for resources, because when the applications get more loaded than usual, so will the CockroachDB processes. The best way to avoid this is to [set resource requests and limits](#resource-requests-and-limits), but if you are unwilling or unable to do that for some reason, you can also set [anti-affinity scheduling policies](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) on your client applications. Anti-affinity policies are placed in the pod spec, so if you wanted to change our provided example load generator app, you'd change [these lines](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml):
~~~ yaml
spec:
diff --git a/src/current/v26.2/migrate-from-avro.md b/src/current/v26.2/migrate-from-avro.md
index de42d232917..eb46e391fce 100644
--- a/src/current/v26.2/migrate-from-avro.md
+++ b/src/current/v26.2/migrate-from-avro.md
@@ -161,7 +161,7 @@ There are additional import [options][option] you can use when importing binary
- `records_terminated_by`, which specifies the unicode character used to indicate new lines in the input binary or JSON file (default: `\n`).
{{site.data.alerts.callout_info}}
-The following example uses sample data generated by [Avro tools](https://github.com/cockroachdb/cockroach/tree/master/pkg/sql/importer/testdata/avro).
+The following example uses sample data generated by Avro tools.
{{site.data.alerts.end}}
For example, to import the data from `simple-schema.json` into a `simple` table, first [create the table]({% link {{ page.version.version }}/create-table.md %}) to import into. Then run `IMPORT INTO` with the following options:
diff --git a/src/current/v26.2/monitoring-and-alerting.md b/src/current/v26.2/monitoring-and-alerting.md
index d6bd689cb1a..2cb49e5e35a 100644
--- a/src/current/v26.2/monitoring-and-alerting.md
+++ b/src/current/v26.2/monitoring-and-alerting.md
@@ -1102,7 +1102,7 @@ Start Prometheus and Alertmanager to begin watching for events to alert on. You
### Events to alert on
{{site.data.alerts.callout_info}}
-Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
+Currently, not all events listed have corresponding alert rule definitions available from the `api/v2/rules/` endpoint. Many events not yet available in this manner are defined in the pre-defined alerting rules. For more details, see [Monitor CockroachDB with Prometheus]({% link {{ page.version.version }}/monitor-cockroachdb-with-prometheus.md %}).
{{site.data.alerts.end}}
#### Node is down
@@ -1111,7 +1111,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** If a node is down, its Prometheus endpoint will return a `Connection refused` error. Otherwise, the `liveness_livenodes` metric will be the total number of live nodes in the cluster.
-- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceDead` alert from our pre-defined alerting rules.
#### Node is restarting too frequently
@@ -1119,7 +1119,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the number of times the `sys_uptime` metric in the node's Prometheus endpoint output was reset back to zero. The `sys_uptime` metric gives you the length of time, in seconds, that the `cockroach` process has been running.
-- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `InstanceFlapping` alert from our pre-defined alerting rules.
#### Node is running low on disk space
@@ -1127,7 +1127,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Divide the `capacity` metric by the `capacity_available` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `StoreDiskLow` alert from our pre-defined alerting rules.
{% include {{page.version.version}}/storage/free-up-disk-space.md %}
@@ -1143,7 +1143,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_ca` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `CACertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Node certificate expires soon
@@ -1151,7 +1151,7 @@ Currently, not all events listed have corresponding alert rule definitions avail
- **How to detect:** Calculate this using the `security_certificate_expiration_node` metric in the node's Prometheus endpoint output.
-- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
+- **Rule definition:** Use the `NodeCertificateExpiresSoon` alert from our pre-defined alerting rules.
#### Changefeed is experiencing high latency
diff --git a/src/current/v26.2/read-committed.md b/src/current/v26.2/read-committed.md
index 6b83f50d88d..0858d1e0244 100644
--- a/src/current/v26.2/read-committed.md
+++ b/src/current/v26.2/read-committed.md
@@ -20,7 +20,7 @@ Whereas `SERIALIZABLE` isolation guarantees data correctness by placing transact
If your workload is already running well under `SERIALIZABLE` isolation, Cockroach Labs does not recommend changing to `READ COMMITTED` isolation unless there is a specific need.
{{site.data.alerts.callout_info}}
-`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md).
+`READ COMMITTED` on CockroachDB provides stronger isolation than `READ COMMITTED` on PostgreSQL. On CockroachDB, `READ COMMITTED` prevents anomalies within single statements. For complete details on how `READ COMMITTED` is implemented on CockroachDB, see the [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md).
{{site.data.alerts.end}}
## Enable `READ COMMITTED` isolation
@@ -918,5 +918,5 @@ SELECT * FROM schedules
- [`SELECT ... FOR UPDATE`]({% link {{ page.version.version }}/select-for-update.md %})
- [Serializable Transactions]({% link {{ page.version.version }}/demo-serializable.md %})
- [What Write Skew Looks Like](https://www.cockroachlabs.com/blog/what-write-skew-looks-like/)
-- [Read Committed RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20230122_read_committed_isolation.md)
+- [Read Committed RFC](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20230122_read_committed_isolation.md)
- [Migration Overview]({% link molt/migration-overview.md %})
diff --git a/src/current/v26.2/restore.md b/src/current/v26.2/restore.md
index d1de15c5b86..a8176aa673e 100644
--- a/src/current/v26.2/restore.md
+++ b/src/current/v26.2/restore.md
@@ -216,11 +216,11 @@ When restoring an individual table that references a user-defined type (e.g., [`
- If there is an existing type in the cluster with the same name that is compatible with the type in the backup, CockroachDB will map the type in the backup to the type in the cluster.
- If there is an existing type in the cluster with the same name but it is _not_ compatible with the type in the backup, the restore will not succeed and you will be asked to resolve the naming conflict. You can do this by either [dropping]({% link {{ page.version.version }}/drop-type.md %}) or [renaming]({% link {{ page.version.version }}/alter-type.md %}) the existing user-defined type.
-In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200331_enums.md#physical-layout). For example:
+In general, two types are compatible if they are the same kind (e.g., an enum is only compatible with other enums). Additionally, enums are only compatible if they have the same ordered set of elements that have also been [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout). For example:
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes', 'no')` are compatible.
- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('no', 'yes')` are not compatible.
-- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not created in the same way.
+- `CREATE TYPE t1 AS ENUM ('yes', 'no')` and `CREATE TYPE t2 AS ENUM ('yes'); ALTER TYPE t2 ADD VALUE ('no')` are not compatible because they were not [created in the same way](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200331_enums.md#physical-layout).
### Object dependencies
diff --git a/src/current/v26.2/schedule-cockroachdb-kubernetes.md b/src/current/v26.2/schedule-cockroachdb-kubernetes.md
index dd67d369c5e..5972aa3012e 100644
--- a/src/current/v26.2/schedule-cockroachdb-kubernetes.md
+++ b/src/current/v26.2/schedule-cockroachdb-kubernetes.md
@@ -118,7 +118,7 @@ For more context on how these rules work, see the [Kubernetes documentation](htt
Specify pod affinities and anti-affinities in `affinity.podAffinity` and `affinity.podAntiAffinity` in the {{ site.data.products.public-operator }}'s custom resource, which is used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-kubernetes.md %}#initialize-the-cluster). If you specify multiple `matchExpressions` labels, the node must match all of them. If you specify multiple `values` for a label, the node can match any of the values.
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
{% include_cached copy-clipboard.html %}
~~~ yaml
diff --git a/src/current/v26.2/schedule-cockroachdb-operator.md b/src/current/v26.2/schedule-cockroachdb-operator.md
index 4630ea6d9d1..25f040d1a91 100644
--- a/src/current/v26.2/schedule-cockroachdb-operator.md
+++ b/src/current/v26.2/schedule-cockroachdb-operator.md
@@ -88,7 +88,7 @@ Specify pod affinities and node anti-affinities in `cockroachdb.crdbCluster.podT
The {{ site.data.products.cockroachdb-operator }} hard-codes the pod template to only allow one pod per Kubernetes node. If you need to override this value, you can [override the pod template]({% link {{ page.version.version }}/override-templates-cockroachdb-operator.md %}#override-the-default-pod).
-The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
+The following configuration attempts to schedule CockroachDB pods in the same zones as the pods that run our example [load generator](https://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/cloud/kubernetes/example-app.yaml) app. It disallows CockroachDB pods from being co-located on the same worker node.
~~~ yaml
cockroachdb: