lburgazzoli opened a new issue #2445:
URL: https://github.com/apache/camel-k/issues/2445
I have the following scenarion:
```
➜ k tree klb cd208ccf823b044089c48669c1ec1d6e4
NAMESPACE NAME
READY REASON AGE
default KameletBinding/cd208ccf823b044089c48669c1ec1d6e4
True 143m
default └─Integration/cd208ccf823b044089c48669c1ec1d6e4
False ReplicaSetNotReady 143m
default
├─ConfigMap/cd208ccf823b044089c48669c1ec1d6e4-application-properties -
143m
default ├─ConfigMap/cd208ccf823b044089c48669c1ec1d6e4-source-000
- 143m
default ├─Deployment/cd208ccf823b044089c48669c1ec1d6e4
- 143m
default │ └─ReplicaSet/cd208ccf823b044089c48669c1ec1d6e4-585565bdf5
- 143m
default │ └─Pod/cd208ccf823b044089c48669c1ec1d6e4-585565bdf5-nptc7
False ContainersNotReady 143m
default └─IntegrationKit/kit-cd208ccf823b044089c48669c1ec1d6e4
- 143m
```
so the POD is not ready for an internal error but the phase of the
integration is still reported as `Running` and the kamelet binding as `Ready`:
```
➜ k get klb cd208ccf823b044089c48669c1ec1d6e4
NAME PHASE
cd208ccf823b044089c48669c1ec1d6e4 Ready
➜ k get it cd208ccf823b044089c48669c1ec1d6e4
NAME PHASE KIT REPLICAS
cd208ccf823b044089c48669c1ec1d6e4 Running 1
➜ k get pods | grep cd208ccf823b044089c48669c1ec1d6e4
cd208ccf823b044089c48669c1ec1d6e4-585565bdf5-nptc7 0/1
CrashLoopBackOff 32 141m
```
I wonder if we can ave a better way to report that the pod is not running.
By looking at the integration resource only, one may mistakenly think the
integration is running but it is not.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
