eventing icon indicating copy to clipboard operation
eventing copied to clipboard

Upgrade from version 1.12.3 to the latest version 1.14 encountered an issue

Open Taylorzhao opened this issue 1 year ago • 4 comments

Describe the bug A clear and concise description of what the bug is. Upgrade from version 1.12.3 to the latest version 1.14 encountered an issue. Following the documentation to execute the kubectl method for upgrading, the error shown in the image appeared. image

Expected behavior A clear and concise description of what you expected to happen.

To Reproduce Steps to reproduce the behavior.

Knative release version 1.12.3

Additional context Add any other context about the problem here such as proposed priority

Taylorzhao avatar May 28 '24 07:05 Taylorzhao

Hi @Taylorzhao we don't support upgrades in this way. We only support upgrading one version at a time (so 1.12 -> 1.13 -> 1.14)

That being said, it looks like you are missing a CRD in your cluster for the inmemorychannels. Do you see the inmemorychannel CRD when you run kubectl get crds ?

Cali0707 avatar May 28 '24 17:05 Cali0707

/triage needs-user-input

Cali0707 avatar May 28 '24 17:05 Cali0707

Hi @Taylorzhao we don't support upgrades in this way. We only support upgrading one version at a time (so 1.12 -> 1.13 -> 1.14)

That being said, it looks like you are missing a CRD in your cluster for the inmemorychannels. Do you see the inmemorychannel CRD when you run kubectl get crds ?

Hi @Cali0707 , I followed your advice and upgraded from 1.12.3 to 1.13. During this process, I installed the crd according to the documentation. However, a new problem occurred, as shown in the figure, the image pull failed. The reason is that the pull permission is denied. In actual use, we do not use this innermemorychannel, but use kafka-channel instead. I hope this upgrade problem can be optimized. image image image

Taylorzhao avatar May 29 '24 08:05 Taylorzhao

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

github-actions[bot] avatar Aug 28 '24 01:08 github-actions[bot]