-
Notifications
You must be signed in to change notification settings - Fork 224
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
Rollback failed: serviceaccount not found #455
Comments
There is a chance that rollbacks aren't supported to 2.x of the chart. The service account creation was made the default as part of #387 changes. Contributions are welcome if there's a need to change things. |
Thank you @lhotari for the clarification. Is it written somewhere that it is a breaking change? |
I have updated the release notes at https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0 |
Thank you. Once I've fixed that (I added the service accounts), another issue I found in rolling back is in the bookie logs: In the security context section I have: fsGroupChangePolicy: "OnRootMismatch" |
I don't have good advice to that. The docs contains https://github.com/apache/pulsar-helm-chart?tab=readme-ov-file#upgrading-to-apache-pulsar-2100-and-above-or-helm-chart-version-300-and-above . |
Another related Pulsar issue: apache/pulsar#22051 |
After upgrading the chart from 2.9.4 to 3.2.0, everthing seems to work fine. However, in order to check if a rollback would work, I have tried to rollback from chart 3.2.0 to 2.9.4 and the error I got is:
failed error: pods "pulsar-zookeeper-2" is forbidden: error looking up service account pulsar2/pulsar-zookeeper: serviceaccount "pulsar-zookeeper" not found
I dont understand why it is looking for a service account which in version 2.9.4 should not be present. Indeed from the command 'helm template' with version 2.9.4, there is no reference to this service account. But when I check for the deployed statefulset there it is:
serviceAccountName: pulsar-zookeeper
What is the reason and how can I solve the issue?
The text was updated successfully, but these errors were encountered: