Skip to content

Commit 0fc3d6d

Browse files
authored
doc: explain how stage and test images (#98)
1 parent 1dfd9e8 commit 0fc3d6d

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,3 +49,26 @@ form produced by `skaffold debug`. To run:
4949
```sh
5050
sh run-its.sh
5151
```
52+
53+
# Staging and Deploying
54+
55+
To stage a set of images for testing use the following command,
56+
where `$REPO` is the image repository where you plan to host the
57+
images.
58+
```sh
59+
skaffold build -p release,deprecated-names --default-repo $REPO
60+
```
61+
62+
The `release` profile causes the images to be pushed to the specified
63+
repository and also enables multi-arch builds using buildx (default
64+
linux/amd64 and linux/arm64). The `deprecated-names` profile enables
65+
using the short-form image names (`go`, `netcore`, `nodejs`, `python`)
66+
which we intend to move away from.
67+
68+
Then configure Skaffold to point to that location:
69+
```sh
70+
skaffold config set --global debug-helpers-registry $REPO
71+
```
72+
73+
You should then be able to use `skaffold debug` and use the
74+
staged images.

0 commit comments

Comments
 (0)