feat: implement working reconciliation logic and documentation

initial commit for working reconciliation logic, no automated test only manually tested for now

config/samples/gitea_v1alpha1_runnergroup.yaml

@@ -1,3 +1,16 @@
+apiVersion: v1
+kind: Secret
+metadata:
+  name: gitea-credentials
+  labels:
+    app.kubernetes.io/name: gitea-runner-operator
+    app.kubernetes.io/managed-by: kustomize
+stringData:
+  # The Gitea API Token (for the Operator to poll for jobs)
+  auth-token: "MMUCFRXCbofYn2L0aT2OP2aug7JhChNJlULKNLgg"
+  # The Runner Registration Token (for the Runner to register itself)
+  registration-token: "5r4lpLA9rKCZZEHyUyKHeA187DoaElcTBySITRRi"
+---
 apiVersion: gitea.bpg.pw/v1alpha1
 kind: RunnerGroup
 metadata:
@@ -6,4 +19,29 @@ metadata:
     app.kubernetes.io/managed-by: kustomize
   name: runnergroup-sample
 spec:
-  # TODO(user): Add fields here
+  # The base URL of your Gitea instance
+  giteaURL: "https://gitea.bpg.pw"
+
+  # Scope of the runners (global, org, or repo)
+  scope: "org"
+  #org: "bapungorg" # Required if scope is 'org' or 'repo'; cannot be used with user
+  user: "bapung" # Required if scope is 'user' or 'repo'; cannot be used with org
+  #repo: "dummy-service-workflow" # Required if scope is 'repo'
+
+  # Labels to identify this runner group
+  labels:
+    - "linux"
+    - "amd64"
+
+  # Maximum number of runners to spawn concurrently
+  maxActiveRunners: 5
+
+  # Reference to the Secret containing the API token
+  authToken:
+    name: gitea-credentials
+    key: auth-token
+
+  # Reference to the Secret containing the Registration token
+  registrationToken:
+    name: gitea-credentials
+    key: registration-token