Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

social.tchncs.de: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#eks

0 posts0 participants0 posts today
Public
Maksim Aniskov

EKS enforces upgrade insights checks as part of cluster upgrades
aws.amazon.com/about-aws/whats
The new control prevents accidental cluster upgrades when issues are already detected that may impact application compatibility with the next Kubernetes version.
EKS upgrade insights automatically scan clusters against a list of potential Kubernetes version upgrade impacting issues such as deprecated Kubernetes API usage.
#AWS #EKS

Amazon Web Services, Inc.Amazon EKS now enforces upgrade insights checks as part of cluster upgrades - AWSDiscover more about what's new at AWS with Amazon EKS now enforces upgrade insights checks as part of cluster upgrades
Public
pacovk

🚨 #AWS #EKS does not include #NGINX community controller.
But it's a common setup for many (40% of all K8s Cluster). The CVE found allows unauthorized to access secrets of anything and anywhere

For more infos and remediation refer to

Kubernetes: kubernetes.io/blog/2025/03/24/

Kubernetes · Ingress-nginx CVE-2025-1974: What You Need to KnowToday, the ingress-nginx maintainers have released patches for a batch of critical vulnerabilities that could make it easy for attackers to take over your Kubernetes cluster. If you are among the over 40% of Kubernetes administrators using ingress-nginx, you should take action immediately to protect your users and data. Background Ingress is the traditional Kubernetes feature for exposing your workload Pods to the world so that they can be useful. In an implementation-agnostic way, Kubernetes users can define how their applications should be made available on the network.
#CVE#Security
Public
Maksim Aniskov

CodePipeline adds native EKS deployment support
aws.amazon.com/about-aws/whats
Previously, if you wanted to deploy to a EKS cluster within a private network, you had to initialize and maintain a compute environment within the private network. Now, you can simply provide the name of the cluster and add this action to your pipeline. The pipeline will automatically establish a connection to deploy your application, without additional infrastructure needed.
#AWS #EKS #CodePipeline

Amazon Web Services, Inc.AWS CodePipeline adds native Amazon EKS deployment support - AWSDiscover more about what's new at AWS with AWS CodePipeline adds native Amazon EKS deployment support
Public
Alon

Ran into another #AWS issue.

No more IPs left in subnet for #EKS.

EKS uses subnet IPs, not local IPs, to connect AWS services. Luckily, VPC has available CIDR, so I created new subnet and migrated worker node.

Other options? Maybe add a secondary CIDR block to the VPC?

#k8s
Public *
simplyblock

We Built a Tool to Help You Understand Your Real EBS Usage!

There is one question in life that is really hard to answer: “What is your actual AWS EBS volume usage?” When talking to customers and users, this question is frequently left open with the note that they’ll check and tell us later. With storage being one of the main cost factors of cloud services such as Amazon’s AWS, this is not what it should be. But who could blame them? It’s not like AWS is making it obvious to you how much of your storage resources (not only capacity but […]

simplyblock.io/blog/ebs-volume

We just open sourced our AWS EBS Volume Usage Exporter on Github. Get an accurate view of your EBS usage in EKS.
#amazonebs#aws#ebs
Public
Kartik

Yesterday I convinced a team to stop using k8s. Their architecture was to use EKS, and my recommendation was to use ECS/Fargate.

Surprisingly the debated internally and went with my recommendation.

Every time I convince a team to stop using k8s, I feel like a Jehovah's witness converting a heathen away from satan.

#eks#ecs#k8s
Public
Feoh

#Pulumi is amazing you guys. If you need to build #infrastructurefan
with code, it's honest to god the best tool I've yet seen in my 30+ year career in terms of being able to actually leverage and re-use your previous efforts.

Like, I just wrote maybe 15 lines of novel configuration total, probably 8 of that being subnet listings for VPCs, and I'm now watching a new #AWS #EKS cluster crawl out of the primordial cloud ooze :)

There are plenty of other tools that do this, but pretty much all of them use DSLs that actually bring more complexity to the table rather than reducing it. Pulumi lets me code in my favorite programming language instead. Priceless. And it's #floss!

(They do have a paid service you can use if you want for storing your infra's state. We just use an S3 bucket)

pulumi.com/

pulumiPulumi - Infrastructure as Code, Secrets Management, and AIPulumi is an infrastructure management platform to automate through infrastructure as code, secure with secrets management, and manage infrastructure with AI.
Public
Karen Bruner

Scenario: AWS #EKS cluster, private API endpoint only, devs need to ssh tunnel through an EC2 bastion host to connect.

`aws eks update-kubeconfig` writes the FQDN of the API endpoint. However, using a tunnel, we need to connect to localhost and the forwarded port.

Any magic way to manage this without editing the kubeconfig file for every EKS cluster after running `aws eks update-kubeconfig`?

ExploreLive feeds
About