[tbs.devenv] Slavina to setup the development environment
Closed, ResolvedPublic5 Estimated Story Points
Actions

Assigned To

Authored By

	dcaro
	Aug 30 2022, 1:39 PM

Description

Follow the instructions in https://github.com/toolforge/buildservice and setup the dev environment.

This might be extra tricky as the current setup has been done only on linux and k8s needs to access docker started
containers.

Status	Assigned	Task
Stalled	LucasWerkmeister	T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes
Stalled	matmarex	T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes
Open	None	T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes
Open	None	T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes
Open	dcaro	T194332 [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs
In Progress	dcaro	T267374 [tbs.beta] Create a toolforge build service beta release
Resolved	Slst2020	T316656 [tbs.devenv] Slavina to setup the development environment

dcaro triaged this task as High priority.Aug 30 2022, 1:39 PM

dcaro created this task.

Slst2020 changed the task status from Open to In Progress.Aug 30 2022, 2:21 PM

Slst2020 moved this task from To Do to Doing on the User-Slst2020 board.

I will try to set up everything directly in minikube, instead of having Harbor run on Docker for Desktop with docker-compose

Harbor runs just fine in minikube. The setup scripts can no longer be used as-is though, so I still need to figure that out.

KHernandez-WMF set the point value for this task to 5.

I needed to create and deploy the Tekton CRDs in two steps; otherwise, everything went fine.

$ HARBOR_IP=192.168.59.1 kubectl apply -k deploy/base-tekton
$ HARBOR_IP=192.168.59.1 kubectl apply -k deploy/devel