When installing as described in the readme I experience an error when I try to set an extra Environment variable.

helm upgrade -i --wait -n apicurio apicurio-registry oci://ghcr.io/eshepelyuk/helm/apicurio-registry --version 2.2.0 --set registry.extraEnv[0].name="AUTH_ENABLED" --set registry.extraEnv[0].value="true"

Error: UPGRADE FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
apicurio-registry:

• registry.extraEnv.0.value: Invalid type. Expected: string, given: boolean

Do I do anything wrong or is it a bug that true can't be parsed as string?

Hi, I would like to ask for a nodeselector feature so that I can deploy to a specific node, Is this possible to add as a feature atm ?
Thanks a million!

Currently the generated ingress-manifests is working with kubernetes >= 1.19 only. I added a PR #6 that handles both older and newer versions.

Hi ,

I am trying to deploy the APICURIO registry using kafka bootstrap server on EKS. I am getting error on " time out waiting for node assignment". Please help me with resolution.

Added kafka bootstrap server details on values.yaml like

uncomment and adjust for kafka persistence

kafka:
bootstrapServers: "kafka-kafka-bootstrap.kafka.svc:9093"

Refer log file below.

2021-09-15 06:18:02,572 INFO [org.apa.kaf.com.uti.AppInfoParser] (main) Kafka version: 2.5.0 ││ 2021-09-15 06:18:02,573 INFO [org.apa.kaf.com.uti.AppInfoParser] (main) Kafka commitId: 66563e712b0b9f84 │
│ 2021-09-15 06:18:02,573 INFO [org.apa.kaf.com.uti.AppInfoParser] (main) Kafka startTimeMs: 1631686682571 │
│ 2021-09-15 06:18:17,005 INFO [io.api.reg.sto.RegistryStorageProducer] (executor-thread-1) Using RegistryStore: io.apicurio.registry.storage.impl.kafkasql │
│ 2021-09-15 06:18:32,576 INFO [org.apa.kaf.cli.adm.int.AdminMetadataManager] (kafka-admin-client-thread | adminclient-1) [AdminClient clientId=adminclient │
│ Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. │
│ 2021-09-15 06:19:02,577 INFO [org.apa.kaf.cli.adm.int.AdminMetadataManager] (kafka-admin-client-thread | adminclient-1) [AdminClient clientId=adminclient │
│ Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. │
│ 2021-09-15 06:19:02,578 INFO [org.apa.kaf.cli.adm.int.AdminMetadataManager] (kafka-admin-client-thread | adminclient-1) [AdminClient clientId=adminclient │
│ Caused by: org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has exited. │
│ 2021-09-15 06:19:02,598 WARN [io.api.reg.met.PersistenceExceptionLivenessCheck] (main) Liveness problem suspected in PersistenceExceptionLivenessCheck be │
│ Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. │
│ 2021-09-15 06:19:02,599 INFO [io.api.reg.met.PersistenceExceptionLivenessCheck] (main) After this event, the error counter is 1 (out of the maximum 5 all │
│ 2021-09-15 06:19:02,630 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): org.apache.kafka.common.errors.TimeoutExcep
<https://teams.microsoft.com/l/message/19:[email protected]/1631687084766?tenantId=c337bf2a-9c18-4772-a0be-2d0457489914&groupId=08d00cc9-d611-4e3b-a614-5f02c28318fe&parentMessageId=1631095701885&teamName=SaaS Kicking Engineers&channelName=General&createdTime=1631687084766>

Hello,

we want use a custom image for registry container but it's not possible with this helm chart because the helper.tpl template automatically the apicurio-registry.image

And also, if we want use sealedSecrets for encrypt postgresql password,username and url it's no possible because the container image will be not sql but mem because registry.sql is not set.

the helpers code:

{{- define "apicurio-registry.image" -}}
{{- $sfx := "" -}}
{{- if hasKey . "sql" -}}
{{- $sfx = "sql" -}}
{{- else if hasKey . "kafka" -}}
{{- $sfx = "kafkasql" -}}
{{- else -}}
{{- $sfx = "mem" -}}
{{- end -}}
{{ printf "%s/%s-%s:%s" .image.registry .image.repository $sfx .image.tag }}
{{- end -}}

how to do that ?

Hi,

The chart's test fails due to the lack of a Docker image configured in the e2e.yaml resource manifest.

I thought about using this chart as a dependency in two I maintain. But the failing test prevents me from doing so because there is no way in Helm to disable tests from a single dependency.

Could please you either provide the missing image or drop the test resource if it is just a junk?

It would be nice if the tls-secret wuld be configurable. Currently it is hard-coded to the ingress-host-name.
I can provide a PR that makes it configurable and defaults to the host-name to be backward-compatbible.

@eshepelyuk What do you think ?

Helm chart deployment workes fine with persistency. Now I need to connect Apicurio CLI and API using OIDC ( Curity ) need helm chart configuration for that implementation.