![]() ![]() Even though non-istio -set service.port=443-parameter at Helm install defines the value. However, your statement is correct I should formally try it out for verification. That's not configured on Istio-Side from my end and would behave totally different from any other workload deployed using istio. Have you tried installing it with the same parameters but without Istio enabled? Just to confirm the issue is not with the chart itself Regarding the HTTPS and port issues, unfortunately our charts are not tested to work with Istio so we can not provide real support for it. Afterwards it proceeds as it seems like skipping the affected action 655 not sure if action 656 till 1314 are skipped as well. #5 /opt/bitnami/magento/vendor/elasticsearc in /opt/bitnami/magento/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php on line 665 #4 /opt/bitnami/magento/vendor/ezimuel/ringphp/src/Core.php(341): GuzzleHttp\Ring\Future\CompletedFutureValue->then() #3 /opt/bitnami/magento/vendor/ezimuel/ringphp/src/Future/CompletedFutureValue.php(55): React\Promise\FulfilledPromise->then() #2 /opt/bitnami/magento/vendor/react/promise/src/FulfilledPromise.php(28): Elasticsearch\Connections\Connection->Elasticsearch\Connections\() #1 /opt/bitnami/magento/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(320): Elasticsearch\Connections\Connection->process5x圎rror() #0 /opt/bitnami/magento/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(665): Exception->_construct() PHP Fatal error: Uncaught Error: Wrong parameters for Elasticsearch\Common\Exceptions\ServerErrorResponseException(]]) in /opt/bitnami/magento/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:665 Magento 18:13:17.04 INFO => Running Magento install script Magento 18:13:16.93 INFO => Trying to connect to Elasticsearch Magento 18:13:16.82 DEBUG => Executing SQL command: Magento 18:13:16.79 INFO => Trying to connect to the database server Magento 12:50:20.19 INFO => Running Magento install scriptĬurrent version of RDBMS is not supported. When checking logs, I noticed it's hung at Running Magento install script: ![]() Warning BackOff 31s (x13 over 4m1s) kubelet Back-off restarting failed container Normal Pulled 3m39s (x3 over 5m40s) kubelet Container image "docker.io/bitnami/magento:2.4.2-debian-10-r135" already present on machine Normal Started 3m39s (x3 over 5m39s) kubelet Started container magento Normal Created 3m39s (x3 over 5m40s) kubelet Created container magento Warning Unhealthy 4m3s (x8 over 5m8s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500 Normal Started 5m38s kubelet Started container istio-proxy Normal Pulled 5m39s kubelet Container image "docker.io/istio/proxyv2:1.10.3" already present on machine Normal Created 5m39s kubelet Created container istio-proxy ![]() Normal Started 5m42s kubelet Started container istio-init Normal Created 5m42s kubelet Created container istio-init Normal Pulled 5m42s kubelet Container image "docker.io/istio/proxyv2:1.10.3" already present on machine ![]() Normal SuccessfulAttachVolume 5m52s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-4ceccbf2-ccb6-4932-97ab-fe1351b618a2" Normal Scheduled 5m53s default-scheduler Successfully assigned magento/magento-7d6d6966d7-sgkhw to kubernetes-worker01 Kubectl -n magento describe pod/magento-7d6d6966d7-sgkhw ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |