apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "15160"
    uid: 1d84811f-29e8-4c07-a2e8-556b03e41126
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:13:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 726.608µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:13:07Z"
    - latency: 960.983µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 756.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 754.914µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 4.399281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 993.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 713.578µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "14828"
    uid: dc5d74b4-52fb-4b98-be16-6b3f94a8b2a9
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:12:07Z"
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.422071ms
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 7.724065ms
      message: 'load-balancer-api-external: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 4.877963ms
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 7.418512ms
      message: 'load-balancer-api-external: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 3.346317ms
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 9.377374ms
      message: 'load-balancer-api-external: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 4.05101ms
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 11.794983ms
      message: 'load-balancer-api-external: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 4.870529ms
      message: 'load-balancer-api-external: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 9.143932ms
      message: 'load-balancer-api-external: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "14827"
    uid: fc440427-1861-4f97-8369-2ea6e5fc8f25
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:12:07Z"
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.40837ms
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 7.810768ms
      message: 'load-balancer-api-internal: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 4.870766ms
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 7.495227ms
      message: 'load-balancer-api-internal: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 4.130755ms
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 9.450675ms
      message: 'load-balancer-api-internal: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 4.092616ms
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 11.269609ms
      message: 'load-balancer-api-internal: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 4.840968ms
      message: 'load-balancer-api-internal: tcp connection to aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 9.225863ms
      message: 'load-balancer-api-internal: resolved host name aa8ec1e3b3b48495a95e29ae13f3a5a6-8db1ea2c2cd1fcf6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-network-check-target-ip-10-0-133-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "15157"
    uid: 4c6b4234-611c-48aa-9947-e5897460daab
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:13:07Z"
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.472311ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:13:07Z"
    - latency: 1.869292ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 1.431728ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 1.786944ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 4.922926ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 1.696156ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 2.101698ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-network-check-target-ip-10-0-138-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "15159"
    uid: 18341af7-732a-411f-83cf-9ea8f153cfe3
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:13:07Z"
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.54µs
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:13:07Z"
    - latency: 865.089µs
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 948.173µs
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 870.034µs
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 5.73059ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 1.287604ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 1.145964ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-network-check-target-ip-10-0-143-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "15158"
    uid: d8f777a1-fd50-4ff7-98c4-801ac8162b7c
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:13:07Z"
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.82302ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:13:07Z"
    - latency: 2.056251ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 1.876207ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 2.176717ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 5.021041ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 1.996499ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 2.340188ms
      message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:07:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T17:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-126-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-126.ec2.internal
      uid: 1cc72ebd-bcb8-48ee-913e-33d37ca4fc1f
    resourceVersion: "14825"
    uid: 686efb31-28df-4f0c-af44-b41cfaa39df5
  spec:
    sourcePod: network-check-source-56d84b9f44-f92fd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T17:12:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052934ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 1.733263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:12:07Z"
    - latency: 906.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 1.452936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:11:07Z"
    - latency: 1.20848ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 1.635062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:10:07Z"
    - latency: 807.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 5.65939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:09:07Z"
    - latency: 997.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T17:08:07Z"
    - latency: 1.689073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T17:08:07Z"
kind: List
metadata:
  resourceVersion: ""