-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/postgresql] Error upgrading: can't evaluate field pullSecrets in type interface {} #8692
Comments
In my case, I don't have |
I was able to workaround this issue by adding |
Someone is changing this chart drastically. In fact V2.0 is bitnami version which is somewhat differente with previous one, starting with the image, and not placing the metrics as sidecar. #8691 so @carrodher is this chart going to bitnami version?? |
Yes, on this issue #7956 and Chart Office Hour meeting, we discussed the differences between the previous stable chart and the Bitnami one. After taking a look at the status of the previous one and the lack of maintenance and owners, the community decided to start working on migration towards a new model. After some weeks working on #8004, today the new version was merged. As it is an important change, the major version was bumped, so currently, the chart is using the At this moment it is documented how to upgrade the chart itself https://github.com/helm/charts/blob/master/stable/postgresql/README.md#upgrade For example, dependencies:
- name: postgresql
version: 0.8.3
repository: https://kubernetes-charts.storage.googleapis.com/
condition: postgresql.enabled
- name: mysql
version: 0.6.0
repository: https://kubernetes-charts.storage.googleapis.com/
condition: mysql.enabled |
@carrodher I don't think the problem that I've reported is because of the changes from the older version. I did had to rename some values from |
I am running this command,
and then getting this error
But before the chart update 3 days ago everything was working fine |
Hi @luisdavim, after some investigations I found that the previous chart was using: ## postgres image repository
image: "postgres"
## postgres image version
## ref: https://hub.docker.com/r/library/postgres/tags/
##
imageTag: "9.6.2"
## Specify a imagePullPolicy
## 'Always' if imageTag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
# imagePullPolicy:
## Specify imagePullSecrets
## ref: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
##
# imagePullSecrets: myregistrykey while the new one: ## Bitnami PostgreSQL image version
## ref: https://hub.docker.com/r/bitnami/postgresql/tags/
##
image:
registry: docker.io
repository: bitnami/postgresql
tag: 10.5.0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
pullPolicy: Always
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
##
# pullSecrets:
# - myRegistrKeySecretName Previously, Using Does it make sense to you? |
Hi @okandas, since there is a new major version, some options can be different, and in this case, there are. In your case I tried doing the following changes: - --set service.type=NodePort,service.nodePort=30543,image=timescale/timescaledb,imageTag=latest-pg10,postgresPassword=rueray,image.pullSecrets=null
+ --set service.type=NodePort,service.nodePort=30543,image.repository=timescale/timescaledb,image.tag=latest-pg10,postgresqlPassword=rueray please note some name changes and Using above configuration, pod is created, but the status is
Postgresql image is non-root image, there are a ton of advantages related to the use of non-root containers, but also there are some disadvantages, one of them is that some utilities (eg. Git) or servers (eg. PostgreSQL) run additional checks to find the user in the Tl;DR $ helm install --name timescaledb \
--set service.type=NodePort,service.nodePort=30543,image.repository=timescale/timescaledb,image.tag=latest-pg10,postgresqlPassword=rueray,securityContext.enabled=false \
stable/postgresql |
@carrodher thank you. your configs worked |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
Version of Helm and Kubernetes:
Which chart:
stable/postgresql
version2.1.0
What happened:
I have a chart that requires the PostgreSQL chart and when running
helm upgrade
on my chart I get the following error from the postgresql chart:Also, I'm not making any changes that would affect the posrgresql chart, all that I'm doing is modifying a docker image tag for a deployment from my own chart.
What you expected to happen:
The upgrade to be done without errors.
How to reproduce it (as minimally and precisely as possible):
I think that if you create any simple helm chart, make it require the postgres chart, deploy it and then try to upgrade it you should be able to reproduce the issue.
The text was updated successfully, but these errors were encountered: