apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "50522" uid: a1188e2a-0048-46ac-8770-18c6240e454e spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T04:20:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 902.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 1.126366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 982.067µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 1.3088ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 912.776µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:44:47Z" - latency: 1.137829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:43:47Z" - latency: 1.457263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:42:47Z" - latency: 1.11729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:47Z" - latency: 1.080433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:47Z" - latency: 852.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "51121" uid: e6ad720b-9d69-427f-b80f-84a8a1e7980a spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:19:47Z" message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.854756ms message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:49:47Z" - latency: 8.338194ms message: 'load-balancer-api-external: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:49:47Z" - latency: 4.987631ms message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 7.427297ms message: 'load-balancer-api-external: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:48:47Z" - latency: 4.785934ms message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 7.700561ms message: 'load-balancer-api-external: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:47:47Z" - latency: 5.206336ms message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 7.832762ms message: 'load-balancer-api-external: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:46:47Z" - latency: 5.07992ms message: 'load-balancer-api-external: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 6.660303ms message: 'load-balancer-api-external: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:45:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "51122" uid: af42245c-c7e0-4b55-b975-400fbd941317 spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:19:47Z" message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.350555ms message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:49:47Z" - latency: 8.378623ms message: 'load-balancer-api-internal: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:49:47Z" - latency: 4.950273ms message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 7.452155ms message: 'load-balancer-api-internal: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:48:47Z" - latency: 5.30177ms message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 7.645712ms message: 'load-balancer-api-internal: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:47:47Z" - latency: 4.905808ms message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 7.876314ms message: 'load-balancer-api-internal: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:46:47Z" - latency: 5.105636ms message: 'load-balancer-api-internal: tcp connection to add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 6.699606ms message: 'load-balancer-api-internal: resolved host name add7916d713764ca5bf9dab08d0e81ef-39f410b37eff4d71.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:45:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-network-check-target-ip-10-0-130-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "50519" uid: 227e970c-509e-4ede-ad5e-5835391a4e4c spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:20:47Z" message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.471113ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 799.942µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 853.526µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 879.665µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 848.32µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:44:47Z" - latency: 922.056µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:43:47Z" - latency: 974.066µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:42:47Z" - latency: 921.208µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:47Z" - latency: 957.343µs message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:47Z" - latency: 1.407177ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-network-check-target-ip-10-0-130-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "50521" uid: a124bc49-4ddf-49d5-b13e-d5a06902bd19 spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:20:47Z" message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.500867ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 1.828337ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 2.402925ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 2.519158ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 2.54457ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:44:47Z" - latency: 2.165779ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:43:47Z" - latency: 2.478972ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:42:47Z" - latency: 2.491336ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:47Z" - latency: 2.269646ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:47Z" - latency: 2.454906ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-network-check-target-ip-10-0-142-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "50520" uid: b7bd5ac6-ee3e-45f7-a319-e469207763ff spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:20:47Z" message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.474451ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 2.295678ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 2.295813ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 2.359104ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 2.437826ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:44:47Z" - latency: 2.30728ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:43:47Z" - latency: 2.537058ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:42:47Z" - latency: 2.558061ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:47Z" - latency: 1.896813ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:47Z" - latency: 2.381964ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:13:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-153.ec2.internal uid: 93d84cd8-bda0-4586-a76f-7679f98f26fb resourceVersion: "51120" uid: 16ca1470-bba6-4187-8050-71b6cdbef3ac spec: sourcePod: network-check-source-989f8b8dc-5lk5q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T04:19:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.169µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:49:47Z" - latency: 1.902404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:49:47Z" - latency: 1.00805ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:48:47Z" - latency: 2.455145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:48:47Z" - latency: 791.625µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:47:47Z" - latency: 1.51239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:47:47Z" - latency: 842.488µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:46:47Z" - latency: 2.079023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:46:47Z" - latency: 1.338552ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:45:47Z" - latency: 2.053294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:45:47Z" kind: List metadata: resourceVersion: ""