You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/references/container-sources.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ One solution to these supply-chain concerns is to deploy Nebari from private loc
12
12
13
13
Deploying Nebari in this fashion eliminates significant supply chain surface-area, but requires identifying all containers used by Nebari.
14
14
15
-
The following configurations demonstrate how to specify a private repo denoted by the string `[PRIVATE_REPO]`.
15
+
The following configurations demonstrate how to specify a private repo denoted by the string `[PRIVATE_REPO]`.
16
16
17
17
**Note:** Authorization tokens are used in the examples below. It is important for administrators to understand the expiration policy of these tokens, because the Nebari k8s cluster may in some cases need to **use these tokens to pull container images at any time during run-time operation**.
0 commit comments