apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "15175"
    uid: 5e1925a0-8813-42f4-a33e-5eeaea20acfa
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:07:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:07:34Z"
    - latency: 863.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 835.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 828.811µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 861.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 1.202903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 1.014542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "14712"
    uid: 649df4d2-051e-454d-a4eb-8f35c51d9933
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:34Z"
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.888611ms
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 9.50247ms
      message: 'load-balancer-api-external: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 4.521813ms
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 10.033298ms
      message: 'load-balancer-api-external: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 5.371689ms
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 7.550952ms
      message: 'load-balancer-api-external: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 5.097557ms
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 6.580713ms
      message: 'load-balancer-api-external: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 7.202592ms
      message: 'load-balancer-api-external: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 6.146222ms
      message: 'load-balancer-api-external: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "14711"
    uid: c3096294-be77-40a4-9087-9f9750c1d229
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:34Z"
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.945871ms
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 9.39443ms
      message: 'load-balancer-api-internal: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 5.926253ms
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 10.004091ms
      message: 'load-balancer-api-internal: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 5.408585ms
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 7.525181ms
      message: 'load-balancer-api-internal: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 5.29208ms
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 6.48826ms
      message: 'load-balancer-api-internal: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 6.843555ms
      message: 'load-balancer-api-internal: tcp connection to ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 6.025223ms
      message: 'load-balancer-api-internal: resolved host name ad3c06190936649ec999cdf4d426957c-6927e663b2b4fa89.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-network-check-target-ip-10-0-131-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "15174"
    uid: 6237c7fb-cdd1-4c20-9dc2-fc4c9e568481
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:07:34Z"
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.469698ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:07:34Z"
    - latency: 2.237977ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 2.325679ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 2.20067ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 2.209793ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 2.182312ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 2.555093ms
      message: 'network-check-target-ip-10-0-131-163: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-network-check-target-ip-10-0-136-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "15173"
    uid: 7a605ef6-4c6e-4264-92da-6fd7493431e8
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:07:34Z"
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.370203ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:07:34Z"
    - latency: 2.121883ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 2.184912ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 2.149232ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 2.145692ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 2.042302ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 2.220172ms
      message: 'network-check-target-ip-10-0-136-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-network-check-target-ip-10-0-139-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "15172"
    uid: f65d5f5b-406a-4922-8bea-ef05f6fe6894
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:07:34Z"
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.307µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:07:34Z"
    - latency: 862.36µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 849.638µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 959.793µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 968.868µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 752.432µs
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 1.706658ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T11:00:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-80.ec2.internal
      uid: 1eb90d79-c015-4d48-abc6-dade82a4fba9
    resourceVersion: "14710"
    uid: a01faecd-2c28-4b4b-950e-4eaa8ef95c37
  spec:
    sourcePod: network-check-source-685456655f-h8954
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T11:06:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.278983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 1.559489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:06:34Z"
    - latency: 876.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 1.71749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:05:34Z"
    - latency: 920.538µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 1.864553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:04:34Z"
    - latency: 1.00857ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 1.56793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:03:34Z"
    - latency: 1.125561ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T11:02:34Z"
    - latency: 1.575676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T11:02:34Z"
kind: List
metadata:
  resourceVersion: ""