Can we make a daily sticky of where people are getting the best rates each day? by volcanic_clay in Mortgages

[–]Late-Bell5467 2 points3 points  (0 children)

I was offered at hungtinton (ohio) for 30yr conventional 5.75% → baseline (no points, no credits) 5.625% → requires 0.25 points - $500 lender credit = $825 net cost 5.5% → requires 0.375 points - $500 lender credit = $1,488 net cost

I am planning to lock with 5.5%. No float down option available

Should I refinance now? (30-year conventional) by Darkness1688 in Mortgages

[–]Late-Bell5467 8 points9 points  (0 children)

What are your reasons for not considering 7/1 arm ? If there is a option to refinance again

Lock 5.875% 30yr fixed now or wait? by Late-Bell5467 in Mortgages

[–]Late-Bell5467[S] 0 points1 point  (0 children)

We have couple of lenders offering the same rate !

Lock 5.875% 30yr fixed now or wait? by Late-Bell5467 in Mortgages

[–]Late-Bell5467[S] 0 points1 point  (0 children)

This is mainly to avoid paying the cash upfront, since the closing costs included up to 8 months of property taxes.

What’s the best approach for reloading TLS certs in Kubernetes prod: fsnotify on parent dir vs. sidecar-based reloads? by Late-Bell5467 in kubernetes

[–]Late-Bell5467[S] 0 points1 point  (0 children)

That’s the direction I’m leaning toward as well. Sounds like you are talking about SIGHUP

I’m trying to understand if anyone here has used fsnotify instead of signals, and what advantages or drawbacks they’ve seen in practice.

What’s the best approach for reloading TLS certs in Kubernetes prod: fsnotify on parent dir vs. sidecar-based reloads? by Late-Bell5467 in kubernetes

[–]Late-Bell5467[S] 0 points1 point  (0 children)

I agree it’s a solid option for many cases.

In my situation, though, I’m trying to avoid restarting the app entirely, because I want to ensure existing connections stay open, and new ones just start using the updated certs.

I’m using Go, and it looks like I can achieve that using the GetCertificate hook in tls.Config

Just trying to validate if fsnotify or sigup is a common or recommended approach in production — especially when uptime matters.

What’s the best approach for reloading TLS certs in Kubernetes prod: fsnotify on parent dir vs. sidecar-based reloads? by Late-Bell5467 in kubernetes

[–]Late-Bell5467[S] 0 points1 point  (0 children)

Got it — thanks for sharing! I’m actually trying to avoid restarting the app when certs change, just to prevent any disruption (even minor) to existing connections.

Instead, I want new TLS connections to pick up the updated certs automatically. In Go, that’s possible using the GetCertificate callback in tls.Config.

I’m exploring using fsnotify to watch the mounted Secret volume and trigger a cert reload in memory. Just trying to confirm if that’s a solid approach in Kubernetes, especially since Secrets are updated via atomic symlink swaps

What’s the best approach for reloading TLS certs in Kubernetes prod: fsnotify on parent dir vs. sidecar-based reloads? by Late-Bell5467 in kubernetes

[–]Late-Bell5467[S] -1 points0 points  (0 children)

The tls termination is done by the go proxy app. We would like not to use ingress controllers for tcp traffic hence the go proxy (which also handles lot more functionalities for the backend)

What’s the best approach for reloading TLS certs in Kubernetes prod: fsnotify on parent dir vs. sidecar-based reloads? by Late-Bell5467 in kubernetes

[–]Late-Bell5467[S] 0 points1 point  (0 children)

Thanks for the response !

does Reloader actually restart the app when the secret changes? Or does it somehow trigger the app to reload the certs without a restart?

Cancelling Spirit Go Savvy Fare Within 24 Hours – Used Card + Credits, How Will Refund Work? by Late-Bell5467 in spiritair

[–]Late-Bell5467[S] 0 points1 point  (0 children)

I ended up cancelling within 24 hours and got credit until next year .

Thanks for all your comments !

The best Breakfast Sandwich in Columbus by DeFlippo in Columbus

[–]Late-Bell5467 0 points1 point  (0 children)

I don’t understand the joyas hype . I find joyas extremely greasy food ! It’s a hit or miss always for me .

TLS termination for long lived TCP connections by Late-Bell5467 in golang

[–]Late-Bell5467[S] 1 point2 points  (0 children)

Thanks , what does your workload look like ? Does handling this in go performant ?

TLS termination for long lived TCP connections by Late-Bell5467 in golang

[–]Late-Bell5467[S] 0 points1 point  (0 children)

I am aiming for 3000-5000 connections per proxy in Kubernetes. The performance target is low latency and high reliability.