search

cloudfoundry-attic / loggregator-k8s-deployment

A deployment of loggregator on kubernetes
6 stars 3 forks source link

Use kubectl -R #8

Closed dprotaso closed 6 years ago

dprotaso commented 6 years ago

https://github.com/cloudfoundry-incubator/loggregator-k8s-deployment/blob/6bd7c16896d6fca27bfb94f651610b46dd83a3c1/deploy.sh#L20

jasonkeene commented 6 years ago

Yeah, we tried this. Is there a way to force the ordering of the objects? For instance the namespace needs to be created first, then configmaps/secrets, then the rest of the objects. We wrote the script to control ordering. If we can delete it I would prefer to though.

dprotaso commented 6 years ago

I’ve seen teams add a prefix to the file 001, 002 On Wed, May 16, 2018 at 11:43 Jason Keene notifications@github.com wrote:

Yeah, we tried this. Is there a way to force the ordering of the objects? For instance the namespace needs to be created first, then configmaps/secrets, then the rest of the objects. We wrote the script to control ordering. If we can delete it I would prefer to though.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cloudfoundry-incubator/loggregator-k8s-deployment/issues/8#issuecomment-389566718, or mute the thread https://github.com/notifications/unsubscribe-auth/AABIgnjEdeAtciXICv2YpHPjTCxAN1nwks5tzEkjgaJpZM4T75Qh .

jasonkeene commented 6 years ago

That's cool, I haven't seen that before. We are investigating writing an operator for loggregator/log-cache which would handle the ordering of the deploy. I'm happy keeping the script until then. Makes acceptance easier. Thanks for the idea though!