apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "12428"
    uid: 3b6dd83f-66c9-472c-9bf8-943f1eeb4dc5
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:18:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:18:29Z"
    - latency: 1.151803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 1.094009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 1.086309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 1.127276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 1.054711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 1.064404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "11932"
    uid: 72faee5e-7106-444f-92b8-3e1724272213
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:17:29Z"
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.459486ms
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 9.009218ms
      message: 'load-balancer-api-external: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 9.924889ms
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 9.110594ms
      message: 'load-balancer-api-external: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 5.294943ms
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 12.157707ms
      message: 'load-balancer-api-external: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 4.692307ms
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 8.813621ms
      message: 'load-balancer-api-external: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 5.471892ms
      message: 'load-balancer-api-external: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 9.085264ms
      message: 'load-balancer-api-external: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "11933"
    uid: c9d9d107-6c92-406e-8ea8-520b824459b9
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:17:29Z"
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.838774ms
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 2.19809ms
      message: 'load-balancer-api-internal: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 3.250047ms
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 3.777363ms
      message: 'load-balancer-api-internal: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 10.631971ms
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 2.04483ms
      message: 'load-balancer-api-internal: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 3.516215ms
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 1.97343ms
      message: 'load-balancer-api-internal: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 4.829235ms
      message: 'load-balancer-api-internal: tcp connection to a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 3.771129ms
      message: 'load-balancer-api-internal: resolved host name a06eb29c6688947bbb0840c3f81c4b84-6076937c993464f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-136-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "12429"
    uid: 1c43c8ed-9650-4513-af50-06a4ad4d98ab
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:18:29Z"
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.265µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:18:29Z"
    - latency: 678.001µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 776.865µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 889.045µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 889.179µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 722.529µs
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 1.10391ms
      message: 'network-check-target-ip-10-0-136-29: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-137-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "12431"
    uid: 8db113ca-edda-4aed-b3c8-b10fd0bdb050
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:18:29Z"
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 709.859µs
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:18:29Z"
    - latency: 1.933919ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 828.649µs
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 1.982589ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 711.578µs
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 730.483µs
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 2.009389ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-ip-10-0-142-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "12430"
    uid: 70d11ef6-6046-4813-a024-a6863b822b66
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:18:29Z"
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.928461ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:18:29Z"
    - latency: 1.983244ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 1.835325ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 643.252µs
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 1.863514ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 1.453975ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 613.393µs
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:11:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-29.ec2.internal
      uid: b232798b-9a8b-41f0-8e86-22fef32fa9dd
    resourceVersion: "11934"
    uid: 9a095011-7f01-445f-b7af-b045416d7004
  spec:
    sourcePod: network-check-source-989f8b8dc-p7q47
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:17:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.411971ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 582.978µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:17:29Z"
    - latency: 2.367375ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 635.728µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:29Z"
    - latency: 2.266997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 481.676µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:29Z"
    - latency: 2.22597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 460.345µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:29Z"
    - latency: 2.097211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:29Z"
    - latency: 499.135µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:29Z"
kind: List
metadata:
  resourceVersion: ""