Summary:
When I run anvil with minikube config, it does not throw an error, and applies kubectl commands, which doesn't supposed to happen.
Expected behavior:
If the minikube profile does not exist, it should not start the anvil server, and throw an error.
Actual behavior:
It starts the anvil server, and also applies kubectl commands, which shouldn't be applied.
Steps to reproduce:
- In config.json, change driver to minikube
- If there are running minikube profiles, stop them.
- Run Anvil on the main branch, by go run .
Zetaforge version:
0.3.2
Operating System
MacOs
Other operating system:
No response
Logs:
2024/08/20 16:43:58 Starting Setup...
2024/08/20 16:43:58 Resource Namespace argo applied
2024/08/20 16:43:58 Resource CustomResourceDefinition clusterworkflowtemplates.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition cronworkflows.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workflowartifactgctasks.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workfloweventbindings.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workflows.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workflowtaskresults.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workflowtasksets.argoproj.io applied
2024/08/20 16:43:58 Resource CustomResourceDefinition workflowtemplates.argoproj.io applied
2024/08/20 16:43:58 Resource ServiceAccount argo applied
2024/08/20 16:43:58 Resource ServiceAccount argo-server applied
2024/08/20 16:43:58 Resource Role argo-role applied
2024/08/20 16:43:59 Resource ClusterRole argo-aggregate-to-admin applied
2024/08/20 16:43:59 Resource ClusterRole argo-aggregate-to-edit applied
2024/08/20 16:43:59 Resource ClusterRole argo-aggregate-to-view applied
2024/08/20 16:43:59 Resource ClusterRole argo-cluster-role applied
2024/08/20 16:43:59 Resource ClusterRole argo-server-cluster-role applied
2024/08/20 16:44:00 Resource RoleBinding argo-binding applied
2024/08/20 16:44:00 Resource ClusterRoleBinding argo-binding applied
2024/08/20 16:44:00 Resource ClusterRoleBinding argo-server-binding applied
2024/08/20 16:44:00 Resource ConfigMap workflow-controller-configmap applied
2024/08/20 16:44:00 Resource Service argo-server applied
2024/08/20 16:44:01 Resource PriorityClass workflow-controller applied
2024/08/20 16:44:01 Resource Deployment argo-server applied
2024/08/20 16:44:01 Resource Deployment workflow-controller applied
2024/08/20 16:44:01 Resource ServiceAccount executor applied
2024/08/20 16:44:01 Resource Role executor applied
2024/08/20 16:44:01 Resource RoleBinding executor-binding applied
2024/08/20 16:44:01 Resource Secret weed-secret applied
2024/08/20 16:44:01 Resource ConfigMap forge-bucket applied
2024/08/20 16:44:01 Resource ConfigMap seaweed-config applied
2024/08/20 16:44:01 Resource Deployment weed applied
2024/08/20 16:44:01 Resource Service weed applied
2024/08/20 16:44:01 Setup Successful
[GIN-debug] GET /ping --> main.main.func3 (4 handlers)
[GIN-debug] POST /execute --> main.main.func4 (4 handlers)
[GIN-debug] GET /rooms --> main.main.func5 (4 handlers)
[GIN-debug] GET /ws/:room --> main.main.func6 (4 handlers)
[GIN-debug] POST /build-context-status --> main.main.func7 (4 handlers)
[GIN-debug] GET /execution/running --> main.main.func8 (4 handlers)
[GIN-debug] GET /execution/:executionId/log --> main.main.func9 (4 handlers)
[GIN-debug] POST /execution/:executionId/terminate --> main.main.func10 (4 handlers)
[GIN-debug] POST /pipeline --> main.main.func11 (4 handlers)
[GIN-debug] GET /pipeline/list --> main.main.func12 (4 handlers)
[GIN-debug] GET /pipeline/filter --> main.main.func13 (4 handlers)
[GIN-debug] DELETE /pipeline/:uuid/:hash --> main.main.func14 (4 handlers)
[GIN-debug] PATCH /pipeline/:uuid/:hash/deploy --> main.main.func15 (4 handlers)
[GIN-debug] GET /pipeline/:uuid/list --> main.main.func16 (4 handlers)
[GIN-debug] GET /pipeline/:uuid/:hash/:index --> main.main.func17 (4 handlers)
[GIN-debug] GET /pipeline/:uuid/:hash/list --> main.main.func18 (4 handlers)
[GIN-debug] POST /pipeline/:uuid/:hash/stop --> main.main.func19 (4 handlers)
[GIN-debug] POST /pipeline/:uuid/:hash/execute --> main.main.func20 (4 handlers)
[GIN-debug] DELETE /pipeline/:uuid/:hash/:index --> main.main.func21 (4 handlers)
[GIN-debug] [WARNING] You trusted all proxies, this is NOT safe. We recommend you to set a value.
Please check https://pkg.go.dev/github.com/gin-gonic/gin#readme-don-t-trust-all-proxies for details.
[GIN-debug] Listening and serving HTTP on :8080
Forwarding from 127.0.0.1:8333 -> 8333
Forwarding from [::1]:8333 -> 8333
Recording:
No response
Anything else?:
No response
Summary:
When I run anvil with minikube config, it does not throw an error, and applies kubectl commands, which doesn't supposed to happen.
Expected behavior:
If the minikube profile does not exist, it should not start the anvil server, and throw an error.
Actual behavior:
It starts the anvil server, and also applies kubectl commands, which shouldn't be applied.
Steps to reproduce:
Zetaforge version:
0.3.2
Operating System
MacOs
Other operating system:
No response
Logs:
Recording:
No response
Anything else?:
No response