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

Feature/pulsar manager initialize #457

Merged
merged 4 commits into from
Feb 14, 2024

Conversation

Mortom123
Copy link
Contributor

See #438 / #438 (comment) 3.PR

Also the Pulsar-Manager Admin interface is exposed on a different, non outward facing, service because of given concerns.

Motivation

Right now you need to initialize the pulsar-manager manually, this can be done as an init job.

Modifications

  1. Change Admin Port exposure of Pulsar Manager to second internal service
  2. Provide means to securely generate a password / use an existing one
  3. Provide a job that runs on init and conditions the Pulsar Manager

Verifying this change

  • Make sure that the change passes the CI checks. Here

@Mortom123
Copy link
Contributor Author

@lhotari, please have a look. :) I was able to figure ssh-access out to the build agents

@Mortom123 Mortom123 force-pushed the feature/pulsar_manager_initialze branch from 4eaf483 to c139660 Compare February 14, 2024 11:45
charts/pulsar/values.yaml Outdated Show resolved Hide resolved
@lhotari lhotari merged commit d0b784a into apache:master Feb 14, 2024
30 checks passed
@lhotari lhotari changed the title Feature/pulsar manager initialze Feature/pulsar manager initialize Feb 14, 2024
@lhotari
Copy link
Member

lhotari commented Feb 14, 2024

Thanks for the great contribution @Mortom123

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.

2 participants