Credentials for Big Bang Packages¶
This document includes details on credentials to access each package in a default install (i.e., without SSO). It is safe to assume that any packages not listed in the two categories below either have no need for authentication or use different methods (e.g., Velero require kubectl access).
Packages With No Built-in Authentication¶
Although the below applications have no built in authentication, Big Bang’s helm values can be configured to deploy authservice in front of these endpoints. Authservice is an Authentication Proxy that can integrate with SSO providers like Keycloak.
- Monitoring (Prometheus)
- Monitoring (Alertmanager)
- cert-manager (controller and certificate resources; no user-facing authentication)
Packages With Built-in Authentication¶
The applications in the table below provide both SSO and built-in authentication. The table gives default credentials and ways to access and/or override those.
| Package (Application) | Default Username | Default Password | Additional Notes |
|---|---|---|---|
| Kiali | N/A | (randomly generated) | Use kubectl -n kiali create token kiali-service-account to create a temporary token |
| Logging (Kibana) | elastic |
(randomly generated) | Use kubectl get secrets -n logging logging-ek-es-elastic-user -o go-template='{{.data.elastic \| base64decode}}' to get the password |
| Grafana | admin |
prom-operator |
Default password can be overridden with Helm values grafana.values.adminPassword |
| Twistlock | admin |
change_this_password |
Admin account will be automatically setup on fresh installs if init.enabled is true. Default password can be overridden by setting twistlock.values.console.credentials.password |
| ArgoCD | admin |
(randomly generated) | Use kubectl -n argocd get secret argocd-initial-admin-secret -o go-template='{{.data.password \| base64decode}}' to get the password. Note: If the argocd-initial-admin-secret does not exist, you will need to reset the admin password. |
| Minio | minio |
minio123 |
Access and secret key can be overridden with Helm values addons.minio.accesskey and addons.minio.secretkey respectively |
| Gitlab | root |
(randomly generated) | Use kubectl -n gitlab get secret gitlab-gitlab-initial-root-password -o go-template='{{.data.password \| base64decode}}' to get the password |
| Sonarqube | admin |
admin |
Default password can be overridden with Helm values addons.sonarqube.values.account.adminPassword |
| Anchore | admin |
(randomly generated) | Use kubectl get secrets -n anchore anchore-anchore-enterprise -o go-template='{{.data.ANCHORE_ADMIN_PASSWORD \| base64decode}}' to get the password, or override with Helm values addons.anchore.values.anchoreGlobal.defaultAdminPassword |
| Mattermost | N/A | N/A | Prompted to setup an account when you first hit the virtual service - this user becomes admin, no default user |
| Keycloak | admin |
password |
Default username and password can be overridden with Helm values addons.keycloak.values.secrets.env.stringData.KEYCLOAK_ADMIN and addons.keycloak.values.secrets.env.stringData.KEYCLOAK_ADMIN_PASSWORD respectively |
| Neuvector | admin |
admin |
You should change the default password when you log into Neuvector. Can also be changed via the chart at the controller.secret.data.userinitcfg.yaml key, see the upstream docs for more details and examples. |
| Harbor | admin |
Harbor12345 |
Default password can be overridden with Helm values addons.harbor.values.harborAdminPassword |
| Fortify | admin |
admin |
You will be prompted to change the admin user password when you first attempt to login to Fortify using the default credentials |
Internal CI-only credentials¶
The credentials in this section are used only by Big Bang’s disposable test profiles. They are not enabled by a default installation and are not supported for consumer development or production deployments.
The GitLab 19 test profile deploys Garage as an internal S3-compatible service.
Garage 0.9.3-bb.2 supports externally managed Secrets but does not generate
random credentials. The test profile therefore supplies fixed, ephemeral
values. The S3 credentials are stored in the
garage/garage-gitlab-credentials Secret:
| Garage credential | Secret key | Retrieval command |
|---|---|---|
| S3 access-key ID | accessKeyId |
kubectl -n garage get secret garage-gitlab-credentials -o go-template='{{base64decode .data.accessKeyId}}' |
| S3 secret key | secretAccessKey |
kubectl -n garage get secret garage-gitlab-credentials -o go-template='{{base64decode .data.secretAccessKey}}' |
The fixed Garage admin API token is configured directly in
tests/test-values.yaml as both garageInit.adminToken and
upstream.environment.GARAGE_ADMIN_TOKEN; it is not stored in the consumer
credential Secret.