-
Notifications
You must be signed in to change notification settings - Fork 0
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
Deploy beamline services to new namespace #7
base: main
Are you sure you want to change the base?
Conversation
Does this need apps.yaml namespace to change? Blocked because need SealedSecret to be generated in new namespace |
@DiamondJoseph this is a fun PR. We do also need to change the apps.yaml namespace because bl45p namespace app will not have permission to deploy to bl45p-beamline. For this reason we can't have argo do the whole transfer for us. When you are ready with the sealed secret. You can:
Out newly namespaced beamline will burst into life. Probably. |
The epics helm charts that are being used are now consistent with the other test beamlines and everything appears to be running OK. Note: I haven't touched the actual ioc configs. |
@marcelldls I think we should take this opportunity to update the iocs values.yaml to point at the latest versions of the generic IOCs. This is something that I think is not super slick to do right now - do we want to make some tooling to do this? can you let me know what you think? |
@gilesknap fair enough. The services, deployment repos for bl45p is not exactly consistent with any other beamline (experimental?) so I was trying to not do more than I need to, also PRs into the deployment repo is a bit of a pain. As for tooling - I believe you have mentioned this as a possible feature for |
Yes up revving is what I'm suggesting. We don't have a strong need to update the IOCs right now. |
No description provided.