apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "69256" uid: 5a6faad7-d4f2-4f62-b5c0-1466cd9fe4ee spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T21:20:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.929µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:02:54Z" - latency: 1.044644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:01:54Z" - latency: 1.21011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:00:54Z" - latency: 1.312767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:59:54Z" - latency: 1.16793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:58:54Z" - latency: 1.442769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:57:54Z" - latency: 1.878082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:56:54Z" - latency: 891.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:55:54Z" - latency: 1.004563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:54:54Z" - latency: 1.514411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "75190" uid: 3227c6f0-8d36-43fe-a8a6-036cb180ffaf spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:19:55Z" message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.738278ms message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:54Z" - latency: 8.647288ms message: 'load-balancer-api-external: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:07:54Z" - latency: 6.864654ms message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:54Z" - latency: 7.975608ms message: 'load-balancer-api-external: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:06:54Z" - latency: 4.50439ms message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:05:54Z" - latency: 7.421439ms message: 'load-balancer-api-external: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:05:54Z" - latency: 5.257636ms message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:04:54Z" - latency: 6.388003ms message: 'load-balancer-api-external: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:04:54Z" - latency: 4.949452ms message: 'load-balancer-api-external: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:03:54Z" - latency: 7.027644ms message: 'load-balancer-api-external: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:03:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "75191" uid: dcf67c67-8fe3-4fa6-b303-0f0d3b975e9f spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T21:19:55Z" message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.733588ms message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:54Z" - latency: 8.393004ms message: 'load-balancer-api-internal: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:07:54Z" - latency: 5.672502ms message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:54Z" - latency: 7.917066ms message: 'load-balancer-api-internal: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:06:54Z" - latency: 4.550911ms message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:05:54Z" - latency: 7.382139ms message: 'load-balancer-api-internal: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:05:54Z" - latency: 5.309471ms message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:04:54Z" - latency: 6.366163ms message: 'load-balancer-api-internal: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:04:54Z" - latency: 4.928719ms message: 'load-balancer-api-internal: tcp connection to a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:03:54Z" - latency: 6.896731ms message: 'load-balancer-api-internal: resolved host name a9d13dbc43cdc4c7ca2a53e0f6e982c2-7fb9ba73f8e99660.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T22:03:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-network-check-target-ip-10-0-132-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "69253" uid: 8f45d0de-e37c-4d08-b9f3-44ba92c21d47 spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:20:54Z" message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.902263ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:02:54Z" - latency: 961.798µs message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:01:54Z" - latency: 1.61727ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:00:54Z" - latency: 1.002711ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:59:54Z" - latency: 1.043303ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:58:54Z" - latency: 1.147432ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:57:54Z" - latency: 2.554269ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:56:54Z" - latency: 913.972µs message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:55:54Z" - latency: 1.22361ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:54:54Z" - latency: 1.557744ms message: 'network-check-target-ip-10-0-132-95: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-network-check-target-ip-10-0-133-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "69254" uid: 584eda4d-3d74-4424-b86e-9a72726e9651 spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:20:54Z" message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.798097ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:02:54Z" - latency: 2.187942ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:01:54Z" - latency: 2.475997ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:00:54Z" - latency: 2.257577ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:59:54Z" - latency: 2.63133ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:58:54Z" - latency: 2.901414ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:57:54Z" - latency: 2.837897ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:56:54Z" - latency: 2.247274ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:55:54Z" - latency: 2.173038ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:54:54Z" - latency: 2.730494ms message: 'network-check-target-ip-10-0-133-58: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-network-check-target-ip-10-0-137-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "69255" uid: d2d75c0d-e659-456d-a0d3-de0f96b49f03 spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T21:20:54Z" message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.728527ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:02:54Z" - latency: 2.55663ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:01:54Z" - latency: 2.77133ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:00:54Z" - latency: 2.15366ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:59:54Z" - latency: 2.408514ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:58:54Z" - latency: 2.384013ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:57:54Z" - latency: 3.036678ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:56:54Z" - latency: 2.217022ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:55:54Z" - latency: 2.485125ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:54:54Z" - latency: 2.345801ms message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T21:53:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T21:13:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-95.ec2.internal uid: f538faaf-2882-4194-bbdb-3ce03f1aacf2 resourceVersion: "75189" uid: a015bee0-992b-417f-bf0c-94afa906c750 spec: sourcePod: network-check-source-7bc5b6bf85-nmx8t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T21:19:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.016484ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:07:54Z" - latency: 1.870908ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:07:54Z" - latency: 991.706µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:06:54Z" - latency: 2.034636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:06:54Z" - latency: 1.182199ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:05:54Z" - latency: 1.873127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:05:54Z" - latency: 1.048972ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:04:54Z" - latency: 1.836315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:04:54Z" - latency: 904.177µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T22:03:54Z" - latency: 1.737511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T22:03:54Z" kind: List metadata: resourceVersion: ""