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.

Sign up for GitHub

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

Jump to bottom

proposal: command to install spin-operator into a kubernetes cluster #38

Open
bacongobbler opened this issue Feb 27, 2024 · 1 comment
Open

proposal: command to install spin-operator into a kubernetes cluster #38

bacongobbler opened this issue Feb 27, 2024 · 1 comment
Labels
type: discussion Needs more clarification or discussion.

Comments

@bacongobbler
Copy link
Collaborator

@michelleN raised a question during today's show and tell: do we want to grant spin k8s the ability to install spin-operator and all its dependencies into a Kubernetes cluster that does not have those systems installed? Why or why not?
@bacongobbler bacongobbler added the type: discussion Needs more clarification or discussion. label Feb 27, 2024
@endocrimes
Copy link
Contributor

I don't think so - We don't want to maintain a Kubernetes Packaging Tool (and kubectl apply -f https://github.com/spinkube/spin-operator/releases/v1.0.0/static-manifests.yaml would be a more understandable experience if we wanted something similar)

We may want something to generate SpinAppExecutors for a provided runtimeClassName?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: discussion Needs more clarification or discussion.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@endocrimes @bacongobbler