Skip to content
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

Guard tag (indicating of detecting abusing containers) not displayed in Control Panel Agent list #3342

Open
jopemachine opened this issue Jan 2, 2025 — with Lablup-Issue-Syncer · 0 comments · May be fixed by #3355
Assignees

Comments

@jopemachine
Copy link
Member

jopemachine commented Jan 2, 2025

Motivation

Currently, the resolve_local_config function in the agent GQL, despite its name, only returns the auto_terminate_abusing_kernel value.

As a result, there is an issue where certain fields, including abusing_report_path, are not displayed correctly in the Backend.AI ControlPanel.

Suggestion

resolve_local_config has significant security risks.Let's deprecate this resolver and add query and mutation GraphQL (GQL) operations for abuse_report.

Impact

Client code, such as ControlPanel, that uses this API needs to be updated accordingly.

 

@jopemachine jopemachine self-assigned this Jan 2, 2025
@jopemachine jopemachine added type:bug Reports about that are not working comp:manager Related to Manager component and removed type:bug Reports about that are not working comp:manager Related to Manager component labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant