-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The two Chart.yaml still uses unavailable image versions 3.5.1 and 13.1.5 #39
Comments
@EricWang1358 The references are to the charts, not the images. However, this seems to be either a local or a temporary issue, since both charts where able to be downloaded in the test-pipeline. Could you please retry? |
Issue: Deployment Timeout for Multiple Pods During Local DeploymentDescriptionThe former problem has been solved temporarily by installing docker service in the WSL2 env instead of using the WSL2 support in the host windows env's Docker Destop. (Wondering why nothing about Docker is mentioned but the Pom file includes the use of k3s-plugin which create k3s clusters in docker and it will collide with the k3s outside docker env by using the same 6443 port. After that, the process still failed due to several pods not becoming Logs
Environment
Pods Failing to DeployThe following pods were reported as timing out or failing to reach the
Steps to Reproduce
Maybe the answers to the Qs below may help
Attachments
Thank you for your patience and help. It would be great help to me as I am so interested in this project, but my deployment skills frustrate me a lot. Added progress.
It seems that the docker container itself encountered some network issue. |
Hi, there actually is a networking issue in k3s fur current ubuntu versions, since "br_netfilter" is not enabled. Try to enable it via modprobe br_netfilter (see https://stackoverflow.com/questions/48148838/kube-dns-error-reply-from-unexpected-source/48151279#48151279) |
Title: The two Chart.yaml still uses unavailable image versions 3.5.1 and 13.1.5
Description of the Issue
The current
Chart.yaml
file references unavailable and outdated image versions, which causes image pull errors during deployment. Below are the problematic entries:Apisix
The image version
3.5.1
is no longer available on Docker Hub, leading to failed image pulls for Apisix.Postgresql
The image version
13.1.5
for Postgresql is also unavailable, causing deployment issues.Steps to Reproduce
mvn clean deploy -Plocal
.Steps to reproduce:
Suggested Solution
Please update the
Chart.yaml
file to reference valid image versions. And even I tried update those manually with 15.3.0 and 3.5.0 (which can be pulled using k3s, it still report the error. I am a little bit frustrated and wonder if you could try reclone your project in a different machine to see if you would encouter the same problem. That would be such a great help! “Maybe there are some more config before just 'mvn clean deply' ? Like the helm config or dealing with both k3s and Docker Desktop. Thanks for your help.System Information:
Also, with problem faced after the [error] report:
During the Maven build process, we encountered deployment timeouts for the
provider-apisix-control-plane
andprovider-apisix-data-plane
components. The deployment rollout could not complete within the allocated timeout, and the following error messages were logged:Expected Behavior:
The deployments for both
provider-apisix-control-plane
andprovider-apisix-data-plane
should complete successfully without exceeding the timeout period. It may be also due to the pull fail above.The text was updated successfully, but these errors were encountered: