test traefik LoadBalancer error?

[dai0384448]

ENV：
CentOS Linux release 7.7.1908 (Core)
helm Version:"v3.3.4",
Docker version 19.03.1, build 74b1e89
kubectl ：v1.20.15

ISSUES:
Follow the document https://oracle.github.io/weblogic-kubernetes-operator/quickstart/create-domain/
The configuration fails according to the document. The error is as follows：

[root@master weblogic-kubernetes-operator]# curl -v -H 'host: sample-domain1.org' http://192.168.1.225:30305/weblogic/ready

• About to connect() to 192.168.1.225 port 30305 (#0)
• Trying 192.168.1.225...
• Connected to 192.168.1.225 (192.168.1.225) port 30305 (#0)

GET /weblogic/ready HTTP/1.1
User-Agent: curl/7.29.0
Accept: /
host: sample-domain1.org

< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Sat, 05 Mar 2022 06:25:13 GMT
< Content-Length: 19
<
404 page not found

• Connection #0 to host 192.168.1.225 left intact
  [root@master weblogic-kubernetes-operator]#
  

[dai0384448]

command： kubectl get svc --all-namespaces
EXTERNAL-IP Is there an impact here?

[lennyphan]

Shouldn't have any impact. What helm command did you use to create the ingress? Can you do a describe on the ingress?

e.g.
kubectl describe ingress sample-domain1-traefik -n sample-domain1-ns

[dai0384448]

$ helm install traefik-operator traefik/traefik
--namespace traefik
--values kubernetes/samples/charts/traefik/values.yaml
--set "kubernetes.namespaces={traefik}"

$ helm upgrade traefik-operator traefik/traefik
--namespace traefik
--reuse-values
--set "kubernetes.namespaces={traefik,sample-domain1-ns}"

[dai0384448]

I operate according to the official manual. Port 80 is mapped to port 30305. Where is it set?There is only external port in VALUES. Could you tell me where to set the internal port?Thank you very much!

[lennyphan]

It's configured as a nodeport in the traefik helm chart provided in kubernetes/samples/charts/traefik/values.yaml

[dai0384448]

Where is the internal port 80 set?

[lennyphan]

I think 80 is a default port for traefik. I couldn't reproduce your issue. can you do a 'kubectl describe' on the 'traefik-operator' service to see if we can tell what endpoints it maps resolves?

[dai0384448]

[root@master ingresses]# kubectl describe pods traefik -n traefik
Name: traefik-operator-56754f97d8-72hnr
Namespace: traefik
Priority: 0
Node: node1/192.168.1.226
Start Time: Tue, 15 Mar 2022 00:01:39 +0800
Labels: app.kubernetes.io/instance=traefik-operator
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=traefik
helm.sh/chart=traefik-9.1.1
pod-template-hash=56754f97d8
Annotations:
Status: Running
IP: 10.244.1.2
IPs:
IP: 10.244.1.2
Controlled By: ReplicaSet/traefik-operator-56754f97d8
Containers:
traefik-operator:
Container ID: docker://437e6881a414f4d28ad1364009205b58d3c5baa40e4ebfa7334246ae50005101
Image: traefik:2.2.8
Image ID: docker-pullable://traefik@sha256:f5af5a5ce17fc3e353b507e8acce65d7f28126408a8c92dc3cac246d023dc9e8
Ports: 9000/TCP, 8000/TCP, 8443/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP
Args:
--global.checknewversion
--global.sendanonymoususage
--entryPoints.traefik.address=:9000/tcp
--entryPoints.web.address=:8000/tcp
--entryPoints.websecure.address=:8443/tcp
--api.dashboard=true
--ping=true
--providers.kubernetescrd
--providers.kubernetesingress
--log.level=INFO
State: Running
Started: Tue, 15 Mar 2022 00:02:01 +0800
Ready: True
Restart Count: 0
Liveness: http-get http://:9000/ping delay=10s timeout=2s period=10s #success=1 #failure=3
Readiness: http-get http://:9000/ping delay=10s timeout=2s period=10s #success=1 #failure=1
Environment:
Mounts:
/data from data (rw)
/tmp from tmp (rw)
/var/run/secrets/kubernetes.io/serviceaccount from traefik-operator-token-kktns (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
data:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
tmp:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
traefik-operator-token-kktns:
Type: Secret (a volume populated by a Secret)
SecretName: traefik-operator-token-kktns
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:

[root@master ingresses]#

[dai0384448]

I configured the entry, but I can't see the SVC

[jshum2479]

When the LB EXTERNAL-IP column is , that means your k8s does not have an LB opened up to the public, so you have to access the traefik service via the node port. In this case, it should be your kubernetes cluster address and port combo. 80:30305 , 443:30443 (first is the target port of the service, second is the node port value)

kubectl cluster-info

I take it your 192.168.1.225 in http://192.168.1.225:30305/weblogic/ready is your curl command is the k8s cluster address.
If not you need to change it.

Also, you have three matching rules

path prefix /console
host ....

So in your curl command host header, you need to use the host you specified in your IngressRoute as your path is /weblogic/ready, it won't match the /console rule. If nothing matches then traefik gives you a 404.

[robertpatrick]

@dai0384448 is this still an issue for you? If so, can you please review @jshum2479's questions/feedback and respond?

[tbarnes-us]

It's been several months without a response, closing.