I did a deploy for the rustfs-operator(v0.0.1) on a kubernetes cluster with 3 replicas , and . well , it didn't start.
# k get all -n rustfs-system
NAME READY STATUS RESTARTS AGE
pod/rustfs-operator-68c89c5d78-lq9z4 0/1 CrashLoopBackOff 5 (103s ago) 4m24s
pod/rustfs-operator-68c89c5d78-t5f9x 0/1 CrashLoopBackOff 5 (76s ago) 4m24s
pod/rustfs-operator-68c89c5d78-zk2ct 0/1 CrashLoopBackOff 5 (100s ago) 4m24s
pod/rustfs-operator-console-84c4644c94-n5qng 1/1 Running 0 6h13m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/rustfs-operator-console ClusterIP x <none> 9090/TCP 7h16m
service/rustfs-operator-metrics ClusterIP x <none> 8080/TCP 7h16m
service/rustfs-operator-sts ClusterIP x <none> 4223/TCP 7h16m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/rustfs-operator 0/3 3 0 4m24s
deployment.apps/rustfs-operator-console 1/1 1 1 6h52m
NAME DESIRED CURRENT READY AGE
replicaset.apps/rustfs-operator-68c89c5d78 3 3 0 4m24s
replicaset.apps/rustfs-operator-console-6784ccdc8f 0 0 0 6h52m
replicaset.apps/rustfs-operator-console-6fb9865b5d 0 0 0 6h27m
replicaset.apps/rustfs-operator-console-84c4644c94 1 1 1 6h13m
#k describe -n rustfs-system pod/rustfs-operator-68c89c5d78-t5f9x
.....
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 2
......
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 4m27s default-scheduler Successfully assigned rustfs-system/rustfs-operator-68c89c5d78-t5f9x to cluster
Normal Pulling 4m27s kubelet Pulling image "rustfs/operator:0.0.1"
Normal Pulled 4m15s kubelet Successfully pulled image "rustfs/operator:0.0.1" in 12.137s (12.137s including waiting). Image size: 39335182 bytes.
Normal Created 80s (x6 over 4m15s) kubelet Container created
Normal Started 80s (x6 over 4m15s) kubelet Container started
Normal Pulled 80s (x5 over 4m14s) kubelet Container image "rustfs/operator:0.0.1" already present on machine and can be accessed by the pod
Warning BackOff 23s (x16 over 4m13s) kubelet Back-off restarting failed container operator in pod rustfs-operator-68c89c5d78-t5f9x_rustfs-system(d171ce91-158e-47b3-ac8b-b05927ab41d4)
# k logs -n rustfs-system pod/rustfs-operator-68c89c5d78-t5f9x
error: unexpected argument '--leader-elect' found
Usage: operator server
For more information, try '--help'.
I saw that you are using the same code in main/latest , so it doesn't look like it is an issue of version.
Any suggestion on what I might be doing wrong ?
Is the leader-elect parameter required for the rustfs server ? I searched the documentation for that argument , but I couldn't find it.
If it's not required, can you please remove it ?
I did a deploy for the rustfs-operator(v0.0.1) on a kubernetes cluster with 3 replicas , and . well , it didn't start.
I saw that you are using the same code in main/latest , so it doesn't look like it is an issue of version.
Any suggestion on what I might be doing wrong ?
Is the
leader-electparameter required for the rustfs server ? I searched the documentation for that argument , but I couldn't find it.If it's not required, can you please remove it ?