Skip to content

Commit

Permalink
Merge pull request #227 from RockefellerArchiveCenter/development
Browse files Browse the repository at this point in the history
Fix link
  • Loading branch information
p-galligan authored Aug 30, 2023
2 parents ded4884 + fe85aee commit 8b79bd7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2023-08-25-not-choosing-kuberenetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ This is not a blog post about our successful implementation of Kubernetes, but r

## Background

I wrote a [blog post] (https://blog.rockarch.org/choosing-kubernetes) in May of last year about how and why we chose to test EKS. To summarize, we thought EKS would help automate our containerized application deployment, provide high uptime for our applications, simplify infrastructure decisions, and alleviate the pain of critical power or network interruptions at the RAC. Furthermore, we were familiar with Amazon’s cloud ecosystem, which made EKS a reasonable choice. We moved ahead with this plan to evaluate EKS, and I, with a lot of help from the RAC’s IT department, stood up an EKS cluster with two worker nodes, updated two microservice applications for containerized deployment, deployed them on EKS using deployment, configuration, and secret files, connected those containers to RDS databases, and set up an ingress controller, ingress files, and created a service mesh for those applications. However, it slowly became clear through that process of setting up the infrastructure that Kubernetes was not the right solution for the RAC.
I wrote a [blog post](https://blog.rockarch.org/choosing-kubernetes) in May of last year about how and why we chose to test EKS. To summarize, we thought EKS would help automate our containerized application deployment, provide high uptime for our applications, simplify infrastructure decisions, and alleviate the pain of critical power or network interruptions at the RAC. Furthermore, we were familiar with Amazon’s cloud ecosystem, which made EKS a reasonable choice. We moved ahead with this plan to evaluate EKS, and I, with a lot of help from the RAC’s IT department, stood up an EKS cluster with two worker nodes, updated two microservice applications for containerized deployment, deployed them on EKS using deployment, configuration, and secret files, connected those containers to RDS databases, and set up an ingress controller, ingress files, and created a service mesh for those applications. However, it slowly became clear through that process of setting up the infrastructure that Kubernetes was not the right solution for the RAC.

## Hypotheses

Expand Down

0 comments on commit 8b79bd7

Please sign in to comment.