kafka proxy
v0.3.12
Der Kafka -Proxy basiert auf der Idee des Cloud SQL -Proxy. Es ermöglicht einen Dienst, sich mit Kafka -Brokern zu verbinden, ohne sich mit SASL/Plain -Authentifizierung und SSL -Zertifikaten befassen zu müssen.
Es wird durch Öffnen von TCP -Steckdosen auf der lokalen Maschine geöffnet und Verbindungen zu den zugehörigen Kafka -Brokern hergestellt, wenn die Sockets verwendet werden. Der Host und der Hafen in Metadaten- und FindCoordinator -Antworten, die von den Makler erhalten wurden, werden durch lokale Kollegen ersetzt. Für entdeckte Makler (nicht als Boostrap -Server konfiguriert) werden lokale Hörer mit zufälligen Ports gestartet. Die dynamische lokale Hörer -Funktion kann deaktiviert werden und eine zusätzliche Liste externer Server -Zuordnungen kann bereitgestellt werden.
Der Proxy kann den TLS -Datenverkehr beenden und Benutzer mithilfe von SASL/Plain authentifizieren. Die Überprüfungsmethode für Anmeldeinformationen ist konfigurierbar und verwendet das Golang -Plugin -System über RPC.
Die Proxys können sich auch gegenseitig mithilfe einer steckbaren Methode authentifizieren, die für andere Kafka -Server und Clients transparent ist. Derzeit wird das Google -ID -Token für Service -Konten implementiert.
Kafka -API -Anrufe können beschränkt werden, um einige Vorgänge zu verhindern, z. B. das Löschen oder Erstellen von Anforderungen.
Sehen:
Kafka -Proxy mit Amazon MSK
Ein Leitfaden zum Kafka -Protokoll
Kafka Protocol Guide
Die folgende Tabelle bietet einen Überblick über unterstützte Kafka -Versionen (angegeben und alle früheren Kafka -Versionen). Da nicht jede Kafka -Version neue Nachrichten/Versionen hinzufügt, die für den Kafka -Proxy relevant sind, können neuere Kafka -Versionen auch funktionieren.
| Kafka -Proxy -Version | Kafka -Version |
|---|---|
| Ab 0,11.0 | |
| 0.2.9 | bis 2.8.0 |
| 0.3.1 | bis 3.4.0 |
| 0.3.11 | bis 3.7.0 |
| 0.3.12 | bis 3.9.0 |
Laden Sie die neueste Version herunter
Linux
curl -Ls https://github.com/grepplabs/kafka-proxy/releases/download/v0.3.12/kafka-proxy-v0.3.12-linux-amd64.tar.gz | tar xz
macos
curl -Ls https://github.com/grepplabs/kafka-proxy/releases/download/v0.3.12/kafka-proxy-v0.3.12-darwin-amd64.tar.gz | tar xz
Bewegen Sie die Binärdatei in Ihren Weg.
sudo mv ./kafka-proxy /usr/local/bin/kafka-proxy
make clean build
Docker -Bilder sind auf Docker Hub verfügbar.
Sie können einen Kafka-Proxy-Container starten, um es auszuprobieren
docker run --rm -p 30001-30003:30001-30003 grepplabs/kafka-proxy:0.3.12 server --bootstrap-server-mapping "localhost:19092,0.0.0.0:30001" --bootstrap-server-mapping "localhost:29092,0.0.0.0:30002" --bootstrap-server-mapping "localhost:39092,0.0.0.0:30003" --dial-address-mapping "localhost:19092,172.17.0.1:19092" --dial-address-mapping "localhost:29092,172.17.0.1:29092" --dial-address-mapping "localhost:39092,172.17.0.1:39092" --debug-enable
Kafka-Proxy ist nun auf localhost:30001 localhost:19092 localhost:30002 localhost:29092 172.17.0.1 localhost:39092 localhost:30003 erreicht. .
Docker-Bilder mit vorkompilierten Plugins in /opt/kafka-proxy/bin/ werden mit <release>-all markiert.
Sie können einen Kafka-Proxy-Container mit dem Auth-LDAP-Plugin starten, um es auszuprobieren
docker run --rm -p 30001-30003:30001-30003 grepplabs/kafka-proxy:0.3.12-all server --bootstrap-server-mapping "localhost:19092,0.0.0.0:30001" --bootstrap-server-mapping "localhost:29092,0.0.0.0:30002" --bootstrap-server-mapping "localhost:39092,0.0.0.0:30003" --dial-address-mapping "localhost:19092,172.17.0.1:19092" --dial-address-mapping "localhost:29092,172.17.0.1:29092" --dial-address-mapping "localhost:39092,172.17.0.1:39092" --debug-enable --auth-local-enable --auth-local-command=/opt/kafka-proxy/bin/auth-ldap --auth-local-param=--url=ldap://172.17.0.1:389 --auth-local-param=--start-tls=false --auth-local-param=--bind-dn=cn=admin,dc=example,dc=org --auth-local-param=--bind-passwd=admin --auth-local-param=--user-search-base=ou=people,dc=example,dc=org --auth-local-param=--user-filter="(&(objectClass=person)(uid=%u)(memberOf=cn=kafka-users,ou=realm-roles,dc=example,dc=org))"
Run the kafka-proxy server
Usage:
kafka-proxy server [flags]
Flags:
--auth-gateway-client-command string Path to authentication plugin binary
--auth-gateway-client-enable Enable gateway client authentication
--auth-gateway-client-log-level string Log level of the auth plugin (default "trace")
--auth-gateway-client-magic uint Magic bytes sent in the handshake
--auth-gateway-client-method string Authentication method
--auth-gateway-client-param stringArray Authentication plugin parameter
--auth-gateway-client-timeout duration Authentication timeout (default 10s)
--auth-gateway-server-command string Path to authentication plugin binary
--auth-gateway-server-enable Enable proxy server authentication
--auth-gateway-server-log-level string Log level of the auth plugin (default "trace")
--auth-gateway-server-magic uint Magic bytes sent in the handshake
--auth-gateway-server-method string Authentication method
--auth-gateway-server-param stringArray Authentication plugin parameter
--auth-gateway-server-timeout duration Authentication timeout (default 10s)
--auth-local-command string Path to authentication plugin binary
--auth-local-enable Enable local SASL/PLAIN authentication performed by listener - SASL handshake will not be passed to kafka brokers
--auth-local-log-level string Log level of the auth plugin (default "trace")
--auth-local-mechanism string SASL mechanism used for local authentication: PLAIN or OAUTHBEARER (default "PLAIN")
--auth-local-param stringArray Authentication plugin parameter
--auth-local-timeout duration Authentication timeout (default 10s)
--bootstrap-server-mapping stringArray Mapping of Kafka bootstrap server address to local address (host:port,host:port(,advhost:advport))
--debug-enable Enable Debug endpoint
--debug-listen-address string Debug listen address (default "0.0.0.0:6060")
--default-listener-ip string Default listener IP (default "0.0.0.0")
--dial-address-mapping stringArray Mapping of target broker address to new one (host:port,host:port). The mapping is performed during connection establishment
--dynamic-advertised-listener string Advertised address for dynamic listeners. If empty, default-listener-ip is used
--dynamic-listeners-disable Disable dynamic listeners.
--dynamic-sequential-min-port int If set to non-zero, makes the dynamic listener use a sequential port starting with this value rather than a random port every time.
--external-server-mapping stringArray Mapping of Kafka server address to external address (host:port,host:port). A listener for the external address is not started
--forbidden-api-keys ints Forbidden Kafka request types. The restriction should prevent some Kafka operations e.g. 20 - DeleteTopics
--forward-proxy string URL of the forward proxy. Supported schemas are socks5 and http
--gssapi-auth-type string GSSAPI auth type: KEYTAB or USER (default "KEYTAB")
--gssapi-disable-pa-fx-fast Used to configure the client to not use PA_FX_FAST.
--gssapi-keytab string krb5.keytab file location
--gssapi-krb5 string krb5.conf file path, default: /etc/krb5.conf (default "/etc/krb5.conf")
--gssapi-password string Password for auth type USER
--gssapi-realm string Realm
--gssapi-servicename string ServiceName (default "kafka")
--gssapi-spn-host-mapping stringToString Mapping of Kafka servers address to SPN hosts (default [])
--gssapi-username string Username (default "kafka")
-h, --help help for server
--http-disable Disable HTTP endpoints
--http-health-path string Path on which to health endpoint (default "/health")
--http-listen-address string Address that kafka-proxy is listening on (default "0.0.0.0:9080")
--http-metrics-path string Path on which to expose metrics (default "/metrics")
--kafka-client-id string An optional identifier to track the source of requests (default "kafka-proxy")
--kafka-connection-read-buffer-size int Size of the operating system's receive buffer associated with the connection. If zero, system default is used
--kafka-connection-write-buffer-size int Sets the size of the operating system's transmit buffer associated with the connection. If zero, system default is used
--kafka-dial-timeout duration How long to wait for the initial connection (default 15s)
--kafka-keep-alive duration Keep alive period for an active network connection. If zero, keep-alives are disabled (default 1m0s)
--kafka-max-open-requests int Maximal number of open requests pro tcp connection before sending on it blocks (default 256)
--kafka-read-timeout duration How long to wait for a response (default 30s)
--kafka-write-timeout duration How long to wait for a transmit (default 30s)
--log-format string Log format text or json (default "text")
--log-level string Log level debug, info, warning, error, fatal or panic (default "info")
--log-level-fieldname string Log level fieldname for json format (default "@level")
--log-msg-fieldname string Message fieldname for json format (default "@message")
--log-time-fieldname string Time fieldname for json format (default "@timestamp")
--producer-acks-0-disabled Assume fire-and-forget is never sent by the producer. Enabling this parameter will increase performance
--proxy-listener-ca-chain-cert-file string PEM encoded CA's certificate file. If provided, client certificate is required and verified
--proxy-listener-cert-file string PEM encoded file with server certificate
--proxy-listener-cipher-suites strings List of supported cipher suites
--proxy-listener-curve-preferences strings List of curve preferences
--proxy-listener-keep-alive duration Keep alive period for an active network connection. If zero, keep-alives are disabled (default 1m0s)
--proxy-listener-key-file string PEM encoded file with private key for the server certificate
--proxy-listener-key-password string Password to decrypt rsa private key
--proxy-listener-read-buffer-size int Size of the operating system's receive buffer associated with the connection. If zero, system default is used
--proxy-listener-tls-enable Whether or not to use TLS listener
--proxy-listener-tls-required-client-subject strings Required client certificate subject common name; example; s:/CN=[value]/C=[state]/C=[DE,PL] or r:/CN=[^val.{2}$]/C=[state]/C=[DE,PL]; check manual for more details
--proxy-listener-write-buffer-size int Sets the size of the operating system's transmit buffer associated with the connection. If zero, system default is used
--proxy-request-buffer-size int Request buffer size pro tcp connection (default 4096)
--proxy-response-buffer-size int Response buffer size pro tcp connection (default 4096)
--sasl-aws-profile string AWS profile
--sasl-aws-region string Region for AWS IAM Auth
--sasl-enable Connect using SASL
--sasl-jaas-config-file string Location of JAAS config file with SASL username and password
--sasl-method string SASL method to use (PLAIN, SCRAM-SHA-256, SCRAM-SHA-512, GSSAPI, AWS_MSK_IAM (default "PLAIN")
--sasl-password string SASL user password
--sasl-plugin-command string Path to authentication plugin binary
--sasl-plugin-enable Use plugin for SASL authentication
--sasl-plugin-log-level string Log level of the auth plugin (default "trace")
--sasl-plugin-mechanism string SASL mechanism used for proxy authentication: PLAIN or OAUTHBEARER (default "OAUTHBEARER")
--sasl-plugin-param stringArray Authentication plugin parameter
--sasl-plugin-timeout duration Authentication timeout (default 10s)
--sasl-username string SASL user name
--tls-ca-chain-cert-file string PEM encoded CA's certificate file
--tls-client-cert-file string PEM encoded file with client certificate
--tls-client-key-file string PEM encoded file with private key for the client certificate
--tls-client-key-password string Password to decrypt rsa private key
--tls-enable Whether or not to use TLS when connecting to the broker
--tls-insecure-skip-verify It controls whether a client verifies the server's certificate chain and host name
--tls-same-client-cert-enable Use only when mutual TLS is enabled on proxy and broker. It controls whether a proxy validates if proxy client certificate exactly matches brokers client cert (tls-client-cert-file)kafka-proxy server --bootstrap-server-mapping "192.168.99.100:32400,0.0.0.0:32399" kafka-proxy server --bootstrap-server-mapping "192.168.99.100:32400,127.0.0.1:32400" --bootstrap-server-mapping "192.168.99.100:32401,127.0.0.1:32401" --bootstrap-server-mapping "192.168.99.100:32402,127.0.0.1:32402" --dynamic-listeners-disable kafka-proxy server --bootstrap-server-mapping "kafka-0.example.com:9092,0.0.0.0:32401,kafka-0.grepplabs.com:9092" --bootstrap-server-mapping "kafka-1.example.com:9092,0.0.0.0:32402,kafka-1.grepplabs.com:9092" --bootstrap-server-mapping "kafka-2.example.com:9092,0.0.0.0:32403,kafka-2.grepplabs.com:9092" --dynamic-listeners-disable kafka-proxy server --bootstrap-server-mapping "192.168.99.100:32400,127.0.0.1:32400" --external-server-mapping "192.168.99.100:32401,127.0.0.1:32402" --external-server-mapping "192.168.99.100:32402,127.0.0.1:32403" --forbidden-api-keys 20 export BOOTSTRAP_SERVER_MAPPING="192.168.99.100:32401,0.0.0.0:32402 192.168.99.100:32402,0.0.0.0:32403" && kafka-proxy server
kafka-proxy server --bootstrap-server-mapping "localhost:19092,0.0.0.0:30001,localhost:30001" --bootstrap-server-mapping "localhost:29092,0.0.0.0:30002,localhost:30002" --bootstrap-server-mapping "localhost:39092,0.0.0.0:30003,localhost:30003" --proxy-listener-cert-file "tls/ca-cert.pem" --proxy-listener-key-file "tls/ca-key.pem" --proxy-listener-tls-enable --proxy-listener-cipher-suites TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256
Die SASL -Authentifizierung wird vom Proxy initiiert. Die SASL -Authentifizierung ist in den Clients deaktiviert und für die Kafka -Makler aktiviert.
kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9093,0.0.0.0:32399" --tls-enable --tls-insecure-skip-verify --sasl-enable --sasl-username myuser --sasl-password mysecret kafka-proxy server --bootstrap-server-mapping "kafka-0.example.com:9092,0.0.0.0:30001" --bootstrap-server-mapping "kafka-1.example.com:9092,0.0.0.0:30002" --bootstrap-server-mapping "kafka-1.example.com:9093,0.0.0.0:30003" --sasl-enable --sasl-username "alice" --sasl-password "alice-secret" --sasl-method "SCRAM-SHA-512" --log-level debug make clean build plugin.unsecured-jwt-provider && build/kafka-proxy server --sasl-enable --sasl-plugin-enable --sasl-plugin-mechanism "OAUTHBEARER" --sasl-plugin-command build/unsecured-jwt-provider --sasl-plugin-param "--claim-sub=alice" --bootstrap-server-mapping "192.168.99.100:32400,127.0.0.1:32400"
GSSAPI / Kerberos -Authentifizierung
kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --sasl-enable --sasl-method "GSSAPI" --gssapi-servicename kafka --gssapi-username kafkaclient1 --gssapi-realm EXAMPLE.COM --gssapi-krb5 /etc/krb5.conf --gssapi-keytab /etc/security/keytabs/kafka.keytab
AWS MSK IAM
kafka-proxy server --bootstrap-server-mapping "b-1-public.kafkaproxycluster.uls9ao.c4.kafka.eu-central-1.amazonaws.com:9198,0.0.0.0:30001" --bootstrap-server-mapping "b-2-public.kafkaproxycluster.uls9ao.c4.kafka.eu-central-1.amazonaws.com:9198,0.0.0.0:30002" --bootstrap-server-mapping "b-3-public.kafkaproxycluster.uls9ao.c4.kafka.eu-central-1.amazonaws.com:9198,0.0.0.0:30003" --tls-enable --tls-insecure-skip-verify --sasl-enable --sasl-method "AWS_MSK_IAM" --sasl-aws-region "eu-central-1" --log-level debug
Die SASL -Authentifizierung wird vom Proxy durchgeführt. Die SASL -Authentifizierung ist für die Clients aktiviert und für die Kafka -Makler deaktiviert.
make clean build plugin.auth-user && build/kafka-proxy server --proxy-listener-key-file "server-key.pem" --proxy-listener-cert-file "server-cert.pem" --proxy-listener-ca-chain-cert-file "ca.pem" --proxy-listener-tls-enable --auth-local-enable --auth-local-command build/auth-user --auth-local-param "--username=my-test-user" --auth-local-param "--password=my-test-password" make clean build plugin.auth-ldap && build/kafka-proxy server --auth-local-enable --auth-local-command build/auth-ldap --auth-local-param "--url=ldaps://ldap.example.com:636" --auth-local-param "--user-dn=cn=users,dc=exemple,dc=com" --auth-local-param "--user-attr=uid" --bootstrap-server-mapping "192.168.99.100:32400,127.0.0.1:32400" make clean build plugin.unsecured-jwt-info && build/kafka-proxy server --auth-local-enable --auth-local-command build/unsecured-jwt-info --auth-local-mechanism "OAUTHBEARER" --auth-local-param "--claim-sub=alice" --auth-local-param "--claim-sub=bob" --bootstrap-server-mapping "192.168.99.100:32400,127.0.0.1:32400"
Überprüfen Sie, ob das vom Proxy -Client verwendete Client -Zertifikat genau das gleiche wie das Client -Zertifikat in der von Proxy initiierten Authentifizierung ist
kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9093,0.0.0.0:32399" --tls-enable --tls-client-cert-file client.crt --tls-client-key-file client.pem --tls-client-key-password changeit --proxy-listener-tls-enable --proxy-listener-key-file server.pem --proxy-listener-cert-file server.crt --proxy-listener-key-password changeit --proxy-listener-ca-chain-cert-file ca.crt --tls-same-client-cert-enable
Authentifizierung zwischen Kafka Proxy Client und Kafka Proxy Server mit Google-ID (Service-Konto JWT)
kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --dynamic-listeners-disable --http-disable --proxy-listener-tls-enable --proxy-listener-cert-file=/var/run/secret/server.cert.pem --proxy-listener-key-file=/var/run/secret/server.key.pem --auth-gateway-server-enable --auth-gateway-server-method google-id --auth-gateway-server-magic 3285573610483682037 --auth-gateway-server-command google-id-info --auth-gateway-server-param "--timeout=10" --auth-gateway-server-param "--audience=tcp://kafka-gateway.grepplabs.com" --auth-gateway-server-param "--email-regex=^[email protected]$" kafka-proxy server --bootstrap-server-mapping "127.0.0.1:32500,127.0.0.1:32400" --bootstrap-server-mapping "127.0.0.1:32501,127.0.0.1:32401" --bootstrap-server-mapping "127.0.0.1:32502,127.0.0.1:32402" --dynamic-listeners-disable --http-disable --tls-enable --tls-ca-chain-cert-file /var/run/secret/client/ca-chain.cert.pem --auth-gateway-client-enable --auth-gateway-client-method google-id --auth-gateway-client-magic 3285573610483682037 --auth-gateway-client-command google-id-provider --auth-gateway-client-param "--credentials-file=/var/run/secret/client/service-account.json" --auth-gateway-client-param "--target-audience=tcp://kafka-gateway.grepplabs.com" --auth-gateway-client-param "--timeout=10"
Stellen Sie eine Verbindung über Test Sockens5 -Proxy -Server her
kafka-proxy tools socks5-proxy --addr localhost:1080 kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --forward-proxy socks5://localhost:1080
kafka-proxy tools socks5-proxy --addr localhost:1080 --username my-proxy-user --password my-proxy-password kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --forward-proxy socks5://my-proxy-user:my-proxy-password@localhost:1080
Verbindung über den Test HTTP -Proxy -Server mithilfe der Connect -Methode herstellen
kafka-proxy tools http-proxy --addr localhost:3128 kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --forward-proxy http://localhost:3128
kafka-proxy tools http-proxy --addr localhost:3128 --username my-proxy-user --password my-proxy-password kafka-proxy server --bootstrap-server-mapping "kafka-0.grepplabs.com:9092,127.0.0.1:32500" --bootstrap-server-mapping "kafka-1.grepplabs.com:9092,127.0.0.1:32501" --bootstrap-server-mapping "kafka-2.grepplabs.com:9092,127.0.0.1:32502" --forward-proxy http://my-proxy-user:my-proxy-password@localhost:3128
Manchmal ist es möglicherweise erforderlich, nicht nur zu bestätigen, dass das Client -Zertifikat gültig ist, sondern auch, dass das Client -Zertifikat DN für einen konkreten Anwendungsfall ausgestellt wird. Dies kann mit den folgenden Argumenten erreicht werden:
--proxy-listener-tls-client-cert-validate-subject bool Whether to validate client certificate subject (default false) --proxy-listener-tls-required-client-subject-common-name string Required client certificate subject common name --proxy-listener-tls-required-client-subject-country stringArray Required client certificate subject country --proxy-listener-tls-required-client-subject-province stringArray Required client certificate subject province --proxy-listener-tls-required-client-subject-locality stringArray Required client certificate subject locality --proxy-listener-tls-required-client-subject-organization stringArray Required client certificate subject organization --proxy-listener-tls-required-client-subject-organizational-unit stringArray Required client certificate subject organizational unit
Durch Einstellen --proxy-listener-tls-client-cert-validate-subject true wird Kafka Proxy das Client-Zertifikat-DN-Felder für die erwarteten Werte inspizieren, die mit den Argumenten --proxy-listener-tls-required-client-* eingestellt wurden. Die Übereinstimmungen sind immer exakt und zusammen mit allen nicht leeren Werten verwendet. Um beispielsweise ein gültiges Zertifikat für country=DE and organization=grepplabs zuzulassen, konfigurieren Sie den Kafka -Proxy auf folgende Weise:
kafka-proxy server --proxy-listener-tls-client-cert-validate-subject true --proxy-listener-tls-required-client-subject-country DE --proxy-listener-tls-required-client-subject-organization grepplabs
.
Selector: MatchLabels: App: MyApp
Vorlage: Metadaten: Labels: App: MyApp Annotationen: prometheus.io/scape: 'true'spec: Container:
-Name: Kafka-Proxy Bild: Grepplabs/Kafka-Proxy: Neueste Argumente:
-'Server'-'--log-format = json'- 9093,127.0.0.1: 32401'- Datei =/var/run/secry/kafka-ca-Chain-Zertifikat/ca-chain.cert.pem'- '--tls-client-cert-file =/var/run/secret/kafka-client-zertifikat/ client.cert.pem'- '--tls-client-key-file =/var/run/secry/kafka-client-key.key.peM'-' –-tls-client-key-password = $ (Tls_client_key_password) '-'--sasl-enable'- '--sasl-jaas-config-file =/var/run/secret/kafka-client-jaas/jaas.config' env:
-Name: TLS_CLIENT_KEY_PASSWORDVALUEFROM: SecretKeyRef: Name: TLS-Client-Key-PasswordKey: Passwort volumemounts:
-Name: "sasl-jaas-config-file" MountPath: "/var/run/heimlich/kafka-client-jaas"-Name: "Tls-ca-Chain-Zertifikat" MountPath: "/var/run/geheim/geheim/ KAFKA-CA-Chain-Zertifikat "-Name:" TLS-Client-Cert-Datei "MountPath:"/var/run/geheim/Kafka-Client-Zertifikat "-Name:" TLS-Client-Key-Datei "MountPath: "/var/run/secret/kafka-client-key" -Ports:
- name: metricscontainerPort: 9080 livenessProbe:httpGet: path: /health port: 9080initialDelaySeconds: 5periodSeconds: 3 readinessProbe:httpGet: path: /health port: 9080initialDelaySeconds: 5periodSeconds: 10timeoutSeconds: 5successThreshold: 2failureThreshold: 5- name: myapp image: myapp: Neueste Ports:
- Containerport: 8080Name: Metriken Env:
- Name: Bootstrap_ServersValue: "127.0.0.1:32400,127.0.0.1:32401,127.0.0.1:32402" Volumes:
-Name: sasl-jaas-config-fileSecret: SecretName: sasl-jaas-config-file-Name: TLS-CA-Chain-Zertifikate: SecretName: TLS-CA-Chain-Zertifikat-Name: TLS-Client-Cert-File-Abecret : SecretName: TLS-Client-Cert-Datei-Name: TLS-Client-Key-fileSecret: SecretName: TLS-Client-Key-Datei .
Repliken: 1
Servicename: Kafka-Proxy
Vorlage: Metadaten: Beschriftungen: App: Kafka-Proxyspec: Container:
-Name: Kafka-Proxy Bild: Grepplabs/Kafka-Proxy: Neueste Argumente:
-'Server'-'--log-format = json'- 9093,127.0.0.1: 32401'- Datei =/var/run/secry/kafka-ca-Chain-Zertifikat/ca-chain.cert.pem'- '--tls-client-cert-file =/var/run/secret/kafka-client-zertifikat/ client.cert.pem'- '--tls-client-key-file =/var/run/secry/kafka-client-key.key.peM'-' –-tls-client-key-password = $ (TLS_CLIENT_KEY_PASSWORD) '-'--SASL-ENABLE'- -Size = 32768'- '-'-kafka-connection-read-Buffer-Größe = 131072'- '-Kafka-Connection-Write-Buffer-Größe = 32768' Env:
-Name: TLS_CLIENT_KEY_PASSWORDVALUEFROM: SecretKeyRef: Name: TLS-Client-Key-PasswordKey: Passwort volumemounts:
-Name: "sasl-jaas-config-file" MountPath: "/var/run/heimlich/kafka-client-jaas"-Name: "Tls-ca-Chain-Zertifikat" MountPath: "/var/run/geheim/geheim/ KAFKA-CA-Chain-Zertifikat "-Name:" TLS-Client-Cert-Datei "MountPath:"/var/run/geheim/Kafka-Client-Zertifikat "-Name:" TLS-Client-Key-Datei "MountPath: "/var/run/secret/kafka-client-key" -Ports:
- Name: MetricsContainerport: 9080 - Name: Kafka -0 -Containerport: 32400 - Name: Kafka -1Containerport: 32401 - Name: Kafka -2Containerport: 32402 Lebendigkeitsprobe: HTTPGET: Path : Pfad : /Health Port: 9080Initialayelayseconds: 5periodSeconds: 10TimeOutSeconds: 5SuccessThreshold: 2FailUrThreshold: 5 Ressourcen: Anfragen: Speicher: 128mi CPU: 1000m restartPolicy: Immer
-Name: sasl-jaas-config-fileSecret: SecretName: sasl-jaas-config-file-Name: TLS-CA-Chain-Zertifikate: SecretName: TLS-CA-Chain-Zertifikat-Name: TLS-Client-Cert-File-Abecret : SecretName: TLS-Client-Cert-Datei-Name: TLS-Client-Key-fileSecret: SecretName: TLS-Client-Key-DateiKubectl Port-Forward Kafka-Proxy-0 32400: 32400 32401: 32401 32402: 32402
Verwenden Sie Localhost: 32400, Localhost: 32401 und Localhost: 32402 als Bootstrap -Server
Kafka.Properties
broker.id=0 advertised.listeners=PLAINTEXT://kafka-0.kafka-headless.kafka:9092 ...
Kubectl Port-Forward -n Kafka Kafka-0 9092: 9092
KAFKA-PROXY-Server-Stiefelstrap-server-Mapping "127.0.0.1:9092,0.0.0.0:19092"--Dial-Address-Mapping "Kafka-0.Kafka-headless.kafka: 9092.0.0.0.0: 9092"
Verwenden Sie Localhost: 19092 als Bootstrap -Server
Strimzi 0,13,0 CRD
apiversion: kafka.strimzi.io/v1beta1kind: kafkametadata: Name: Test-Cluster
Namespace: Kafkaspec: Kafka: Version: 2.3.0Replicas: 3Listener: Ebene: {} TLS: {} config: offsets.topic.Replication.factor: 3 transaction.state.log.Replication.factor: 3 transaction.state.log. Min.ISR: 2 Num.Partitions: 60 Standard.replikation.Factor: 3Storage: Typ: JBOD Volumes:
- ID: 0 Typ: Persistent Claim Größe: 20GI DeleteClaim: True
Zookeeper: Repliken: 3Storage: Typ: Persistent-Claim-Größe: 5GI DeleteClaim: True
Entityoperator: Topicoperator: {} Benutzeroperator: {}Kubectl Port-Forward -n Kafka Test-Cluster-Kafka-0 9092: 9092 Kubectl Port-Forward -n Kafka Test-Cluster-Kafka-1 9093: 9092 Kubectl Port-Forward -n Kafka Test-Cluster-Kafka-2 9094: 9092 KAFKA-PROXY-Server-Log-Level-Debuggen -Stiefelstrap-Server-Mapping "127.0.0.1:9092,0.0.0.0:19092" -Stiefelstrap-Server-Mapping "127.0.0.1:9093,0.0.0.0:19093" -Stiefelstrap-Server-Mapping "127.0.0.1:9094,0.0.0.0:19094" -Dial-Address-Mapping "Test-Cluster-Kafka-0.test-Cluster-kafka-brokers.kafka.svc.cluster.local: 9092,0.0.0.0: 9092" -Dial-Address-Mapping "Test-Cluster-Kafka-1.test-Cluster-Kafka-Brokers.kafka.svc.cluster.local: 9092,0.0.0.0: 9093" -Dial-Address-Mapping "Test-Cluster-kafka-2.test-cluster-kafka-brokers.kafka.svc.cluster.local: 9092,0.0.0.0: 9094"
Verwenden Sie Localhost: 19092 als Bootstrap -Server
Cloud SQL Proxy
Sarama
