-
Notifications
You must be signed in to change notification settings - Fork 31
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
add more configurable options for pod template #35
Comments
@wey-gu Oh, Good idea! |
After merged, please configure Notes:
For example: $ export NEBULA_CLUSTER_NAME=nebula # the name for nebula cluster
$ export NEBULA_CLUSTER_NAMESPACE=nebula # the namespace you want to install the nebula cluster
$ export STORAGE_CLASS_NAME=standard # the storage class for the nebula cluster
$ helm install "${NEBULA_CLUSTER_NAME}" nebula-operator/nebula-cluster \
--namespace="${NEBULA_CLUSTER_NAMESPACE}" --create-namespace\
--set nameOverride=${NEBULA_CLUSTER_NAME} \
--set nebula.storageClassName="${STORAGE_CLASS_NAME}" \
--set-string 'nebula.podAnnotations.sidecar\.istio\.io/inject='false
$ kubectl get pod -n ${NEBULA_CLUSTER_NAMESPACE} -l app.kubernetes.io/cluster=${NEBULA_CLUSTER_NAME} \
-o custom-columns='NAME:.metadata.name,Inject:.metadata.annotations.sidecar\.istio\.io/inject'
NAME Inject
nebula-graphd-0 false
nebula-graphd-1 false
nebula-metad-0 false
nebula-metad-1 false
nebula-metad-2 false
nebula-storaged-0 false
nebula-storaged-2 false |
@veezhang wow, thanks!!! |
This was referenced Jun 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the tests of MEG friends, it's found there could be a conflict between nebulaCluster pods and istio-proxy sidecar pods, in order to disable the sidecar, below annotation fields are needed.
While for now, there is no such configuration interface to do so.
Is it feasible to add configurable options on this kind of k/v pairs via
values.yaml
?The text was updated successfully, but these errors were encountered: