Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
This repository is currently being migrated. It's locked while the migration is in progress.

[WIP] storageos: Add compute-only deployment support#95

Draft
darkowlzz wants to merge 1 commit into
storageos:masterfrom
darkowlzz:compute-only
Draft

[WIP] storageos: Add compute-only deployment support#95
darkowlzz wants to merge 1 commit into
storageos:masterfrom
darkowlzz:compute-only

Conversation

@darkowlzz

Copy link
Copy Markdown
Contributor

No description provided.

@croomes

croomes commented Apr 9, 2019

Copy link
Copy Markdown
Contributor

I'm not sure I like having separate DaemonSets for compute and storage nodes. We should be able to pass selectors and determine dynamically? This may be ok for now, but let's have a look at whether the current label implementation should be revised.

@croomes

croomes commented Apr 15, 2019

Copy link
Copy Markdown
Contributor

Now that k8s node labels are passed to StorageOS, we should be able to set storageos.com/deployment=computeonly on the k8s nodes to enable compute only. This lets us have a single DaemonSet with mixed node configs. This wasn't clear in the docs before (fixed recently) https://docs.storageos.com/docs/reference/labels

@avestuk

avestuk commented May 29, 2019

Copy link
Copy Markdown
Contributor

storageos.com/deployment=computeonly is passed to StorageOS from k8s node labels. This does allow us to do mixed deployments with a single Daemonset.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants