Skip to content

[SRVKE-1687] Unify KafkaChannel and KafkaBroker secret format #95471

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

Merged
merged 1 commit into from
Jul 21, 2025

Conversation

ochromy
Copy link

@ochromy ochromy commented Jul 1, 2025

Version(s):
serverless-docs-1.35+

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 1, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 1, 2025

@ochromy
Copy link
Author

ochromy commented Jul 11, 2025

QE review request here.

@@ -32,14 +32,14 @@ $ oc create secret -n knative-eventing generic <secret_name> \
--from-literal=user="my-sasl-user"
----
** Use the key names `ca.crt`, `password`, and `sasl.mechanism`. Do not change them.
Copy link
Contributor

Choose a reason for hiding this comment

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

(all of the key names must be such, so protocol, and user should be also listed here ) ( I suppose the original reason for this note is the ca.crt , as this is not obvious that it needs to be literally that, but since we list other, we should probably list all of them?)

@@ -32,14 +32,14 @@ $ oc create secret -n knative-eventing generic <secret_name> \
--from-literal=user="my-sasl-user"
----
** Use the key names `ca.crt`, `password`, and `sasl.mechanism`. Do not change them.
** If you want to use SASL with public CA certificates, you must use the `tls.enabled=true` flag, rather than the `ca.crt` argument, when creating the secret. For example:
** If you want to use SASL with public CA certificates, you must use the protocol="SASL_SSL" flag, rather than the ca.crt argument, when creating the secret. For example:
Copy link
Contributor

@maschmid maschmid Jul 15, 2025

Choose a reason for hiding this comment

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

I don't think this makes sense as is... It did make sense with the original format, as not listing the "ca.crt" would not work if you also didn't explicitly enable TLS with tls.enabled=true .. However, with the new format, the protocol is required to be specified either way, and if it is set to protocol=SASL_SSL it means SSL is enabled. (you can also optionally use protocol=SASL_PLAIN to use SASL over plaintext, without using TLS )

(the only difference between "with public CA certificates" now is that the "ca.crt" argument is not specified.

We could perhaps simplify the whole section by having just a single example with "ca.crt", and having a note that would say "ca.crt" is optional, if the Kafka cluster is using a public CA certificate (verified by one of the default certificate authorities present in the default system truststores in the knative kafka images, if we wanted to be pedantic)

(same comment applies to the sasl-channels, as they now use the same format)

Copy link
Author

Choose a reason for hiding this comment

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

I see, thanks for the explanation and suggestion. I'll update this.

Copy link
Author

Choose a reason for hiding this comment

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

@maschmid Updated and pushed.
Please let me know if this matches what you suggested.

Copy link
Contributor

Choose a reason for hiding this comment

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

looks good to me!

@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 16, 2025
@maschmid
Copy link
Contributor

QE approved

@ochromy
Copy link
Author

ochromy commented Jul 18, 2025

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 18, 2025
@rh-tokeefe
Copy link
Contributor

/label peer-review-in-progress

@openshift-ci openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Jul 18, 2025
Copy link
Contributor

@rh-tokeefe rh-tokeefe left a comment

Choose a reason for hiding this comment

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

LGTM

--from-literal=saslType="SCRAM-SHA-512" \
--from-literal=user="my-sasl-user"
----
[NOTE]
Copy link
Contributor

Choose a reason for hiding this comment

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

Kafka is a product name, so you might want to consider creating an attribute for Kafka.

@rh-tokeefe
Copy link
Contributor

/label peer-review-done

@openshift-ci openshift-ci bot added the peer-review-done Signifies that the peer review team has reviewed this PR label Jul 18, 2025
@rh-tokeefe
Copy link
Contributor

/remove-label peer-review-needed
/remove-label peer-review-in-progress

@ochromy
Copy link
Author

ochromy commented Jul 19, 2025

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jul 19, 2025
@ShaunaDiaz ShaunaDiaz removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Jul 21, 2025
@briandooley
Copy link
Contributor

/remove-label merge-review-needed
/label merge-review-in-progress

@openshift-ci openshift-ci bot added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jul 21, 2025
Copy link
Contributor

@briandooley briandooley left a comment

Choose a reason for hiding this comment

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

Made a few small suggestions.

----
[NOTE]
====
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA that is trusted by the system truststore.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA that is trusted by the system truststore.
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA whose certificate is already in the system truststore.

----
[NOTE]
====
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA that is trusted by the system truststore.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA that is trusted by the system truststore.
The `ca.crt` key is optional if the Kafka cluster uses a certificate signed by a public CA whose certificate is already in the system truststore.

Copy link

openshift-ci bot commented Jul 21, 2025

@ochromy: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@ochromy
Copy link
Author

ochromy commented Jul 21, 2025

Good suggestions, @briandooley!
I've pushed the changes.

@briandooley briandooley merged commit f745eda into openshift:serverless-docs-main Jul 21, 2025
2 checks passed
@briandooley
Copy link
Contributor

/cherry-pick serverless-docs-1.35

@openshift-cherrypick-robot

@briandooley: new pull request created: #96411

In response to this:

/cherry-pick serverless-docs-1.35

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.

@briandooley
Copy link
Contributor

/cherry-pick serverless-docs-1.36

@openshift-cherrypick-robot

@briandooley: new pull request created: #96413

In response to this:

/cherry-pick serverless-docs-1.36

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.

@briandooley
Copy link
Contributor

/cherry-pick serverless-docs-1.37

@openshift-cherrypick-robot

@briandooley: new pull request created: #96524

In response to this:

/cherry-pick serverless-docs-1.37

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
merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants