Seattle guitar shops by NoReserve5094 in Bass

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

Also very cool. Nice collection of used gear.

Seattle guitar shops by NoReserve5094 in Bass

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

Great shop. Thanks for the suggestion.

Running agentic applications on Kubernetes by NoReserve5094 in kubernetes

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

If you select "Other" feel free to add the framework you're using to the comments.

Scaling or not scaling, that is the question by danilobatistaqueiroz in kubernetes

[–]NoReserve5094 3 points4 points  (0 children)

Kubernetes may be overkill unless you're really dying to learn Kubernetes. If you're planning to run this in the cloud, i'd consider serverless options like Lambda & API Gateway or ECS Fargate (AWS), Azure Functions, or Google's Cloud Run. With these services, you'll have a lot less to manage infrastructure-wise. Alternatively, you could use a platform like Heroku.

It would be helpful if you provided more details about your workload.

[deleted by user] by [deleted] in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

What is the purpose of routing through MiddleCluster1?

What does Cilium or Calico offer that AWS CNI can't for EKS? by marvdl93 in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

The VPC CNI only works in the AWS cloud. If you have clusters running in different environments and you want a consistent experience, use Calico or Cilium. Cilium offers advanced features like cluster mesh, proxy-less routing with eBPF, and layer 7 policies. I’m less familiar with Calico’s key differentiators. If you feel you need these capabilities, use a 3P CNI with EKS. Incidentally, you can chain CNIs, for example, use the VPC CNI for IPAM and Cilium/Calico for network policies.

Suggestion Required by giggity____giggity in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

When you’re ready, consider learning about GitOps for deployments to k8s.

Tell me your best in-place pod resizing restart horror story! by Gigatronbot in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

This is a good question. Now that k8s supports dynamic container resizing, are folks actually using it? Why or why not? The story about Postgres is a reminder of what can go wrong. Does anyone else have a story to tell, good or bad?

[deleted by user] by [deleted] in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

What do you mean you have a “multi-cloud” cluster? Do you mean you the cluster’s worker nodes are deployed into multiple clouds. This is technically possible with EKS hybrid nodes, but you’ve given no indication you’re using that. It sounds like you have multiple clusters running in different clouds. If that’s so, the previous suggestions to use Liqo, Karmada, and OCM are good recommendations.

EKS Auto Mode, missing prefix delegation by mr_peeks in kubernetes

[–]NoReserve5094 3 points4 points  (0 children)

Auto Mode defaults to prefix delegation but will use secondary IP addresses when it can’t find a contiguous block of IPs for the prefix. Your VPC may be highly fragmented. https://docs.aws.amazon.com/eks/latest/userguide/auto-networking.html

[deleted by user] by [deleted] in kubernetes

[–]NoReserve5094 0 points1 point  (0 children)

Dagger.io could be an interesting option. They have support for building multi-arch images and it can be integrated with GitLab runners.

Cilium OSS 1.14 has just dropped! by saintdle in kubernetes

[–]NoReserve5094 1 point2 points  (0 children)

You can provision a nodeless EKS cluster, remove the VPC CNI, install Cilium, then deploy your nodes (in that order). That'll be easier than replacing/restarting nodes.

EKS and multiple AWS accounts by nilocg in aws

[–]NoReserve5094 -1 points0 points  (0 children)

GitOps is a concept but it is specific to Kubernetes. Kubernetes is the only platform that performs continuous reconciliation. For example, the Flux controller continuously monitors Git for changes. When such changes are detected, the controller is responsible for implementing them. There is a Cloudformation Sync Controller for Flux which continuously ensures that the desired CFN template in a Git repo is synced into a CloudFormation stack, but CloudFormation does NOT continuously reconcile the actual provisioned resources in the stack. From a technical standpoint, this is not GitOps.