apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14543"
    uid: 2ffb79c6-e1a3-4f97-af05-2e1e01edcea0
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:30:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.184µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:40Z"
    - latency: 838.727µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 1.056565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 1.225431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 1.123091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 1.433136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 981.601µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14203"
    uid: 7da1a2da-b77c-443f-a3de-a5fce1d85500
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:29:40Z"
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.317341ms
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 6.660603ms
      message: 'load-balancer-api-external: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 4.666139ms
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 7.085891ms
      message: 'load-balancer-api-external: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 4.987788ms
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 7.216099ms
      message: 'load-balancer-api-external: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 5.6575ms
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 8.662911ms
      message: 'load-balancer-api-external: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 4.28304ms
      message: 'load-balancer-api-external: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 5.286116ms
      message: 'load-balancer-api-external: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:25:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14202"
    uid: 6ac36c74-9a12-48b2-9259-c55ea07920fe
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:29:40Z"
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.277652ms
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 6.752488ms
      message: 'load-balancer-api-internal: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 4.077485ms
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 7.15425ms
      message: 'load-balancer-api-internal: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 4.986896ms
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 7.165173ms
      message: 'load-balancer-api-internal: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 5.642954ms
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 8.633007ms
      message: 'load-balancer-api-internal: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 4.251005ms
      message: 'load-balancer-api-internal: tcp connection to a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 6.078439ms
      message: 'load-balancer-api-internal: resolved host name a794c6b70613f4f7f9354e0e675e3676-c1cf0d81ab83f138.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:25:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-network-check-target-ip-10-0-134-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14542"
    uid: 892ded4e-ddc3-47de-a134-7fadfc6b4a74
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:30:40Z"
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.186748ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:40Z"
    - latency: 2.08147ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 1.727402ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 1.935647ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 1.932168ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 1.801278ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 2.042842ms
      message: 'network-check-target-ip-10-0-134-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-network-check-target-ip-10-0-138-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14540"
    uid: 681802df-71af-4a3f-a0b1-e201fc0d1069
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:30:40Z"
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.243976ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:40Z"
    - latency: 888.35µs
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 957.767µs
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 1.2352ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 970.694µs
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 984.11µs
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 1.446705ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-network-check-target-ip-10-0-143-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14541"
    uid: a978973b-50d5-454c-a67d-3caa87c24f73
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:30:40Z"
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.129748ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:30:40Z"
    - latency: 2.067458ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 2.197861ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 2.150756ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 2.218246ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 2.433091ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 2.280992ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-235.ec2.internal
      uid: c2f5a061-bce8-479f-a66c-7f05af194bae
    resourceVersion: "14201"
    uid: 92041bd9-e41c-4bc6-a50e-4f6b366546d2
  spec:
    sourcePod: network-check-source-7cbc45fddc-g9cbs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T08:29:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 1.70532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:29:40Z"
    - latency: 866.772µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 1.694625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:28:40Z"
    - latency: 1.027385ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 1.936935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:27:40Z"
    - latency: 764.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 1.840598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:26:40Z"
    - latency: 1.190972ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:25:40Z"
    - latency: 1.162556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T08:25:40Z"
kind: List
metadata:
  resourceVersion: ""