Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 1. A
1.1. Access Operator
An optional operator that simplifies the sharing of Kafka connection information and credentials between namespaces. Connection details are stored centrally in a Secret resource.
1.2. Authentication
Defines how clients prove their identity to the Kafka cluster. Streams for Apache Kafka manages authentication as a client-server relationship:
- Server-Side: The Kafka cluster’s listeners are configured to require a specific authentication type.
Client-Side: A client (a
KafkaUseror a client-based Kafka component managed by Streams for Apache Kafka) must be configured to provide matching credentials.- Listener authentication (Server-Side)
-
Listener authentication is configured per listener in the
spec.kafka.listenersarray of theKafkacustom resource. Supported types includetls,scram-sha-512, andcustom. - Client authentication (Kafka user)
-
For Kafka users, authentication is managed using the
KafkaUsercustom resource. Supported types aretls,tls-external(using an external CA), andscram-sha-512. Streams for Apache Kafka automatically creates the necessarySecretresources for the user. - Client authentication (Kafka components)
-
For Streams for Apache Kafka-managed components, authentication is managed in the custom resource of the component, such as
KafkaConnect. Supported types includetls,scram-sha-256,scram-sha-512,plain, andcustom.
For more information, see the following:
1.3. Authorization (cluster-wide)
Defines which actions an authenticated client is permitted to perform on Kafka resources, such as writing to or reading from a topic. Configuration involves setting a cluster-wide mechanism and then, if required, defining user-specific rules.
- Cluster-wide authorization
-
This defines the overall mechanism used by the Kafka cluster to control client actions. It’s configured in the
spec.kafka.authorizationsection of theKafkacustom resource. Supported types includesimple(using the Kafka’s built-in authorizer) andcustom(using custom authorizers). - User authorization (ACLs)
-
This defines specific Access Control Lists (ACLs) for a user, granting permissions to perform actions on
Kafkaresources. The ACLs are defined in thespec.authorizationsection of theKafkaUsercustom resource. If using a custom authorization mechanism, user permissions are typically managed within the external authorization system and not through theKafkaUserresource.
For more information, see the following:
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}