Change Registry Password
This guide explains how to change the authentication password for a CloudRaya Container Registry and what impact this action has on existing workflows.
Changing the registry password is useful when credentials are compromised, rotated as part of security policy, or no longer accessible.
⚠️ Important Security Notice
Changing a registry password immediately invalidates the previous password.
Any service, application, or pipeline using the old password will fail authentication until updated.
This action is intentional and irreversible for security reasons.
When Should You Change the Registry Password?
Change the registry password if:
- Credentials are exposed or suspected to be compromised
- A team member with access leaves the organization
- You follow periodic credential rotation policies
- CI/CD pipelines fail due to lost credentials
- You want to enforce tighter access control
What Happens When You Change the Password?
What Changes
- You set a new registry password yourself (it is not auto-generated)
- Old credentials stop working immediately
- New credentials must be used for:
docker login- CI/CD pipelines
- Kubernetes image pulls (private images)
What Does NOT Change
- Registry URL
- Registry username
- Stored images and repositories
- Storage usage
- Existing tags and metadata
No data is deleted or modified.
How to Change the Registry Password
- Open Dashboard → Storage → CloudRaya Container Registry
- Select the registry you want to manage
- Click View Detail
- Click Change Password
- Enter and confirm your new password, then submit
Make sure to store it securely.
After Changing: Required Actions
After changing the password, you must update all integrations.
Docker Login
docker login <registry-endpoint>Use the new password when prompted.
CI/CD Pipelines
Update registry credentials in:
- GitHub Actions secrets
- GitLab CI variables
- Jenkins credentials
- Any external automation tools
Kubernetes (Private Images)
If your workloads pull images from this registry:
- Update the
imagePullSecrets - Recreate secrets if necessary
📄 See: Integrate Container Registry with Kubernetes
Best Practices
- Change passwords periodically as part of security hygiene
- Avoid hardcoding registry credentials in code
- Use secret managers or encrypted CI/CD variables
- Rotate credentials immediately after team changes
- Validate pipelines after changing credentials
Common Issues After Changing the Password
| Issue | Cause | Solution |
|---|---|---|
docker pull fails | Old password cached | Re-run docker login |
| CI pipeline fails | Secrets not updated | Update pipeline credentials |
| Kubernetes pods stuck | Old imagePullSecret | Recreate secret |