Skip to content

Commit

Permalink
2.4.7 docs edit
Browse files Browse the repository at this point in the history
Signed-off-by: reggie-k <[email protected]>
  • Loading branch information
reggie-k committed Jul 13, 2022
1 parent 75e6453 commit dc9e755
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ your feedback and introduced additional access control settings that control acc

#### Pod Logs UI

Since 2.4.6, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy.
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.6
#### 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.

Expand Down
4 changes: 2 additions & 2 deletions docs/operator-manual/upgrading/2.3-2.4.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,9 +151,9 @@ p, role:test-db-admins, logs, get, staging-db-admins/*, allow

### Pod Logs UI

Since 2.4.6, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy.
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.6
### 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.

Expand Down

0 comments on commit dc9e755

Please sign in to comment.