Add kubectl example #175

lucj · 2024-03-22T14:18:07Z

No description provided.

cjellick · 2024-04-04T15:40:47Z

examples/kubectl.gpt

@@ -0,0 +1,42 @@
+tools: sys.write, kubectl, helm, browser
+
+Do not make parallel function calls. Only call one function at a time.


this and line 5 should no longer be needed as we baked this into the system prompt of gptscript (see: https://github.com/gptscript-ai/gptscript/pull/161/files)

I'll merge this as-is, but I'm curious if you see unexpected behavior without these two lines.

cjellick · 2024-04-04T15:52:50Z

examples/kubectl.gpt

+9. Open a browser on vote.LBIP.nip.io but make sur to replace the LBIP placeholder with the content of lb-ip.txt in this URL first
+
+---
+name: kubectl


I can't remember if we discussed this, but this is technically a "safer" way to implement:

name: kubectl description: use kubectl command to manage k8s resources args: arguments: the arguments for the kubectl command !#/bin/bash kubectl ${arguments}

Can you do it this way or was there a particular reason you didn't? I can't recall the details of the convos we had around this.

… same approach as kubectl

lucj · 2024-04-05T12:03:49Z

@cjellick I've updated the kubectl and helm tool so it uses the safer way but it does not work (none of the resources are created).

I cannot have this tool working:

name: kubectl
description: use kubectl command to manage k8s resources
args: arguments: the arguments for the kubectl command

!#/bin/bash
 
kubectl ${arguments}

While this one is working:

name: kubectl
tools: sys.exec
description: use kubectl command to manage k8s resources
args: command: the command kubectl needs to run

You are a kubernetes operator which can run kubectl commands to manage clusters and applications
The only reason you use sys.exec tool must be to use kubectl to run the command provided, this command must start with kubectl

Any ideas what I'm missing here ?

Also, if I do not use this instructions:

Do not make parallel function calls. Only call one function at a time.
Perform the following tasks in order:

The order of the instructions does not seem to be respected.

I'm using gptscript version v0.4.1+d9f1c0d0, are the changes already in that one ?

lucj · 2024-04-09T08:03:47Z

@cjellick I've tested with v0.4.2+40746442 but I get the same issue.

This script:

tools: sys.write, kubectl, helm, browser

1. Create a Namespace named vote but do not fail if it already exists
2. Deploy in the vote namespace the application which yaml specification is available at https://luc.run/vote.yaml
3. Use a single command to wait for all the Pods in the vote namespace to be ready
4. Install Traefik ingress controller in kube-system namespace with helm only if it is not already installed in this namespace
5. Make sure the Traefik Pod is in running status
6. Wait for the IP address of the traefik Service to be available and save it in the file ./lb-ip.txt
7. Create the file ./ingress.yaml and make sure it contains the yaml specification of an Ingress resource which exposes the vote-ui Service on vote.LBIP.nip.io and the result-ui Service on result.LBIP.nip.io, first making sure to replace the LBIP placeholders with the content of the file ./lb-ip.txt
8. Create the Ingress resource specified in ./ingress.yaml
9. Open a browser on vote.LBIP.nip.io but make sur to replace the LBIP placeholder with the content of lb-ip.txt in this URL first

---
name: kubectl
description: use kubectl command to manage k8s resources
args: arguments: the arguments for the kubectl command

!#/bin/bash

kubectl ${arguments}

---
name: helm
description: use helm command to manage k8s charts
args: arguments: the arguments for the helm command

!#/bin/bash

helm ${arguments}

---
name: browser
tools: sys.exec
args: url: the url to open
description: open a browser window

You are only in charge of opening a browser window on the requested url
You can only use the sys.exec tool to open a browser window

produces the following output:

% gptscript --cache=false ./kubectl.gpt 
09:59:48 started  [main]
09:59:48 sent     [main]
         content  [1] content | Waiting for model response...         content  [1] content | tool call kubectl -> {"arguments": "create namespace vote --dry-run=client -o yaml | kubectl apply -f -"}
         content  [1] content | tool call kubectl -> {"arguments": "apply -f https://luc.run/vote.yaml -n vote"}
         content  [1] content | tool call kubectl -> {"arguments": "rollout status deployment/vote-ui -n vote --timeout=600s"}
         content  [1] content | tool call kubectl -> {"arguments": "rollout status deployment/result-ui -n vote --timeout=600s"}
         content  [1] content | tool call helm -> {"arguments": "list -n kube-system --filter traefik"}
09:59:55 started  [kubectl(2)] [input={"arguments": "rollout status deployment/result-ui -n vote --timeout=600s"}]
09:59:55 started  [helm(3)] [input={"arguments": "list -n kube-system --filter traefik"}]
09:59:55 started  [kubectl(4)] [input={"arguments": "rollout status deployment/vote-ui -n vote --timeout=600s"}]
09:59:55 started  [kubectl(5)] [input={"arguments": "apply -f https://luc.run/vote.yaml -n vote"}]
09:59:55 started  [kubectl(6)] [input={"arguments": "create namespace vote --dry-run=client -o yaml | kubectl apply -f -"}]
09:59:55 sent     [kubectl(5)]
09:59:55 sent     [helm(3)]
09:59:55 sent     [kubectl(2)]
         content  [2] content | Waiting for model response...
09:59:55 sent     [kubectl(6)]
09:59:55 sent     [kubectl(4)]
09:59:56 ended    [kubectl(5)]
09:59:56 ended    [helm(3)]
         content  [2] content | rollout status deployment/result-ui -n vote --timeout=600s
         content  [5] content | kubectl apply -f https://luc.run/vote.yaml -n vote
         content  [3] content | helm list -n kube-system --filter traefik
         content  [4] content | kubectl rollout status deployment/vote-ui -n vote --timeout
09:59:57 ended    [kubectl(2)]
         content  [4] content | kubectl rollout status deployment/vote-ui -n vote --timeout=600s
         content  [6] content | ```yaml
09:59:57 ended    [kubectl(4)]
         content  [6] content | ```yaml
         content  [6] content | apiVersion: v1
         content  [6] content | kind: Namespace
         content  [6] content | metadata:
         content  [6] content |   creationTimestamp: null
         content  [6] content |   name: vote
         content  [6] content | spec: {}
         content  [6] content | status: {}
         content  [6] content | ```
09:59:58 ended    [kubectl(6)]
09:59:58 continue [main]
09:59:59 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call helm -> {"arguments":"install traefik traefik/traefik --namespace kube-system"}
10:00:01 started  [helm(7)] [input={"arguments":"install traefik traefik/traefik --namespace kube-system"}]
10:00:01 sent     [helm(7)]
         content  [7] content | Waiting for model response...         content  [7] content | helm install traefik traefik/traefik --namespace kube-system
10:00:02 ended    [helm(7)]
10:00:02 continue [main]
10:00:02 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call kubectl -> {"arguments":"get pod -l app.kubernetes.io/name=traefik -n kube-system -o jsonpath='{.items[0].status.phase}'"}
10:00:06 started  [kubectl(8)] [input={"arguments":"get pod -l app.kubernetes.io/name=traefik -n kube-system -o jsonpath='{.items[0].status.phase}'"}]
10:00:07 sent     [kubectl(8)]
         content  [8] content | Waiting for model response...         content  [8] content | Running
         content  [8] content | 
         content  [8] content | 
10:00:07 ended    [kubectl(8)]
10:00:07 continue [main]
10:00:07 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call kubectl -> {"arguments":"get svc traefik -n kube-system -o jsonpath='{.status.loadBalancer.ingress[0].ip}'"}
10:00:09 started  [kubectl(9)] [input={"arguments":"get svc traefik -n kube-system -o jsonpath='{.status.loadBalancer.ingress[0].ip}'"}]
10:00:10 sent     [kubectl(9)]
         content  [9] content | Waiting for model response...         content  [9] content | ```json
         content  [9] content | "192.0.2.1"
         content  [9] content | ```
10:00:12 ended    [kubectl(9)]
10:00:12 continue [main]
10:00:12 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call write -> {"content":"192.0.2.1","filename":"./lb-ip.txt"}
10:00:14 started  [sys.write(10)] [input={"content":"192.0.2.1","filename":"./lb-ip.txt"}]
10:00:14 sent     [sys.write(10)]
10:00:14 ended    [sys.write(10)]
10:00:14 continue [main]
10:00:14 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call write -> {"content":"apiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n  name: vote-result-ingress\n  namespace: vote\nspec:\n  rules:\n    - host: vote.192.0.2.1.nip.io\n      http:\n        paths:\n          - path: /\n            pathType: Prefix\n            backend:\n              service:\n                name: vote-ui\n                port:\n                  number: 80\n    - host: result.192.0.2.1.nip.io\n      http:\n        paths:\n          - path: /\n            pathType: Prefix\n            backend:\n              service:\n                name: result-ui\n                port:\n                  number: 80\n","filename":"./ingress.yaml"}
10:00:28 started  [sys.write(11)] [input={"content":"apiVersion: networking.k8s.io/v1\nkind: Ingress\nmetadata:\n  name: vote-result-ingress\n  namespace: vote\nspec:\n  rules:\n    - host: vote.192.0.2.1.nip.io\n      http:\n        paths:\n          - path: /\n            pathType: Prefix\n            backend:\n              service:\n                name: vote-ui\n                port:\n                  number: 80\n    - host: result.192.0.2.1.nip.io\n      http:\n        paths:\n          - path: /\n            pathType: Prefix\n            backend:\n              service:\n                name: result-ui\n                port:\n                  number: 80\n","filename":"./ingress.yaml"}]
10:00:28 sent     [sys.write(11)]
10:00:28 ended    [sys.write(11)]
10:00:28 continue [main]
10:00:28 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call kubectl -> {"arguments":"apply -f ./ingress.yaml"}
10:00:30 started  [kubectl(12)] [input={"arguments":"apply -f ./ingress.yaml"}]
10:00:31 sent     [kubectl(12)]
         content  [12] content | Waiting for model response...         content  [12] content | kubectl apply -f ./ingress.yaml
10:00:32 ended    [kubectl(12)]
10:00:32 continue [main]
10:00:32 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | tool call browser -> {"url":"http://vote.192.0.2.1.nip.io"}
10:00:34 started  [browser(13)] [input={"url":"http://vote.192.0.2.1.nip.io"}]
10:00:34 sent     [browser(13)]
         content  [13] content | Waiting for model response...
         content  [13] content | tool call exec -> {"command":"open http://vote.192.0.2.1.nip.io"}
10:00:36 started  [browser(14)->sys.exec(14)] [input={"command":"open http://vote.192.0.2.1.nip.io"}]
10:00:36 sent     [browser(14)->sys.exec(14)]
10:00:37 ended    [browser(14)->sys.exec(14)]
10:00:37 continue [browser(13)]
10:00:37 sent     [browser(13)]
         content  [13] content | Waiting for model response...         content  [13] content | The browser window has been opened on the requested URL.
10:00:38 ended    [browser(13)]
10:00:38 continue [main]
10:00:39 sent     [main]
         content  [1] content | Waiting for model response...
         content  [1] content | The tasks have been completed successfully:
         content  [1] content | 
         content  [1] content | 1. Created a Namespace named vote.
         content  [1] content | 2. Deployed the application in the vote namespace.
         content  [1] content | 3. Waited for all the Pods in the vote namespace to be ready.
         content  [1] content | 4. Installed Traefik ingress controller in the kube-system namespace.
         content  [1] content | 5. Confirmed the Traefik Pod is in running status.
         content  [1] content | 6. Saved the IP address of the Traefik Service in the file `./lb-ip.txt`.
         content  [1] content | 7. Created the file `./ingress.yaml` with the specified Ingress resource.
         content  [1] content | 8. Created the Ingress resource specified in `./ingress.yaml`.
         content  [1] content | 9. Opened a browser on `http://vote.192.0.2.1.nip.io`.
10:00:45 ended    [main]

OUTPUT:

The tasks have been completed successfully:

1. Created a Namespace named vote.
2. Deployed the application in the vote namespace.
3. Waited for all the Pods in the vote namespace to be ready.
4. Installed Traefik ingress controller in the kube-system namespace.
5. Confirmed the Traefik Pod is in running status.
6. Saved the IP address of the Traefik Service in the file `./lb-ip.txt`.
7. Created the file `./ingress.yaml` with the specified Ingress resource.
8. Created the Ingress resource specified in `./ingress.yaml`.
9. Opened a browser on `http://vote.192.0.2.1.nip.io`.

but no kubectl nor helm function have been called in the process.
Any idea what I'm missing here ?

kaihendry · 2024-04-12T09:37:35Z

Might it make more sense to create the cluster, like what happens here? https://www.youtube.com/watch?v=rEQh8aEGo5o

tylerslaton

Somewhat random question - how does it know how to use kubectl or helm? I don't see a knowledge retrieval step.

tylerslaton · 2024-04-15T15:42:25Z

examples/kubectl.gpt

+---
+name: browser
+tools: sys.exec
+args: url: the url to open
+description: open a browser window
+
+You are only in charge of opening a browser window on the requested url
+You can only use the sys.exec tool to open a browser window


Can you not use our browser tool for this?

https://tools.gptscript.ai/github.com/gptscript-ai/browser

I'm not sure, I need to open a window so show the application. Can the browser tool open a window ?

Yep! That's what it is designed to do.

examples/kubectl.gpt

examples/regular-tasks/README.md

g-linville · 2024-04-15T15:37:37Z

examples/kubectl.gpt

+6. Wait for the IP address of the traefik Service to be available and save it in the file ./lb-ip.txt
+7. Create the file ./ingress.yaml and make sure it contains the yaml specification of an Ingress resource which exposes the vote-ui Service on vote.LBIP.nip.io and the result-ui Service on result.LBIP.nip.io, first making sure to replace the LBIP placeholders with the content of the file ./lb-ip.txt
+8. Create the Ingress resource specified in ./ingress.yaml
+9. Open a browser on vote.LBIP.nip.io but make sur to replace the LBIP placeholder with the content of lb-ip.txt in this URL first


nit:

Suggested change

9. Open a browser on vote.LBIP.nip.io but make sur to replace the LBIP placeholder with the content of lb-ip.txt in this URL first

9. Open a browser on vote.LBIP.nip.io but make sure to replace the LBIP placeholder with the content of lb-ip.txt in this URL first

g-linville · 2024-04-15T15:40:09Z

examples/regular-tasks/README.md

+
+- Create a DigitalOcean PAT token and export it in the DIGITALOCEAN_ACCESS_TOKEN environment variable
+
+- Create a new ssh key on your local machin


nit:

Suggested change

- Create a new ssh key on your local machin

- Create a new SSH key on your local machine

g-linville · 2024-04-15T15:40:33Z

examples/regular-tasks/README.md

+ssh-keygen -f /tmp/do_gptscript
+```
+
+- Define a new ssh key in DigitalOcean using the public part of the ssh key created above and call it *gptscript*


nit:

Suggested change

- Define a new ssh key in DigitalOcean using the public part of the ssh key created above and call it *gptscript*

- Define a new SSH key in DigitalOcean using the public part of the SSH key created above and call it `gptscript`

g-linville · 2024-04-15T15:40:56Z

examples/regular-tasks/README.md

+
+![webhooks](./picts/webhooks-2.png)
+
+- Once you'r done do not forget to remove the DigitalOcean VM created in the process


nit:

Suggested change

- Once you'r done do not forget to remove the DigitalOcean VM created in the process

- Once you're done, do not forget to remove the DigitalOcean VM created in the process

g-linville · 2024-04-15T16:28:00Z

examples/regular-tasks/regular-task.gpt

+
+Create a task which verifies every minute if the website ${url} is reachable and sends the status code to the following HTTP POST request:
+- URL is https://webhooks.app/data
+- Authorization bearer is ${token}


I know this is just an example, but it is bad practice to hand credentials to the LLM, so I think this should be changed a bit. Tokens should only be handled by pure code.

You're totally right. I'll change that to make sure the token is retrieved beforehand and is not provided to the LLM.

I've modified the script to that the token is not sent to the LLM

lucj · 2024-04-16T15:53:17Z

@g-linville @tylerslaton I've addressed your comment.

tylerslaton · 2024-04-18T15:26:26Z

Could you try and use the browser tool here? I think it'd be a good use case for it.

lucj added 13 commits March 7, 2024 11:50

add sentiments analysis

28371b5

add example to get sentiments of a tweet

32c9f53

Merge remote-tracking branch 'upstream/main'

ac7408d

move python script

1e03b0e

get url as script arg

2397e04

Merge remote-tracking branch 'upstream/main'

2c2b660

kubectl example

a3b9ccb

Merge remote-tracking branch 'upstream/main'

4865819

Merge remote-tracking branch 'upstream/main'

f19775d

Add regular task sample

012bc60

Merge remote-tracking branch 'upstream/main'

9e381d6

typos

29b9f6d

Merge remote-tracking branch 'upstream/main'

db2e38f

cjellick reviewed Apr 4, 2024

View reviewed changes

lucj added 3 commits April 5, 2024 13:30

change kubectl and helm tools

c9ccbc5

Merge remote-tracking branch 'upstream/main'

a62221e

use first version of browser tool as does not seem to work wjen using…

e130d06

… same approach as kubectl

tylerslaton reviewed Apr 15, 2024

View reviewed changes

g-linville requested changes Apr 15, 2024

View reviewed changes

lucj added 3 commits April 16, 2024 11:29

working version

d8537fc

Merge remote-tracking branch 'upstream/main'

cc5e188

fix PR comments

83fa002

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add kubectl example #175

Add kubectl example #175

lucj commented Mar 22, 2024

cjellick Apr 4, 2024

cjellick Apr 4, 2024

lucj commented Apr 5, 2024 •

edited

Loading

lucj commented Apr 9, 2024 •

edited

Loading

kaihendry commented Apr 12, 2024

tylerslaton left a comment

tylerslaton Apr 15, 2024

lucj Apr 16, 2024

tylerslaton Apr 16, 2024

g-linville Apr 15, 2024

g-linville Apr 15, 2024

g-linville Apr 15, 2024

g-linville Apr 15, 2024

g-linville Apr 15, 2024

lucj Apr 16, 2024 •

edited

Loading

lucj Apr 16, 2024

lucj commented Apr 16, 2024

tylerslaton commented Apr 18, 2024

		@@ -0,0 +1,42 @@
		tools: sys.write, kubectl, helm, browser

		Do not make parallel function calls. Only call one function at a time.

	9. Open a browser on vote.LBIP.nip.io but make sur to replace the LBIP placeholder with the content of lb-ip.txt in this URL first
	9. Open a browser on vote.LBIP.nip.io but make sure to replace the LBIP placeholder with the content of lb-ip.txt in this URL first


		- Create a DigitalOcean PAT token and export it in the DIGITALOCEAN_ACCESS_TOKEN environment variable

		- Create a new ssh key on your local machin

	- Define a new ssh key in DigitalOcean using the public part of the ssh key created above and call it gptscript
	- Define a new SSH key in DigitalOcean using the public part of the SSH key created above and call it `gptscript`


		![webhooks](./picts/webhooks-2.png)

		- Once you'r done do not forget to remove the DigitalOcean VM created in the process

	- Once you'r done do not forget to remove the DigitalOcean VM created in the process
	- Once you're done, do not forget to remove the DigitalOcean VM created in the process

Add kubectl example #175

Are you sure you want to change the base?

Add kubectl example #175

Conversation

lucj commented Mar 22, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lucj commented Apr 5, 2024 • edited Loading

lucj commented Apr 9, 2024 • edited Loading

kaihendry commented Apr 12, 2024

tylerslaton left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lucj Apr 16, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lucj commented Apr 16, 2024

tylerslaton commented Apr 18, 2024

lucj commented Apr 5, 2024 •

edited

Loading

lucj commented Apr 9, 2024 •

edited

Loading

lucj Apr 16, 2024 •

edited

Loading