kafka proxy
v0.3.12
O proxy Kafka é baseado na idéia do proxy da nuvem SQL. Ele permite que um serviço se conecte aos corretores Kafka sem ter que lidar com certificados SASL/Plain Authentication e SSL.
Ele funciona abrindo soquetes TCP na máquina local e proxying conexões com os corretores Kafka associados quando os soquetes são usados. O host e o porto nas respostas de metadados e findcoordinator recebidas dos corretores são substituídos por contrapartes locais. Para corretores descobertos (não configurados como servidores Boostrap), os ouvintes locais são iniciados em portas aleatórias. O recurso dinâmico dos ouvintes locais pode ser desativado e uma lista adicional de mapeamentos de servidores externos pode ser fornecida.
O proxy pode encerrar o tráfego do TLS e autenticar usuários usando o SASL/PLANE. O método de verificação de credenciais é configurável e usa o sistema de plug -in de Golang sobre o RPC.
Os proxies também podem se autenticar usando um método frugável que é transparente para outros servidores e clientes Kafka. Atualmente, o token do Google ID para contas de serviço é implementado, ou seja, solicitações de cliente proxy e envia a conta de serviço JWT e o servidor proxy recebe e valida ao Google JWKS.
As chamadas da API da KAFKA podem ser restritas para impedir algumas operações, por exemplo, exclusão de tópicos ou solicitações de produção.
Ver:
Proxy Kafka com Amazon MSK
Um guia para o protocolo Kafka
Guia do protocolo Kafka
A tabela a seguir fornece uma visão geral das versões Kafka suportadas (especificadas uma e todas as versões Kafka anteriores). Como nem todo lançamento da Kafka adiciona novas mensagens/versões relevantes para o proxy Kafka, as versões Kafka mais recentes também podem funcionar.
| Versão de proxy Kafka | Versão kafka |
|---|---|
| de 0,11.0 | |
| 0.2.9 | a 2.8.0 |
| 0.3.1 | a 3.4.0 |
| 0.3.11 | a 3.7.0 |
| 0.3.12 | a 3.9.0 |
Baixe o último lançamento
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
Mova o binário para o seu caminho.
sudo mv ./kafka-proxy /usr/local/bin/kafka-proxy
make clean build
As imagens do Docker estão disponíveis no Docker Hub.
Você pode lançar um contêiner Kafka-Proxy para experimentá-lo com
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 agora estará acessível no localhost:30001 , localhost:30002 e localhost:30003 , conectando-se a corretores Kafka em Docker (Network Bridge Gateway 172.17.0.1 ) Publicidade dos ouvintes localhost:19092 , localhost:29092 localhost:39092 .
Imagens do docker com plugins pré-compilados localizados em /opt/kafka-proxy/bin/ são marcados com <release>-all .
Você pode lançar um contêiner Kafka-Proxy com plugin Auth-LDAP para experimentá-lo com
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
A autenticação SASL é iniciada pelo proxy. A autenticação SASL está desativada nos clientes e ativada nos corretores Kafka.
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"
Autenticação GSSAPI / Kerberos
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
A autenticação SASL é realizada pelo proxy. A autenticação SASL é ativada nos clientes e desativada nos corretores Kafka.
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"
Validar esse certificado de cliente usado pelo Proxy Client é exatamente o mesmo que o certificado de cliente em autenticação iniciada por proxy
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
Autenticação entre Kafka Proxy Client e Kafka Proxy Server com Google-ID (Conta de Serviço 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"
Conecte -se através do servidor proxy de meias de teste5
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
Conecte através do servidor proxy HTTP de teste usando o método Connect
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
Às vezes, pode ser necessário não apenas validar que o certificado do cliente é válido, mas também que o Certificado de Cliente DN é emitido para um caso de uso concreto. Isso pode ser alcançado usando o seguinte conjunto de argumentos:
--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
Ao configurar --proxy-listener-tls-client-cert-validate-subject true , o Proxy Kafka inspecionará os campos DN do certificado de cliente para os valores esperados definidos com os argumentos --proxy-listener-tls-required-client-* . As correspondências são sempre exatas e usadas juntas, para todos os valores não vazios. Por exemplo, para permitir um certificado válido para country=DE e organization=grepplabs , configure o proxy Kafka da seguinte maneira:
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
--- APIVERSION: APPS/V1KIND: DIPLAÇÃOMETADATATA: Nome: MyAppSpec: Replicas: 1
Seletor: MatchLabels: App: MyApp
Modelo: Metadados: Rótulos: App: MyApp Anotações: Prometheus.io/scrape: 'True'Spec: Containers:
-Nome: Kafka-Proxy Imagem: Grepplabs/Kafka-Proxy: Últimas Args:
-'Server'-' ---Log-format = JSON'- '--Bootstrap-Server-Mapping = Kafka-0: 9093.127.0.0.1: 32400'-' --Bootstrap-Server-Mapping = Kafka-1: 9093.127.0.0.1: 32401'- '--BootStrap-Server-mapp = Kafka-2: 9093.127.0.0.1: 32402'-'--tls-enable '--tls-ca-chan-Cert- Arquivo =/var/run/secret/kafka-ca-chan-certificate/ca-chhain.cert.pem'- '--tls-client-chert-File =/var/run/secret/kafka-clientctificate/ client.Cert.Pem'- '--tls-client-key-File =/var/run/secret/kafka-client-key/client.key.pem'-'--tls-client-key-password = $ (TLS_CLIENT_KEY_PASSWORD) '-' --SL-ENABLE'- '--SL-JAAS-CONFIG-FILE =/var/run/secret/kafka-client-jaas/jaas.config' Env:
-Nome: tls_client_key_passwordValueFrom: SecretKeyRef: Nome: TLS-Client-key-PasswordKey: Senha Volumemounts:
-Nome: "SASL-JAAS-Config-File" MountPath: "/var/run/secret/kafka-client-jaaS"-Nome: "TLS-CA-Chain-Certificate" MountPath: "/var/Run/Secret/ Kafka-Ca-Chain-Certificado "-Nome:" TLS-Client-Cert-File "MountPath:"/var/run/secret/kafka-client-certificate "-Nome:" TLS-Client-Key-File "MountPath: Portas "/var/run/secret/kafka-client-chave":
- Nome: METRICSCONTINERSPORT: 9080 LIGADOPROBE: HTTPGET: Caminho: /Porta de saúde: 9080InitialDelaySegunds: 5PeriodSeconds: 3 prontidão: 5periodsEct: /Path: /9080InitialDelaySoSTSS: 5PeriodSech: : 5- Nome: MyApp Imagem: MyApp: Últimas portas:
- Containerport: 8080Name: Metrics Env:
- Nome: bootstrap_serversValue: "127.0.1:32400,127.0.0.1:32401,127.0.0.1:32402" Volumes:
-Nome: SASL-JAAS-Config-FileSecret: SecretName: SASL-JAAS-CONFIG-FILE-NOME: TLS-CA-Chain-CertificatesEcret: SecretName: TLS-CA-C-Crectificate-Nome: TLS-Client-FileSecret : SecretName: TLS-Client-Cert File-Nome: TLS-Client-key-FileSecret: SecretName: TLS-Client-key-File --- APIVERSION: APPS/V1KIND: StatefulSetMetadata: Nome: Kafka-proxyspec: Seletor: MatchLabels: App: Kafka-proxy
Replicas: 1
NOME DO SERVIÇO: KAFKA-PROXY
Modelo: Metadados: Rótulos: App: Kafka-proxyspec: Containers:
-Nome: Kafka-Proxy Imagem: Grepplabs/Kafka-Proxy: Últimas Args:
-'Server'-' ---Log-format = JSON'- '--Bootstrap-Server-Mapping = Kafka-0: 9093.127.0.0.1: 32400'-' --Bootstrap-Server-Mapping = Kafka-1: 9093.127.0.0.1: 32401'- '--BootStrap-Server-mapp = Kafka-2: 9093.127.0.0.1: 32402'-'--tls-enable '--tls-ca-chan-Cert- Arquivo =/var/run/secret/kafka-ca-chan-certificate/ca-chhain.cert.pem'- '--tls-client-chert-File =/var/run/secret/kafka-clientctificate/ client.Cert.Pem'- '--tls-client-key-File =/var/run/secret/kafka-client-key/client.key.pem'-'--tls-client-key-password = $ (TLS_CLIENT_KEY_PASSWORD) '-' --SL-ENABLE'- '--SL-JAAS-CONFIG-FILE =/var/run/secret/kafka-client-jaas/jaas.config'-' --proxy-request-buffer -size = 32768'- '--proxy-resposta-buffer-size = 32768'-'-Proxy-listener-leit-buffer-size = 32768'- '-Proxy-listener-write-buffer-size = 131072 '-' --kafka-conexão-leitura-buffer-size = 131072'- '--kafka-conexão-write-buffer-size = 32768' Env:
-Nome: tls_client_key_passwordValueFrom: SecretKeyRef: Nome: TLS-Client-key-PasswordKey: Senha Volumemounts:
-Nome: "SASL-JAAS-Config-File" MountPath: "/var/run/secret/kafka-client-jaaS"-Nome: "TLS-CA-Chain-Certificate" MountPath: "/var/Run/Secret/ Kafka-Ca-Chain-Certificado "-Nome:" TLS-Client-Cert-File "MountPath:"/var/run/secret/kafka-client-certificate "-Nome:" TLS-Client-Key-File "MountPath: Portas "/var/run/secret/kafka-client-chave":
- Nome: MetricsContainerport: 9080 - Nome: Kafka -0ContainerPort: 32400 - Nome: Kafka -1Containerport: 32401 - Nome: Kafka -2ContainerPort: 32402 Livorness: Httpget: Path: /Healths: 908InInitialDial caminho : /Porta de saúde: 9080InitialDelayaySeconds: 5PeriodSeconds: 10TimeoutSegunds: 5successhreshold: 2FailurethReshold: 5 Recursos: Solicitações: Memória: 128MI CPU: 1000m RestartPolicy: Volumes sempre: Volumes:
-Nome: SASL-JAAS-Config-FileSecret: SecretName: SASL-JAAS-CONFIG-FILE-NOME: TLS-CA-Chain-CertificatesEcret: SecretName: TLS-CA-C-Crectificate-Nome: TLS-Client-FileSecret : SecretName: TLS-Client-Cert File-Nome: TLS-Client-key-FileSecret: SecretName: TLS-Client-Key-FileKubectl Port-forward Kafka-proxy-0 32400: 32400 32401: 32401 32402: 32402
Use localhost: 32400, localhost: 32401 e localhost: 32402 como servidores de bootstrap
kafka.properties
broker.id=0 advertised.listeners=PLAINTEXT://kafka-0.kafka-headless.kafka:9092 ...
kubectl porta-forward -n kafka kafka-0 9092: 9092
kafka-proxy servidor-bootstrap-server-map "127.0.0.1:9092,0.0.0.0:19092"--Dial-address-mapping "kafka-0.kafka heateless.kafka: 9092,0.0.0.0: 9092"
Use localhost: 19092 como servidores de bootstrap
Strimzi 0,13.0 CRD
APIVERSION: KAFKA.STRIMZI.IO/V1BETA1KIND: KAFKAMETADATA: NOME: CLUTER DE TESTE
Namesace: Kafkaspec: Kafka: Versão: 2.3.0Replicas: 3Listeners: Plain: {} tls: {} config: offsets.topic.Replication.Factor: 3 transaction.state.log.replication.factor: 3 transaction.state.log. min.isr: 2 num.partições: 60 default.replication.Factor: 3Storage: Tipo: Volumes JBOD:
- ID: 0 Tipo: Tamanho da reivindicação persistente: 20GI DeleteClaim: true
Zookeeper: Replicas: 3Storage: Tipo: Tamanho da reivindicação persistente: 5GI DeleteClaim: true
EntityOperator: TopicOperator: {} UserOperator: {}kubectl porta-forward -n kafka test-cluster-kafka-0 9092: 9092 kubectl porta-forward -n kafka test-cluster-kafka-1 9093: 9092 kubectl porta-forward -n kafka test-cluster-kafka-2 9094: 9092 Servidor Kafka-Proxy-Debug de nível de log --BootStrap-Server-mapping "127.0.0.1:9092,0.0.0.0:19092" --BootStrap-Server-mapping "127.0.0.1:9093,0.0.0.0:19093" --Bootstrap-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: 9092" -Dial-address-mapping "Test-Cluster-kafka-1.test-cluster-kafka-brokers.kafka.svc.cluster.local: 9092,0.0.0: 9093" -Dial-address-mapping "Test-cluster-kafka-2.test-cluster-kafka-brokers.kafka.svc.cluster.local: 9092,0.0.0: 9094"
Use localhost: 19092 como servidores de bootstrap
Cloud SQL Proxy
Sarama
