Refactor KEB after Reconciler removal

[PK85]

Description
This ticket is an outcome of the TASK.

AC

• 1) Remove (or modify) unnecessary steps (listed in the previous comment)
  • 1.1) LM manager does not get any overrides, additional components and Kyma Version.
  • 1.2) make keb-config.yaml global per environment (right now it is per KymaVersion See)
    COnfig for plan is not Kyma version oriented #779
  • 1.3) follow Comment
• 2) Cleanup RuntimeInput, InputBuilderFactory Cleanup RuntimeInput, InputBuilderFactory #786
• 3) Remove unused packages, make sure reconciler dependency is not used
  Remove unused packages #789, Remove reconciler dependency #802
• 4) Remove kcp rc commands from skr-e2e-tests @MarekMichali Remove kcp reconciliations from skr test #782
• 5) Release tp DEV, provide a cluster for all teams to tests
• 6) Release to STAGE, provide a cluster for all teams to tests
• 7) Release to PROD, provide a cluster for all teams to tests

Note

• first remove renconciler steps (use feature flag for every environment) Disable reconciler steps #751, then
• cleanup KEB code Remove overrides and reconciler steps #775

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

[kyma-bot]

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

[kyma-bot]

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[piotrmiskiewicz]

Ideas, how to avoid problems with ArgoCD:

1. Change kind: to kind_ArgoSucks:, then implement a config/reader_for_argo which do a string.replace operation on the input. Example

runtimeConfiguration: |-
    own_cluster:
      kyma-template: |-
        apiVersion: operator.kyma-project.io/v1beta2
        kind_ArgoSucks: Kyma
        metadata:
          labels:
            "operator.kyma-project.io/managed-by": "lifecycle-manager"
        name: tbd
        namespace: kcp-system
      spec:
        channel: fast
        modules: []
      additional-components: []
    default:
      kyma-template: |-
        apiVersion: operator.kyma-project.io/v1beta2
        kind_ArgoSucks: Kyma
        metadata:
          labels:
            "operator.kyma-project.io/managed-by": "lifecycle-manager"
        name: tbd
        namespace: kcp-system
      spec:
        channel: fast
        modules:
          - name: api-gateway
          - name: istio
          - name: btp-operator
      additional-components: []

Disadvantage: Ugly config
2. Configure kind: Kyma outside of the main config:

kymaTemplateKind: Kyma
runtimeConfiguration: |-
    own_cluster:
      kyma-template: |-
        apiVersion: operator.kyma-project.io/v1beta2
        metadata:
          labels:
            "operator.kyma-project.io/managed-by": "lifecycle-manager"
        name: tbd
        namespace: kcp-system
      spec:
        channel: fast
        modules: []
      additional-components: []
    default:
      kyma-template: |-
        apiVersion: operator.kyma-project.io/v1beta2
        metadata:
          labels:
            "operator.kyma-project.io/managed-by": "lifecycle-manager"
        name: tbd
        namespace: kcp-system
      spec:
        channel: fast
        modules:
          - name: api-gateway
          - name: istio
          - name: btp-operator
      additional-components: []