apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "16689" uid: 5095af8e-e3d7-4b26-9699-a91d0fc0f995 spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T18:44:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.093792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:23Z" - latency: 1.220507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:23Z" - latency: 1.0791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 919.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 983.935µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 1.383291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 1.00299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 951.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:23Z" - latency: 977.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:23Z" - latency: 979.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "15964" uid: 728767a1-17b0-4e68-9626-5e0995312c64 spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:43:23Z" message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.532277ms message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 8.346135ms message: 'load-balancer-api-external: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:23Z" - latency: 4.459966ms message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 9.764453ms message: 'load-balancer-api-external: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:23Z" - latency: 4.805999ms message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 7.650196ms message: 'load-balancer-api-external: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:47:23Z" - latency: 3.733108ms message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 8.372024ms message: 'load-balancer-api-external: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:46:23Z" - latency: 4.559955ms message: 'load-balancer-api-external: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 7.479685ms message: 'load-balancer-api-external: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "15963" uid: 3c528bff-94a8-41ce-a9b3-5c6dec01ea8e spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:43:23Z" message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.925062ms message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 8.306716ms message: 'load-balancer-api-internal: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:23Z" - latency: 4.442312ms message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 9.69278ms message: 'load-balancer-api-internal: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:23Z" - latency: 4.506142ms message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 7.463163ms message: 'load-balancer-api-internal: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:47:23Z" - latency: 3.867643ms message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 8.395497ms message: 'load-balancer-api-internal: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:46:23Z" - latency: 4.555453ms message: 'load-balancer-api-internal: tcp connection to a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 7.428788ms message: 'load-balancer-api-internal: resolved host name a381a0d6d3cbf456c9da47125add007e-7d607df68428c242.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:45:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-network-check-target-ip-10-0-129-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "16688" uid: d1c09c1c-e0fa-4ca3-a5a3-770db815e88c spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:44:23Z" message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.565902ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:23Z" - latency: 2.197302ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:23Z" - latency: 2.067026ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 2.279304ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 2.309806ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 2.642802ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 2.594531ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 2.023334ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:23Z" - latency: 2.38408ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:23Z" - latency: 2.054846ms message: 'network-check-target-ip-10-0-129-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-network-check-target-ip-10-0-132-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "16686" uid: 21ec6d0e-8b8e-4354-85a4-55abe38a7a7d spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:44:23Z" message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.385739ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:23Z" - latency: 1.011513ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:23Z" - latency: 861.492µs message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 974.384µs message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 1.030887ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 1.594683ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 868.743µs message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 1.013336ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:23Z" - latency: 988.999µs message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:23Z" - latency: 1.02687ms message: 'network-check-target-ip-10-0-132-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-network-check-target-ip-10-0-135-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "16687" uid: 7394edd8-f247-4ebd-8519-fd7de95ce13d spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:44:23Z" message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.385754ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:23Z" - latency: 2.12566ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:23Z" - latency: 2.562437ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 2.101413ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 2.44589ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 2.278487ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 2.273783ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 2.324399ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:23Z" - latency: 2.536016ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:23Z" - latency: 2.465909ms message: 'network-check-target-ip-10-0-135-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:37:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-114-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-114.ec2.internal uid: b4e26053-a57f-4807-b3f6-2cc47190c990 resourceVersion: "15962" uid: 9260c05a-0b65-4f16-a179-5f96488a28cc spec: sourcePod: network-check-source-7d88cb55d8-fr59d targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T18:43:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 777.302µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:23Z" - latency: 1.766812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:23Z" - latency: 904.144µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:23Z" - latency: 1.800569ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:23Z" - latency: 891.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:23Z" - latency: 1.64959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:47:23Z" - latency: 819.284µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:23Z" - latency: 1.630495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:46:23Z" - latency: 819.909µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:23Z" - latency: 1.704968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:45:23Z" kind: List metadata: resourceVersion: ""