I am encountering an issue whereby Octopus finds multiple viable release plans when creating a release. The Octopus process for the project contains multiple steps which involve upgrading kubernetes helm charts for each package in the release. We are conditionally running two of these steps for certain channels only. We are using version rules for each channel.
When a release is created for one of the packages that we only deploy on a certain channel then it appears that Octopus does not use the version rules to determine the correct channel. Instead it will either go to the default channel (if set) or it will fail.
I’m not sure if this is a problem with how we are using Octopus or if it is an Octopus limitation. Could someone please help? I am happy to provide more details or a log if required.