-
Notifications
You must be signed in to change notification settings - Fork 68
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
Update dicom-server-deploy.yaml #2740
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dicom-server was working in MIDRC staging because this was manually added to the deployment. Without it, network policies prevent dicom-server from connecting to the "orthanc" DB.
Things were working in MIDRC prod because there existed a "dicom-server" g3auto secret containing the same DB creds as the "orthanc" secret, and network policies are created based on those secrets (netpol assume the dicom-server service uses the "dicom-server" secret). When the DB creds were changed, but the "unused" "dicom-server" secret was not updated, things stopped working.
This change should allow us to skip setting up network policies for this service.
Please find the detailed integration test report here Please find the ci env pod logs here |
Link to JIRA ticket if there is one:
New Features
Breaking Changes
Bug Fixes
Improvements
Dependency updates
Deployment changes