Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle Operators #154

Open
aceeric opened this issue Feb 13, 2025 · 0 comments
Open

How to handle Operators #154

aceeric opened this issue Feb 13, 2025 · 0 comments

Comments

@aceeric
Copy link

aceeric commented Feb 13, 2025

Hello @ChristofferNissen I'm asking a question here in response to helm/helm#13455 (comment)

Do you (how do you) handle the Operator pattern. E.g.:

  1. Install the MinIO Operator
  2. Deploy a MinoIO Tenant Resource
  3. The Operator creates Deployment / StatefulSet resources with image refs that are (typically) embedded in Go code

In our crude brute-force approach we provision a single-node cluster, install all the workloads for which we want images, then install resources that trigger operators to do their thing (e.g. MinIO), then we snapshot the containerd cache.

Is this something you've discovered a clever solution for? Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant