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.

Sign up for GitHub

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

Jump to bottom

Helm: add Troubleshoot section to kubernetes 1.25 migration guide #5483

Merged
merged 3 commits into from
Jul 12, 2023
Merged

Helm: add Troubleshoot section to kubernetes 1.25 migration guide #5483

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e72395d
Helm: add Troubleshoot section to kubernetes 1.25 migration guide
krajorama Jul 12, 2023
4595553
Apply suggestions from code review
krajorama Jul 12, 2023
e28517d
Small typo and lint fix.
krajorama Jul 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions ...charts/mimir-distributed/migration-guides/migrate-to-kubernetes-version-1.25.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,17 @@ Grafana Mimir does not require any special permissions on the hosts that it
runs on. Because of this, you can deploy it in environments that enforce the
Kubernetes [Restricted security policy](https://kubernetes.io/docs/concepts/security/pod-security-standards/).
{{% /admonition %}}

## Troubleshoot

If you have upgraded to Kubernetes 1.25 and see the following error containing PodSecurityPolicy during a Helm release upgrade:

```
resource mapping not found for name: "mimir" namespace: "" from "":
no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first
```

krajorama marked this conversation as resolved.
Show resolved Hide resolved
1. Optionally follow the Kubernetes [Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller](https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/) guide to replace PodSecurityPolicy.
1. Set the `rbac.create` value to `false`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That shouldn't be necessary because the chart already doesn't render it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this way you can reuse this doc on older chart versions!

1. Remove PodSecurityPolicy from the Helm release history following the [Updating API Versions of a Release Manifest](https://helm.sh/docs/topics/kubernetes_apis/#updating-api-versions-of-a-release-manifest) Helm documentation in order to proceed with the upgrade.
1. Upgrade the deployment. The chart will not install PodSecurityPolicy objects anymore.
krajorama marked this conversation as resolved.
Show resolved Hide resolved
Loading