Vincent

Thx, only one thing to clarify: For example, if there are two validators in the config.yaml, with both of them having no config or app defined. We assign 0.0.0.0:26657 to...

Since #744 was closed, close this feature as well. Orchestration of the upgrade is implemented in the kn-plugin-operator.

@rscottwatson This issue is a duplicate of https://github.com/knative/operator/issues/1131. In 1.6, we removed the v1alpha1 CRDs. You should migrate all existing CRs and CRDs into v1beta1 in 1.5 by running the...

Per the discussion in the slack channel: https://knative.slack.com/archives/CEPGNPHP1/p1659142102677399. I am now thinking of merging the migration tasks into the part of the operator's reconciling job, so that the migration can...

Whether this is a valuable feature? Yes with no doubts. Where and how can we implement it? I have been debating with myself for years literally regarding this issue. Just...

This feature is implemented in the operator's CLI plugin by https://github.com/knative-sandbox/kn-plugin-operator/pull/207. We will be able to accomplish the upgrade across multiple minor versions with one line command.

The operator's CLI plugin has implemented this feature. PLZ download further version of https://github.com/knative-sandbox/kn-plugin-operator to use the feature as of 1.7.

This is a little far away. If you are still on 1.1, you need to upgrade to 1.2, then to 1.3... until 1.6, which is the latest. For operator, you...

Per the discussion in the slack channel: https://knative.slack.com/archives/CEPGNPHP1/p1659142102677399. I am now thinking of merging the migration tasks into the part of the operator's reconciling job, so that the migration can...

@unzld You can install operator 1.5 over 1.3 for sure. however, you have to incrementally upgrade serving and eventing from 1.3 to 1.4 and to 1.5.