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
Equinix metal is no longer available as a service. This change removes
references to Qeuinix metal.
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
@@ -477,4 +476,4 @@ The config options are fairly straight forward.
477
476
478
477
The GARM API server has the option to enable TLS, but I suggest you use a reverse proxy and enable TLS termination in that reverse proxy. There is an `nginx` sample in this repository with TLS termination enabled.
479
478
480
-
You can of course enable TLS in both garm and the reverse proxy. The choice is yours.
479
+
You can of course enable TLS in both garm and the reverse proxy. The choice is yours.
Each of these providers can be used to set up a runner pool for a repository, organization or enterprise.
@@ -540,7 +538,7 @@ Let's unpack the command and explain what happened above. We added a new pool of
540
538
541
539
We also specified the `--min-idle-runners` option to tell GARM to always keep at least 1 runner idle in the pool. This is useful for repositories that have a lot of workflows that run often, and we want to make sure that we always have a runner ready to pick up a job.
542
540
543
-
If we review the output of the command, we can see that the pool was created with a maximum number of 5 runners. This is just a default we can tweak when creating the pool, or later using the `garm-cli pool update` command. We can also see that the pool was created with a runner botstrap timeout of 20 minutes. This timeout is important on provider where the instance may take a long time to spin up. For example, on Equinix Metal, some operating systems can take a few minutes to install and reboot. This timeout can be tweaked to a higher value to account for this.
541
+
If we review the output of the command, we can see that the pool was created with a maximum number of 5 runners. This is just a default we can tweak when creating the pool, or later using the `garm-cli pool update` command. We can also see that the pool was created with a runner botstrap timeout of 20 minutes. This timeout is important on provider where the instance may take a long time to spin up. For example, if you're deploying an Ironic node on OpenStack, some operating systems can take a few minutes to install and reboot. This timeout can be tweaked to a higher value to account for this.
544
542
545
543
The pool was created with the `--enabled` flag set to `false`, so the pool won't create any runners yet:
546
544
@@ -574,7 +572,7 @@ ubuntu@garm:~/garm$ garm-cli pool list --all
@@ -813,4 +811,4 @@ To view existing jobs, run the following command:
813
811
garm-cli job list
814
812
```
815
813
816
-
If you've just set up GARM and have not yet created a pool or triggered a job, this will be empty. If you've configured everything and still don't receive jobs, you'll need to make sure that your URLs (discussed at the begining of this article), are correct. GitHub needs to be able to reach the webhook URL that our GARM instance listens on.
814
+
If you've just set up GARM and have not yet created a pool or triggered a job, this will be empty. If you've configured everything and still don't receive jobs, you'll need to make sure that your URLs (discussed at the begining of this article), are correct. GitHub needs to be able to reach the webhook URL that our GARM instance listens on.
0 commit comments