Running with gitlab-runner 13.0.0-rc2 (926834bc)
  on docker-auto-scale 72989761
section_start:1590090305:prepare_executor
Preparing the "docker+machine" executor
Using Docker executor with image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.15.0 ...
Pulling docker image registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.15.0 ...
Using docker image sha256:93c7f924bc641f744a2ea17f02bfeeb23403a531c459d1471dd50037e274922e for registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v0.15.0 ...
section_end:1590090371:prepare_executor
section_start:1590090371:prepare_script
Preparing environment
Running on runner-72989761-project-4422333-concurrent-0 via runner-72989761-stg-srm-1590090305-1442b206...
section_end:1590090375:prepare_script
section_start:1590090375:get_sources
Getting source from Git repository
$ eval "$CI_PRE_CLONE_SCRIPT"
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/gitlab-org/monitor/monitor-sandbox/.git/
Created fresh repository.
From https://ci-api.gstg.gitlab.net/gitlab-org/monitor/monitor-sandbox
 * [new ref]         refs/pipelines/12776647 -> refs/pipelines/12776647
 * [new branch]      master                  -> origin/master
Checking out 314c35cf as master...

Skipping Git submodules setup
section_end:1590090377:get_sources
section_start:1590090377:restore_cache
Restoring cache
section_end:1590090378:restore_cache
section_start:1590090378:download_artifacts
Downloading artifacts
section_end:1590090380:download_artifacts
section_start:1590090380:build_script
Running before_script and script
$ auto-deploy check_kube_domain
$ auto-deploy download_chart
Creating /root/.helm 
Creating /root/.helm/repository 
Creating /root/.helm/repository/cache 
Creating /root/.helm/repository/local 
Creating /root/.helm/plugins 
Creating /root/.helm/starters 
Creating /root/.helm/cache/archive 
Creating /root/.helm/repository/repositories.yaml 
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 
Adding local repo with URL: http://127.0.0.1:8879/charts 
$HELM_HOME has been configured at /root/.helm.
Not installing Tiller due to 'client-only' flag having been set
"gitlab" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused
...Successfully got an update from the "gitlab" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/
Deleting outdated charts
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):
	Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: connect: connection refused
...Successfully got an update from the "gitlab" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
Saving 1 charts
Downloading postgresql from repo https://kubernetes-charts.storage.googleapis.com/
Deleting outdated charts
$ auto-deploy ensure_namespace
NAME                                   STATUS   AGE
monitor-sandbox-4422333-dast-default   Active   204d
$ auto-deploy initialize_tiller
Checking Tiller...
Tiller is listening on localhost:44134
Client: &version.Version{SemVer:"v2.16.6", GitCommit:"dd2e5695da88625b190e6b22e9542550ab503a47", GitTreeState:"clean"}
[debug] SERVER: "localhost:44134"

Kubernetes: &version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.10-gke.36", GitCommit:"34a615f32e9a0c9e97cdb9f749adb392758349a6", GitTreeState:"clean", BuildDate:"2020-04-06T16:33:17Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}
Server: &version.Version{SemVer:"v2.16.6", GitCommit:"dd2e5695da88625b190e6b22e9542550ab503a47", GitTreeState:"clean"}

$ auto-deploy create_secret
Create secret...
$ auto-deploy deploy
Release "dast-default-postgresql" has been upgraded.
LAST DEPLOYED: Thu May 21 19:46:38 2020
NAMESPACE: monitor-sandbox-4422333-dast-default
STATUS: DEPLOYED

RESOURCES:
==> v1/Pod(related)
NAME                       READY  STATUS   RESTARTS  AGE
dast-default-postgresql-0  1/1    Running  0         2m17s

==> v1/Secret
NAME                     TYPE    DATA  AGE
dast-default-postgresql  Opaque  1     2m16s

==> v1/Service
NAME                              TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)   AGE
dast-default-postgresql           ClusterIP  10.12.14.113  <none>       5432/TCP  2m16s
dast-default-postgresql-headless  ClusterIP  None          <none>       5432/TCP  2m16s

==> v1/StatefulSet
NAME                     READY  AGE
dast-default-postgresql  1/1    2m16s


NOTES:
** Please be patient while the chart is being deployed **

PostgreSQL can be accessed via port 5432 on the following DNS name from within your cluster:

    dast-default-postgresql.monitor-sandbox-4422333-dast-default.svc.cluster.local - Read/Write connection

To get the password for "user" run:

    export POSTGRES_PASSWORD=$(kubectl get secret --namespace monitor-sandbox-4422333-dast-default dast-default-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)

To connect to your database run the following command:

    kubectl run dast-default-postgresql-client --rm --tty -i --restart='Never' --namespace monitor-sandbox-4422333-dast-default --image docker.io/bitnami/postgresql:9.6.16 --env="PGPASSWORD=$POSTGRES_PASSWORD" --command -- psql --host dast-default-postgresql -U user -d dast-default -p 5432



To connect to your database from outside the cluster execute the following commands:

    kubectl port-forward --namespace monitor-sandbox-4422333-dast-default svc/dast-default-postgresql 5432:5432 &
    PGPASSWORD="$POSTGRES_PASSWORD" psql --host 127.0.0.1 -U user -d dast-default -p 5432

WARNING: Rolling tag detected (bitnami/postgresql:9.6.16), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/

secret "dast-default-secret" deleted
secret/dast-default-secret replaced
No helm values file found at '.gitlab/auto-deploy-values.yaml'
Deploying new stable release...
Release "dast-default" has been upgraded.
LAST DEPLOYED: Thu May 21 19:46:43 2020
NAMESPACE: monitor-sandbox-4422333-dast-default
STATUS: DEPLOYED

RESOURCES:
==> v1/Deployment
NAME          READY  UP-TO-DATE  AVAILABLE  AGE
dast-default  1/1    1           1          2m13s

==> v1/Pod(related)
NAME                           READY  STATUS       RESTARTS  AGE
dast-default-66497cc7d8-v7w8m  1/1    Running      0         17s
dast-default-7f9c5f998c-h6dn8  0/1    Terminating  0         2m13s

==> v1/Service
NAME                      TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)   AGE
dast-default-auto-deploy  ClusterIP  10.12.13.108  <none>       5000/TCP  2m13s

==> v1beta1/Ingress
NAME                      HOSTS                                                                         ADDRESS        PORTS    AGE
dast-default-auto-deploy  dast-4422333-dast-default.34.67.11.220.nip.io,le-4422333.34.67.11.220.nip.io  35.222.156.35  80, 443  2m13s


NOTES:
Application should be accessible at

    http://dast-4422333-dast-default.34.67.11.220.nip.io
deployment "dast-default" successfully rolled out
$ auto-deploy persist_environment_url
section_end:1590090421:build_script
section_start:1590090421:after_script
Running after_script
section_end:1590090423:after_script
section_start:1590090423:archive_cache
Saving cache
section_end:1590090424:archive_cache
section_start:1590090424:upload_artifacts_on_success
Uploading artifacts for successful job
Uploading artifacts...
environment_url.txt: found 1 matching files        
Uploading artifacts to coordinator... ok            id=37227566 responseStatus=201 Created token=D-MAvsFf
section_end:1590090428:upload_artifacts_on_success
Job succeeded