aloosnetmatch commented on issue #761:
URL: https://github.com/apache/solr-operator/issues/761#issuecomment-2721872746
We had our initial issues with the "nonp" cluster.
Here we "manually" configure the readinessGates
I took the time to spin up a new "test" cluster. A similar cluster without
the affinity rules
When i do a "kubectl get pod" on one of the nodes in both namespaces and
compare the results I spot this interesting part .
Under status I see the
type: Ready
status: 'False'
message: >-
corresponding condition of pod readiness gate
"solr.apache.org/isNotStopped" does not exist.**
```status:
phase: Running
conditions:
- type: PodReadyToStartContainers
status: 'True'
lastProbeTime: null
lastTransitionTime: '2025-03-13T14:57:53Z'
- type: Initialized
status: 'True'
lastProbeTime: null
lastTransitionTime: '2025-03-13T14:57:55Z'
- type: Ready
status: 'False'
lastProbeTime: null
lastTransitionTime: '2025-03-13T14:57:38Z'
**reason: ReadinessGatesNotReady
message: >-
corresponding condition of pod readiness gate
"solr.apache.org/isNotStopped" does not exist.**
- type: ContainersReady
status: 'True'
lastProbeTime: null
lastTransitionTime: '2025-03-13T15:00:32Z'
- type: PodScheduled
status: 'True'
lastProbeTime: null
lastTransitionTime: '2025-03-13T14:57:38Z'```
Here are the files that i used to compare:
[nonp-cluster.txt](https://github.com/user-attachments/files/19232472/nonp-cluster.txt)
[test-cluster.txt](https://github.com/user-attachments/files/19232471/test-cluster.txt)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
