apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61080" uid: c6e06861-60bb-4ce8-8121-dfcb0815bad1 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:45:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.589µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 1.092794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 1.146771ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 845.119µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 1.015167ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 1.24989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:06Z" - latency: 1.186017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:06Z" - latency: 1.448851ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:06Z" - latency: 870.55µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:06Z" - latency: 1.112257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61083" uid: 68e4a062-622e-411a-832a-ef794e7e12f7 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:44:06Z" message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.277749ms message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 6.577759ms message: 'load-balancer-api-external: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:06Z" - latency: 4.488605ms message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 8.526761ms message: 'load-balancer-api-external: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:06Z" - latency: 5.240389ms message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 8.092548ms message: 'load-balancer-api-external: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:06Z" - latency: 4.755917ms message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 9.187613ms message: 'load-balancer-api-external: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:06Z" - latency: 5.345483ms message: 'load-balancer-api-external: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 10.886598ms message: 'load-balancer-api-external: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61082" uid: 2f6c794a-37d9-4166-b16a-10f42556e968 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:44:06Z" message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.423284ms message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 6.434132ms message: 'load-balancer-api-internal: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:06Z" - latency: 5.600807ms message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 8.557612ms message: 'load-balancer-api-internal: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:06Z" - latency: 5.252711ms message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 8.036479ms message: 'load-balancer-api-internal: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:06Z" - latency: 3.851042ms message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 9.13695ms message: 'load-balancer-api-internal: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:06Z" - latency: 5.334564ms message: 'load-balancer-api-internal: tcp connection to a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 10.937144ms message: 'load-balancer-api-internal: resolved host name a4fadf0a842d8481398934f1f97f95b4-66d873a84383b2f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:16:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-network-check-target-ip-10-0-128-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61075" uid: f747af84-7e34-46e2-b168-558590af6bc9 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:45:06Z" message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.143µs message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 1.716363ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 817.674µs message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 1.115558ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 831.146µs message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 1.096272ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:06Z" - latency: 1.441718ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:06Z" - latency: 979.838µs message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:06Z" - latency: 1.094059ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:06Z" - latency: 1.020364ms message: 'network-check-target-ip-10-0-128-217: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-network-check-target-ip-10-0-129-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61076" uid: 3c7f37d7-1e18-4492-9ffc-3eea31f1cce0 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:45:06Z" message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.998752ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 1.839409ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 1.846512ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 1.782518ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 1.833879ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 1.990502ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:06Z" - latency: 1.797905ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:06Z" - latency: 1.829328ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:06Z" - latency: 1.974847ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:06Z" - latency: 1.908303ms message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-network-check-target-ip-10-0-137-76 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61077" uid: 216fa6fa-9fde-43df-a0be-83ec58db3ad0 spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:45:06Z" message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.002431ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 2.488468ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 2.391515ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 2.149925ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 2.440679ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 1.842028ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:15:06Z" - latency: 2.305623ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:14:06Z" - latency: 2.352495ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:13:06Z" - latency: 2.483018ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:12:06Z" - latency: 2.005765ms message: 'network-check-target-ip-10-0-137-76: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:11:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:38:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-217-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-217.ec2.internal uid: 091db5cf-b497-44f5-9d14-28eba8db90de resourceVersion: "61078" uid: a135c303-ba61-4dd4-aaf0-e1de8847f00f spec: sourcePod: network-check-source-869dcfcdcd-2z7l4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:44:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.534µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:20:06Z" - latency: 2.076955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:20:06Z" - latency: 922.37µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:19:06Z" - latency: 1.815603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:19:06Z" - latency: 806.521µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:18:06Z" - latency: 1.802642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:18:06Z" - latency: 847.508µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:17:06Z" - latency: 1.705211ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:17:06Z" - latency: 1.022834ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:16:06Z" - latency: 1.73101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:16:06Z" kind: List metadata: resourceVersion: ""