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
{{ message }}
This repository was archived by the owner on Dec 16, 2025. It is now read-only.
tilt-up: env-vars-for-wl-cluster $(ENVSUBST)$(KUBECTL)$(KUSTOMIZE)$(TILT) cluster ## Start a mgt-cluster & Tilt. Installs the CRDs and deploys the controllers
574
577
EXP_CLUSTER_RESOURCE_SET=true $(TILT) up --port=10351
Copy file name to clipboardExpand all lines: docs/develop.md
+3-23Lines changed: 3 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,32 +24,12 @@ make tilt-up
24
24
25
25
> To access the Tilt UI please go to: `http://localhost:10351`
26
26
27
-
You should make sure that everything in the UI looks green. If not, you can trigger the Tilt workflow again. To establish a connection to your OpenStack project, you must supply a secret containing the `clouds.yaml` file.
To transfer the credentials stored in the secret mentioned above to the operator, the user must create an `OpenStackClusterStackReleaseTemplate` object and specify this secret in the `identityRef` field. The `clouds.yaml` file may contain one or more clouds, so the user must specify desired connection to a specific cloud by using the `cloudName` field. Refer to the `examples/cspotemplate.yaml` file for more details. Afterward, apply this template to the local Kind cluster, which was built by the previous `make` command.
Now, proceed to apply the `ClusterStack` to the local Kind cluster. For more details see `examples/clusterstack.yaml`.
40
-
41
-
```bash
42
-
kubectl apply -f <path-to-openstack-clusterstack>
43
-
```
44
-
45
-
Please be patient and wait for the operator to execute the necessary tasks. In case your `ClusterStack` object encounters no errors and `openstacknodeimagereleases` is ready, you can deploy a workload cluster. This could be done by applying cluster-template. See the example of this template in `examples/cluster.yaml`.
46
-
47
-
```bash
48
-
kubectl apply -f <path-to-cluster-template>
49
-
```
27
+
You should make sure that everything in the UI looks green. If not, you can trigger the Tilt workflow again. In the case of the `cspotemplate`, this might be necessary, as it cannot be applied right after the startup of the cluster and fails. Tilt unfortunately does not include a waiting period.
50
28
51
29
In case you want to change some code, you can do so and see that Tilt triggers on save. It will update the container of the operator automatically.
52
30
31
+
If you want to change something in your ClusterStack or Cluster custom resources, you can have a look at `.cluster`.yaml and `.clusterstack.yaml`, which Tilt uses.
32
+
53
33
To tear down the workload cluster press the "Delete Workload Cluster" button. After a few minutes, the resources should be deleted.
0 commit comments