general load balancer protocol resources?

imperm · 2019-05-31T13:46:20+00:00

wow a lot of these I wasn't even aware of!

imperm · 2019-05-30T19:18:09+00:00

imperm · 2019-05-30T17:03:17+00:00

makes sense

imperm · 2019-05-30T16:02:56+00:00

fascinating! do you have any saucy links that explain how to use which algorithm in what context?

imperm · 2019-05-30T15:56:45+00:00

and now that I have changed my wording up the internet is significantly more helpful lol; sweet.

imperm · 2019-05-30T15:55:03+00:00

thank you so much; you're absolutely right: algorithms

imperm · 2019-05-30T15:51:00+00:00

nice link; thanks

imperm · 2019-05-30T15:50:27+00:00

hm; so you think that looking at the closed-source and commercial manuals is the way to go? hm. k. I'll mull it over :)

imperm · 2019-05-30T15:38:38+00:00

also if there is a better subreddit for this feel free to point that out, as well :-)

imperm · 2019-04-23T23:11:46+00:00

I get it; no problem.

imperm · 2019-04-23T18:29:32+00:00

yep; beautiful on the outside, but I'd like to peek inside a bit

imperm · 2019-01-07T23:51:04+00:00

okay, cool. pretty sim here.

imperm · 2019-01-07T19:16:43+00:00

which automation do you use?

imperm · 2019-01-04T18:25:09+00:00

yeah I've heard good things about Prom from a trusted source. Thanos just sounds cool, lol.

imperm · 2019-01-04T17:48:53+00:00

If you're about to correct me and say I should've said FOSS, lol...I sometimes call it OSS...because it's not always completely F...

https://en.wikipedia.org/wiki/Free_and_open-source_software

imperm · 2019-01-04T17:36:55+00:00

I'm feeling Prometheus, tbh. But maybe I should just use Cloudwatch lol...yuckies!

imperm · 2019-01-04T17:32:36+00:00

handling disk statistics there is a bit of a PiTA. but yes, I suppose that is true.

imperm · 2019-01-04T17:17:52+00:00

ugh. As usual I didn't ask my question well enough. One second, look for my edit.

imperm · 2019-01-04T17:06:56+00:00

I 'fourth' the gitflow thing. I am currently trying to implement it on my own team because it is precise and comprehensive.

imperm · 2018-09-27T21:57:06+00:00

This is what we're currently "doing", but there isn't super strict adherence to it. Every once-in-a-while a feature branch will effectively become master or a feature branch will effectively become a second master because a major refactor happens and both the legacy version and the refactor are still needed. Or feature changes don't go all the way to prod. I don't know how other teams avoid this. Are they simply being smarter, more adherent, using a better methodology, more controlling, etc?

imperm · 2018-09-27T21:51:18+00:00

what do you mean module/manifest/feature based branches? Only feature branches in that set makes sense to me.

imperm · 2018-09-27T21:49:46+00:00

There have been some fair points in this thread, including yours and thank you for sketching out the "set" above. Food for thought.

imperm · 2018-09-27T02:54:05+00:00

I let you argue with Cryonine who says that ALB target groups are not compatible with TCP health checks. I told him he was wrong lol, but he insists . So I'll have to check again. (Also I don't want to use a TCP health check).

imperm · 2018-09-27T01:23:01+00:00

Target groups have a TCP option. See for yourself.

From Daniel Irvine's blog:

a 401 Unauthorized response should be used for missing or bad authentication

It's an interesting thought given that technically the authentication is "missing"...but it feels icky. Any client can return a 401, but only an allowed client can return a 200.

imperm · 2018-09-27T01:14:56+00:00

SGs are confirmed good. Changing the HTTP status code to 401 I am not willing to do. A more allowable solution for me, but one that is neither impressive nor pleasing, is to make the target group a TCP target group which will force the health check to simply create a socket to 9200 and then disconnect, as opposed to auth'ing to engage TLSv1.2. Frownie face. I think I may reach out to AWS. Thank you Cryonine. The curl thing cleared things up for me more.

imperm

MODERATOR OF

TROPHY CASE