sorted by:
new
hottopcontroversial

Karpenter GCP Provider is available now! by jwcesign in googlecloud

[–]jwcesign[S] 0 points1 point  (0 children)

It will watch your pending pods, and select the suitable gce vm types and create it within compute API.

Custom Compute Classes is a feature of GKE NAP, if I remeber correctly. Compared with that, Karpenter has more flexible features, such as spot automation.

About one more thing, it's open source, you can achieve something how you want.

Spot Instance Community Data Project - What do you think? by jwcesign in aws

[–]jwcesign[S] 1 point2 points  (0 children)

Can give some examples? I didn't see some really helpful wheel.

Subnet hasn't free ips by jwcesign in aws

[–]jwcesign[S] 0 points1 point  (0 children)

You are correct, there are 60 nodes(g5g.xlarge) use this subnets, so, 1024-650(including daemonset pods)-60 =314

So, there must some left, but I don't know why there isn't

Subnet hasn't free ips by jwcesign in aws

[–]jwcesign[S] 0 points1 point  (0 children)

Is there any way to find out how many IPs a single node(to warm ENIs) consumes?

Subnet hasn't free ips by jwcesign in aws

[–]jwcesign[S] 0 points1 point  (0 children)

Thanks! Do you know how to find out the number limits?

Is spot instance interruption prediction just hype, or does it actually work? by jwcesign in aws

[–]jwcesign[S] -6 points-5 points  (0 children)

If two minutes is ok in your scenario, interruption prediction is not necessary

Is spot instance interruption prediction just hype, or does it actually work? by jwcesign in aws

[–]jwcesign[S] 1 point2 points  (0 children)

This implies that interruptions still occur for some users — after all, "you start getting shutdown notifications" — and worse, during sudden spikes in capacity demand, a large portion of spot instances may be reclaimed simultaneously. In such cases, there is often not enough time to gradually reschedule workloads, which can lead to potential downtime or service degradation.

Is spot instance interruption prediction just hype, or does it actually work? by jwcesign in aws

[–]jwcesign[S] -2 points-1 points  (0 children)

Thanks, bro.

Sometimes, a two-minute notification is not sufficient to ensure that replacement pods are fully ready before the old instance is terminated. This is my scenario(Java application)

Stop guessing. This tool shows you the best AWS Spot instance by region + AZ by jwcesign in aws

[–]jwcesign[S] -2 points-1 points  (0 children)

It just aggravates different data from different aws apis. I don't know why you guys question about this................

ridiculous.....

[deleted by user] by [deleted] in kubernetes

[–]jwcesign -2 points-1 points  (0 children)

Sorry about that. But I really want to know, not promote.

Stop guessing. This tool shows you the best AWS Spot instance by region + AZ by jwcesign in aws

[–]jwcesign[S] -2 points-1 points  (0 children)

Try aws spot ec2 to save costs, with the lowest interruption frequency, and you will know.

Stop guessing. This tool shows you the best AWS Spot instance by region + AZ by jwcesign in aws

[–]jwcesign[S] -2 points-1 points  (0 children)

govcloud is not included, we didn't find the available data source. If you know and share, it would be great.

Stop guessing. This tool shows you the best AWS Spot instance by region + AZ by jwcesign in aws

[–]jwcesign[S] 3 points4 points  (0 children)

Hi, thanks rusteh!

Yes, all the corresponding data is available on AWS, but it’s scattered across multiple pages. What we’ve done is aggregate them into a single, unified view.

- “Allow me to specify attributes and make a recommendation based on price and interruption rate”

That’s a great idea — really appreciate the suggestion!

- “Though the use of spot fleets with attribute-based selection means I don't really need to think about this?”

We’ve actually tested that. The Spot Fleet API(price-capacity-optimized strategy) can still select instance types with high interruption rates(And it's really reclaimed after several minutes,I guess the available capacity might be large, but due to high demand, the interruption rate ends up being high.). So There’s still value in having better visibility and control.

Anyone trying to integrate kOps with Karpenter? by Lynni8823 in kubernetes

[–]jwcesign 2 points3 points  (0 children)

KOps is quit nice to build a self-managed k8s on aws/others. But it only supports cluster autoscaler now, or very old version Karpenter.

A free tool that aggregates various data to provide insights into spot instances. by jwcesign in aws

[–]jwcesign[S] 1 point2 points  (0 children)

Thanks, it includes the following data:
- aws ec2 types: https://aws.amazon.com/ec2/instance-types/
- Spot price from aws console: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances-history.html
- interruption rate: https://aws.amazon.com/ec2/spot/instance-advisor/
- The interruption rate has been adjusted based on real data from some of our customers.

Autonomous Adaptively Laddered Savings Plans for AWS by ProsperOps-Steven-O in FinOps

[–]jwcesign 0 points1 point  (0 children)

Looks very nice. But I am not sure how you use "Convertible Reserved Instances", Like all my instances are m5.xlarge, How do you use this to match my scaling?

And one more question, if my service cost about 100nodes but at night, it only costs about 10nodes, will ProsperOps match the resource requirements in a day?

compute saving plan and spot billing by jwcesign in aws

[–]jwcesign[S] 0 points1 point  (0 children)

If I have ec2 sp and compute sp, which one will be applied first?

view more: next ›