You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Let me describe a high view sequence of my commands...
I've installed the workflow with helm, created two apps, made some git push at these apps, deleted the release, deleted the namespace because of Error: secrets "builder-key-auth" already exists, deleted the registry, database and builder s3 buckets because of the below deis-controller logs and finally reinstalled the workflow to the cluster with all necessary deis configuration.
Is there any way I could attach the running apps (started from the old release) to this new release so I could do deis apps and see them?
$ kubectl -n deis logs deis-controller-3875226455-sz1p8 -f
system information:
Django Version: 1.10.6
Python 3.5.2
Django checks:
System check identified no issues (2 silenced).
Health Checks:
Checking if database is alive
There was a problem connecting to the database
FATAL: password authentication failed for user "XXXXXXXXXXXXXXX"
The text was updated successfully, but these errors were encountered:
Let me describe a high view sequence of my commands...
I've installed the workflow with
helm
, created two apps, made somegit push
at these apps, deleted the release, deleted the namespace because ofError: secrets "builder-key-auth" already exists
, deleted the registry, database and builder s3 buckets because of the belowdeis-controller
logs and finally reinstalled the workflow to the cluster with all necessary deis configuration.Is there any way I could attach the running apps (started from the old release) to this new release so I could do
deis apps
and see them?The text was updated successfully, but these errors were encountered: