apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14458"
    uid: 6ddd6cbf-cdaa-4e7d-ba35-b6f9b06ce28d
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:32Z"
    - latency: 1.352123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 929.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 1.041375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 1.240717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 1.483089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 960.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14109"
    uid: d9262e31-456a-4869-863f-f7e2807be4d3
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:32Z"
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.911544ms
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 8.785208ms
      message: 'load-balancer-api-external: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 3.703981ms
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 8.966316ms
      message: 'load-balancer-api-external: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 4.15515ms
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 6.723593ms
      message: 'load-balancer-api-external: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 3.985384ms
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 12.744665ms
      message: 'load-balancer-api-external: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 5.755635ms
      message: 'load-balancer-api-external: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 8.782112ms
      message: 'load-balancer-api-external: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14108"
    uid: 3a909e1b-18da-4749-93d8-37ace4c042d1
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:32Z"
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.856334ms
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 8.831675ms
      message: 'load-balancer-api-internal: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 5.085293ms
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 8.997967ms
      message: 'load-balancer-api-internal: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 4.227593ms
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 6.628034ms
      message: 'load-balancer-api-internal: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 2.888479ms
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 12.764222ms
      message: 'load-balancer-api-internal: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 4.878592ms
      message: 'load-balancer-api-internal: tcp connection to adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 8.824392ms
      message: 'load-balancer-api-internal: resolved host name adc796cd5eec5495e9bec63ec44a5f06-226ec180b59dfe4a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-128-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14457"
    uid: f5846243-e831-4333-a61c-94422458adae
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:32Z"
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.558066ms
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:32Z"
    - latency: 1.19549ms
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 861.987µs
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 876.396µs
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 862.026µs
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 853.226µs
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 1.164951ms
      message: 'network-check-target-ip-10-0-128-56: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-130-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14455"
    uid: 50a3ec25-a047-4162-861b-8d08fcdddda7
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:32Z"
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.132561ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:32Z"
    - latency: 2.173957ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 2.024155ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 2.341168ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 2.279284ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 2.40646ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 2.147983ms
      message: 'network-check-target-ip-10-0-130-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-ip-10-0-133-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14456"
    uid: 726ddffa-a0a2-4583-9fc8-831274d29c13
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:08:32Z"
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.210737ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:08:32Z"
    - latency: 2.197646ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 2.224757ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 2.34044ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 2.196481ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 2.162398ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 2.287233ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-56.ec2.internal
      uid: 6a4f2521-6e70-4125-a769-b0cd12401b88
    resourceVersion: "14106"
    uid: f6bf2159-d191-4cd2-8185-6ed7856422d9
  spec:
    sourcePod: network-check-source-7d88cb55d8-2lq46
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:07:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.961µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 1.675551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:07:32Z"
    - latency: 1.149052ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 1.805094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:06:32Z"
    - latency: 793.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 1.728289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:05:32Z"
    - latency: 899.059µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 2.092613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:04:32Z"
    - latency: 932.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:03:32Z"
    - latency: 1.554365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:03:32Z"
kind: List
metadata:
  resourceVersion: ""