diff --git a/CHANGELOG.md b/CHANGELOG.md index 8d976a322697c..ff5d5a790e3fd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -13,9 +13,13 @@ commands, and helps to troubleshoot the application state. Argo CD is used to manage the critical infrastructure of multiple organizations, which makes security the top priority of the project. We've listened to your feedback and introduced additional access control settings that control access to Kubernetes Pod logs and the new Web Terminal feature. -#### Known UI Issue for Pod Logs Access +#### Pod Logs UI -Currently, upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. +Since 2.4.7, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy. + +#### Known pod logs UI issue prior to 2.4.7 + +Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. ### OpenTelemetry Tracing Integration diff --git a/docs/operator-manual/upgrading/2.3-2.4.md b/docs/operator-manual/upgrading/2.3-2.4.md index d4d272b90ec1a..78bc3d4686645 100644 --- a/docs/operator-manual/upgrading/2.3-2.4.md +++ b/docs/operator-manual/upgrading/2.3-2.4.md @@ -149,9 +149,13 @@ p, role:test-db-admins, applications, *, staging-db-admins/*, allow p, role:test-db-admins, logs, get, staging-db-admins/*, allow ``` -## Known UI issue +### Pod Logs UI -Currently, upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. +Since 2.4.7, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy. + +### Known pod logs UI issue prior to 2.4.7 + +Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. ## Test repo-server with its new dedicated Service Account diff --git a/ui/src/app/applications/components/resource-details/resource-details.tsx b/ui/src/app/applications/components/resource-details/resource-details.tsx index e5fa9345505e5..d832e7cbda777 100644 --- a/ui/src/app/applications/components/resource-details/resource-details.tsx +++ b/ui/src/app/applications/components/resource-details/resource-details.tsx @@ -42,7 +42,16 @@ export const ResourceDetails = (props: ResourceDetailsProps) => { const page = parseInt(new URLSearchParams(appContext.history.location.search).get('page'), 10) || 0; const untilTimes = (new URLSearchParams(appContext.history.location.search).get('untilTimes') || '').split(',') || []; - const getResourceTabs = (node: ResourceNode, state: State, podState: State, events: Event[], extensionTabs: ResourceTabExtension[], tabs: Tab[], execEnabled: boolean) => { + const getResourceTabs = ( + node: ResourceNode, + state: State, + podState: State, + events: Event[], + extensionTabs: ResourceTabExtension[], + tabs: Tab[], + execEnabled: boolean, + logsAllowed: boolean + ) => { if (!node || node === undefined) { return []; } @@ -78,30 +87,32 @@ export const ResourceDetails = (props: ResourceDetailsProps) => { const onClickContainer = (group: any, i: number) => SelectNode(selectedNodeKey, group.offset + i, 'logs', appContext); - tabs = tabs.concat([ - { - key: 'logs', - icon: 'fa fa-align-left', - title: 'LOGS', - content: ( -