You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Traefik return 404 page not found - Kubernetes on Cloudstack 4.17.2.0 #7517
According to the guide: On successfully deploying the yaml file, a new Public IP Address in the same network as the cluster will be created. It will automatically have the firewall and port forwarding rules configured to distribute any traffic amongst the cluster worker nodes
However, upon inspecting the LB rules, I noticed that the control node was also added as a backend server ?
Furthermore, I created and deployed a file that defines a basic deployment, service, and ingress. However, when I curl http://k8s.lab.com.vn/, the response is "404 page not found". Is there a mistake in my YAML file?
Thanks for your help!
Today I following this procedure to deploy k8s with traefik ingress.
I am facing an error with traefik ingress: "Error syncing load balancer: failed to ensure load balancer: error retrieving load balancer rules: invalid character '<' looking for beginning of value"
Cloudstack version: 4.19.0.1
K8S: Version: v1.26.0
traefik: v3.1.2
Here is full describe of service:
Name: traefik
Namespace: default
Labels: app.kubernetes.io/instance=traefik-default
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=traefik
helm.sh/chart=traefik-30.1.0
Annotations: meta.helm.sh/release-name: traefik
meta.helm.sh/release-namespace: default
service.beta.kubernetes.io/cloudstack-load-balancer-proxy-protocol: enabled
Selector: app.kubernetes.io/instance=traefik-default,app.kubernetes.io/name=traefik
Type: LoadBalancer
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.107.132.3
IPs: 10.107.132.3
Port: http 80/TCP
TargetPort: http/TCP
NodePort: http 30893/TCP
Endpoints: <none>
Port: https 443/TCP
TargetPort: https/TCP
NodePort: https 32256/TCP
Endpoints: <none>
Session Affinity: None
External Traffic Policy: Cluster
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal EnsuringLoadBalancer 58s (x6 over 2m14s) service-controller Ensuring load balancer
Warning SyncLoadBalancerFailed 58s (x6 over 2m14s) service-controller Error syncing load balancer: failed to ensure load balancer: error retrieving load balancer rules: invalid character '<' looking for beginning of value
2024-08-21 22:09:17,133 WARN [c.c.k.c.u.KubernetesClusterUtil] (API-Job-Executor-47:ctx-4b9b2287 job-16540 ctx-d327ad2e) (logid:584f4248) API endpoint for Kubernetes cluster : tuanlab-k8s not available
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at java.base/sun.security.ssl.SSLSocketImpl.handleEOF(SSLSocketImpl.java:1701)
at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1519)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1421)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:456)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:427)
at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:580)
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:201)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1613)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1541)
at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
at com.cloud.kubernetes.cluster.utils.KubernetesClusterUtil.isKubernetesClusterServerRunning(KubernetesClusterUtil.java:239)
at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterStartWorker.startKubernetesClusterOnCreate(KubernetesClusterStartWorker.java:546)
at com.cloud.kubernetes.cluster.KubernetesClusterManagerImpl.startKubernetesCluster(KubernetesClusterManagerImpl.java:1321)
at org.apache.cloudstack.api.command.user.kubernetes.cluster.CreateKubernetesClusterCmd.execute(CreateKubernetesClusterCmd.java:294)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:172)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:112)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:654)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:602)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:489)
at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:478)
at java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
... 28 more
Thanks for you idea.
Sorry, but are you mistaken? Deleting the main release and installing version 1.1.0 are the same. I have checked the two manifest deployment.yaml files, and they are exactly the same.
Thanks for you idea.
Sorry, but are you mistaken? Deleting the main release and installing version 1.1.0 are the same. I have checked the two manifest deployment.yaml files, and they are exactly the same.
Thanks for you idea.
Sorry, but are you mistaken? Deleting the main release and installing version 1.1.0 are the same. I have checked the two manifest deployment.yaml files, and they are exactly the same.
It is used to recreate ccm with latest 1.1.0
If you have already installed 1.1.0, ignore it
Activity
weizhouapache commentedon May 18, 2023
@tuanhoangth1603
have you solved the issue ?
tuanhoangth1603 commentedon May 18, 2023
I follow this guide and the issue was solved.
https://doc.traefik.io/traefik/getting-started/install-traefik/
tuanhoangth1603 commentedon Aug 21, 2024
Hello,
Today I following this procedure to deploy k8s with traefik ingress.
I am facing an error with traefik ingress: "Error syncing load balancer: failed to ensure load balancer: error retrieving load balancer rules: invalid character '<' looking for beginning of value"
Here is full describe of service:
weizhouapache commentedon Aug 21, 2024
any logs on cloudstack management server and in the pod
cloud-controller-manager?tuanhoangth1603 commentedon Aug 21, 2024
Thanks for your reply. Here is logs of CCM
tuanhoangth1603 commentedon Aug 21, 2024
and I also found this log in mgmt to be helpful
tuanhoangth1603 commentedon Aug 22, 2024
Hi @weizhouapache,
Do you have any suggestion for this issue ?
weizhouapache commentedon Aug 22, 2024
@tuanhoangth1603
it looks like failed to get the cks nodes/vms
"tuanlab-k8s-control-1917579d77d"and"tuanlab-k8s-node-191757a899c"can you try with cloudstack-kubernetes-provider v1.1.0 ?
delete cloudstack-kubernetes-provider 1.0.0
kubectl delete -f
https://raw.githubusercontent.com/apache/cloudstack-kubernetes-provider/main/deployment.yaml
install 1.1.0
kubectl apply -f
https://github.com/apache/cloudstack-kubernetes-provider/releases/download/v1.1.0/deployment.yaml
tuanhoangth1603 commentedon Aug 22, 2024
Thanks for you idea.
Sorry, but are you mistaken? Deleting the main release and installing version 1.1.0 are the same. I have checked the two manifest deployment.yaml files, and they are exactly the same.
weizhouapache commentedon Aug 22, 2024
It is used to recreate ccm with latest 1.1.0
weizhouapache commentedon Aug 22, 2024
It is used to recreate ccm with latest 1.1.0
If you have already installed 1.1.0, ignore it