apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61296" uid: 54042006-4040-4e4c-b6c7-c7c238a5c5e4 spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T17:08:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 1.152808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 949.126µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 1.270434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 1.694911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 1.114466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:38:42Z" - latency: 1.096236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:37:42Z" - latency: 1.053603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:36:42Z" - latency: 912.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:35:42Z" - latency: 1.061076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61297" uid: f638f822-eaf5-45ca-b21c-5a51bf3e52ff spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T17:07:42Z" message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.981158ms message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 9.844443ms message: 'load-balancer-api-external: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:43:42Z" - latency: 4.942497ms message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 7.85278ms message: 'load-balancer-api-external: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:42:42Z" - latency: 5.317934ms message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 7.764722ms message: 'load-balancer-api-external: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:41:42Z" - latency: 5.519081ms message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 7.420887ms message: 'load-balancer-api-external: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:40:42Z" - latency: 4.024616ms message: 'load-balancer-api-external: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 7.979925ms message: 'load-balancer-api-external: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:39:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61298" uid: 885b9665-e9e5-4c95-a1eb-7d46d56670bd spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T17:07:42Z" message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.772293ms message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 9.688328ms message: 'load-balancer-api-internal: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:43:42Z" - latency: 5.577324ms message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 7.928879ms message: 'load-balancer-api-internal: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:42:42Z" - latency: 4.54424ms message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 7.805251ms message: 'load-balancer-api-internal: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:41:42Z" - latency: 5.528043ms message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 7.454946ms message: 'load-balancer-api-internal: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:40:42Z" - latency: 4.019855ms message: 'load-balancer-api-internal: tcp connection to a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 7.898741ms message: 'load-balancer-api-internal: resolved host name a6a8ee58b83984333a01ba4288e319f9-6561e201a1c521fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T17:39:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-network-check-target-ip-10-0-135-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61294" uid: 67722349-1248-4fd6-a789-b803f2bf5f35 spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T17:08:42Z" message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.192422ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 1.868961ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 1.736628ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 1.675117ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 2.022362ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 2.063139ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:38:42Z" - latency: 1.693195ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:37:42Z" - latency: 1.838838ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:36:42Z" - latency: 1.718373ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:35:42Z" - latency: 1.671527ms message: 'network-check-target-ip-10-0-135-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-network-check-target-ip-10-0-135-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61293" uid: 2d7dab6c-4cd1-46c5-8a6c-440936d6a7ae spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T17:08:42Z" message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.104086ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 2.317157ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 2.357296ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 2.09649ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 2.281955ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 2.408085ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:38:42Z" - latency: 2.007087ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:37:42Z" - latency: 2.074277ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:36:42Z" - latency: 2.222049ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:35:42Z" - latency: 2.035524ms message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-network-check-target-ip-10-0-143-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61292" uid: 83c93353-af13-42ee-97c9-e389178dc616 spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T17:08:42Z" message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.314428ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 927.312µs message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 1.015045ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 920.402µs message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 1.43001ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 1.368809ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:38:42Z" - latency: 1.169472ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:37:42Z" - latency: 1.106834ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:36:42Z" - latency: 1.084809ms message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:35:42Z" - latency: 856.403µs message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:34:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T17:01:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-124.ec2.internal uid: 5b252fff-97d7-46b4-8450-13227821ab30 resourceVersion: "61295" uid: 03918288-8a42-4959-b06b-2f44626a7613 spec: sourcePod: network-check-source-869dcfcdcd-px4mw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T17:07:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 791.086µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:43:42Z" - latency: 2.162734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:43:42Z" - latency: 1.025542ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:42:42Z" - latency: 1.930429ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:42:42Z" - latency: 1.207055ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:41:42Z" - latency: 1.699685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:41:42Z" - latency: 913.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:40:42Z" - latency: 1.940142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:40:42Z" - latency: 992.677µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:39:42Z" - latency: 2.058017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T17:39:42Z" kind: List metadata: resourceVersion: ""