Add README with repository access information and OWNERS file

- Add OWNERS file with hyperfleet team approvers
- Update README with repository descriptions and access information
- Include steps for repository access and team membership requirements

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: xueli181114

README.md

@@ -1,2 +1,18 @@
 # hyperfleet-e2e
-HyperFleet E2E Testing - Black-box end-to-end tests for HyperFleet cluster lifecycle management. Validates Critical User    Journeys (CUJ) including cluster creation, scaling, updates, and deletion. Integrates with Prow for automated testing. Uses    Kind clusters for test isolation and real component validation.
+
+HyperFleet E2E Testing - Black-box end-to-end tests for HyperFleet cluster lifecycle management. Validates Critical User Journeys (CUJ) including cluster creation, scaling, updates, and deletion. Integrates with Prow for automated testing. Uses Kind clusters for test isolation and real component validation.
+
+## Repository Access
+
+All members of the **hyperfleet** team have write access to this repository.
+
+### Steps to Apply for Repository Access
+
+If you're a team member and need access to this repository:
+
+1. **Verify Organization Membership**: Ensure you're a member of the `openshift-hyperfleet` organization
+2. **Check Team Assignment**: Confirm you're added to the hyperfleet team within the organization
+3. **Repository Permissions**: All hyperfleet team members automatically receive write access
+4. **OWNERS File**: Code reviews and approvals are managed through the OWNERS file
+
+For access issues, contact a repository administrator or organization owner.