lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964354768
In order to perform an isolated knative test, I exported the knative service
created by the integration and modified it to create a new ksvc:
- changed the image to ghcr.io/knative/helloworld-go:latest
- removed the mounted volumes
- removed the heatlh check probes
The final result:
```
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
annotations:
serving.knative.dev/creator: kubernetes-admin
serving.knative.dev/lastModifier:
system:serviceaccount:a1b2c3d4e5:camel-k-operator
labels:
bindings.knative.dev/include: "true"
camel.apache.org/generation: "1"
camel.apache.org/integration: basic
name: basic
namespace: a1b2c3d4e5
spec:
template:
metadata:
annotations:
autoscaling.knative.dev/minScale: "1"
creationTimestamp: null
labels:
camel.apache.org/integration: basic
spec:
containerConcurrency: 0
containers:
- env:
- name: TARGET
value: "Go Sample v1"
image: ghcr.io/knative/helloworld-go:latest
name: integration
enableServiceLinks: false
imagePullSecrets:
- name: gcr-json-key
timeoutSeconds: 300
traffic:
- latestRevision: true
percent: 100
```
This ksvc worked all 3 services were created.
```
k get svc | grep basic
basic ClusterIP
None <none> 80/TCP
4m9s
basic-00001 ClusterIP
172.20.70.175 <none> 80/TCP,443/TCP
4m10s
basic-00001-private ClusterIP
172.20.1.209 <none>
80/TCP,443/TCP,9090/TCP,9091/TCP,8022/TCP,8012/TCP 4m10s
```
Then I changed the ksvc and added a heath probe that would never succeed:
```
readinessProbe:
successThreshold: 1
tcpSocket:
port: 3000
```
And now I get the same situation where the pod fails, and the basic service
is not created.
So I think I can assume that the lack of one svc is actually a consequence,
and not a cause of the pod failure.
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
