We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems Diskpool requires you to know the nodenames before hand
cat <<EOF | kubectl create -f - apiVersion: "openebs.io/v1alpha1" kind: DiskPool metadata: name: pool-on-node-3 namespace: mayastor spec: node: node3 disks: ["/dev/sdc"] EOF
This is problematic if you do not have this information as nodes will get added and removed on demand for Azure Kubernetes and will get new node names
I think it will be better to target disk pools by a common node label if possible
That way new nodes spun up that have this common label will have the diskpool associated with it
https://learn.microsoft.com/en-us/azure/aks/cluster-autoscaler?tabs=azure-cli
The text was updated successfully, but these errors were encountered:
This is an interesting problem, and we might be able to solve in different ways:
Sorry, something went wrong.
No branches or pull requests
It seems Diskpool requires you to know the nodenames before hand
cat <<EOF | kubectl create -f -
apiVersion: "openebs.io/v1alpha1"
kind: DiskPool
metadata:
name: pool-on-node-3
namespace: mayastor
spec:
node: node3
disks: ["/dev/sdc"]
EOF
This is problematic if you do not have this information as nodes will get added and removed on demand for Azure Kubernetes and will get new node names
I think it will be better to target disk pools by a common node label if possible
That way new nodes spun up that have this common label will have the diskpool associated with it
https://learn.microsoft.com/en-us/azure/aks/cluster-autoscaler?tabs=azure-cli
The text was updated successfully, but these errors were encountered: