This Task serves as a template for requesting access to AIPCC-owned systems and resources, including GitLab repositories and groups, Quay repositories, and Konflux tenants.

Do not edit this template directly. Instead, copy this Task, update the title, and fill in the relevant sections below. All access requests must be tracked in Jira for security, compliance, and audit purposes. Requests made through Slack, email, or other ad-hoc channels are not considered valid unless captured here.

All approvals, decisions, and provisioning steps must be recorded in the created Task. Incomplete requests or missing approvals may delay or block access. Access may be reviewed or revoked if it is no longer required.

HOW TO USE THIS TEMPLATE

1. Copy this Task and ensure it is linked under AIPCC-10105.
2. Update the Task title using this format: Grant (System) Access for (User) to (Resource / Group / Tenant).
3. Fill in all required sections. Failing to fill required section will result in delays in processing the request.
4. Provide a business justification; explain clearly why this access is needed. Access is granted only when there is a concrete, work-related need.
5. Ensure any required approvals are provided as comments on the created Task.

GENERAL REQUEST INFORMATION (required for all requests)

• Requestor's name: Kapil Nema
• Requestor's Red Hat email: knema@redhat.com
• Organization and team: RHOAI Kubeflow Training
• System(s) requested: Quay

QUAY / KONFLUX ACCESS REQUESTS

Access to AIPCC-owned Quay repositories and Konflux tenants follows the same request and approval process and is granted at the same time. If you are unsure whether you need the access, do not request it. Requests without a clear justification may be denied. Any access beyond read-only requires both a business justification and manager approval.

Please provide:

• Justification for access: I need to access AIPCC images to be able to develop MPI training images based on AIPCC
• Link to your MR:

Instructions for creating the MR:

1. Follow the workflow instructions outlined here: https://gitlab.cee.redhat.com/service/app-interface#workflow.
2. Add or update the relevant permission files with your user details.
3. Ensure your changes follow the structure shown in this example MR: https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/162764/diffs.
4. Once your MR is ready, paste the link into this Jira ticket. The request will not be reviewed until the MR link is provided.

GITLAB ACCESS REQUESTS

Please try authenticating via this link first https://red.ht/GitLabSSO and check if your permissions were updated. In case you didn't receive the role you expected proceed with following the steps bellow.

Please provide:

• GitLab group(s) requested:
• Requested access level: guest / reporter / developer / maintainer
• Justification for access: (be specific about what you need to do in GitLab and why)
• Manager's approval for non-read access (if applicable): yes / no (the requestor’s manager must approve elevated access by commenting directly on this Jira ticket)

Approval requirements:

• Guest: No additional approval required. (Cannot see code, just repository existence)
• Reporter: No additional approval required.
• Developer: If the requestor is not part of the AIPCC organization, manager approval is required. The manager must comment on this Jira ticket.
• Maintainer: Requires explicit approval from dhellman@redhat.com. Approval must be given as a comment on this Jira ticket.

Once approved:

1. The requestor will be added to the appropriate Rover group(s).
2. After, the requestor must authenticate using https://red.ht/GitLabSSO.