You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/concepts/workspaces/workspace-initialization.md
+153-4Lines changed: 153 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,156 @@ You can use this url to construct a kubeconfig for your controller. To do so, us
95
95
96
96
### Code Sample
97
97
98
-
* It is important to use the kcp-dev controller runtime fork, as regular controller runtime is not able to deal with all logical clusters being name "cluster"
99
-
* LogicalClusters cannot updated using update api, but must be updated using patch api
100
-
101
-
// TODO paste in sample once it is finished
98
+
When writing a custom initializer, the following needs to be taken into account:
99
+
100
+
* You need to use the kcp-dev controller-runtime fork, as regular controller-runtime is not able to work as under the hood all LogicalClusters have the sam name
101
+
* You need to update LogicalClusters using patches; They cannot be updated using the update api
102
+
103
+
Keeping this in mind, you can use the following example as a starting point for your intitialization controller
0 commit comments