Avoids the schema-registry service name, becuase it interferes ...

with container configuration, as  Kubernetes creates the env SCHEMA_REGISTRY_PORT
if the service has been created first.

Author: solsson

61schema-registry-service.yml renamed to 60schemas-service.yml

@@ -1,7 +1,7 @@
 apiVersion: v1
 kind: Service
 metadata:
-  name: schema-registry
+  name: schemas
   namespace: kafka
 spec:
   ports:

60schema-registry.yml renamed to 61schemas.yml

@@ -1,7 +1,7 @@
 apiVersion: apps/v1beta1
 kind: Deployment
 metadata:
-  name: schema-registry
+  name: schemas
   namespace: kafka
 spec:
   replicas: 1
@@ -11,12 +11,12 @@ spec:
         app: schema-registry
     spec:
       containers:
-      - name: schema-registry
+      - name: cp-schema-registry
         image: confluentinc/cp-schema-registry@sha256:ac1eb34d9a60ce8904eb1bc01fd94bf1f6513924ca507734679d4b513133714c
         env:
         - name: SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL
           value: zookeeper:2181
         - name: SCHEMA_REGISTRY_HOST_NAME
-          value: schema-registry
+          value: schemas
         ports:
         - containerPort: 8081