toredash

8 ms·

1.
by toredash 29d ago
And what an update it was. I still remember how Windows ME looked at first, the feeling of something better. That didn't last long
2.
by toredash 29d ago
Didn't we eagerly await on updates in the good old days of Windows?
3.
by toredash 2mo ago
Cross zone latency has noticeable effect: https://news.ycombinator.com/item?id=45512351
4.
by toredash 2mo ago
I would really see this compared to what AWS is offering via RDS
5.
by toredash 4mo ago
Managed a fairly large matomo site in the past. Using queue plugin ( https://plugins.matomo.org/QueuedTracking ) with Redis Cluster really improves the situation. We actually built a custom plugin with Nginx + Lua to avoid PH
6.
by toredash 5mo ago
Is there any DNS based software to do block/allow? Kinda lika what's present in CiliumNetworkPolicies in Kubernetes networking?
7.
by toredash 10mo ago
I often find myself trying to tell people that KISS is a good thing. If something is somewhat complex it will be really complex after a few years and a few rotations of personnel.
8.
by toredash 11mo ago
If the image repositories were AZ bound resources, that would make the CI build process more efficient. Or, if the resources that CI build is utilizing within the image (after the image is pulled and started) is AZ bound, then yes the build
9.
by toredash 11mo ago
> If you have the setup on 3 AZs how would you route traffic only to the AZ where your RDS resides? So specifically for RDS, AWS will provide two endpoint for the client application: A writer and a reader endpoint. Similar to this: mydbc
10.
by toredash 11mo ago
> And I don't understand how a tool like this fits into formal risk analysis and where it presents an optimum solution for those risks. Seems it does not fit your risk analysis?
11.
by toredash 11mo ago
> Most people should start with a single-zone setup and just accept that there's a risk associated with zone failure. If you have a single-zone setup, you have a node group in that one zone, you have the managed database in the same
12.
by toredash 11mo ago
Are you thinking about already-cached container images on the host level ? Not sure how AZP fits in here? Since you mentioned it, what I've done before when it comes to improving CI builds, is to use karpenter + local SSD mounts with v
13.
by toredash 11mo ago
AWS publish their own metrics for cross-AZ and internal-AZ latency: https://eu-central-1.console.aws.amazon.com/nip/ (Network Manager > Infrastructure Performance) > In general the goal should be to deploy as muc
14.
by toredash 11mo ago
That was the origin for this solution. A client app had to issue millions of small SQL queries where the first query had to complete before the second query could be made. Millions of MS adds up. Lowest possible latency would of course be r
15.
by toredash 11mo ago
I would LOVE to pitch something else I'm working on that is solving this problem in EKS, cross zone data transfer. It's a plugin that enables traffic re-direction for any service that is using an IP in any given VPC. If you have s
16.
by toredash 11mo ago
I was surprised to. Of course it makes sense when you look at it hard enough, two seperate DCs won't have the same latency than internal DC communication. It might have the same physical wire-speed, but physical distance matter.
17.
by toredash 11mo ago
The nice thing about this solution, its not limited to RDS. I used RDS as an example as many are familiar with it and are known to the fact that it will change AZ during maintenance events. Any hostname for a service in AWS that can relocat
18.
by toredash 11mo ago
> Kyverno requirement makes it limited. You don't have to use Kyverno. You could use a standard mutating webhook, but you would have to generate your own certificate and mutate on every Pod.CREATE operations. Not really a problem bu
19.
by toredash 11mo ago
As it stands now, it doesn't. Unless you modify the Kyverno Policy to be of a background scanning. I would create a similar policy where Kyverno at intervals would check the Deployment spec to see if the endpoint is changed, and alter
20.
by toredash 11mo ago
Totally agree! This service is published more as a concept to be built on top of, than a complete solution. You wouldn't even need IAM rights to read RDS information, you need subnet information. As subnets are zonal, it does not if th
21.
by toredash 11mo ago
Agree, Kubernetes isn't for everyone. This solution came from an specific issue with a client which had ad hoc performance problems when a Pod was placed in the "in-correct" AZ. So this solution was created to place the Pods
22.
by toredash 11mo ago
Yes I get that. But are we talking HA for this lookup service that I've made? If yes, that's a simple update of the manifest to have 3 replicas with ab affinity setting to spread that out over different AZ. Kyverno would use the i
23.
by toredash 11mo ago
I'm not sure I follow. Are you talking about the AZP service, or ... ?
24.
by toredash 11mo ago
If the AZP deployment fails, yes your correct there is no hints anywhere. If the lookup to AZP fails for whatever reason, it would be noted in the Kyverno logs. And based on if you -require- this policy to take affect or not, you have to de
25.
Automatic K8s pod placement to match external service zones(github.com)
82 points by toredash 11mo ago|46 comments
26.
by toredash 11mo ago
Hi HN, I wanted to share something I've worked a bit to solve regarding Kubernetes: its scheduler has no awareness of the network topology for external services that workloads communicate with. If a pod talks to a database (e.g AWS RDS
27.
by toredash 2y ago
Next challenge: Wifi
28.
by toredash 2y ago
Still have two Fire tablets (HD). Works for streaming and reading but surfing can be a drag
29.
by toredash 2y ago
Fun that people -still- don't understand the feature set that VMware provides. He/She is thinking about VMware Fault Tolerance
30.
by toredash 2y ago
Same.

More ›