Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(workflow-v2.2.0): releasing workflow-v2.2.0(-e2e) #310

Merged
merged 3 commits into from
Jul 21, 2016

Conversation

smothiki
Copy link
Contributor

charts for v2.2.0. Tested by installing deis on v1.2.5 k8s cluster
There are some errors from deisrel which I manually corrected. Please take a closer look before giving LGTM

@smothiki smothiki added this to the v2.2 milestone Jul 20, 2016
@smothiki smothiki self-assigned this Jul 20, 2016
@@ -0,0 +1,5 @@
# Deis Router 2.0.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 2.2.0 -- deisrel error you mentioned @smothiki ?

@@ -0,0 +1,5 @@
[e2e]
org = "deisci"
dockerTag = "canary"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be tagged to a specific git tag

@bacongobbler
Copy link
Member

from grokking the chart it appears that there are 18 instances in workflow-v2.2.0 that are using the canary images. We should switch them to git tags. I'm aware that we know this internally, just posting publicly :)

@smothiki
Copy link
Contributor Author

@bacongobbler updated to git tags

[minio]
org = "deisci"
pullPolicy = "Always"
dockerTag = "canary"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

canary

@smothiki
Copy link
Contributor Author

Fixed

@bacongobbler
Copy link
Member

Awesome. Back to testing!

@bacongobbler
Copy link
Member

bacongobbler commented Jul 20, 2016

Both @mboersma and I are hanging for a very long time when we attempt to uninstall workflow-v2.2.0 from our cluster:

Uninstall the listed objects? (y/N) y
---> Running `kubectl delete` ...
---> service "deis-builder" deleted

---> service "deis-controller" deleted

---> service "deis-database" deleted

[WARN] Not uninstalling Service deis-logger-redis because of "helm-keep" annotation.
---> Use kubectl to uninstall keeper manifests.

---> service "deis-logger" deleted

---> service "deis-minio" deleted

---> service "deis-monitor-grafana" deleted

---> service "deis-monitor-influxapi" deleted

---> service "deis-monitor-influxui" deleted

---> service "deis-nsqd" deleted

[WARN] Not uninstalling Service deis-registry because of "helm-keep" annotation.
---> Use kubectl to uninstall keeper manifests.

[WARN] Not uninstalling Service deis-router because of "helm-keep" annotation.
---> Use kubectl to uninstall keeper manifests.

---> service "deis-workflow-manager" deleted

---> replicationcontroller "deis-builder" deleted

---> replicationcontroller "deis-controller" deleted

---> replicationcontroller "deis-database" deleted

---> replicationcontroller "deis-logger" deleted

---> replicationcontroller "deis-logger-redis" deleted

---> replicationcontroller "deis-minio" deleted

---> replicationcontroller "deis-monitor-grafana" deleted

---> replicationcontroller "deis-monitor-influxdb" deleted

---> replicationcontroller "deis-nsqd" deleted

---> replicationcontroller "deis-registry" deleted

---> replicationcontroller "deis-router" deleted

---> replicationcontroller "deis-workflow-manager" deleted

---> daemonset "deis-logger-fluentd" deleted

---> daemonset "deis-monitor-telegraf" deleted

The problem seems to be coming from the reigstry-proxy as everything zips by as soon as it's removed.

---> daemonset "registry-proxy" deleted

---> secret "builder-ssh-private-keys" deleted

---> secret "builder-key-auth" deleted

---> secret "django-secret-key" deleted

---> secret "database-creds" deleted

[WARN] Not uninstalling Secret logger-redis-creds because of "helm-keep" annotation.
---> Use kubectl to uninstall keeper manifests.

---> secret "objectstorage-keyfile" deleted

---> secret "deis-router-dhparam" deleted

---> serviceaccount "deis-builder" deleted

---> serviceaccount "deis-controller" deleted

---> serviceaccount "deis-database" deleted

---> serviceaccount "deis-logger-fluentd" deleted

---> serviceaccount "deis-logger" deleted

---> serviceaccount "deis-minio" deleted

---> serviceaccount "deis-monitor-telegraf" deleted

---> serviceaccount "deis-nsqd" deleted

---> serviceaccount "deis-registry" deleted

---> serviceaccount "deis-router" deleted

---> serviceaccount "deis-workflow-manager" deleted

[WARN] Not uninstalling Namespace deis because of "helm-keep" annotation.
---> Use kubectl to uninstall keeper manifests.

---> Done

Total time is ~2 minutes in comparison to the old ~15 seconds.


[minio]
org = "deisci"
pullPolicy = "Always"
Copy link
Member

@mboersma mboersma Jul 20, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be changed to:
pullPolicy = "IfNotPresent"

arschles pushed a commit to arschles/deis-workflow that referenced this pull request Jul 20, 2016
…arts

as discussed at
deis/charts#310 (comment), the
herein-removed deisrel command for generating new helm charts may have
a bug.

Since I don’t believe it’s too hard to manually go change the params
files, this PR changes instructions to indicate that the files should
be manually edited
@kmala kmala added the LGTM2 label Jul 21, 2016
@mboersma mboersma merged commit d4dfe7b into master Jul 21, 2016
@mboersma mboersma deleted the release-v2.2.0 branch July 21, 2016 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants