Repository navigation
Conversation
|
@squakez please inform me if any changes are required |
|
Please, rebase, there is a conflict. Also, don't worry about the |
21fa6b7 to
b60ebc8
Compare
|
@squakez hey pushed the changes the main reason for the recent failure stems from the fact that tests are using still camel k |
b60ebc8 to
a347a55
Compare
|
@squakez did it, pleaase have a look, than you! |
a347a55 to
3b5f84b
Compare
|
@squakez rebased it, use agent on this one to fix the ci errors |
squakez
left a comment
There was a problem hiding this comment.
If we merge this we must create a follow up issue in order to remind to revert the upgrade test change when moving to the next minor version
|
|
3b5f84b to
969c4fe
Compare
|
@squakez please have a look, the arkmq one now references camel-k correctly |
|
Ouch. We have the same namespace problem for network policy workflow now. Please, fix and it should be complete to be merged afterwards. |
969c4fe to
3bdd6d2
Compare
|
@squakez done, please have a look! |
Fixes #6652
Standardize the default namespace for global (cluster-scoped/descoped) Camel K operator installations to
camelinstead ofcamel-k. This aligns with the namespace convention adopted across the Camel ecosystem, such as in camel-tooling/camel-monitor-operator#195, so all Camel-based operators deploy into the same default namespace.Summary of Changes
install/overlays/all-namespaces/kustomization.yamlto usecamelas the default namespace.DEFAULT_NSand theinstall-k8s-globaltarget to default tocamel.e2e/support/test_support.goto copy dev registry configurations and dump the operator namespace fromcamel.e2e/upgrade/upgrade_test.goto install the previous released operator version intocamelby wrapping the remote overlay in a local Kustomization specifying the operator namespace.camelnamespace.camel.Antigravity on behalf of Keerthan