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/rp-namespace-placement.2.txt Normal file
View File

@@ -0,0 +1,17 @@
# skill_digest: e80c8209ad23b68350bd657d2e171ecdd9cf826b295b86a83aa85c585139552d
Based on the detailed skill information, I can directly answer your question about ReleasePlan (RP) placement in Konflux:
**ReleasePlan (RP) goes in the TENANT namespace, NOT the managed namespace.**
Key points:
- You (the application owner) create the ReleasePlan in your tenant namespace
- The ReleasePlan references your Application and describes the release action
- Platform Engineers will create a corresponding ReleasePlanAdmission (RPA) in the managed namespace, which contains the actual release credentials and pipeline details
So to summarize:
- ✅ ReleasePlan: Created by you, goes in TENANT namespace
- 🔒 ReleasePlanAdmission: Created by Platform Engineer, goes in MANAGED namespace
The two resources work together across different namespaces, with the RPA referencing your tenant-namespace ReleasePlan and providing the necessary release pipeline configuration and credentials.
Would you like me to elaborate on how these two resources interact in the release workflow?