kubernetes-service

multiple app nodes how to expose jmx in kubernetes?

由 纵饮孤独 提交于 2019-12-20 08:12:10
问题 In kubernetes I can expose services with service . This is fine. Lets say I have 1 web instance and 10 java server instances. I have a windows gateway I'm used to access those 10 java servers instances via the jconsole installed on it. Obviously I do not expose all apps jmx port via kubernetes service. What are my options here? how should I allow this external to kubernetes cluster windows gateway access to those 10 servers jmx ports? Any practices here? 回答1: Another option is to forward JMX

Cannot connect to a Mongodb pod in Kubernetes (Connection refused)

由 青春壹個敷衍的年華 提交于 2019-12-11 10:46:27
问题 I have a few remote virtual machines, on which I want to deploy some Mongodb instances and then make them accessible remotely, but for some reason I can't seem to make this work. These are the steps I took: I started a Kubernetes pod running Mongodb on a remote virtual machine. Then I exposed it through a Kubernetes NodePort service. Then I tried to connect to the Mongodb instance from my laptop, but it didn't work. Here is the command I used to try to connect: $ mongo host:NodePort (by "host

How to make use of Kubernetes port names?

由 允我心安 提交于 2019-12-08 17:32:05
问题 In a kubernetes deployment I specify a port like so: containers: - name: nginx image: nginx:latest ports: - name: nginx-port containerPort: 80 protocol: TCP Now in a service I can reference that port like so (allows me to only specify the external port in the service): spec: type: ClusterIP ports: - name: nginx-port port: 80 targetPort: nginx-port protocol: TCP Now the question, can I reference service and port elsewhere using the following syntax nginx-service.default.svc.cluster.local:nginx

Requests timing out when accesing a Kubernetes clusterIP service

由 前提是你 提交于 2019-12-06 05:19:38
问题 I am looking for help to troubleshoot this basic scenario that isn't working OK: Three nodes installed with kubeadm on VirtualBox VMs running on a MacBook: sudo kubectl get nodes NAME STATUS ROLES AGE VERSION kubernetes-master Ready master 4h v1.10.2 kubernetes-node1 Ready <none> 4h v1.10.2 kubernetes-node2 Ready <none> 34m v1.10.2 The Virtualbox VMs have 2 adapters: 1) Host-only 2) NAT. The node IP's from the guest computer are: kubernetes-master (192.168.56.3) kubernetes-node1 (192.168.56.4

multiple app nodes how to expose jmx in kubernetes?

由 此生再无相见时 提交于 2019-12-02 16:38:15
In kubernetes I can expose services with service . This is fine. Lets say I have 1 web instance and 10 java server instances. I have a windows gateway I'm used to access those 10 java servers instances via the jconsole installed on it. Obviously I do not expose all apps jmx port via kubernetes service. What are my options here? how should I allow this external to kubernetes cluster windows gateway access to those 10 servers jmx ports? Any practices here? Another option is to forward JMX port from K8 pod to your local PC with kubectl port-forward . I do it like this: 1). Add following JVM

What's the difference between ClusterIP, NodePort and LoadBalancer service types in Kubernetes?

由 走远了吗. 提交于 2019-11-27 10:01:30
1 - I'm reading the documentation and I'm slightly confused with the wording. It says: ClusterIP : Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster. This is the default ServiceType NodePort : Exposes the service on each Node’s IP at a static port (the NodePort). A ClusterIP service, to which the NodePort service will route, is automatically created. You’ll be able to contact the NodePort service, from outside the cluster, by requesting <NodeIP>:<NodePort> . LoadBalancer : Exposes the service externally using a cloud

What&#39;s the difference between ClusterIP, NodePort and LoadBalancer service types in Kubernetes?

由 泪湿孤枕 提交于 2019-11-26 15:01:43
问题 1 - I'm reading the documentation and I'm slightly confused with the wording. It says: ClusterIP : Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster. This is the default ServiceType NodePort : Exposes the service on each Node’s IP at a static port (the NodePort). A ClusterIP service, to which the NodePort service will route, is automatically created. You’ll be able to contact the NodePort service, from outside the
订阅 kubernetes-service