apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "18033"
    uid: a49e324e-618b-44bb-abb1-93f948bbd65f
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:16:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.730097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:16:45Z"
    - latency: 965.254µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 1.41965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 1.333798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 920.054µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 1.422853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 1.197413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "17575"
    uid: 6f92f4b3-eaef-4717-8219-c39822f4bfbb
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:15:45Z"
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.942555ms
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 7.260802ms
      message: 'load-balancer-api-external: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 5.104788ms
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 9.411369ms
      message: 'load-balancer-api-external: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 5.456817ms
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 8.89178ms
      message: 'load-balancer-api-external: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 4.197201ms
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 9.137144ms
      message: 'load-balancer-api-external: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 4.772429ms
      message: 'load-balancer-api-external: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 9.634419ms
      message: 'load-balancer-api-external: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "17574"
    uid: 8eec80a7-c5fb-4758-9530-2e224531d967
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:15:45Z"
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.561293ms
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 7.177602ms
      message: 'load-balancer-api-internal: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 5.09342ms
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 9.340554ms
      message: 'load-balancer-api-internal: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 5.433299ms
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 8.992504ms
      message: 'load-balancer-api-internal: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 4.152407ms
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 9.066879ms
      message: 'load-balancer-api-internal: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 5.309101ms
      message: 'load-balancer-api-internal: tcp connection to a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 9.574172ms
      message: 'load-balancer-api-internal: resolved host name a452956c887e14445844e8ffbddee702-0da4bae6ee35e1fc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-129-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "18030"
    uid: 52c3d310-6b9a-4147-a128-a09e17a09142
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:16:45Z"
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.699µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:16:45Z"
    - latency: 902.139µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 949.218µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 1.62839ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 1.026859ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 681.01µs
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 1.327744ms
      message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-135-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "18031"
    uid: ab1936b3-c350-4415-be34-a18e39805d78
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:16:45Z"
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286696ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:16:45Z"
    - latency: 2.108361ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 2.251251ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 2.36584ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 2.038862ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 2.219846ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 2.844317ms
      message: 'network-check-target-ip-10-0-135-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-ip-10-0-142-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "18032"
    uid: 47c7e4f0-5daf-4569-be83-7f5429fe743a
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:16:45Z"
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.233249ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:16:45Z"
    - latency: 2.308016ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 2.03839ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 2.093394ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 1.955432ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 2.15236ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 1.912624ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:09:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-139.ec2.internal
      uid: d3636bdf-c0b7-479f-b194-cb8efa4173f8
    resourceVersion: "17573"
    uid: f3cd3ba7-3430-4726-aea4-138971c71795
  spec:
    sourcePod: network-check-source-989f8b8dc-ddfq4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T19:15:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.038219ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 1.775351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:45Z"
    - latency: 1.277179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 2.049658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:45Z"
    - latency: 1.27414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 2.129595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:45Z"
    - latency: 1.098838ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 1.927933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:45Z"
    - latency: 914.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:45Z"
    - latency: 2.337451ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:45Z"
kind: List
metadata:
  resourceVersion: ""