apache / apache/camel-k

Default IntegrationProfile

Open
#6,776 0 comments 0 reactions 0 assignees View on GitHub
kind/feature
Dominant language
Go
Stars
927
Forks
387
Avg merge
15h 5m
Merged PRs (30d)
36

Description

### Requirement

We should consider that any Integration can use, by default, an IntegrationProfile named "default" if it exists in its same namespace or the same namespace annotated with the default to use. In this way we can let the admin to provide a specific default profile in each namespace and avoid to request the user to annotate the integrations explicitly.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how Integrations currently resolve their IntegrationProfile and how namespace annotations are read. Check the existing Integration and IntegrationProfile behavior before deciding how same-namespace and annotated namespace defaults should be prioritized. Done means an Integration can use the appropriate default profile without an explicit annotation, with behavior covered for both namespace cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.