Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAR injector support for Camel-K #19

Open
tardieu opened this issue Jan 22, 2021 · 1 comment
Open

KAR injector support for Camel-K #19

tardieu opened this issue Jan 22, 2021 · 1 comment
Assignees

Comments

@tardieu
Copy link
Member

tardieu commented Jan 22, 2021

To deploy Camel-K integrations using kubectl with need yaml such as:

apiVersion: v1
kind: Pod
metadata:
  name: stock-source
spec:
  containers:
  - name: stock-source
    image: localhost:5000/kar/kar-examples-stock-source
    env:
    - name: KAFKA_BROKERS
      valueFrom:
        secretKeyRef:
          name: kar.ibm.com.runtime-config
          key: kafka_brokers

See https://github.com/IBM/kar/blob/main/examples/camel-k/deploy/stocks.yaml.

We could extend the mutating webhook to permit something like:

apiVersion: v1
kind: Pod
metadata:
  name: stock-source
  annotations:
    kar.ibm.com/runtime: camel
spec:
  containers:
  - name: stock-source
    image: localhost:5000/kar/kar-examples-stock-source
@tardieu tardieu assigned tardieu and dgrove-oss and unassigned tardieu Jan 22, 2021
@dgrove-oss
Copy link
Member

How much control do we have over the container that needs the runtime config? What we are actually doing in the sidecar injector is injecting a VolumeMount of the kar.ibm.com.runtime-config secret. Doing the same for the camel container would be significantly simpler than mucking with the environment more directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants