Spring Boot – How do I establish communication between pods in Kubernetes?

I have a problem communicating between Service Type: NodePort and Service Type: ClusterIp in Kubernetes.
The error is 404 not found
I also checked that the name of the service matches the endpoint name and they are both deployed in the same cluster and namespace, but for some reason it can not.
I'm trying to set up a ServiceIp-based architecture that communicates with different backend microservices.
Help is urgent and thank you.

ServiceIp:

apiVersion: v1
Type: Service
metadata:
name: gatewaykubernetes
labels:
app: gatewaycubernetes
Specification:
Type: NodePort
Voter:
app: gatewaycubernetes
ports:
– Name: http
Port: 8888
nodePort: 32200
targetPort: http

Service type ClusterIp:

apiVersion: v1
Type: Service
metadata:
Name: registro
labels:
App: registro
Specification:
Voter:
App: registro
ports:
– Name: http
Harbor: 9082

Kubectl gets the svc namespace

GatewayCubernetes 10.103.255.36 8888: 32200 / TCP 31m

registro 10.101.53.120 9082 / TCP 44d

ConsultingGeneral 10.111.199.16 9080 / TCP 44d

My idea is that you have access to the registration and general consulting services through GatewayCubernet

I use: spring-cloud-cubs-dependencies, spring-cloud-cubs-discovery, spring-cloud-starter-gateway, spring-boot-starter-webflux, spring-cloud-starter-cube-networks, spring-cloud-starter-gateway, spring- Cloud Kubernetes Config, Spring Boot Starter Actuator

debian – Subversion error: svn: E120171: Error executing context: An error occurred during SSL communication

I get this error when checking out.

svn: E170013: Unable to connect to a repository at URL 'https://some.host/some/repo/'
svn: E120171: Error running context: An error occurred during SSL communication

$ svn –version

svn, version 1.10.4 (r1850624)
   compiled Jul 28 2019, 02:44:06 on x86_64-pc-linux-gnu

Copyright (C) 2019 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.9 (compiled with 1.3.9)
  - handles 'http' scheme
  - handles 'https' scheme

The following authentication credential caches are available:

* Plaintext cache in /home/kusan/.subversion
* Gnome Keyring
* GPG-Agent
* KWallet (KDE)

Please help me to solve this problem. I'm on a clean install of Debian 10. It worked well in Debian 9. Thank you in advance.

java – microservice decomposition and inter-service communication

Enter image description here

I read theory, but need practical architectural advice on the actual implementation in Java for microservices. In the context of the enclosed screenshot. Here is my setup.

Contract project consisting of the following 4 modules.

  1. Order History (Jar File, Docker Container)
  2. Ordering (Jar file, Docker container)
  3. Order Tracking (Jar File, Docker Container)
  4. Order dispute (Jar file, Docker container)
  5. Service (WAR file, Docker container)

Service (5) sits on the front page (order.example.com), receives an HTTP request, then calls 1 or 2 or 3 or 4 (depending on the URI) via gRPC and returns the result to the client.

Q1. Is 1, 2, 3, 4 considered as a microservice or is OrderManagement or ShoppingCart a microservice?

Q2. The shopping cart has the same setup as the order (stands behind cart.example.com). Communication between order and shopping cart via Like Messaging (Kafka)?

Is that correct? I hope I do not have a nano-anti-pattern here?

WiFi detection and communication between routers

I work in an environment consisting of 4 OpenWrt routers, which each serve and contain several clients via WLAN. Each of them offers Internet access to customers.

I have 3 questions about this scenario and would be happy if any of you could answer one of these questions (you can only answer one question and I'll still be very grateful):

1) Which command or package can I use in a router (via ssh or another mechanism) to determine the IP address and hostname of the other routers? Would avahi help me or would I have to know the IP of the other router before?
What if I add a new router to this environment, do I have to manually configure each router to discover the new one?

2) Given that I collect latency and packet loss measurements in each router when clients can no longer access Internet services, how can I tell if every router / network is overloaded or if I just do not have Internet access (ISP? In both cases, the ping command would most likely not work and the packages would also be discarded.

3) Taking into account the fact that the routers are connected via a high-speed wireless connection, which protocol or software should be used so that they can communicate with each other, e.g. Eg by pinging (assuming they already know each other – question 1)?

Note: These questions are not specific to OpenWrt routers.

Communication design from class to class

I'm working on a project with a class structure like this:

class A {
  constructor() {
    this.bInstances = this.makeBInstances();
  }

  makeBInstances() {
    // return new B()s
  }
}

// So on with class B and C.

I try to find out how best to communicate with each other. Sharing class instances is not ideal because it makes testing difficult and unreliable. Singletons are also vague and unreliable. They make sure that I do not need to pass instances, but I also need to import and use the instance so my problem is not completely resolved. Reinitializing singletons for each test is also tedious.

The best solution that I have thought of before is sending and listening to events. Like this:

class B {
  constructor() {
    this.listenForAEvents();
  }

  listenForAEvents() {
    document.addEventListener('event_from_class_A', () => {
      // react to A class' signal
      this.doSomething();
    });
  }

  doSomething() {
    // do something
    // create CustomEvent and emit it
    // handle that Event from another class
  }
}

I like that because it makes testing very easy and decouples classes from dependencies. As long as I emit an event that contains the right data, it does not matter which instances I have.

My question is: is this the right way? Are there any other alternatives?

[DICHVUSOCKS.US] 12h05 UPDATE 24 / 24- Good socks

Payment Immediately perfect money, Bitcoin, wmtransfer, dash, ETH (Please click on buy socks)
Update Tools Client Dichvusocks.us http://dichvusocks.us/tools.php Link Check Socks http://check.dichvusocks.us/
LIVE | 104.238.97.230:31800 | 0.75 | Arizona | 85260 | ip-104-238-97-230.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 12.246.170.142:8963 | 0.34 | Indiana | 46356 | c-73-8-54-97.hsd1.in.comcast.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 198.12.157.77:53681 | 1.61 | Arizona | 85260 | GoDaddy.com, LLC | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.216.124:57139 | 0.24 | Arizona | 85260 | ip-192-169-216-124.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.140.74:54972 | 4,64 | Arizona | 85260 | ip-192-169-140-74.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 132.148.3.216:12841 | 0.26 | Arizona | 85260 | ip-166-62-80-198.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.215.114:31518 | 0.26 | Arizona | 85260 | ip-192-169-215-114.ip.secureserver.net | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 192.169.156.211:1220 | 0.26 | Arizona | 85260 | ip-192-169-156-211.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 104.238.97.215:19395 | 0.26 | Arizona | 85260 | ip-104-238-97-215.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 104.238.97.230:18665 | 0.26 | Arizona | 85260 | ip-104-238-97-230.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.90.50.71:22358 | 1,93 | California | 92821 | millcity.dreamhost.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 166.62.85.232:9306 | 0.26 | Arizona | 85260 | ip-166-62-85-232.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.243.124:40553 | 2,33 | Arizona | 85260 | ip-192-169-243-124.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.202.104:26673 | 0.91 | Arizona | 85260 | ip-192-169-202-104.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 192.169.249.80:54647 | 0.24 | Unknown | Unknown | | Unknown | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 174.75.238.82:16409 | 1.82 | Louisiana | 70726 | Cox Communications | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 50.62.35.107:46730 | 0.24 | Arizona | 85260 | ip-50-62-35-107.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us

dichvusocks
Reviewed by dichvusocks on
,
[DICHVUSOCKS.US] 12h05 UPDATE 24 / 24- Good socks
Payment Immediately perfect money, Bitcoin, wmtransfer, dash, ETH (Please click on buy socks)
Update Tools Client Dichvusocks.us http://dichvusocks.us/tools.php Link Check Socks http://check.dichvusocks.us/
LIVE | 104.238.97.230:31800 | 0.75 | Arizona | 85260 | ip-104-238-97-230.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 12.246.170.142:8963 | 0.34 | Indiana | 46356 | c-73-8-54-97.hsd1.in.comcast.net | United States | Blacklist: Yes | Checked for

Rating: 5

,

nginx – Digital Ocean: Communication from drop to drop over private networks?

I am working on configuring Nginx as a load balancer and reversing proxy requests to a node application on another droplet. I have two Digital Ocean droplets (Ubuntu 18.04 for both) and have enabled private networking. My droplets are in the same region.

Can I use the private IP address for the server IP in the upstream configuration block in my nginx.conf file? My Node app runs Express js on port 3000.

Upstream NodeApiApp {
server 10.1.2.150:3000 fail_timeout = 0;
Keepalive 60;
}

Currently I can not bring the two droplets for communication. Can you give me hints where the problem could be?

The website shows this error: 504 Gateway timeout, When reconciling the error logs for Nginx, the following error appears:

