apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "62024" uid: ffa62c5e-a0f8-4545-9f84-e47cb269992b spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T17:35:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 957.538µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 5.02694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 1.301754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:53:42Z" - latency: 1.23172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:52:42Z" - latency: 973.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:51:42Z" - latency: 1.050927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:50:42Z" - latency: 912.291µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:49:42Z" - latency: 920.754µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:48:42Z" - latency: 1.01148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:47:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "64703" uid: 0d5ba948-dae2-4ec9-8c23-8085805cf9d7 spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T17:34:42Z" message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.558493ms message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:58:42Z" - latency: 11.977176ms message: 'load-balancer-api-external: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:58:42Z" - latency: 18.025918ms message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:57:42Z" - latency: 12.366623ms message: 'load-balancer-api-external: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:57:42Z" - latency: 17.356306ms message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 11.302468ms message: 'load-balancer-api-external: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:56:42Z" - latency: 15.976935ms message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 10.371075ms message: 'load-balancer-api-external: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:55:42Z" - latency: 22.986668ms message: 'load-balancer-api-external: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 16.357126ms message: 'load-balancer-api-external: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:54:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "64704" uid: eb598ba8-1d0e-4429-acca-3a605d9df915 spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T17:34:42Z" message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.209327ms message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:58:42Z" - latency: 11.927477ms message: 'load-balancer-api-internal: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:58:42Z" - latency: 19.182371ms message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:57:42Z" - latency: 12.298887ms message: 'load-balancer-api-internal: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:57:42Z" - latency: 16.361389ms message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 11.331966ms message: 'load-balancer-api-internal: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:56:42Z" - latency: 16.300973ms message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 10.404052ms message: 'load-balancer-api-internal: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:55:42Z" - latency: 35.537432ms message: 'load-balancer-api-internal: tcp connection to a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 16.698679ms message: 'load-balancer-api-internal: resolved host name a756852771c0044279d6ba9a0e15a6dd-c7c3820165848559.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T17:54:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-129-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "62023" uid: 6d3fe283-5346-4491-813d-bb582deefcee spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:35:42Z" message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.277011ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 2.208107ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 6.152101ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 2.826906ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:53:42Z" - latency: 2.560071ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:52:42Z" - latency: 2.507897ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:51:42Z" - latency: 3.0355ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:50:42Z" - latency: 2.060397ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:49:42Z" - latency: 2.214992ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:48:42Z" - latency: 2.641593ms message: 'network-check-target-ip-10-0-129-127: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:47:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-138-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "62021" uid: 54b71dc0-1182-429e-949d-e271518bad87 spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:35:42Z" message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.545µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 846.524µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 6.60685ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 1.506621ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:53:42Z" - latency: 964.85µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:52:42Z" - latency: 969.458µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:51:42Z" - latency: 1.543852ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:50:42Z" - latency: 1.147169ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:49:42Z" - latency: 839.429µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:48:42Z" - latency: 980.088µs message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:47:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-ip-10-0-139-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "62022" uid: 3f7230c5-ff89-476e-9d44-a2d0f8d2e24e spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T17:35:42Z" message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220043ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 2.081736ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 5.677214ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 2.578779ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:53:42Z" - latency: 2.539587ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:52:42Z" - latency: 2.416937ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:51:42Z" - latency: 2.574975ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:50:42Z" - latency: 2.262334ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:49:42Z" - latency: 2.345126ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:48:42Z" - latency: 2.653036ms message: 'network-check-target-ip-10-0-139-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:47:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T17:28:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-17.ec2.internal uid: 9ab3f56d-4303-40f3-8bbf-18cbacdf10cc resourceVersion: "64700" uid: 664073a1-688d-429c-8ffa-0cd3cc5700ea spec: sourcePod: network-check-source-6f78d59f99-qkkwm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T17:34:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.198404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:58:42Z" - latency: 1.670264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T17:58:42Z" - latency: 1.059353ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:57:42Z" - latency: 1.926007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T17:57:42Z" - latency: 925.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:56:42Z" - latency: 1.77825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T17:56:42Z" - latency: 1.195488ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:55:42Z" - latency: 1.735751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T17:55:42Z" - latency: 915.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T17:54:42Z" - latency: 6.113147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T17:54:42Z" kind: List metadata: resourceVersion: ""