You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/08/30 10:46:41 UTC
[GitHub] [camel-k] fredcoq opened a new issue #2528: kamelet binding : camel controller fail reconcile the kafka sink resource.
fredcoq opened a new issue #2528:
URL: https://github.com/apache/camel-k/issues/2528
**What is observed:**
Strimzi Kafka cluster and Camel controller are installed and healthy.
KafkaTopic: my-topic is created an healthy.
The KameletBinding minio-resource is submitted to the cluster.
The minio-source-binding is created but stay in pending state.
- Kubernetes ressource satus
```Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning KameletError 6m50s (x20 over 45m) camel-k-kamelet-binding-controller Cannot reconcile KameletBinding minio-source-binding: could not determine sink URI: the server could not find the requested resource (get kafkas.kafka.strimzi.io my-cluster)
```
- camel-controler pod log:
```{"level":"error","ts":1627235132.8817902,"logger":"controller-runtime.manager.controller.kamelet-binding-controller","msg":"Reconciler error","name":"minio-source-binding","namespace":"kafka","error":"could not determine sink URI: the server could not find the requested resource (get kafkas.kafka.strimzi.io my-cluster)","errorVerbose":"the server could not find the requested resource (get kafkas.kafka.strimzi.io my-cluster)\ncould not determine sink URI ....```
**To reproduce :**
Software & releases
* Minikube Kubernetes 1.20.2
* Private docker local registry.
* Kafka 2.8.0 kafka:my-cluster installed with strimzi operator in namespace kafka (plain text and no authentication)
* Camel-k operator 1.5.0 installed with helm in namespace kafka.
**What is expected:**
Have the minio-source-binding resource created and in healthy state.
As I was suspecting some authorizations issueI, I modified the camel controler RBAC to a cluster role without any improvments.
-------------------
**Additional set-up infoamtions.**
Camel-k installation configuration
```
helm install \
--namespace kafka \
--set platform.build.registry.address=192.168.1.40:45000 \
--set platform.build.registry.insecure=true \
--set platform.profile=kubernetes \
--set plateform.cluster=kubernetes \
--generate-name \
camel-k/camel-k
```
KameletBinding spec.
```
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: minio-source-binding
namespace: kafka
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: minio-source
properties:
accessKey: -----------
bucketName: test
endpoint: "http://minio2.kafka:9000"
secretKey: ----------
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
```
KafkaTopic spec.
```
apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaTopic
metadata:
name: my-topic
namespace: kafka
labels:
strimzi.io/cluster: my-cluster
spec:
partitions: 1
replicas: 1
config:
retention.ms: 7200000
segment.bytes: 1073741824
```
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] fredcoq closed issue #2528: kamelet binding : camel controller fail reconcile the kafka sink resource.
Posted by GitBox <gi...@apache.org>.
fredcoq closed issue #2528:
URL: https://github.com/apache/camel-k/issues/2528
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] fredcoq commented on issue #2528: kamelet binding : camel controller fail reconcile the kafka sink resource.
Posted by GitBox <gi...@apache.org>.
fredcoq commented on issue #2528:
URL: https://github.com/apache/camel-k/issues/2528#issuecomment-908239470
This recent commit I just discovered should address it https://github.com/apache/camel-k/commit/ec840637294200f593ca3e8fcf9c9dae5ac20109
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] fredcoq closed issue #2528: kamelet binding : camel controller fail reconcile the kafka sink resource.
Posted by GitBox <gi...@apache.org>.
fredcoq closed issue #2528:
URL: https://github.com/apache/camel-k/issues/2528
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] fredcoq commented on issue #2528: kamelet binding : camel controller fail reconcile the kafka sink resource.
Posted by GitBox <gi...@apache.org>.
fredcoq commented on issue #2528:
URL: https://github.com/apache/camel-k/issues/2528#issuecomment-908174675
I tested also topics created with v1beta1 api : same behavior of camel-k operator which is not able to query kafka cluster resources. In fact since stimzi operator 0.23 even if it accept the creation of resources (topics and users) with v1beta1 api they are managed as v1beta2.
Re-tested on a new strimzi cluster version 0.22 : it works as expected.
Latest version of kafka that are managed by strimizi 0.23+ should require an update of camel-k strimzi api.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org