I have a multithreaded application that listens to events and needs to respond to them instantly.
With the application running, my server is under 5% CPU load in a 1 core server.
I wonder though, would increasing the number of threads my server has lower response time?
Seems intuitive but just to make sure.
I have a network switch, a Linux server, and my computer. The computer and server are both connected to the switch. If I connect the serial port of the server to the switch through a Serial to Ethernet adapter, will my computer be able to access that Serial Console, or will I have to connect the server directly to the computer?
NOTE: the switch is a smart managed Ethernet switch, not a Serial COM switch.
I am not trying to connect to the Serial of the switch. I want to connect to the Serial of the server through the switch.
Do I need a GPU on a text and console only server? No GPU as in no iGPU and dGPU. Im going to be using SSH, so I dont need a display out.
Im using Linux, but the OS shouldn't affect the results
I have a Kubernetes cluster using the Antrea CNI.
The problem is that I can't curl any domain names.
I can do nslookup inside the pod and get the IP of any domain, but I can't directly curl the domain.
For example, I can't curl https://google.com but I can curl https://1.1.1.1
Am I missing something, or is it normal? What do I need to do in order to fix this?
Here is the pod's container's ip route show table all
default via 10.42.4.1 dev eth0
10.42.4.0/24 dev eth0 scope link src 10.42.4.26
broadcast 10.42.4.0 dev eth0 table local scope link src 10.42.4.26
local 10.42.4.26 dev eth0 table local scope host src 10.42.4.26
broadcast 10.42.4.255 dev eth0 table local scope link src 10.42.4.26
broadcast 127.0.0.0 dev lo table local scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local scope host src 127.0.0.1
local 127.0.0.1 dev lo table local scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local scope link src 127.0.0.1
fe80::/64 dev eth0 metric 256
local ::1 dev lo table local metric 0
local fe80::e08c:e8ff:fef3:4877 dev eth0 table local metric 0
multicast ff00::/8 dev eth0 table local metric 256
My cluster's cidr is 10.42.0.0/16
I have a k3s cluster with a master on a cloud VPS but with 2 remote worker nodes, both on the same network. They're connected via a VPN to the cloud provider. The worker nodes were able to join just fine and were able to create new pods, but it seems that communication is a problem because I can't contact the pods from an Ingress.
When I run my Traefik Ingress (I tried Nginx too, same result), it keeps returning 502 even though the configuration seems correct, so it can't contact the backend. The backend pods are on the remote workers, while the ingress controller is on the VPS.
The backend deployment:
apiVersion: apps/v1
kind: Deployment
metadata:
name: kiwoonapi
spec:
replicas: 3
selector:
matchLabels:
app: kiwoonapi
template:
metadata:
labels:
app: kiwoonapi
spec:
containers:
- name: backend
imagePullPolicy: IfNotPresent
image: *pullplace*
ports:
- containerPort: 80
imagePullSecrets:
- name: *secret*
The service:
apiVersion: v1
kind: Service
metadata:
name: kiwoonapisvc
labels:
run: kiwoonapi
spec:
selector:
app: kiwoonapi
ports:
- protocol: TCP
port: 80
targetPort: 80
The Ingress:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: kiwoonapi-ingress
annotations:
kubernetes.io/ingress.class: traefik
spec:
rules:
- host: *domain*
http:
paths:
- path: /api
pathType: Prefix
backend:
service:
name: kiwoonapisvc
port:
number: 80
tls:
- hosts:
- *domain*
secretName: *domain-crt*
Status of the cluster:
kubectl get pods
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system local-path-provisioner-5ff76fc89d-qzmpc 1/1 Running 0 54m
kube-system metrics-server-86cbb8457f-rhrcf 1/1 Running 0 54m
kube-system coredns-7448499f4d-xf5lj 1/1 Running 0 54m
kube-system helm-install-traefik-crd-q8c28 0/1 Completed 0 54m
kube-system helm-install-traefik-xd7vp 0/1 Completed 1 54m
kube-system svclb-traefik-jd8cr 2/2 Running 0 53m
kube-system traefik-97b44b794-ht2l4 1/1 Running 0 53m
kube-system svclb-traefik-9zcvm 2/2 Running 0 52m
kube-system svclb-traefik-zlj7w 2/2 Running 0 49m
default kiwoonapi-6c668ffd67-lsbll 1/1 Running 0 49m
default kiwoonapi-6c668ffd67-csqz9 1/1 Running 0 49m
default kiwoonapi-6c668ffd67-89x95 1/1 Running 0 49m
kubectl get svc --all-namespaces
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 54m
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 54m
kube-system metrics-server ClusterIP 10.43.109.147 <none> 443/TCP 54m
kube-system traefik LoadBalancer 10.43.176.123 10.0.0.131,10.0.0.98,192.168.0.4 80:30410/TCP,443:32524/TCP 53m
default kiwoonapisvc ClusterIP 10.43.96.214 <none> 80/TCP 47m
kubectl get ing
NAME CLASS HOSTS ADDRESS PORTS AGE
kiwoonapi-ingress <none> *domain* 10.0.0.131,10.0.0.98,192.168.0.4 80, 443 42m
The Dockerfile does expose port 80 and 443. I'm not sure if not including 443 in the deployment somehow affects it.
The LoadBalancer used is not from the cloud: it's something that's built into k3s and essentially piggybacks off an existing node.
Anyone see a problem in the configuration somewhere? I'm able to provide more information if needed.
I'm trying to create a Debian server where one connection is to an OpenVPN VPN and another is direct. I've got a VPS in the cloud but it's only got a single Ethernet NIC (does that matter?). I'm only using the VPN connection to backup the VPS drives to my SMB drives, and I want everything else to go thru a non-tunneled connection.
How can I do this?
Is there a way I can direct which internet interface a command on the terminal goes through?
I'm trying to access a Windows 10 virtual machine from my Linux host by using virsh console.
But when I do so, I get the empty console that many others have experienced.
virsh console win10
Connected to domain 'win10'
Escape character is ^] (Ctrl + ])
And I can't type at all. Anyway, is there a configuration that I can do in the VM to allow this, specifically for Windows? Thanks