Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Taylorzhao opened this issue May 28, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter

Comments

@Taylorzhao
Copy link

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 Taylorzhao added the kind/bug Categorizes issue or PR as related to a bug. label May 28, 2024
@Cali0707
Copy link
Member

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
Copy link
Member

/triage needs-user-input

@knative-prow knative-prow bot added the triage/needs-user-input Issues which are waiting on a response from the reporter label May 28, 2024
@Taylorzhao
Copy link
Author

Taylorzhao commented May 29, 2024

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

Copy link

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants