You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting an external S3, this error is recieved:
Error: ConfigMap in version "v1" cannot be handled as a ConfigMap: v1.ConfigMap.Data: ReadString: expects " or n, but found t, error found in #10 byte of ...|"s3.ssl":true},"kind|..., bigger context ...|dpoint":"s3.eu-central-1.wasabisys.com","s3.ssl":true},"kind":"ConfigMap","metadata":{"annotations":|...
The issue is that config-map.yaml reader expect a "true" for s3.ssl: so a logical true (not double quoted fails!. Using '"true"' or '"false"' for this setting works!
Hi,
When setting an external S3, this error is recieved:
Error: ConfigMap in version "v1" cannot be handled as a ConfigMap: v1.ConfigMap.Data: ReadString: expects " or n, but found t, error found in #10 byte of ...|"s3.ssl":true},"kind|..., bigger context ...|dpoint":"s3.eu-central-1.wasabisys.com","s3.ssl":true},"kind":"ConfigMap","metadata":{"annotations":|...
yaml
....
minio:
defaultBuckets: hasura-plus
enabled: false
nameOverride: ''
nodeSelector: {}
podAnnotations: {}
podSecurityContext: {}
replicaCount: 1
resources: {}
securityContext: {}
service:
port: 80
type: ClusterIP
serviceAccount:
annotations: {}
create: true
name: ''
storage:
enabled: true
external:
accessKey: ...
bucket: zpot-co-data
enabled: true
secretKey: ...
ssl: true
endpoint: s3.eu-central-1.wasabisys.com
rules: null
tolerations: []
Great job!
The text was updated successfully, but these errors were encountered: