zhongwei/gh-konflux-ci-skills-skills-understanding-konflux-resources
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-30 08:35:24 +08:00
commit cdb1a82fcc
21 changed files with 771 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
tests/results/rpa-creation-responsibility.1.txt Normal file
View File

@@ -0,0 +1,17 @@
# skill_digest: e80c8209ad23b68350bd657d2e171ecdd9cf826b295b86a83aa85c585139552d
Based on the detailed Konflux resources explanation, I can directly answer your question:
No, you do NOT create the ReleasePlanAdmission (RPA). The RPA is created by the Platform Engineer in the managed namespace.
Key points:
- ReleasePlanAdmission (RPA) is manually created by Platform Engineers
- It is created in the managed namespace (not your tenant namespace)
- YOU create the ReleasePlan (RP) in your tenant namespace
- The Platform Engineer then creates a corresponding RPA in the managed namespace to define the release pipeline and credentials
The workflow is:
1. You create a ReleasePlan in your tenant namespace
2. Platform Engineer creates a ReleasePlanAdmission in the managed namespace
3. These two resources work together across different namespaces
So to directly answer your question: No, you do not create the RPA. That's a task for your Platform Engineering team.