I there any downtime in kubernetes upgrade? [closed] - amazon-web-services

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am planning to upgrade the kubernetes version of AWS EKS from 1.15 to 1.16. I understood that there is no downtime while upgrading the cluster plane of the kubernetes. But I am not sure if there is a downtime while upgrading the worker nodes of the kubernetes.
Is there any downtime while upgrading the kubernetes version?

It depends on how you have deployed your workload on the cluster and how you are planning to upgrade the worker nodes. Note the following items
Drain each worker node one by one and upgrade each one by one.
Use deployment, statefulset, daemonset instead of bare pods directly.
https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/

Related

Is Istio or AWS App mesh for service mesh implementation on EKS [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 months ago.
Improve this question
We are building up product which will have set of microservices communicating with each other.
We are using EKS as kubernetes service from aws. For Service mesh, There are two ways to go for it.
Install Istio over EKS cluster.
Use AWS App Mesh service with EKS.
The more I read about it, There are its own advantages of using one over other but not sure which one to go with.
Istio is more matured whereas App Mesh is able to integrate with different AWS services like XRay, Cloudwatch etc. easily.
Any inputs over this is appreciated.
This may lead to highly opinionated answers and usually this doesn't fly well on Stackoverflow. As you pointed out there isn't a specific answer other than "it depends". Your own background, organization goals, requirements etc. count more than the point opinion of individuals for this.

How do I best integrate AWS MWAA and Docker? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
Our data pipeline setup currently makes use of Docker containers running on EC2 instances and Apache Airflow as the orchestration tool. We're trying to move to MWAA for the advantages associated with a managed service(scalability, maintenance, scheduler monitoring etc...). My question is what's the best way to integrate Docker with MWAA? Currently we run our services/app via the DockerOperator on Airflow. Would we need to get Docker running on the MWAA environment? Any suggestions would be appreciated.
I would suggest to go ahead with ECS or ECS Fargate and run your Docker containers there.
MWAA supports open-source integrations with Fargate and other services, so can be easily integrated with Airflow to orchestrate

AWS EKS NodeCreationFailure [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Following the AWS guide on creating an EKS cluster, I get this error:
NodeCreationFailure Unhealthy nodes in the Kubernetes cluster
I followed the required IAM roles for both the cluster and the nodegroup. Also tried using Private and/or Public subnets. The error does not appear in their documentation as well so I am unable to troubleshoot this further

Cloud Formation Support for Rate-Based WAF Rule [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I want to set up a Cloud Formation in aws to attach a Rate Based Rule to my LB. I have been reading the AWS documentation for hours, and I know how to create a regular WAF Rule in Cloud Formation and attach them to my LB in Cloud Formation. The problem is I cant find how to create a Rule of type Rate-Based of WAF in CF, there is not RateBasedRule object in Cloud Formation. Does anyone knows how to get around this?
After talking to aws support itself: This feature is not yet supported by aws as of today.

Comparison between Amazon web services (AWS) or Rackspace cloud servers? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
There are two major offering of cloud computing environment by Amazon through AWS and by Rackspace through Rackspace cloud. I wanted to know more about What are cons/pros of one platform over other. That will help me in deciding platform for my future applications.
Please see some of these links to better analyze & understand the difference between Amazon Cloud Server with Rackspace Cloud.
Things come into my mind:
Amazon server stack has CHOICES possibly everything, but Rackspace server stack is fixed.
Control everything on your server stack with Amazon but Rackspace - NOPE.
You can play around with various services (EBS, EIP, S3, etc) in Amazon server to suite your price, you can't with Rackspace, since you are priced for the whole stack.
In Amazon - single EBS AMI, you can have many different instance types of machine.
Difference:
http://www.distractable.net/tech/amazon-aws-ec2-vs-rackspace-high-level-comparison/
Goodby Rackspace:
http://code.mixpanel.com/amazon-vs-rackspace/
Performance Analysis:
http://www.thebitsource.com/featured-posts/rackspace-cloud-servers-versus-amazon-ec2-performance-analysis/