cirocosta

---
apiVersion: v1
kind: Namespace
metadata:
  name: git-serve-controller
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: git-serve-controller

cirocosta

#!/bin/bash

set -o errexit

main () {
	local stats_collector_pid

	make_all_jobs_active
	login

cirocosta

# run a server
./a.out -server

# run a client
./a.out

# see that the server does not finish writing right away

cirocosta

diff --git a/atc/atccmd/command.go b/atc/atccmd/command.go
index e33d9eee8..cd7006969 100644
--- a/atc/atccmd/command.go
+++ b/atc/atccmd/command.go
@@ -11,6 +11,7 @@ import (
 	_ "net/http/pprof"
 	"net/url"
 	"os"
+	"runtime"
 	"strings"

cirocosta

a

cirocosta

trying it out

There are two ways of trying this out:

local build

As long as you have access to a cluster, you can get Concourse to run workloads there.

cirocosta

a

cirocosta

#!/bin/bash

set -o errexit
set -o xtrace

main() {
        local namespaces=$(list_namespaces)

        for namespace in $namespaces; do
                local tasks=$(list_tasks $namespace)

cirocosta

#!/bin/bash

set -o errexit

main() {
        case $1 in
        run)
                prepare_fs

                empty

cirocosta

1. get `apiserver` to allow privileged

the flag `--allow-privileged` in `kube-apiserver` 
(https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) 
is not set to `true` by default.

concourse workers need to run as privileged though.

to configure that flag, modify `/var/snap/microk8s/current/args/kube-apiserver` adding
that flag.