Add Channel field to Manifest.Spec instead of the Channel label

[nesmabadr]

Description

In the Manifest, we have the channel defined as a label operator.kyma-project.io/channel. We need to stop depending on this label and introduce a Channel field in the Manifest.Spec instead.

Reasons

No response

Acceptance Criteria

• Introduce an optional Channel field to the v1beta2.Manifest spec
• Prioritize using the spec field over the label
• Remove adding the channel label from the manifest
• Create an issue to have the Channel field mandatory in the next API version.
• Make sure backwards compatibility is handled and tested.

Feature Testing

No response

Testing approach

No response

Attachments

No response

[nesmabadr]

Blocked by #1456 . Currently we don't reference the channel label anywhere except in the test utils, so when we introduce the change to avoid ssa unless there is a change in version or channel, we can process with this issue.

[c-pius]

In #1681 it has been decided that ModuleTemplates will be tied to versions. An assignment of modules to channels will happen via a separate CR, but eventually, we will always install a version of a module. Version is already part of the manifest. We need to evaluate if we even need channel info as part of the Manifest at all, or if we can completely rely on the version.

Blocked by #1456 . Currently we don't reference the channel label anywhere except in the test utils, so when we introduce the change to avoid ssa unless there is a change in version or channel, we can process with this issue.

Also seen that we only us this label in a test. Are we even relying on it somewhere?

[c-pius]

Closing for the reasons mentioned above. Deprecation of the label should be handled in: #1839