-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: improve garm-provider dev setup and adjust docs for new garm v0.1.5 #78
base: main
Are you sure you want to change the base?
Conversation
e2cb200
to
d4ca9da
Compare
d4ca9da
to
63189f9
Compare
@@ -0,0 +1,108 @@ | |||
# nonk8s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does nonk8s
mean here?
* **Repository permissions**: | ||
* `Administration: Read & write` - needed to generate JIT config/registration token, remove runners, etc. | ||
* `Metadata: Read-only` - automatically enabled by above | ||
* `Webhooks: Read & write` - needed to install webhooks on repositories |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Webhook permissions aren't required yet, as it's not implemented on the operator
* `Webhooks: Read & write` - needed to install webhooks on repositories | ||
* **Organization permissions**: | ||
* `Self-hosted runners: Read & write` - needed to manage runners in an organization | ||
* `Webhooks: Read & write` - needed to install webhooks on organizations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Webhook permissions aren't required yet, as it's not implemented on the operator
@@ -3,8 +3,7 @@ | |||
.idea | |||
/bin/ | |||
/hack/bin/garm-provider-k8s | |||
/hack/local-development/kubernetes/configmap.yaml | |||
/hack/local-development/kubernetes/garm-operator-all.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really want to track the garm-operator-all.yaml
in this repo?
We just fetch the file from the operator repo and it's only needed during development-face (which is then covered by our development description)
fixes #71
see title