brickpattern opened a new issue, #623:
URL: https://github.com/apache/solr-operator/issues/623
**Issue:** IP used in startup Probe happens to be EKS Node IP and not the
K8S cluster internal IPs
**Setup:**
Environment: AWS EKS
EKS : 1.27
Solr Operator : v0.7.1
ZK: inbuilt
Solr Cloud: v9.3
All modules running in same namespace Solr
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 19m default-scheduler Successfully assigned
solr/solr-solrcloud-0 to ip-xx-yy-xx-yy.us-west-2.internal
Normal Pulled 19m kubelet Container image
"library/busybox:1.28.0-glibc" already present on machine
Normal Created 19m kubelet Created container cp-solr-xml
Normal Started 19m kubelet Started container cp-solr-xml
Normal Pulling 19m kubelet Pulling image
"my-custom-sol-registry:0.2"
Normal Pulled 19m kubelet Successfully pulled image
"my-custom-sol-registry:0.2" in 17.833156703s (17.833176263s including waiting)
Normal Created 19m kubelet Created container
solrcloud-node
Normal Started 19m kubelet Started container
solrcloud-node
Warning Unhealthy 19m kubelet Startup probe failed: Get
"http://xx.yy.xx.yy:8983/solr/admin/info/system": context deadline exceeded
(Client.Timeout exceeded while awaiting headers)
```
Q - should the Startup Probe is hitting the actual NODE (underlying eks
node) IP?
--
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]
