Skip to content
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

Nats-Kafka briddge fails with error starting bridge, error signing nonce: unable to extract key pair from file : nkeys: no nkey seed found #5225

Open
Rudraksh95 opened this issue Mar 18, 2024 · 0 comments
Labels
defect Suspected defect such as a bug or regression

Comments

@Rudraksh95
Copy link

Observed behavior

nats kafka bridge running in kubernetes (image tag nats-kafka:1.4.2) is crashing with no nkey seed found upon using username password authentication type

config map
nats: {
Servers: ["host:4222"[],
ConnectTimeout: 5000,
MaxReconnects: 5,
ReconnectWait: 5000,
tls: {
root: "/etc/ssl/certs/nats/ca.pem",
cert: "/etc/ssl/certs/nats/tls.crt",
key: "/etc/ssl/certs/nats/tls.key"
}
usercredentials: "/opt/nats/usercreds.conf"
},

usercreds.conf as a secrets file mounted on the pod
Name: nats-kafka-bridge
Namespace:
Labels:
Annotations:

Data
usercreds.conf: '{"authorization":{"password":"password","user":"user"}}'

Expected behavior

the bridge should be able to connect to the nats server with username pass and not nkeys

Server and client version

nats-kafka:1.4.2
nats-server: 2.10.7

Host environment

No response

Steps to reproduce

No response

@Rudraksh95 Rudraksh95 added the defect Suspected defect such as a bug or regression label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Suspected defect such as a bug or regression
Projects
None yet
Development

No branches or pull requests

1 participant