Closed dennyzhang closed 6 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/158447865
The labels on this github issue will be updated when the story is started.
Made below changes. Run ./deploy.sh again.
Looks like it starts. Not sure about the consequence yet.
diff --git a/deploy.sh b/deploy.sh
index 9ed8194..604e977 100755
--- a/deploy.sh
+++ b/deploy.sh
@@ -25,9 +25,9 @@ function patch_objects {
patch='{"spec": {"template": {"metadata": {"labels": {"randomversion": "'$RANDOM'"}}}}}'
kubectl patch statefulset log-cache --namespace oratos --patch "$patch"
kubectl patch deployment log-cache-nozzle --namespace oratos --patch "$patch"
- kubectl patch deployment syslog-nozzle --namespace oratos --patch "$patch"
+ # kubectl patch deployment syslog-nozzle --namespace oratos --patch "$patch"
kubectl patch deployment log-cache-scheduler --namespace oratos --patch "$patch"
- kubectl patch deployment loggregator-emitter --namespace oratos --patch "$patch"
+ #kubectl patch deployment loggregator-emitter --namespace oratos --patch "$patch"
kubectl patch deployment loggregator-rlp --namespace oratos --patch "$patch"
kubectl patch deployment loggregator-router --namespace oratos --patch "$patch"
kubectl patch daemonset loggregator-fluentd --namespace oratos --patch "$patch"
Ah, yeah. We moved the syslog-nozzle and loggregator-emitter to optional components. I guess because we apply them in all our environments the patch worked for us. We will fix the deploy script.
@jasonkeene , thanks for the quick response.
Yeah, it looks fine. I'm actively exploring it now. Great work!
Hi there
Thanks for effort. I'm trying it. Looks like it bumps into below issue.
Any suggestions to help me out? Thanks!
Note: I'm a 100% newbie to cloudfoundry.