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
You can also install the inlets-operator using a single command using [arkade](https://get-arkade.dev/), arkade runs against any Kubernetes cluster.
250
+
251
+
Install with inlets PRO:
252
+
253
+
```bash
254
+
arkade install inlets-operator \
255
+
--provider linode \
256
+
--region us-east \
257
+
--access-key <Linode API Access Key> \
258
+
--license $(cat $HOME/inlets-pro-license.txt)
259
+
```
260
+
261
+
Install with inlets OSS:
262
+
263
+
```bash
264
+
arkade install inlets-operator \
265
+
--provider linode \
266
+
--region us-east \
267
+
--access-key <Linode API Access Key>
268
+
```
269
+
270
+
You can also install using kubectl without helm: (Change `-provider` and `-region` in `./artifacts/operator.yaml`)
271
+
272
+
```bash
273
+
# Create a secret to store the access token
274
+
275
+
kubectl create secret generic inlets-access-key \
276
+
--from-literal inlets-access-key=<Linode API Access Key>
277
+
278
+
kubectl apply -f ./artifacts/crds/
279
+
280
+
# Apply the operator deployment and RBAC role
281
+
kubectl apply -f ./artifacts/operator-rbac.yaml
282
+
kubectl apply -f ./artifacts/operator.yaml
283
+
```
284
+
229
285
## Expose a service with a LoadBalancer
230
286
231
287
The LoadBalancer type is usually provided by a cloud controller, but when that is not available, then you can use the inlets-operator to get a public IP and ingress. The free OSS version of inlets provides a HTTP tunnel, inlets PRO can provide TCP and full functionality to an IngressController.
0 commit comments