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

[v2.12.0] Ensure CI/documentation reflect changes to default admin credentials #553

Closed
2 tasks
derek-ho opened this issue Dec 21, 2023 · 3 comments
Closed
2 tasks
Labels
v2.12.0 Issues targeting release v2.12.0

Comments

@derek-ho
Copy link
Contributor

Background

Previously, when installing the security plugin demo configuration, the cluster was spun up with the default admin credentials, admin:admin. A change was made in main and backported to 2.x for the 2.12.0 release, which now requires an initial admin password to be passed in via the environment variable OPENSEARCH_INITIAL_ADMIN_PASSWORD. This will break some CI/testing that relies on OpenSearch to come up without setting this environment variable. This tracking issue is to ensure compliance with the new changes.

Coming from: opensearch-project/security#3624

Acceptance Criteria

  • All documentation references to the old default credentials admin:admin are removed
  • Ensure that CI/testing is working with main and 2.x branches
@prudhvigodithi
Copy link
Collaborator

[Triage]
Thanks @derek-ho, I dont see job-scheduler explicitly using security plugin anywhere in the code or tests and did not see any automation issues (AUTOCUT) created with build failures. So no actions required for job-scheduler with security admin password change. @joshpalis @owaiskazi19 can you please do 2PR and confirm.

Adding @bbarani @peterzhuamazon @DarshitChanpura

Thank you

@joshpalis
Copy link
Member

@prudhvigodithi +1, Job Scheduler has no security test workflow so we're in compliance here

@prudhvigodithi
Copy link
Collaborator

Thanks @joshpalis, closing this issue.

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

No branches or pull requests

3 participants