apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32425" uid: 8c31c7aa-6fcd-4ce8-a140-233551390845 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T09:44:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.94µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 1.017986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 955.27µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 1.429858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 860.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 977.823µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:14:32Z" - latency: 1.038829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:13:32Z" - latency: 985.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:12:32Z" - latency: 1.280211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:11:32Z" - latency: 854.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:10:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32427" uid: 6045990e-0b79-4081-ae39-1f0185d37b54 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T09:43:32Z" message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.690823ms message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 8.495592ms message: 'load-balancer-api-external: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:19:32Z" - latency: 5.278746ms message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 7.433912ms message: 'load-balancer-api-external: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:18:32Z" - latency: 4.874918ms message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 8.398817ms message: 'load-balancer-api-external: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:17:32Z" - latency: 5.078725ms message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 10.857701ms message: 'load-balancer-api-external: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:16:32Z" - latency: 4.982024ms message: 'load-balancer-api-external: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 7.428586ms message: 'load-balancer-api-external: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:15:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32426" uid: 3da232f3-b4a1-4d9f-a0fc-44fad23820a2 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T09:43:32Z" message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.700201ms message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 8.421776ms message: 'load-balancer-api-internal: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:19:32Z" - latency: 5.311301ms message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 7.384975ms message: 'load-balancer-api-internal: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:18:32Z" - latency: 4.851381ms message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 8.358339ms message: 'load-balancer-api-internal: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:17:32Z" - latency: 5.058376ms message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 10.828804ms message: 'load-balancer-api-internal: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:16:32Z" - latency: 4.785661ms message: 'load-balancer-api-internal: tcp connection to ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 7.439973ms message: 'load-balancer-api-internal: resolved host name ab173c6c5a83d497f9ae8bbd37624cc5-55350ff09f9fb21b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T10:15:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-135-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32423" uid: 321bfd56-a9bc-4248-a99d-c325e30c9661 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:44:32Z" message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.86689ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 1.979555ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 1.689069ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 1.929366ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 1.924485ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 1.828303ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:14:32Z" - latency: 2.127777ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:13:32Z" - latency: 1.838718ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:12:32Z" - latency: 1.775829ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:11:32Z" - latency: 1.994119ms message: 'network-check-target-ip-10-0-135-204: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:10:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-141-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32422" uid: 72d615ac-aec9-46cf-b84c-5364818ccbb0 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:44:32Z" message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.199245ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 2.179241ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 1.896054ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 2.276562ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 2.24231ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 2.269424ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:14:32Z" - latency: 2.320936ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:13:32Z" - latency: 2.531996ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:12:32Z" - latency: 2.189803ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:11:32Z" - latency: 2.241778ms message: 'network-check-target-ip-10-0-141-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:10:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-ip-10-0-143-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32421" uid: 805df149-c9ba-43a5-81ec-dc53b0239198 spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:44:32Z" message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 795.213µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 871.32µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 918.998µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 935.669µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 939.152µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 1.000605ms message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:14:32Z" - latency: 960.266µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:13:32Z" - latency: 865.34µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:12:32Z" - latency: 813.021µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:11:32Z" - latency: 911.112µs message: 'network-check-target-ip-10-0-143-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:10:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:37:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-234.ec2.internal uid: 06e45e4d-4ca5-4d4f-a6b5-5c3fd129c246 resourceVersion: "32424" uid: 254b4af1-6b53-472d-b0a4-85d6c03e9e4c spec: sourcePod: network-check-source-989f8b8dc-6m8vm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T09:43:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054448ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:19:32Z" - latency: 1.781366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:19:32Z" - latency: 993.953µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:18:32Z" - latency: 1.649571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:18:32Z" - latency: 1.269604ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:17:32Z" - latency: 1.819593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:17:32Z" - latency: 880.448µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:16:32Z" - latency: 1.957346ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:16:32Z" - latency: 1.21087ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T10:15:32Z" - latency: 1.657684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T10:15:32Z" kind: List metadata: resourceVersion: ""