Echo · Phoenix Framework

system text

22:31:53

You are an expert AI assistant editor for a blog. Your role is to help users refine, correct, and improve their blog posts. Focus on clarity, grammar, tone, and flow.
You are grounded in reality and must avoid hallucinations. Do not invent facts or modify the core meaning of the user's text unless requested.
You have a tool called `edit_text`. YOU MUST CALL THIS TOOL BY RESPONDING WITH A VALID TOOL CALL JSON PAYLOAD.
DO NOT WRITE PYTHON, JAVASCRIPT, OR ANY OTHER CODE. DO NOT WRAP YOUR RESPONSE IN `print()` OR ANY OTHER FUNCTION.

user text

22:32:00

Here is the current content of the blog:

# Have Kubernetes operators gone too far?

What does this even mean? Well, to be honest, I am not sure myself, but let's start with a short story.

I was setting up an AWS environment recently. I had an EKS cluster, some APIs, and an RDS database. The RDS password was stored in AWS Secrets Manager, but my app only supported reading secrets from environment variables. Now I am lazy, and I don't want to update my app to read the secret from AWS Secrets Manager, but luckily I remembered the [External Secrets Operator](https://external-secrets.io/latest/). I have used it in the past and remember it was easy to set up, and it just worked.

So let's install it: Go get the CRDs bundle from [here](https://github.com/external-secrets/external-secrets/blob/main/deploy/crds/bundle.yaml), and would you look at the 28k lines long and needs a `--server-side` to apply because the CRDs are too big and `kubectl` doesn't support it. Whatever apply it and move on. Let's install the operator itself, and now I have 3 services running in my cluster
* external-secrets-cert-controller
* external-secrets
* external-secrets-webhook

I just wanted to move 1 secret from AWS to the EKS cluster, and now I have thousands of lines of YAML and more microservices than secrets. Why are there 28k lines of yaml definitions? Why does it take 3 services to copy 1 secret? What happened here?

Story time over. Let me just try to set something straight: I don't hate a specific operator or Kubernetes. I have used External Secrets in the past for multiple years, and arguably, I owe my career to Kubernetes. But it is starting to feel like a Kubernetes cluster is turning into a Node project with all the NPM dependencies to do the simplest thing. And I know I am part of the problem, reaching for an Operator to read a single secret.

---

User request:

user text

22:32:00

Can you proof read this real quick

model functionCall

22:32:29

Function Call:

{
"args": {
"replacements": [
{
"new_text": "Now, I am lazy, and I didn't want to update my app to read the secret from AWS Secrets Manager, but luckily I remembered the [External Secrets Operator](https://external-secrets.io/latest/). I had used it in the past and remembered it being easy to set up—it just worked.",
"old_text": "Now I am lazy, and I don't want to update my app to read the secret from AWS Secrets Manager, but luckily I remembered the [External Secrets Operator](https://external-secrets.io/latest/). I have used it in the past and remember it was easy to set up, and it just worked."
},
{
"new_text": "So let's install it: Go get the CRDs bundle from [here](https://github.com/external-secrets/external-secrets/blob/main/deploy/crds/bundle.yaml), and would you look at that—it's 28k lines long and needs a `--server-side` flag to apply because the CRDs are too big and `kubectl` doesn't support it. Whatever, apply it and move on. Let's install the operator itself. Now I have three services running in my cluster:",
"old_text": "So let's install it: Go get the CRDs bundle from [here](https://github.com/external-secrets/external-secrets/blob/main/deploy/crds/bundle.yaml), and would you look at the 28k lines long and needs a `--server-side` to apply because the CRDs are too big and `kubectl` doesn't support it. Whatever apply it and move on. Let's install the operator itself, and now I have 3 services running in my cluster"
},
{
"new_text": "I just wanted to move one secret from AWS to the EKS cluster, and now I have thousands of lines of YAML and more microservices than secrets. Why are there 28k lines of YAML definitions? Why does it take three services to copy one secret? What happened here?",
"old_text": "I just wanted to move 1 secret from AWS to the EKS cluster, and now I have thousands of lines of YAML and more microservices than secrets. Why are there 28k lines of yaml definitions? Why does it take 3 services to copy 1 secret? What happened here?"
},
{
"new_text": "Story time over. Let me just try to set something straight: I don't hate a specific operator or Kubernetes. I have used External Secrets for years, and arguably, I owe my career to Kubernetes. But it is starting to feel like a Kubernetes cluster is turning into a Node project with all its NPM dependencies just to do the simplest thing. And I know I am part of the problem, reaching for an operator to read a single secret.",
"old_text": "Story time over. Let me just try to set something straight: I don't hate a specific operator or Kubernetes. I have used External Secrets in the past for multiple years, and arguably, I owe my career to Kubernetes. But it is starting to feel like a Kubernetes cluster is turning into a Node project with all the NPM dependencies to do the simplest thing. And I know I am part of the problem, reaching for an Operator to read a single secret."
}
]
},
"name": "edit_text"
}

Conversation