@@ -31,6 +31,12 @@ Before creating a plugin, read the [Kubernetes Plugins documentation][plugins].
31
31
designed to provide the same command-line arguments, kubeconfig parser,
32
32
Kubernetes API REST client, and printing logic.
33
33
34
+ ** Unofficial Quickstart for Go:** For Go plugins, there's a
35
+ [ GitHub template repo] ( https://github.com/replicatedhq/krew-plugin-template )
36
+ that implements these best practices and also configures GoReleaser and a
37
+ GitHub Action to create releases when a tag is pushed. Note: this template
38
+ repo is not maintained by the Krew project.
39
+
34
40
Below you will create a small plugin named ` foo ` which prints the environment
35
41
variables to the screen and exits.
36
42
@@ -192,10 +198,10 @@ wildcard may install more files than desired.
192
198
` ` ` yaml
193
199
files: [{from: "*", to: "."}]
194
200
` ` `
195
-
201
+
196
202
This copies out binaries for both platforms to the installation directory
197
203
onto the user’s machine, despite only one of them will be used :
198
-
204
+
199
205
` ` ` text
200
206
.
201
207
└── krew-foo-windows.exe
@@ -248,7 +254,7 @@ plugin name.
248
254
# ### Specifying a plugin download URL
249
255
250
256
krew plugins must be packaged as `.zip` or `.tar.gz` archives and should be made
251
- available for download publicly.
257
+ available for download publicly.
252
258
Downloading from a URL also requires a checksum of the downloaded content :
253
259
254
260
- `uri` : URL to the archive file (`.zip` or `.tar.gz`)
0 commit comments