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

Use helm to deploy Piraeus to connect to linstor with multiple controllers #480

Closed
am6737 opened this issue May 27, 2023 · 2 comments
Closed
Labels
enhancement New feature or request v1 This affects only Operator v1

Comments

@am6737
Copy link

am6737 commented May 27, 2023

#piraeusdatastore/linstor-csi#184
I was modified the value in helm deployment of Piraeus. The yaml file controllerEndpoint: "10.10.10.1, 10.10.10.2, 10.10.10.3"
The piraeus-csi-node-linstor-endpoint parameter still exists, is it because it exists and causes failure? How can I delete it?

piraeus-csi-node

  linstor-csi-plugin:
    Container ID:  
    Image:         quay.io/piraeusdatastore/piraeus-csi:v1.1.0
    Image ID:      
    Port:          9808/TCP
    Host Port:     0/TCP
    Args:
      --csi-endpoint=unix://$(CSI_ENDPOINT)
      --node=$(KUBE_NODE_NAME)
      --linstor-endpoint=$(LS_CONTROLLERS)
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Liveness:       http-get http://:9808/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      CSI_ENDPOINT:          /csi/csi.sock
      DRIVER_REG_SOCK_PATH:  /var/lib/kubelet/plugins/linstor.csi.linbit.com/csi.sock
      KUBE_NODE_NAME:         (v1:spec.nodeName)
      LS_CONTROLLERS:        10.10.10.1,10.10.10.2,10.10.10.3

piraeus-operator log

2023-05-27T12:31:51Z	DEBUG	LinstorSatelliteSet-controller	reconcile spec	{"Op": "reconcileSpec", "Controller": "linstorsatelliteset", "Spec": {"priorityClassName":"","storagePools":{"lvmPools":[],"lvmThinPools":[],"zfsPools":[]},"automaticStorageType":"None","sslSecret":"","drbdRepoCred":"","imagePullPolicy":"IfNotPresent","satelliteImage":"quay.io/piraeusdatastore/piraeus-server:v1.23.0","controllerEndpoint":"10.10.10.1,10.10.10.2,10.10.10.3","resources":{},"kernelModuleInjectionImage":"quay.io/piraeusdatastore/drbd9-bionic:v9.1.14","kernelModuleInjectionMode":"Compile","kernelModuleInjectionExtraVolumeMounts":null,"kernelModuleInjectionResources":{},"affinity":{},"tolerations":[],"serviceAccountName":"","additionalEnv":null,"monitoringImage":"quay.io/piraeusdatastore/drbd-reactor:v1.2.0","monitoringBindAddress":"","linstorHttpsClientSecret":"","sidecars":null,"extraVolumes":null,"mountDrbdResourceDirectoriesFromHost":false}}
2023-05-27T12:31:51Z	ERROR	LinstorSatelliteSet-controller	could not fetch nodes from LINSTOR, continue with empty node list	{"Name": "piraeus-ns", "Namespace": "piraeus-datastore", "Op": "reconcileLinstorStatus", "error": "Get \"/v1/nodes?limit=0&nodes=k8s-1&nodes=k8s-3&nodes=k8s-2&offset=0\": unsupported protocol scheme \"\""}
@WanzenBug
Copy link
Member

@WanzenBug WanzenBug added enhancement New feature or request v1 This affects only Operator v1 labels May 30, 2023
@am6737
Copy link
Author

am6737 commented May 30, 2023

In Operator v1 we add this argument explicitly: https://github.com/piraeusdatastore/piraeus-operator/blob/master/pkg/controller/linstorcsidriver/linstorcsidriver_controller.go#LL706C1-L706C43

We can problably remove that.

I think it should be more flexible as optional
Thank you for everything you 've done

@am6737 am6737 closed this as completed May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v1 This affects only Operator v1
Projects
None yet
Development

No branches or pull requests

2 participants