[Bug] Does the MongoDB operator support the Hygon C86 7375 32 core Processor

[huliangshan]

What did you do to encounter the bug?
Steps to reproduce the behavior:

1. The CPU mechanism of k8s node is hygon
2. He will trigger a restart, and the logs of the last and current restarts cannot be seen

What did you expect?
A clear and concise description of what you expected to happen.

What happened instead?
A clear and concise description of what happened instead

Screenshots

Operator Information

• Operator Version 0.12.0
• MongoDB Image used null

Kubernetes Cluster Information

• Distribution
• Version v1.24.17
• Image Registry location (quay, or an internal registry) quay

Additional context
Add any other context about the problem here.

If possible, please include:

• The operator logs
• Below we assume that your replicaset database pods are named mongo-<>. For instance:

❯kubectl get pod -n mongodb
NAME                                          READY   STATUS             RESTARTS       AGE
mongodb-kubernetes-operator-bdbcc5f74-4gq49   0/1     CrashLoopBackOff   45 (91s ago)   3h28m

But I can start it normally using the manage command in the image, provided that the environment variables are preset

[huliangshan]

View node sys log：

kernel: [535683.124138] entrypoint[213248]: segfault at 560c9f594320 ip 00007fd48127dead sp 00007ffe272f9468 error 4 in libc-2.28.so[7fd481259000+1cd000]

[m1kola]

Could you please share describe of the pod?

[huliangshan]