feat(api): deprecate IntegrationPlatform#6575
Merged
squakez merged 1 commit intoapache:mainfrom Apr 22, 2026
Merged
Conversation
oscerd
approved these changes
Apr 19, 2026
This was referenced Apr 19, 2026
Contributor
|
|
squakez
force-pushed
the
feat/deprecate_itp
branch
2 times, most recently
from
ac44348 to
db3b2f9
Compare
Contributor
|
|
gansheer
approved these changes
Apr 21, 2026
This is a prerequisite for next gen architecture of Camel K, where we aim to simplify the API. From now on, the configuration which was previously part of the IntegrationPlatform custom resource, has to be configured as environment variable on the operator. Ref apache#6454
squakez
force-pushed
the
feat/deprecate_itp
branch
from
db3b2f9 to
5c1428a
Compare
Contributor
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a prerequisite for next gen architecture of Camel K, where we aim to simplify the API. From now on, the configuration which was previously part of the IntegrationPlatform custom resource, has to be configured as environment variable on the operator.
Ref #6454
Missing work: