-
Notifications
You must be signed in to change notification settings - Fork 42
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
Remove RHOSAK #339
Remove RHOSAK #339
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.
/lgtm
@bdattoma need a QE approval here -- I saw you made a comment on the RHODS ticket, so I figure I'll tag you here. |
A question: is the |
I have no idea -- @lucferbux ? I'm only the author of this PR because everyone was standing around pointing fingers at each other like the Spiderman meme. I have no knowledge on anything here, I just deleted the resources as they were labeled RHOSAK. Can't deploy RHOSAK if there are no resources to deploy. |
No idea either, I don't see that file deployed anywhere and I don't have any context about it, not sure how or where is used. |
I did a try creating a custom tile in the dashboard (i.e., OdhApplication object) with the enablement flow. It creates the config map automatically after clicking on "Enable" button in Explore page.
Wdyt? There's probably no harm in having that CM floating in the redhat-ods-applications namespace.. @lucferbux @andrewballantyne This is the app definition I used, in case you wanna give a try yourselves:
|
If there is a configmap created by the effort -- we'd need some build upgrade script to delete it. I'm not in the business of writing scripts to delete resources on a customer cluster. @bdattoma please reply on the ticket and tag Jeff. Pretty sure we want these resources gone, the unused configmap should be cleaned up by us in some fashion -- but that's really not for this PR. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bdattoma, lucferbux The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Added the label based on Berto approving. |
a5a21c9
into
red-hat-data-services:main
https://issues.redhat.com/browse/RHODS-8275