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

rpk/config: Make redpanda.advertised* optional #100

Merged
merged 3 commits into from
Nov 17, 2020

Conversation

0x5d
Copy link
Contributor

@0x5d 0x5d commented Nov 16, 2020

Checklist

When referencing a related issue, remember to migrate duplicate stories from the
external tracker. This is not relevant for most users.

@@ -316,6 +316,9 @@ func writeNodeConfig(
conf := config.DefaultConfig()
conf.Redpanda.Id = int(nodeID)

conf.Redpanda.AdvertisedKafkaApi = &config.SocketAddress{}
conf.Redpanda.AdvertisedRPCAPI = &config.SocketAddress{}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't this the main problem, that they are not null

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope. rpk container never left them as null. The problem appeared when running it standalone.

@0x5d 0x5d marked this pull request as ready for review November 17, 2020 01:55
Copy link
Contributor

@emaxerrno emaxerrno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

I tested manually too.

agallego in ~/Downloads/test λ ./rpk version && ./rpk container purge && ./rpk container start -n 3 && ./rpk api status
 (rev 680dd828)
Stopping node 1
Stopping node 2
Stopping node 0
Deleted data for node 0
Deleted data for node 2
Deleted data for node 1
Deleted cluster data.
Downloading latest version of Redpanda
Starting cluster
  NODE ID  ADDRESS          CONFIG                                                  
  0        127.0.0.1:59457  /Users/agallego/.rpk/cluster/node-0/conf/redpanda.yaml  
  1        127.0.0.1:59459  /Users/agallego/.rpk/cluster/node-1/conf/redpanda.yaml  
  2        127.0.0.1:59460  /Users/agallego/.rpk/cluster/node-2/conf/redpanda.yaml  

Cluster started! You may use 'rpk api' to interact with the cluster. E.g:

rpk api status

  Redpanda Cluster Status                   
                                            
  0 (127.0.0.1:59457)      (No partitions)  

@dotnwat
Copy link
Member

dotnwat commented Nov 17, 2020

@0x5d does this fix #99?

@emaxerrno
Copy link
Contributor

@dotnwat I think it does.

@dotnwat
Copy link
Member

dotnwat commented Nov 17, 2020

ok when we find out let's make sure to update the pr message so that it links this pr to the issue.

@emaxerrno
Copy link
Contributor

also @0x5d we should update the release notes. 0pendingreleasenotes.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rpk/config: Make redpanda.advertised* optional
3 participants