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

Loftsman as an Kubernetes operator? #10

Open
rockholla opened this issue Mar 23, 2021 · 1 comment
Open

Loftsman as an Kubernetes operator? #10

rockholla opened this issue Mar 23, 2021 · 1 comment
Labels
enhancement New feature or request needs design Marked as something that needs further design prior to starting implementation

Comments

@rockholla
Copy link
Contributor

We've done a fair amount design-wise with the manifest schema and otherwise to support the idea of making Loftsman an operator running in the Kubernetes cluster. Tracking this possibility officially here.

@rockholla rockholla added the enhancement New feature or request label Mar 23, 2021
@rockholla rockholla added the needs design Marked as something that needs further design prior to starting implementation label Mar 30, 2021
@rockholla
Copy link
Contributor Author

One idea around this is to actually encapsulate ability to deploy the operator into a cluster via the CLI, a given version of the CLI still encapsulating the version of stuff to deploy or pointers to those artifacts at least, so a workflow that looks like:

$ loftsman operator deploy  [--namespace] [other options]

which would deploy the operator as a step that is setting up your cluster not unlike initializing the cluster otherwise with needed CNIs, other base setup/config.

And then further operations would simply apply manifests to manage things in the cluster moving forward, e.g.

kubectl apply loftmanmanifest -n [loftsman manifest tracking namespace] -f ./manifest.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs design Marked as something that needs further design prior to starting implementation
Projects
None yet
Development

No branches or pull requests

1 participant