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

Align sonar QG by complies #101

Closed
Rolika4 opened this issue Jun 20, 2024 · 0 comments
Closed

Align sonar QG by complies #101

Rolika4 opened this issue Jun 20, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Rolika4
Copy link

Rolika4 commented Jun 20, 2024

We are encountering issues with RBAC permissions impacting the functionality of SonarQube and sonar-operator during the Tekton pipeline scans and within the KubeRocketCI environment. The primary concern is the inability of our ci-sonar user to set the default branch during scans. Additionally, there are problems with the SonarQube widget in KubeRocketCI for users with the developer role. This task involves redefining the RBAC permissions for SonarQube and ensuring the sonar-operator usage aligns with these updated permissions to resolve these issues.

Tasks:

  1. Analyze the current RBAC settings to identify the limitations causing the described issues.
  2. Redefine the RBAC permissions to allow the ci-sonar user to set the default branch during Tekton pipeline scans.
  3. Address the SonarQube widget issues in KubeRocketCI for the developer role by adjusting the necessary permissions or configurations.
  4. Ensure the sonar-operator usage is fully aligned with the updated RBAC settings to prevent similar issues.
  5. Conduct thorough testing to verify that the issues are resolved without introducing any new permissions-related problems.
  6. Document the changes made to the RBAC settings and any other relevant configurations for future reference.
@Rolika4 Rolika4 self-assigned this Jun 20, 2024
@Rolika4 Rolika4 converted this from a draft issue Jun 20, 2024
@Rolika4 Rolika4 added the enhancement New feature or request label Jun 20, 2024
Rolika4 pushed a commit that referenced this issue Jun 20, 2024
@Rolika4 Rolika4 closed this as completed Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant