Schema Registry on Kubernetes, publicly accesible












0















I have a three nodes kubernetes cluster on Azure, with three Kafka brokers and one zookeeper instance. Kafka brokers and zookeeper are publicly accessible by deploying their correspondent services (Load Balancer).



Now I'm deploying a schema registry, and I would like it to be accessible from outside the kubernetes cluster.
I'm following the same steps than before, but not able to access the schema registry api from outside the kubernetes cluster.
If I curl the schema registry from within the docker container, everything works fine, so I assume the schema registry is properly running.
Here are my schema registry yamls descriptors:



Schema Registry deployment:



apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: schema-registry
spec:
replicas: 1
template:
metadata:
labels:
name: schema-registry
spec:
containers:
- env:
- name: SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL
value: zookeeper-cluster-ip:2181
- name: SCHEMA_REGISTRY_HOST_NAME
value: registry-0.schema.default.svc.cluster.local
- name: SCHEMA_REGISTRY_LISTENERS
value: http://0.0.0.0:8081
name: schema-registry
image: confluentinc/cp-schema-registry:5.0.1
ports:
- containerPort: 8081
restartPolicy: Always


Schema Registry Service:



apiVersion: v1
kind: Service
metadata:
name: schema-registry
labels:
name: schema-registry
spec:
ports:
- port: 8081
selector:
name: schema-registry
type: LoadBalancer


After the service is deployed, the public ip is generated:



kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
schema-registry LoadBalancer X.X.X.X. X.X.X.X. 8081:30921/TCP 13m


, so I run



curl -X GET -i -H "Content-Type: application/vnd.schemaregistry.v1+json" http://X.X.X.X:8081/subjects


But no response.
From within the container, I'm getting a response from the curl command.



The reason why I want the schema registry to be accessible from outside the cluster is that we want to access it from a Nifi cluster.



Is that possible?










share|improve this question

























  • I wonder if using the Confluent Helm Charts would produce a different result

    – cricket_007
    Nov 27 '18 at 18:36
















0















I have a three nodes kubernetes cluster on Azure, with three Kafka brokers and one zookeeper instance. Kafka brokers and zookeeper are publicly accessible by deploying their correspondent services (Load Balancer).



Now I'm deploying a schema registry, and I would like it to be accessible from outside the kubernetes cluster.
I'm following the same steps than before, but not able to access the schema registry api from outside the kubernetes cluster.
If I curl the schema registry from within the docker container, everything works fine, so I assume the schema registry is properly running.
Here are my schema registry yamls descriptors:



Schema Registry deployment:



apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: schema-registry
spec:
replicas: 1
template:
metadata:
labels:
name: schema-registry
spec:
containers:
- env:
- name: SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL
value: zookeeper-cluster-ip:2181
- name: SCHEMA_REGISTRY_HOST_NAME
value: registry-0.schema.default.svc.cluster.local
- name: SCHEMA_REGISTRY_LISTENERS
value: http://0.0.0.0:8081
name: schema-registry
image: confluentinc/cp-schema-registry:5.0.1
ports:
- containerPort: 8081
restartPolicy: Always


Schema Registry Service:



apiVersion: v1
kind: Service
metadata:
name: schema-registry
labels:
name: schema-registry
spec:
ports:
- port: 8081
selector:
name: schema-registry
type: LoadBalancer


After the service is deployed, the public ip is generated:



kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
schema-registry LoadBalancer X.X.X.X. X.X.X.X. 8081:30921/TCP 13m


, so I run



curl -X GET -i -H "Content-Type: application/vnd.schemaregistry.v1+json" http://X.X.X.X:8081/subjects


But no response.
From within the container, I'm getting a response from the curl command.



The reason why I want the schema registry to be accessible from outside the cluster is that we want to access it from a Nifi cluster.



Is that possible?










share|improve this question

























  • I wonder if using the Confluent Helm Charts would produce a different result

    – cricket_007
    Nov 27 '18 at 18:36














0












0








0








I have a three nodes kubernetes cluster on Azure, with three Kafka brokers and one zookeeper instance. Kafka brokers and zookeeper are publicly accessible by deploying their correspondent services (Load Balancer).



Now I'm deploying a schema registry, and I would like it to be accessible from outside the kubernetes cluster.
I'm following the same steps than before, but not able to access the schema registry api from outside the kubernetes cluster.
If I curl the schema registry from within the docker container, everything works fine, so I assume the schema registry is properly running.
Here are my schema registry yamls descriptors:



Schema Registry deployment:



apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: schema-registry
spec:
replicas: 1
template:
metadata:
labels:
name: schema-registry
spec:
containers:
- env:
- name: SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL
value: zookeeper-cluster-ip:2181
- name: SCHEMA_REGISTRY_HOST_NAME
value: registry-0.schema.default.svc.cluster.local
- name: SCHEMA_REGISTRY_LISTENERS
value: http://0.0.0.0:8081
name: schema-registry
image: confluentinc/cp-schema-registry:5.0.1
ports:
- containerPort: 8081
restartPolicy: Always


Schema Registry Service:



apiVersion: v1
kind: Service
metadata:
name: schema-registry
labels:
name: schema-registry
spec:
ports:
- port: 8081
selector:
name: schema-registry
type: LoadBalancer


After the service is deployed, the public ip is generated:



kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
schema-registry LoadBalancer X.X.X.X. X.X.X.X. 8081:30921/TCP 13m


, so I run



curl -X GET -i -H "Content-Type: application/vnd.schemaregistry.v1+json" http://X.X.X.X:8081/subjects


But no response.
From within the container, I'm getting a response from the curl command.



The reason why I want the schema registry to be accessible from outside the cluster is that we want to access it from a Nifi cluster.



Is that possible?










share|improve this question
















I have a three nodes kubernetes cluster on Azure, with three Kafka brokers and one zookeeper instance. Kafka brokers and zookeeper are publicly accessible by deploying their correspondent services (Load Balancer).



Now I'm deploying a schema registry, and I would like it to be accessible from outside the kubernetes cluster.
I'm following the same steps than before, but not able to access the schema registry api from outside the kubernetes cluster.
If I curl the schema registry from within the docker container, everything works fine, so I assume the schema registry is properly running.
Here are my schema registry yamls descriptors:



Schema Registry deployment:



apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: schema-registry
spec:
replicas: 1
template:
metadata:
labels:
name: schema-registry
spec:
containers:
- env:
- name: SCHEMA_REGISTRY_KAFKASTORE_CONNECTION_URL
value: zookeeper-cluster-ip:2181
- name: SCHEMA_REGISTRY_HOST_NAME
value: registry-0.schema.default.svc.cluster.local
- name: SCHEMA_REGISTRY_LISTENERS
value: http://0.0.0.0:8081
name: schema-registry
image: confluentinc/cp-schema-registry:5.0.1
ports:
- containerPort: 8081
restartPolicy: Always


Schema Registry Service:



apiVersion: v1
kind: Service
metadata:
name: schema-registry
labels:
name: schema-registry
spec:
ports:
- port: 8081
selector:
name: schema-registry
type: LoadBalancer


After the service is deployed, the public ip is generated:



kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
schema-registry LoadBalancer X.X.X.X. X.X.X.X. 8081:30921/TCP 13m


, so I run



curl -X GET -i -H "Content-Type: application/vnd.schemaregistry.v1+json" http://X.X.X.X:8081/subjects


But no response.
From within the container, I'm getting a response from the curl command.



The reason why I want the schema registry to be accessible from outside the cluster is that we want to access it from a Nifi cluster.



Is that possible?







kubernetes apache-kafka confluent-schema-registry






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 27 '18 at 13:22









lloiacono

2,08822028




2,08822028










asked Nov 27 '18 at 9:09









joselejosele

176




176













  • I wonder if using the Confluent Helm Charts would produce a different result

    – cricket_007
    Nov 27 '18 at 18:36



















  • I wonder if using the Confluent Helm Charts would produce a different result

    – cricket_007
    Nov 27 '18 at 18:36

















I wonder if using the Confluent Helm Charts would produce a different result

– cricket_007
Nov 27 '18 at 18:36





I wonder if using the Confluent Helm Charts would produce a different result

– cricket_007
Nov 27 '18 at 18:36












1 Answer
1






active

oldest

votes


















0














A simple problem with a firewall rule was the cause of the problem.
Service and deployment config was ok.
Thanks anyway!






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496116%2fschema-registry-on-kubernetes-publicly-accesible%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    A simple problem with a firewall rule was the cause of the problem.
    Service and deployment config was ok.
    Thanks anyway!






    share|improve this answer




























      0














      A simple problem with a firewall rule was the cause of the problem.
      Service and deployment config was ok.
      Thanks anyway!






      share|improve this answer


























        0












        0








        0







        A simple problem with a firewall rule was the cause of the problem.
        Service and deployment config was ok.
        Thanks anyway!






        share|improve this answer













        A simple problem with a firewall rule was the cause of the problem.
        Service and deployment config was ok.
        Thanks anyway!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 '18 at 11:38









        joselejosele

        176




        176
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496116%2fschema-registry-on-kubernetes-publicly-accesible%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)