apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "190621" uid: 7e84b4fc-3288-4dcb-9a7d-ebdc54503d55 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T21:53:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:49:27Z" - latency: 1.207433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:48:27Z" - latency: 1.306017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:47:27Z" - latency: 1.112131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 1.149402ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 908.396µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 988.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 1.415857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 947.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:41:27Z" - latency: 3.155033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:40:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "186142" uid: f0373a62-84d5-4498-9bf6-6d8432377072 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T21:52:27Z" message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.494828ms message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 6.846777ms message: 'load-balancer-api-external: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:46:27Z" - latency: 5.242791ms message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 7.029845ms message: 'load-balancer-api-external: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:45:27Z" - latency: 4.797497ms message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 7.521701ms message: 'load-balancer-api-external: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:44:27Z" - latency: 4.510858ms message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 8.146751ms message: 'load-balancer-api-external: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:43:27Z" - latency: 4.768137ms message: 'load-balancer-api-external: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 7.491158ms message: 'load-balancer-api-external: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "186141" uid: d4967f7a-ce5a-45d9-aeee-16a05e9554f6 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T21:52:27Z" message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.41966ms message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 6.872015ms message: 'load-balancer-api-internal: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:46:27Z" - latency: 5.149711ms message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 7.063638ms message: 'load-balancer-api-internal: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:45:27Z" - latency: 4.809244ms message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 7.54117ms message: 'load-balancer-api-internal: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:44:27Z" - latency: 4.548995ms message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 8.211644ms message: 'load-balancer-api-internal: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:43:27Z" - latency: 4.767986ms message: 'load-balancer-api-internal: tcp connection to a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 7.434325ms message: 'load-balancer-api-internal: resolved host name a0619f4486f4c4343b7b4940ed1ea54a-305c90a339366ba0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T22:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-network-check-target-ip-10-0-131-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "190619" uid: 57be1b64-60ce-440f-9199-114e12fd9206 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T21:53:27Z" message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.424µs message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:49:27Z" - latency: 1.490457ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:48:27Z" - latency: 1.079657ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:47:27Z" - latency: 1.058186ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 1.188135ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 893.069µs message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 968.283µs message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 970.178µs message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 1.340982ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:41:27Z" - latency: 3.317583ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:40:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-network-check-target-ip-10-0-135-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "190618" uid: 3cbaeb4a-48cf-429b-b932-fa362a66e9a1 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T21:53:27Z" message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.586565ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:49:27Z" - latency: 2.171383ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:48:27Z" - latency: 2.38031ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:47:27Z" - latency: 3.199674ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 2.04233ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 1.999939ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 2.582293ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 2.172513ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 2.07054ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:41:27Z" - latency: 2.503881ms message: 'network-check-target-ip-10-0-135-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:40:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-network-check-target-ip-10-0-136-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "190620" uid: 8e1c623e-26f3-49c6-93aa-139aa5a938f2 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T21:53:27Z" message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.097482ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:49:27Z" - latency: 2.954506ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:48:27Z" - latency: 2.328485ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:47:27Z" - latency: 2.639603ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 2.523082ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 2.328788ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 2.398558ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 2.61419ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 2.300096ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:41:27Z" - latency: 2.812251ms message: 'network-check-target-ip-10-0-136-47: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:40:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T21:46:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-110.us-east-2.compute.internal uid: 644c947e-2f5f-4575-9506-8f8d17e7da60 resourceVersion: "186140" uid: 3447d88f-beda-42db-b493-229fe956b5c4 spec: sourcePod: network-check-source-6f78d59f99-2k5vn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T21:52:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 825.303µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:46:27Z" - latency: 1.885149ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T22:46:27Z" - latency: 1.0811ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:45:27Z" - latency: 1.967066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T22:45:27Z" - latency: 1.029697ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:44:27Z" - latency: 2.065522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T22:44:27Z" - latency: 922.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:43:27Z" - latency: 2.220272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T22:43:27Z" - latency: 1.260933ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T22:42:27Z" - latency: 2.050923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T22:42:27Z" kind: List metadata: resourceVersion: ""