Back to Charts

⚠️ Repo Archive Notice

stable/schema-registry-ui/README.md

latest4.5 KB
Original Source

⚠️ Repo Archive Notice

As of Nov 13, 2020, charts in this repo will no longer be updated. For more information, see the Helm Charts Deprecation and Archive Notice, and Update.

Schema-Registry-UI Helm Chart

This helm chart creates a Schema-Registry-UI server.

This is a web tool for the confluentinc/schema-registry in order to create / view / search / evolve / view history & configure Avro schemas of your Kafka cluster.

DEPRECATION NOTICE

This chart is deprecated and no longer supported.

Prerequisites

  • Kubernetes 1.8
  • A running Kafka Installation
  • A running Zookeeper Installation
  • A running Schema-Registry installation

Chart Components

This chart will do the following:

  • Create a Schema-Registry-UI deployment
  • Create a Service configured to connect to the available Schema-Registry-UI pods on the configured client port.

Installing the Chart

You can install the chart with the release name srui as below.

console
$ helm install --name srui schema-registry-ui

If you do not specify a name, helm will select a name for you.

console{%raw}
$ kubectl get all -l app=schema-registry-ui
NAME                          DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/srui-schema-registry-ui   1         1         1            1           23m

NAME                                DESIRED   CURRENT   READY     AGE
rs/srui-schema-registry-ui-bcb4c994c   1         1         1         23m

NAME                                      READY     STATUS    RESTARTS   AGE
po/srui-schema-registry-ui-bcb4c994c-qjqbj   1/1       Running   1          23m
  1. deploy/srui-schema-registry-ui is the Deployment created by this chart.
  2. rs/srui-schema-registry-ui-bcb4c994c is the ReplicaSet created by this Chart's Deployment.
  3. po/srui-schema-registry-ui-bcb4c994c-qjqbj is the Pod created by the ReplicaSet under this Chart's Deployment.

Configuration

You can specify each parameter using the --set key=value[,key=value] argument to helm install.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

console
$ helm install --name my-release -f values.yaml schema-registry-ui

Tip: You can use the default values.yaml

Parameters

The following table lists the configurable parameters of the SchemaRegistryUI chart and their default values.

ParameterDescriptionDefault
replicaCountThe number of SchemaRegistryUI Pods in the Deployment1
image.repositoryThe SchemaRegistryUI image repositorylandoop/schema-registry-ui
image.tagThe SchemaRegistryUI image tag0.9.5
image.imagePullPolicyImage Pull PolicyIfNotPresent
schemaRegistry.urlURL to the schema registry endpointhttp://localhost
schemaRegistry.portPort for the schema registry8081
schemaRegistry.proxyWhether to proxy Schema Registry endpoint via the internal webserverfalse
schemaRegistry.allowGlobalSupport for global compatibility level configuration support —i.e change the default compatibility level of your schema registryfalse
schemaRegistry.allowTransitiveSupport for transitive compatibility levels (Schema Registry version 3.1.1 or better)false
schemaRegistry.allowDeletionSupport for Schema deletion (Schema Registry version 3.3.0 or better)false
schemaRegistry.readOnlyModeSupport for readonly mode (overwrites settings for global compatibility configuration and schema deletion)false
service.typeType of the serviceLoadBalancer
service.portPort to use80
service.annotationsKubernetes service annotations{}
service.loadBalancerSourceRangesLimit load balancer source IPs to list of CIDRs (where available))None
ingress.enabledIngress rules. Disabled by defaultfalse
ingress.annotationsIngress annotations{}
ingress.pathIngress path/
ingress.hostsIngress accepted hostnames[schema-registry-ui.local]
ingress.tlsIngress TLS configuration/
nodeSelectorNode labels for pod assignment{}
tolerationsList of node taints to tolerate[]
affinityNode/pod affinities{}
resourcesCPU/Memory resource requests/limits{}