You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "pguptajsq (via GitHub)" <gi...@apache.org> on 2024/11/26 14:43:38 UTC
[I] pipe and integration creation based on YAML file fails , [camel-k]
pguptajsq opened a new issue, #5963:
URL: https://github.com/apache/camel-k/issues/5963
### What happened?
i have this yaml and applied , it created pipe and integration but it showing error
```
kubectl logs pipe/test
error: no kind "Pipe" is registered for version "camel.apache.org/v1" in scheme "pkg/scheme/scheme.go:28"
```
and also Integration
```
kubectl get it
NAME PHASE READY RUNTIME PROVIDER RUNTIME VERSION CATALOG VERSION KIT REPLICAS
test Error False quarkus 3.15.0 3.15.0 kit-ct1up2gro8bs73dchil0 1
```
```
kind: Pipe
metadata:
name: test
namespace: camel-k
spec:
sink:
properties:
channel: channelname
destinationName: destinan
password: '{{pass}}'
queueManager: JSQ.UAT.BSSB
serverName: serverip
serverPort: "1414"
username: app
ref:
apiVersion: camel.apache.org/v1
kind: Kamelet
name: jms-ibm-mq-sink
source:
properties:
queueNameOrArn: queue
region: us-west-2
accessKey: "dummy"
secretKey: "dummy/sk45"
ref:
apiVersion: camel.apache.org/v1
kind: Kamelet
name: aws-sqs-source
```
Any idea what's missing here?
Another Query how we can pass ServiceAccount to pipe yaml instead of aws accesskey and secretkey
### Steps to reproduce
_No response_
### Relevant log output
_No response_
### Camel K version
_No response_
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by Andrea Cosentino <an...@gmail.com>.
This
({{ env:AWS_ACCESS_KEY_ID }})
Should be RAW({{ env:AWS_ACCESS_KEY_ID }})
Same for the secret key. I wrote it above
Il mar 3 dic 2024, 10:05 pguptajsq (via GitHub) <gi...@apache.org> ha scritto:
>
> pguptajsq commented on issue #5963:
> URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513928561
>
> `apiVersion: camel.apache.org/v1
> kind: Pipe
> metadata:
> name: test-backend-sqs-to-ibmmq-pavan
> namespace: camel-k
> labels:
> helm.sh/chart: universal-chart_v2.48.4
> app: test-backend
> junipersquare.com/initiating_pull_request: pr-1427
> junipersquare.com/initiating_repo: test-backend
> junipersquare.com/requestor: euanlau
> tags.datadoghq.com/env: prpay1427
> tags.datadoghq.com/version: pr-1427
> annotations:
> app: payments-backend1
> department: eng
> junipersquare.com/initiating_pull_request: pr-1427
> junipersquare.com/initiating_repo: test-backend1
> junipersquare.com/requestor: euanlau
> product: gpx fa
> tags.datadoghq.com/env: prpay1427
> tags.datadoghq.com/version: pr-1427
> team: payments
> annotations:
> app: payments-backend1
> trait.camel.apache.org/kubernetes.volumes: |
> volumes:
> - name: aws-credentials-volume
> secret:
> secretName: camel-sqs-cred # Reference the secret where
> AWS credentials are stored
> volumeMounts:
> - mountPath: /etc/camel/resources.d/_secrets/camel-sqs-cred #
> Mount path for the secret
> name: aws-credentials-volume
> trait.camel.apache.org/kubernetes.env: |
> - name: AWS_ACCESS_KEY_ID
> valueFrom:
> secretKeyRef:
> name: camel-sqs-cred
> key: aws-access-key-id # AWS access key from the secret
> - name: AWS_SECRET_ACCESS_KEY
> valueFrom:
> secretKeyRef:
> name: camel-sqs-cred
> key: aws-secret-access-key # AWS secret access key from
> the secret
>
> spec:
> source:
> ref:
> kind: Kamelet
> apiVersion: camel.apache.org/v1
> name: aws-sqs-source
> properties:
> queueNameOrArn: "queuename"
> region: "us-west-2"
> accessKey: "({{ env:AWS_ACCESS_KEY_ID }})"
> secretKey: "({{ env:AWS_SECRET_ACCESS_KEY }})"
> sink:
> ref:
> kind: Kamelet
> apiVersion: camel.apache.org/v1
> name: jms-ibm-mq-sink
> properties:
> channel: "test.TO.BSSB.UAT.CHAN"
> destinationName: "test.UAT.BSSB.MT.INPUT"
> password: "{{/mq-app-password}}"
> queueManager: "JSQ.UAT.BSSB"
> serverName: "ip"
> serverPort: "1414"
> username: "app"`
>
>
> --
> 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
>
>
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2506528249
Yes, the [trait configuration in Pipes](https://camel.apache.org/camel-k/2.5.x/pipes/pipes.html#_traits_configuration) is different.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2507215611
Hello. All the information is provided in the links in the documentation posted in previous comments, please, go through it.
1. You must specify traits via annotation
2. Once you've specified the secret to use, you can use any camel properties normally as `{{my.camel.property}}`
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2516142634
getting kubectl apply -f pipe1.yaml
Error from server (BadRequest): error when creating "pipe1.yaml": Pipe in version "v1" cannot be handled as a Pipe: strict decoding error: unknown field "mounts" getting this
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2514491126
That component, with that authentication mechanism,have been around for many years, so I can only suppose it is something on your side. We cannot help more than this.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2502901531
this is sample of pipe yaml . i am passing service account in pipe but still getting beloow error
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: aws2-sqs://ququ?accessKey=xxxxxx&amazonAWSHost=amazonaws.com&autoCreateQueue=false&delay=500&deleteAfterRead=true&greedy=false&overrideEndpoint=false&protocol=https®ion=us-west-2&secretKey=xxxxxx&useDefaultCredentialsProvider=false due to: useDefaultCredentialsProvider is set to false, useProfileCredentialsProvider is set to false, useSessionCredentials is set to false, AmazonSQSClient or accessKey and secretKey must be specified
`apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
spec:
serviceAccountName: camel-k-routes
sink:
properties:
channel:pavan.TO.BSSB.UAT.CHAN
destinationName: pavanUAT.BSSB.MT.INPUT
password: '{{pavan-backend/mq-app-password}}'
queueManager:paban.UAT.BSSB
serverName: ip
serverPort: "1414"
username: app
ref:
apiVersion: camel.apache.org/v1
kind: Kamelet
name: jms-ibm-mq-sink
source:
properties:
queueNameOrArn: queuearn
region: us-west-2
ref:
apiVersion: camel.apache.org/v1
kind: Kamelet
name: aws-sqs-source`
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2502756025
how we can pass ServiceAccount to pipe yaml instead of aws accesskey and secretkey to access aws sqs ?
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2516528007
Please, you need to carefully read and understand the solutions we have already proposed. This problem was previously discussed in this thread [1]. The configuration of annotations in Pipes is different than in Integrations.
[1] https://github.com/apache/camel-k/issues/5963#issuecomment-2506528249
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513781688
Okay , apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: sqs-to-ibmmq
namespace: camel-k
labels:
annotations:
trait.camel.apache.org/kubernetes.volumes: |
volumes:
- name: aws-credentials-volume
secret:
secretName: camel-sqs-cred # Reference the secret where AWS credentials are stored
volumeMounts:
- mountPath: /etc/camel/resources.d/_secrets/camel-sqs-cred # Mount path for the secret
name: aws-credentials-volume
trait.camel.apache.org/kubernetes.env: |
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-access-key-id # AWS access key from the secret
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-secret-access-key # AWS secret access key from the secret
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queuename"
region: "us-west-2"
accessKey: "{{ env:AWS_ACCESS_KEY_ID }}"
secretKey: "{{ env:AWS_SECRET_ACCESS_KEY }}"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{{mq-app-password}}"
queueManager: "reat.UAT.BSSB"
serverName: "IP"
serverPort: "1414"
username: "app" , i tried this yaml also. but
Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create route source: Route(source)[From[aws2-sqs:{{queueNameOrArn}}?accessKey=xxxxxx because of Failed to resolve endpoint: aws2-sqs://queue name?accessKey=xxxxxx&amazonAWSHost=amazonaws.com&autoCreateQueue=false&delay=500&deleteAfterRead=true&greedy=false&maxMessagesPerPoll=1&overrideEndpoint=false&protocol=https®ion=us-west-2&secretKey=xxxxxx&sessionToken=xxxxxx&useDefaultCredentialsProvider=false&useProfileCredentialsProvider=false&useSessionCredentials=false due to: The security token included in the request is invalid. (Service: Sqs, Status Code: 403, Request ID: 877ef9f1-9e7d-5bf6-9e7f-a6392799a81d)
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513928561
`apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: test-backend-sqs-to-ibmmq-pavan
namespace: camel-k
labels:
helm.sh/chart: universal-chart_v2.48.4
app: test-backend
junipersquare.com/initiating_pull_request: pr-1427
junipersquare.com/initiating_repo: test-backend
junipersquare.com/requestor: euanlau
tags.datadoghq.com/env: prpay1427
tags.datadoghq.com/version: pr-1427
annotations:
app: payments-backend1
department: eng
junipersquare.com/initiating_pull_request: pr-1427
junipersquare.com/initiating_repo: test-backend1
junipersquare.com/requestor: euanlau
product: gpx fa
tags.datadoghq.com/env: prpay1427
tags.datadoghq.com/version: pr-1427
team: payments
annotations:
app: payments-backend1
trait.camel.apache.org/kubernetes.volumes: |
volumes:
- name: aws-credentials-volume
secret:
secretName: camel-sqs-cred # Reference the secret where AWS credentials are stored
volumeMounts:
- mountPath: /etc/camel/resources.d/_secrets/camel-sqs-cred # Mount path for the secret
name: aws-credentials-volume
trait.camel.apache.org/kubernetes.env: |
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-access-key-id # AWS access key from the secret
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
name: camel-sqs-cred
key: aws-secret-access-key # AWS secret access key from the secret
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queuename"
region: "us-west-2"
accessKey: "({{ env:AWS_ACCESS_KEY_ID }})"
secretKey: "({{ env:AWS_SECRET_ACCESS_KEY }})"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{{/mq-app-password}}"
queueManager: "JSQ.UAT.BSSB"
serverName: "ip"
serverPort: "1414"
username: "app"`
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2509651975
@squakez : I tried using the access key and secret, but it's not working. Could you please provide a sample pipe.yaml file that uses secrets from Kubernetes secrets? Alternatively, is there a way to use an IAM role through a service account in the pipe.yaml
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2503059388
The usage of ServiceAccount has nothing to do with the Kamelet or component configuration. You still need to provide secret, likely in the form of [Camel properties which are backed by a Secret config](https://camel.apache.org/camel-k/next/configuration/runtime-config.html#runtime-config-props).
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2514457651
Still same issue Caused by: software.amazon.awssdk.services.sqs.model.SqsException: Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'hMg4ZI09YH7RNqzswja69tK20cHVncx0RApiU0fJLrU='. (Service: Sqs, Status Code: 400, Request ID: b4c352cb-e952-5053-b9e8-0d0317df63a2)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125)
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2515122266
@pguptajsq I think you can take as a reference this chat thread: https://camel.zulipchat.com/#narrow/channel/257299-camel-k/topic/Hashicorp.20Token.20in.20modeline/near/480962291
Ideally you should be able to put in your Pipe or Integration specification a Camel property, such as `{{my.aws.key}}`. Then, you need to provide a secret containing such variable, eg, `kubectl create secret generic my-secret --from-literal my.aws.key=123456`. Finally you can run your Pipe or Integration mounting the secret via `mount.config=secret:my-secret`. At runtime, the variable will be using the secret value.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2507116487
Hi Team , could you please help me to leverage k8s secrets in pipe.yaml . here i am trying but its not working. how pipe.yaml will read secrets from k8s . could you please give me proper yaml
apiVersion: camel.apache.org/v1
kind: pipe
metadata:
name: payments-backend-sqs-to-ibmmq-pavan
namespace: camel-k
spec:
traits:
mount:
configs:
- name: camel-sqs-cred
mountPath: /mnt/secrets
optional: false
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queyename"
region: "us-west-2"
accessKeyId: "{{ env:aws-access-key-id }}"
secretAccessKey: "{{ env:aws-secret-access-key }}"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jms-ibm-mq-sink
properties:
channel: "test.TO.BSSB.UAT.CHAN"
destinationName: "test.UAT.BSSB.MT.INPUT"
password: "{testbackend/mq-app-password}}"
queueManager: "test.UAT.BSSB"
serverName: "ip4"
serverPort: "1414"
username: "app"
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513771089
Use a secret, you cannot refer a service account.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513795937
Surround the secret key parameter with RAW().
Do you have special char in the key like + or /?
Then use RAW({{env...}})
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2514372398
This
({{ env:AWS_ACCESS_KEY_ID }})
Should be RAW({{ env:AWS_ACCESS_KEY_ID }})
Same for the secret key. I wrote it above
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2501548685
Hello. It seems the installation did not proceed correctly. I suggest you to clean the previous installation and proceed from scratch following the [official Camel K installation guides](https://camel.apache.org/camel-k/next/installation/installation.html).
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #5963: pipe and integration creation based on YAML file fails ,
URL: https://github.com/apache/camel-k/issues/5963
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513837273
Can you post the pipe now? It seems you syntax is wrong
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513811382
Now getting aused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: aws2-sqs://queue-jaeaccessKey=xxxxxx)&amazonAWSHost=amazonaws.com&autoCreateQueue=false&delay=500&deleteAfterRead=true&greedy=false&maxMessagesPerPoll=1&overrideEndpoint=false&protocol=https®ion=us-west-2&secretKey=xxxxxx)&sessionToken=xxxxxx&useDefaultCredentialsProvider=false&useProfileCredentialsProvider=false&useSessionCredentials=false due to: Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'n89f/dLinHLU1RT5+GtK0ZOBXg7Ov6gUs8MgPGbLap4='.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513697701
Hello, there should be enough documentation about this matter as shared in the previous comments. This is how to configure on an Integration: https://camel.apache.org/camel-k/2.5.x/configuration/runtime-config.html#runtime-config-props - the mechanisms for the Pipe is identical.
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2513755516
"I followed the documentation, but it's not picking up the secrets and is giving the error: Caused by: j: java.lang.IllegalArgumentException: useDefaultCredentialsProvider is set to false, useProfileCredentialsProvider is set to false, useSessionCredentials is set to false, AmazonSQSClient or accessKey and secretKey must be specified
In my pipe.yaml, it works when I directly use the AWS accessKey and secretKey, but I cannot commit these keys to GitHub for security reasons. Instead, I want to use a Kubernetes ServiceAccount with IRSA roles in the kind: pipe Kubernetes configuration. How can I achieve this, or how can I reference Kubernetes secrets inside the pipe.yaml file
kid: pipe
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: aws-sqs-source
properties:
queueNameOrArn: "queue-name"
region: "us-west-2"
accessKey: "keyname"
secretKey: "secrets"
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2501550212
You may also want to check the [Camel K troubleshooting guide](https://camel.apache.org/camel-k/next/troubleshooting/troubleshooting.html).
--
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
Re: [I] pipe and integration creation based on YAML file fails , [camel-k]
Posted by "pguptajsq (via GitHub)" <gi...@apache.org>.
pguptajsq commented on issue #5963:
URL: https://github.com/apache/camel-k/issues/5963#issuecomment-2503116974
Okay. thank you .
now i am getting error on integration , these integration automatically created when apply pipe yaml .
is there way we can pass traits to integration from pipe.yaml
` kubectl logs payments-backend-sqs-to-ibmmq-pavan-8454c5755c-rngns
exec /opt/java/openjdk/bin/java: exec format erro`
from pipe.yaml how we can set
` traits:
affinity:
node-affinity-labels: "kubernetes.io/arch in(amd64)"`
when i am applying yaml with above traits setting , i am getting
Error from server (BadRequest): error when creating "pipe.yaml": Pipe in version "v1" cannot be handled as a Pipe: strict decoding error: unknown field "spec.traits"
--
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