apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "76429" uid: 2feabe2f-ff64-410b-bde1-c9591b5b6090 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T12:35:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.82µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:31:47Z" - latency: 1.193012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:30:47Z" - latency: 857.309µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:29:47Z" - latency: 935.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 966.714µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 1.23984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 1.394157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 945.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 819.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:23:47Z" - latency: 1.542146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "72767" uid: 63a57c5e-57cf-4700-a007-0309a1058cc5 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T12:34:47Z" message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.332109ms message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 12.301207ms message: 'load-balancer-api-external: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:28:47Z" - latency: 3.639464ms message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 10.005111ms message: 'load-balancer-api-external: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:27:47Z" - latency: 4.534183ms message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 8.656079ms message: 'load-balancer-api-external: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:26:47Z" - latency: 4.826298ms message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 9.488657ms message: 'load-balancer-api-external: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:25:47Z" - latency: 4.89502ms message: 'load-balancer-api-external: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 8.418493ms message: 'load-balancer-api-external: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:24:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "72766" uid: 0b1238b2-4459-4d03-b14f-84bee4988f60 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T12:34:47Z" message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.28274ms message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 12.42231ms message: 'load-balancer-api-internal: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:28:47Z" - latency: 5.496832ms message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 10.114632ms message: 'load-balancer-api-internal: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:27:47Z" - latency: 4.535103ms message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 8.814278ms message: 'load-balancer-api-internal: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:26:47Z" - latency: 4.789329ms message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 9.564098ms message: 'load-balancer-api-internal: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:25:47Z" - latency: 4.921128ms message: 'load-balancer-api-internal: tcp connection to a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 8.633622ms message: 'load-balancer-api-internal: resolved host name a8c9bf444bdfe4814a356eb59d1e6e10-a67130a713cd04fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T13:24:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-network-check-target-ip-10-0-129-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "76427" uid: d5875a72-f6ec-4a59-aef8-43bb292585e3 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T12:35:47Z" message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.135881ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:31:47Z" - latency: 2.227492ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:30:47Z" - latency: 2.297566ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:29:47Z" - latency: 2.224079ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 2.992933ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 2.322484ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 2.565469ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 2.558111ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 2.370034ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:23:47Z" - latency: 2.314776ms message: 'network-check-target-ip-10-0-129-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-network-check-target-ip-10-0-131-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "76428" uid: 59cb882b-634b-487f-82b4-bf74141f1a5d spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T12:35:47Z" message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.987511ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:31:47Z" - latency: 2.142964ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:30:47Z" - latency: 1.82228ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:29:47Z" - latency: 2.188921ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 3.060247ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 2.088747ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 2.276887ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 2.153106ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 1.936945ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:23:47Z" - latency: 1.837578ms message: 'network-check-target-ip-10-0-131-210: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-network-check-target-ip-10-0-134-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "76426" uid: 1aabb2d3-8ed4-45f7-8b2b-327de4fca5e5 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T12:35:47Z" message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 824.81µs message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:31:47Z" - latency: 1.191598ms message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:30:47Z" - latency: 1.03265ms message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:29:47Z" - latency: 1.13137ms message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 1.05213ms message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 893.249µs message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 1.097796ms message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 869.473µs message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 926.538µs message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:23:47Z" - latency: 823.68µs message: 'network-check-target-ip-10-0-134-119: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:22:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T12:28:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-119-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-119.ec2.internal uid: 0623006f-ed2c-4b0c-8c4b-6fcd09f94137 resourceVersion: "72765" uid: c153854a-486b-4e0f-8bd3-3240ae047fe6 spec: sourcePod: network-check-source-7bc5b6bf85-4lhxw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T12:34:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:28:47Z" - latency: 1.841265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T13:28:47Z" - latency: 1.021627ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:27:47Z" - latency: 2.792926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T13:27:47Z" - latency: 1.233315ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:26:47Z" - latency: 2.071635ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T13:26:47Z" - latency: 1.202329ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:25:47Z" - latency: 1.944817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T13:25:47Z" - latency: 1.431779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T13:24:47Z" - latency: 2.038085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T13:24:47Z" kind: List metadata: resourceVersion: ""