apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "68950" uid: 4da97db5-75a0-47eb-9407-f890699028ad spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-12T00:54:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 1.201286ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 1.452696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 836.403µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 1.230865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:18:02Z" - latency: 1.197991ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:17:02Z" - latency: 1.255145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:16:02Z" - latency: 1.146265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:15:02Z" - latency: 1.232668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:14:02Z" - latency: 1.200036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "69875" uid: 4b582ab5-08d7-45cd-aac3-648c9caea294 spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-12T00:53:02Z" message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.651911ms message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:23:02Z" - latency: 9.109144ms message: 'load-balancer-api-external: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:23:02Z" - latency: 4.556363ms message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 8.717005ms message: 'load-balancer-api-external: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:22:02Z" - latency: 4.414143ms message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 8.219544ms message: 'load-balancer-api-external: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:21:02Z" - latency: 4.504759ms message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 7.04029ms message: 'load-balancer-api-external: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:20:02Z" - latency: 4.888184ms message: 'load-balancer-api-external: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 8.45661ms message: 'load-balancer-api-external: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "69874" uid: 7649c792-4ff6-48cd-a78e-5bbca52f5095 spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-12T00:53:02Z" message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.736954ms message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:23:02Z" - latency: 9.031478ms message: 'load-balancer-api-internal: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:23:02Z" - latency: 4.567952ms message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 8.66757ms message: 'load-balancer-api-internal: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:22:02Z" - latency: 5.421826ms message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 8.27447ms message: 'load-balancer-api-internal: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:21:02Z" - latency: 3.326485ms message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 6.905266ms message: 'load-balancer-api-internal: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:20:02Z" - latency: 4.898578ms message: 'load-balancer-api-internal: tcp connection to a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 8.483879ms message: 'load-balancer-api-internal: resolved host name a4fdabf2789524bf1b779cbb2abdb105-ce524b211187c4bf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-12T01:19:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-136-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "68948" uid: f64e4580-4d8e-4033-8e6f-20ff50857434 spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-12T00:54:02Z" message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.088039ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 1.899022ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 2.124237ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 1.832902ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 1.943759ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:18:02Z" - latency: 2.157288ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:17:02Z" - latency: 2.169636ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:16:02Z" - latency: 1.973912ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:15:02Z" - latency: 1.979133ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:14:02Z" - latency: 1.998582ms message: 'network-check-target-ip-10-0-136-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-139-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "68947" uid: 39321944-7fb0-449e-801b-806e6d3a127e spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-12T00:54:02Z" message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.019205ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 1.992783ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 2.14ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 1.687887ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 2.206517ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:18:02Z" - latency: 2.119424ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:17:02Z" - latency: 2.070516ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:16:02Z" - latency: 2.500122ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:15:02Z" - latency: 2.415697ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:14:02Z" - latency: 1.943984ms message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-network-check-target-ip-10-0-142-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "68946" uid: c8672e4f-8084-4e3b-9549-ece193b22e48 spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-12T00:54:02Z" message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.189µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 842.708µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 912.149µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 801.914µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 1.677583ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:18:02Z" - latency: 978.95µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:17:02Z" - latency: 964.222µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:16:02Z" - latency: 1.64024ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:15:02Z" - latency: 990.889µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:14:02Z" - latency: 805.653µs message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:13:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-12T00:47:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-242.ec2.internal uid: 816e2a02-cad0-4795-8647-e5fd2f19ba71 resourceVersion: "69872" uid: 91aabcb4-0333-401d-bf03-0fc41212be94 spec: sourcePod: network-check-source-6f8b768455-ddmw5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-12T00:53:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 773.314µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:23:02Z" - latency: 2.565396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-12T01:23:02Z" - latency: 659.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:22:02Z" - latency: 2.095974ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-12T01:22:02Z" - latency: 952.072µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:21:02Z" - latency: 2.006965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-12T01:21:02Z" - latency: 853.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:20:02Z" - latency: 1.82882ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-12T01:20:02Z" - latency: 705.084µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-12T01:19:02Z" - latency: 1.733791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-12T01:19:02Z" kind: List metadata: resourceVersion: ""