deploy k8s-topgun worker from the main pipeline

[cirocosta]

Hey,

After #191, we now target a k8s-topgun-tagged worker in the main pipeline, but it turns out that there's no where in ci.concourse-ci.org where that worker gets automatically updated.

ps.: we already do something similar for the pks worker that we have deployed in prod-pks-worker-deployment:

ci/pipelines/concourse.yml

Lines 1188 to 1207 in 2a811fa

	- put: prod-pks-worker-deployment
	inputs: [cbd, concourse-release, vsphere-xenial-stemcell, prod]
	tags: [pks]
	params:
	manifest: cbd/cluster/external-worker.yml
	stemcells:
	- vsphere-xenial-stemcell/*.tgz
	releases:
	- concourse-release/*.tgz
	ops_files:
	- prod/pks-worker/ops.yml
	vars_files:
	- cbd/versions.yml
	vars:
	azs: [default]
	deployment_name: prod-external-worker
	external_worker_network_name: default
	instances: 1
	tsa_host: ci.concourse-ci.org
	worker_vm_type: medium.disk

Thanks!

[jamieklassen]

Before I forget, I want to mention that the topgun worker used for the bosh-topgun-* jobs should be automatically upgraded too. Also the darwin worker...

[taylorsilva]

I'm picking this up because I need it to get feedback about the rest of my work 😅

[taylorsilva]

Worker is alive on the topgun cluster on GKE

$ kubectl get pods -n ci-topgun-worker
NAME                        READY   STATUS    RESTARTS   AGE
ci-topgun-worker-worker-0   1/1     Running   0          105s

$ fly -t nci workers
name             containers  platform  tags        team                   state    version
...
ci-topgun-worker-0            0           linux     k8s-topgun  none                   running  2.2
...

Need to have to auto re-deploy somewhere now.

[taylorsilva]

To manually redeploy this worker check out the work on this branch: https://github.com/concourse/hush-house/tree/ci-topgun-worker
PR to merge this branch in: concourse/hush-house#90

Will eventually add something in CI so this worker is updated when CI is updated. May try to use this resource to deploy the helm chart.

[taylorsilva]

Work to get the k8s-topgun worker deploying through ci is being done on the deploy-ci-topgun-worker branch in ci

https://github.com/concourse/ci/tree/deploy-ci-topgun-worker

Edit: Realized this work is related to concourse/prod#45, since both tasks want to deploy charts within the hush-house repo. Work on that task appears to be paused.

[jamieklassen]

Regardless of whether prod deploys continuously, we should really think carefully about the automation that does deploy it -- there should be a single button that deploys all of ci's web pods, worker pods, PR worker pods, windows worker, Darwin worker, topgun worker and k8s-topgun worker. This kinda implies a single source of truth for the version of Concourse deployed in all these environments.

[jamieklassen]

blocked on concourse/prod#45 - I expect the configuration for the various worker pools to move during the course of that issue.

[taylorsilva]

The work done on this issue so far assumes that the bosh-prod-deploy job will still be the job that deploys prod, just renamed to prod-deploy instead.

[github-actions]

This issue has had no activity for a while. It has been labeled stale, and will be closed in one week.