apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64303" uid: 3d9db491-ab4b-4b72-a159-574b06835339 spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T00:22:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 952.172µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 1.101928ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 1.060932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 895.028µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 855.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 1.236842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:52:52Z" - latency: 1.021975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:51:52Z" - latency: 1.133222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:50:52Z" - latency: 842.173µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:49:52Z" - latency: 1.002362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:48:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64305" uid: 8108bfba-36f8-412e-a62c-0628d2411f20 spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T00:21:52Z" message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.671239ms message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 8.276276ms message: 'load-balancer-api-external: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:57:52Z" - latency: 4.339554ms message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 6.793441ms message: 'load-balancer-api-external: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:56:52Z" - latency: 4.705302ms message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 6.754504ms message: 'load-balancer-api-external: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:55:52Z" - latency: 4.223891ms message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 6.687283ms message: 'load-balancer-api-external: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:54:52Z" - latency: 5.411334ms message: 'load-balancer-api-external: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 6.71109ms message: 'load-balancer-api-external: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:53:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64304" uid: e6bb34be-be4f-4fc0-a65b-cf7867de7846 spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T00:21:52Z" message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.546885ms message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 8.319166ms message: 'load-balancer-api-internal: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:57:52Z" - latency: 4.046375ms message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 6.912342ms message: 'load-balancer-api-internal: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:56:52Z" - latency: 4.152115ms message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 6.844059ms message: 'load-balancer-api-internal: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:55:52Z" - latency: 4.211345ms message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 6.754598ms message: 'load-balancer-api-internal: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:54:52Z" - latency: 5.360226ms message: 'load-balancer-api-internal: tcp connection to a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 6.740921ms message: 'load-balancer-api-internal: resolved host name a5807735dd3ac4a1c835c881bc7a244b-51554112c8350e0f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T00:53:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-131-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64298" uid: 9353668d-5561-4f53-ac26-fd8c090bcdc9 spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T00:22:52Z" message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.845µs message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 1.577619ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 840.328µs message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 1.028925ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 1.062201ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 1.000307ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:52:52Z" - latency: 921.81µs message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:51:52Z" - latency: 952.085µs message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:50:52Z" - latency: 940.553µs message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:49:52Z" - latency: 1.050207ms message: 'network-check-target-ip-10-0-131-121: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:48:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-134-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64299" uid: 5ce46117-140a-49bc-ad48-ce2b4f171d45 spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T00:22:52Z" message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.304819ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 2.946849ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 1.855542ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 1.828655ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 1.89441ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 1.771775ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:52:52Z" - latency: 2.455233ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:51:52Z" - latency: 2.446977ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:50:52Z" - latency: 1.740182ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:49:52Z" - latency: 1.988967ms message: 'network-check-target-ip-10-0-134-124: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:48:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-network-check-target-ip-10-0-141-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64300" uid: fd1a8c34-4bd9-48eb-99f9-76ad8f42804f spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T00:22:52Z" message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.677428ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 2.619939ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 2.196802ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 1.982953ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 2.412272ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 2.286444ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:52:52Z" - latency: 2.705419ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:51:52Z" - latency: 2.468106ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:50:52Z" - latency: 2.110436ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:49:52Z" - latency: 2.217436ms message: 'network-check-target-ip-10-0-141-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:48:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T00:15:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-121.ec2.internal uid: ee0a0832-740a-4a57-b20d-d7fcf8b59932 resourceVersion: "64301" uid: 29fafc50-8268-47e5-a23d-6b642a2bf6ed spec: sourcePod: network-check-source-7bc5b6bf85-2dnw6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T00:21:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.669µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:57:52Z" - latency: 2.896505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T00:57:52Z" - latency: 1.053707ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:56:52Z" - latency: 1.783557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T00:56:52Z" - latency: 1.009782ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:55:52Z" - latency: 1.706997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T00:55:52Z" - latency: 882.782µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:54:52Z" - latency: 1.683535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T00:54:52Z" - latency: 1.081093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T00:53:52Z" - latency: 2.062255ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T00:53:52Z" kind: List metadata: resourceVersion: ""