apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "30967" uid: a2445051-0e30-457e-8f62-9a29c2f9982a spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T16:45:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:52:11Z" - latency: 893.782µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:51:11Z" - latency: 1.025133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 1.11541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 1.029775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 1.015361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 1.343539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 1.055098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:45:11Z" - latency: 1.279406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:44:11Z" - latency: 1.046125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "29666" uid: 079e6878-9cca-4661-a051-5a12591296ed spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:44:11Z" message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.856345ms message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 7.551773ms message: 'load-balancer-api-external: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:50:11Z" - latency: 5.592849ms message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 8.251694ms message: 'load-balancer-api-external: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:49:11Z" - latency: 5.876124ms message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 6.797382ms message: 'load-balancer-api-external: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:48:11Z" - latency: 3.492826ms message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 7.029513ms message: 'load-balancer-api-external: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:47:11Z" - latency: 5.543923ms message: 'load-balancer-api-external: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 8.08931ms message: 'load-balancer-api-external: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "29667" uid: 584c0f35-e681-4739-9c92-902d7fd9fab1 spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:44:11Z" message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.124228ms message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 7.517409ms message: 'load-balancer-api-internal: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:50:11Z" - latency: 5.575575ms message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 8.221126ms message: 'load-balancer-api-internal: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:49:11Z" - latency: 5.918887ms message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 6.75085ms message: 'load-balancer-api-internal: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:48:11Z" - latency: 4.288929ms message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 7.108502ms message: 'load-balancer-api-internal: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:47:11Z" - latency: 5.556391ms message: 'load-balancer-api-internal: tcp connection to ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 8.067667ms message: 'load-balancer-api-internal: resolved host name ac7996195a3694476b276f26c5efb0f4-244123cfee8c663d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:46:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-129-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "30964" uid: 94bafa0b-7d28-422f-a56d-f4936518d173 spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:11Z" message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.713µs message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:52:11Z" - latency: 1.303104ms message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:51:11Z" - latency: 887.387µs message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 1.818401ms message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 1.004885ms message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 1.240974ms message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 1.5164ms message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 969.543µs message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:45:11Z" - latency: 927.107µs message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:44:11Z" - latency: 867.787µs message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-135-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "30965" uid: 3fa6d889-4f66-415a-b39b-9844335dabaa spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:11Z" message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.381076ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:52:11Z" - latency: 2.480615ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:51:11Z" - latency: 2.386682ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 2.396563ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 2.425019ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 2.258941ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 2.50885ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 2.366306ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:45:11Z" - latency: 2.385952ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:44:11Z" - latency: 2.395521ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-network-check-target-ip-10-0-137-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "30966" uid: 3cdf6719-2b45-4cf7-9f2b-cb50dee1699a spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:11Z" message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.284964ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:52:11Z" - latency: 2.45213ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:51:11Z" - latency: 2.387094ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 2.303883ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 2.574679ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 2.200271ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 2.389607ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 1.984026ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:45:11Z" - latency: 2.100349ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:44:11Z" - latency: 2.422801ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-45-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-45.ec2.internal uid: 55724d3c-5087-46ed-a63e-e2496b175086 resourceVersion: "29665" uid: 3f58fc14-0f99-4e43-8a34-487892c200ad spec: sourcePod: network-check-source-dbd9cf844-nms9g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T16:44:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.121177ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:50:11Z" - latency: 2.143805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:50:11Z" - latency: 1.01493ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:49:11Z" - latency: 2.261095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:49:11Z" - latency: 1.000179ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:48:11Z" - latency: 1.842905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:48:11Z" - latency: 1.234846ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:47:11Z" - latency: 1.7561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:47:11Z" - latency: 808.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:46:11Z" - latency: 1.757934ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:46:11Z" kind: List metadata: resourceVersion: ""