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

-c param did not work #52

Closed
wolfstudy opened this issue Apr 14, 2020 · 3 comments
Closed

-c param did not work #52

wolfstudy opened this issue Apr 14, 2020 · 3 comments
Assignees

Comments

@wolfstudy
Copy link
Contributor

Following the README.md, the -c means A k8s namespace for installing the Pulsar release, when the -c is specified, the out as follows:

$ ./scripts/pulsar/prepare_helm_release.sh -n pulsar -k sn-platform-pulsar -c --control-center-admin admin --control-center-password admin

Output:

create the credentials for the admin user of control center (grafana & pulsar-manager)
Error from server (NotFound): namespaces "pulsar" not found
generate the token keys for the pulsar cluster
The private key and public key are generated to /var/folders/qz/g2fh76dx5rj4q_fbkfh1q3th0000gn/T/tmp.1Ia65DaF and /var/folders/qz/g2fh76dx5rj4q_fbkfh1q3th0000gn/T/tmp.qzeh7zvU successfully.
Error from server (NotFound): namespaces "pulsar" not found
generate the tokens for the super-users: proxy-admin,broker-admin,admin
generate the token for proxy-admin
Error from server (NotFound): namespaces "pulsar" not found
generate the token for broker-admin
Error from server (NotFound): namespaces "pulsar" not found
generate the token for admin
^C

So i used the following command to create namespace:

$ kubectl create namespace pulsar

Output:

namespace/pulsar created

And then run the command, everything is ok:

$ ./scripts/pulsar/prepare_helm_release.sh -n pulsar -k sn-platform-pulsar -c --control-center-admin admin --control-center-password admin
create the credentials for the admin user of control center (grafana & pulsar-manager)
secret/sn-platform-pulsar-admin-secret created
generate the token keys for the pulsar cluster
The private key and public key are generated to /var/folders/qz/g2fh76dx5rj4q_fbkfh1q3th0000gn/T/tmp.R9eO84Aa and /var/folders/qz/g2fh76dx5rj4q_fbkfh1q3th0000gn/T/tmp.xbc7OHke successfully.
secret/sn-platform-pulsar-token-asymmetric-key created
generate the tokens for the super-users: proxy-admin,broker-admin,admin
generate the token for proxy-admin
secret/sn-platform-pulsar-token-proxy-admin created
generate the token for broker-admin
secret/sn-platform-pulsar-token-broker-admin created
generate the token for admin
secret/sn-platform-pulsar-token-admin created
-------------------------------------

The jwt token secret keys are generated under:
    - 'sn-platform-pulsar-token-asymmetric-key'

The jwt tokens for superusers are generated and stored as below:
    - 'proxy-admin':secret('sn-platform-pulsar-token-proxy-admin')
    - 'broker-admin':secret('sn-platform-pulsar-token-broker-admin')
    - 'admin':secret('sn-platform-pulsar-token-admin')

The credentials of the administrator of Control Center (Grafana & Pulsar Manager)
is stored at secret 'sn-platform-pulsar-admin-secret
@sijie
Copy link
Member

sijie commented Apr 14, 2020

Interesting... are you using the latest master?

@wolfstudy
Copy link
Contributor Author

Interesting... are you using the latest master?

Yes, latest master code

@sijie sijie self-assigned this Apr 16, 2020
@sijie
Copy link
Member

sijie commented Jul 15, 2020

Closed this issue since the problem has been fixed in the latest master.

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

No branches or pull requests

3 participants