Bump Go stream client to v0.13-alpha #756
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@Gsantomaggio I bumped the Go stream client in the system tests to latest released
v0.7-alpha
.System tests are now failing with
because https://github.com/rabbitmq/rabbitmq-stream-go-client/blob/3356a455a15a24877ca82911594ad64c842008a3/pkg/stream/server_frame.go#L426 adds a wrong hostname and port: It adds the K8s internal hostname
mqtt-stomp-stream-server-0.mqtt-stomp-stream-nodes.rabbitmq-system
instead of the K8s node IP address and it adds port 5552 instead of the K8s node port although K8s node IP address and K8s node port are set incluster-operator/system_tests/utils.go
Lines 952 to 953 in 6f1c4df
The Go client in the system tests runs outside the K8s cluster.
System tests use Service type NodePort.
Is there a way to use the Go client outside a K8s cluster with Service type NodePort?
It used to work with the older version
github.com/rabbitmq/rabbitmq-stream-go-client v0.0.0-20210422170636-520637be5dde
.