Skip to content

Conversation

twoGiants
Copy link
Contributor

Overhauled the Camel K operator installation and configuration. Fixed issues with the overall setup, a few typos and wrong directory paths.

The Pipe CR had a typo in the Broker name "bad-word-broker". Now it is correctly "badword-broker". That was the reason for the "bad" comments not reaching the Slack sink.

Issue #6423.

/cherry-pick release-1.19

Proposed Changes

Update 7 - Connect Slack via Camel-K.

  • Remove Camel-k CLI installation.
  • Add installation via Kustomize and update link to installation docs.
  • Fix secret path.
  • Fix bookstore-broker name.
  • Fix slack-sink manifests path.
  • Fix typo in Pipe broker name.
  • Change pipe name to align with manifest.
  • Add kubectl patch ... command additionally to kubectl edit ....
  • Correct "Verification" message => only "bad" comments go to the Slack sink.

Copy link

netlify bot commented Oct 6, 2025

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit bf6b3f8
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/68e62ed8f1b12000086559dd
😎 Deploy Preview https://deploy-preview-6424--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@knative-prow knative-prow bot requested review from Leo6Leo and nainaz October 6, 2025 10:23
@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 6, 2025
@twoGiants twoGiants changed the title Fix section "7-Connect Slack via Camel-K" in e2e Fix section "7-Connect Slack via Camel-K" in e2e tutorial. Oct 6, 2025
Overhauled the Camel K operator installation and configuration. Fixed
issues with the overall setup, a few typos and wrong directory paths.

The Pipe CR had a typo in the Broker name "bad-word-broker". Now it is
correctly "badword-broker"

Issue knative#6423.

Signed-off-by: Stanislav Jakuschevskij <sjakusch@redhat.com>
@twoGiants twoGiants force-pushed the issue-6423-fix-step-7-connect-slack branch from 971e0b6 to af08818 Compare October 6, 2025 13:22
Here, we will be connecting `bookstore-broker` with a new Broker called `badword-broker`. And we will be creating a Trigger that helps us perform the filtering with the extension `badwordfilter: good`.

- 1: Append the following content to your `node-server/config/200-broker.yaml`:
- 1: Create a new file named `slack-sink/config/200-broker.yaml` and add the following content:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/knative/docs/tree/main/code-samples/eventing/bookstore-sample-app/solution/slack-sink/config

I am assuming the changes for the code files will be updated later right?

Same question for some of the few path changes in this PR as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one should be named 100-broker.yaml as in the solution! Missed that one.

I am assuming the changes for the code files will be updated later right?

Yeah, I opened the issue #6426 for the solution fixes. I am working on it today. Hope to open a PR for it today too.

Signed-off-by: Stanislav Jakuschevskij <sjakusch@redhat.com>
@twoGiants twoGiants force-pushed the issue-6423-fix-step-7-connect-slack branch from afc502c to bf6b3f8 Compare October 8, 2025 09:28
@dprotaso
Copy link
Member

dprotaso commented Oct 8, 2025

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Oct 8, 2025
Copy link

knative-prow bot commented Oct 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, twoGiants

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 8, 2025
@knative-prow knative-prow bot merged commit 1818bf3 into knative:main Oct 8, 2025
19 checks passed
@dprotaso
Copy link
Member

dprotaso commented Oct 8, 2025

/cherry-pick release-1.19

@knative-prow-robot
Copy link
Contributor

@dprotaso: new pull request created: #6434

In response to this:

/cherry-pick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants