added k3s support for RPi cluster #83
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@stevef1uk is attempting to deploy a commit to the RowBoat Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have run this on my RPi cluster successfully. I have tried to isolate this as much as possible from the core code base. The AI only changed one source file.
In testing this locally I wasted a lot of time as the Example Agent is not being automatically updated to call the Agents I generated so I thought this was a bug and spent hours trying to fix it without success. Eventually I realised after watching your video more carefully that this could be done through CoPilot :-)
I have updated the README to explain how someone else can try this. There will be a need to edit the kubernetes files. I didn't write a clever shell script to do that. Sorry! It really needs someone else to run it on a clean cluster as though I didi clean it out I am using it for other services so I couldn't delete it & recreate. As my cluster is public I have tested this using port-forwarding and added a couple of scripts in the k8s/arm64 directory to set this up & tear it down.