Update Helm chart for Crossplane 2.1.3#36
Conversation
nekr0z
left a comment
There was a problem hiding this comment.
Thank you for your effort.
Please consider that this chart is published in the Yandex Cloud Marketplace, and that there are numerous existing installations that your changes should not break. I've highlighted the main points (but there obviously are others).
Please keep your changes minimal, and don't introduce "cosmetic" changes that potentially break the upgrade process.
| credentials: {{ .Values.provider.config.creds | default "" | b64enc }} | ||
| --- | ||
| apiVersion: yandex-cloud.jet.crossplane.io/v1alpha1 | ||
| apiVersion: yandex-cloud.m.jet.crossplane.io/v1beta1 |
There was a problem hiding this comment.
This will likely break things for people upgrading from previous versions.
| repository: ${REGISTRY}/${IMAGE_PATH}/crossplane | ||
| # -- The Crossplane image tag. Defaults to the value of `appVersion` in `Chart.yaml`. | ||
| tag: 1.20.1 | ||
| tag: "" |
There was a problem hiding this comment.
What exactly is the reason for this?
| # -- A list of Provider packages to install. | ||
| packages: [] | ||
| packages: | ||
| - xpkg.upbound.io/yandexcloud/crossplane-provider-yc:v0.14.0 # with this dont need template for provider |
There was a problem hiding this comment.
This will fail on any Kubernetes cluster that has no network connection to xpkg.upbound.io, which is unacceptable.
| # Endpoint to yandex cloud api | ||
| endpoint: ${YC_API_ENDPOINT} | ||
| # Cloud ID your cloud in YC | ||
| cloudId: "" |
I took a fresh chart from the crossplane-stable/crossplane repository and adapted it here. I checked the installation with a fresh ArgoCD (Helm chart version: 7.3.11-2) for YC and it works without errors. The Issue error has been fixed #35
The error in the provider's profile also disappeared: {"level":"info","ts":"2025-12-10T21:06:32Z","logger":"crossplane-provider-yc","msg":"Provider has missing RBAC permissions for monitoring CRDs, controller SafeStart capability will be disabled"}The installation and configuration of the provider has been moved to a more logical location in values:
provider.packageandprovider.configThis PR requires a release update