github org renamed : Intreecom ⟶ Treetscom

.github/workflows/release.yaml

@@ -35,7 +35,7 @@ jobs:
           file: ./Dockerfile
           platforms: linux/amd64 # ,linux/arm64,linux/arm/v7  (uncomment once the fix for long builds is found).
           push: true
-          tags: ghcr.io/intreecom/robotlb:latest,ghcr.io/intreecom/robotlb:${{ github.ref_name }}
+          tags: ghcr.io/treetscom/robotlb:latest,ghcr.io/treetscom/robotlb:${{ github.ref_name }}
 
   upload_helm:
     runs-on: ubuntu-latest
@@ -53,6 +53,6 @@ jobs:
           helm package --app-version "${{ github.ref_name }}" --dependency-update ./helm
           helm show chart *.tgz
           helm registry login -u ${{ github.actor }} -p ${{ secrets.GITHUB_TOKEN }} ghcr.io
-          helm push *.tgz oci://ghcr.io/intreecom/charts
+          helm push *.tgz oci://ghcr.io/treetscom/charts
         env:
           HELM_EXPERIMENTAL_OCI: 1

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Intree
+Copyright (c) 2026 Treets
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -23,10 +23,10 @@ If you meet all the requirements, you can deploy `robotlb`.
 The recommended way to deploy this operator is using the Helm chart.
 
 ```bash
-helm show values oci://ghcr.io/intreecom/charts/robotlb > values.yaml
+helm show values oci://ghcr.io/treetscom/charts/robotlb > values.yaml
 # Edit values.yaml to suit your needs
 # Set `envs.ROBOTLB_HCLOUD_TOKEN`.
-helm install robotlb oci://ghcr.io/intreecom/charts/robotlb -f values.yaml
+helm install robotlb oci://ghcr.io/treetscom/charts/robotlb -f values.yaml
 ```
 
 After the chart is installed, you should be able to create `LoadBalancer` services.
@@ -142,4 +142,4 @@ spec:
 
 ## Star History
 
-[![Star History Chart](https://api.star-history.com/svg?repos=Intreecom/robotlb&type=Date)](https://star-history.com/#Intreecom/robotlb&Date)
+[![Star History Chart](https://api.star-history.com/svg?repos=Treetscom/robotlb&type=Date)](https://star-history.com/#Treetscom/robotlb&Date)

helm/templates/NOTES.txt

@@ -1,4 +1,4 @@
 The RobotLB Operator was successfully installed.
 Please follow the readme to create loadbalanced services.
 
-README: https://github.com/intreecom/robotlb
+README: https://github.com/treetscom/robotlb

helm/values.yaml

@@ -3,7 +3,7 @@
 # Declare variables to be passed into your templates.
 
 image:
-  repository: ghcr.io/intreecom/robotlb
+  repository: ghcr.io/treetscom/robotlb
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
   tag: ""

tutorial.md

@@ -347,7 +347,7 @@ After you have chosen the subnet, Hetzner will give you the gateway address that
 Let's log in to our robot servers by their public IPs and set up private networking interfaces. I won't be using the `ip` command as suggested in a hint by Hetzner, instead, I will be using `netplan` to make my interface setup persistent.
 
 ```bash
-ssh intree-prod-kube-agent-1
+ssh treets-prod-kube-agent-1
 vim /etc/netplan/01-netcfg.yaml
 ```
 
@@ -447,7 +447,7 @@ Once the cluster is ready, we can deploy our RobotLB. Before that, create an hcl
 
 ```bash
 helm install robotlb  \
-    oci://ghcr.io/intreecom/charts/robotlb \
+    oci://ghcr.io/treetscom/charts/robotlb \
     --set envs.ROBOTLB_HCLOUD_TOKEN="<hcloud token>" \
     --namespace robotlb \
     --create-namespace \