2019/07/20 21:53:59 [error] 3136 # 3136: * Timeout of 1165 upstream (110:
Connection timeout) when connecting to upstream, client: 68.12.133.91, server: api.example.com, request: "GET / HTTP / 2.0", upstream: "http://10.1.2.150:3000/", Host: "api.example.com"

When I complete my node app logs, no activity is displayed.

After inserting SSH into my load balancer droplet, I can not ping or telnet into my second droplet. Could it be a firewall problem? If so, what would be a common configuration for inbound / outbound rules for droplet communication?

Based on the documents, I would have thought that these two virtual private server instances would have been able to communicate with each other because they are in the same region. I chose to enable the private network when I deploy these instances. The private network should be all set up.

dnd 5e – How do ships without a communication system forward information?

I looked in the Dark Matter supplement (for 5th Edition D & D, by Mage Hand Press) for the least common ship systems, when I noticed that all the fighter-class ships (with the exception of the Lakshayan Ashigaru frame) lacked a communication system ,

Does that mean that warships can not communicate with their allies, not even other warships? I have reviewed the book and, to my knowledge, it seems not possible for warships to do so, except for an external (pilot) radio and relay station setup.

PS. I realize that posting this question here is a shot into the dark, considering I could not even mark it properly, but I could not find any discussion about the supplement elsewhere. Please comment if you know a special forum! DS.

[DICHVUSOCKS.US]23h15 PM UPDATE 24 / 24- Good socks

Payment Immediately perfect money, Bitcoin, wmtransfer, dash, ETH (Please click on buy socks)
Update Tools Client Dichvusocks.us http://dichvusocks.us/tools.php Link Check Socks http://check.dichvusocks.us/
LIVE | 208.113.182.208:51492 | 0.04 | California | 92821 | ps28713.dreamhostps.com | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 192.169.192.77:13915 | 0.26 | Arizona | 85260 | ip-132-148-18-104.ip.secureserver.net | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 216.212.224.157:61952 | 0.15 | Georgia | 31792 | 216.212.224.157.rose.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 166.62.57.217:10265 | 0.26 | Arizona | 85260 | ip-97-74-6-64.ip.secureserver.net | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 132.148.145.56:36082 | 0.26 | Arizona | 85260 | ip-132-148-145-56.ip.secureserver.net | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 192.169.140.100:4538 | 0.26 | Arizona | 85260 | ip-192-169-140-100.ip.secureserver.net | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 69.58.7.165:34852 | 0.25 | California | 91730 | Frontier Communications | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 198.12.157.28:45956 | 0.89 | Arizona | 85260 | ip-198.12-157-28.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.90.50.55:22358 | 0.93 | California | 92821 | millcity.dreamhost.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 145.239.108.241:23493 | 0.42 | le-de-France | Unknown | nouba.pck.nerim.net | France | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 162.211.181.119:8893 | 0.25 | California | 91748 | G Network LLC | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 64.118.88.12:27137 | 0,99 | New Jersey | 07310 | drive9810.123servers.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 95.110.227.5:57729 | 0.41 | Unknown | Unknown | | Unknown | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.118.86.4:27137 | 0.77 | New Jersey | 07310 | drive9810.123servers.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 166.62.83.182:58593 | 0,95 | Arizona | 85260 | ip-166-62-89-69.ip.secureserver.net | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.118.87.39:27137 | 0.66 | New Jersey | 07310 | drive9810.123servers.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.118.86.33:27137 | 0.88 | New Jersey | 07310 | drive9810.123servers.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us
LIVE | 64.118.86.54:30365 | 0,95 | New Jersey | 07310 | drive9810.123servers.com | United States | Blacklist: Yes | Tested at http://dichvusocks.us

dichvusocksReviewed bydichvusockson,[DICHVUSOCKS.US] 23h15 PM UPDATE 24 / 24- Good socks
Payment Immediately perfect money, Bitcoin, wmtransfer, dash, ETH (Please click on buy socks)
Update Tools Client Dichvusocks.us http://dichvusocks.us/tools.php Link Check Socks http://check.dichvusocks.us/
LIVE | 208.113.182.208:51492 | 0.04 | California | 92821 | ps28713.dreamhostps.com | United States | Blacklist: No | Tested at http://dichvusocks.us
LIVE | 192.169.192.77:13915 | 0.26 | Arizona | 85260 | ip-132-148-18-104.ip.secureserver.net | United States | Blacklist: No | Checked for
Rating:5

,