apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "22688"
    uid: 3bdb986b-d752-4fd8-9a20-b511e4888296
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:05:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.417384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:05:10Z"
    - latency: 879.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 1.218202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 1.446863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 954.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 1.398315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 966.345µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "21567"
    uid: 3bb5fbd9-e6ba-4b6e-8379-f6506e40047f
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:04:10Z"
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.899091ms
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 8.480584ms
      message: 'load-balancer-api-external: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 3.642755ms
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 8.037322ms
      message: 'load-balancer-api-external: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 3.847903ms
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 8.525796ms
      message: 'load-balancer-api-external: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 5.674552ms
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 8.995015ms
      message: 'load-balancer-api-external: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 4.857035ms
      message: 'load-balancer-api-external: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 9.815431ms
      message: 'load-balancer-api-external: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "21566"
    uid: fcfd23a2-7d87-45dd-9e4c-b174930d4982
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:04:10Z"
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.908647ms
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 8.585634ms
      message: 'load-balancer-api-internal: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 4.998721ms
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 8.170484ms
      message: 'load-balancer-api-internal: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 5.91125ms
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 8.741567ms
      message: 'load-balancer-api-internal: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 5.66932ms
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 8.952791ms
      message: 'load-balancer-api-internal: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 4.903134ms
      message: 'load-balancer-api-internal: tcp connection to a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 9.785239ms
      message: 'load-balancer-api-internal: resolved host name a0b796c22382647c892e953860eef6d8-340b2fae480c0130.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-network-check-target-ip-10-0-129-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "22685"
    uid: de7aee79-94ae-42d0-adc2-1d93dac1e50b
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:05:10Z"
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036584ms
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:05:10Z"
    - latency: 882.859µs
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 878.327µs
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 1.989038ms
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 1.009419ms
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 1.71085ms
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 1.707446ms
      message: 'network-check-target-ip-10-0-129-159: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-network-check-target-ip-10-0-136-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "22687"
    uid: c53912ab-24f8-4c15-96f5-f69432725691
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:05:10Z"
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.387429ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:05:10Z"
    - latency: 1.939244ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 2.014978ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 2.72638ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 2.07282ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 3.272128ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 2.446311ms
      message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-network-check-target-ip-10-0-140-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "22686"
    uid: 217b94bb-2f50-4754-b209-ded179f7ae17
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:05:10Z"
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306205ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:05:10Z"
    - latency: 2.119308ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 2.0577ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 2.75013ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 2.491515ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 2.374689ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 2.354662ms
      message: 'network-check-target-ip-10-0-140-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:59:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T00:58:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-159.ec2.internal
      uid: cfea8332-7a99-4bbf-8c25-a93a0701c4fc
    resourceVersion: "21565"
    uid: c58380ee-a168-4ccd-a62e-44dc8121dc9b
  spec:
    sourcePod: network-check-source-685456655f-lkfhm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T01:04:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 851.9µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 1.819493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:04:10Z"
    - latency: 889.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 1.986107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:03:10Z"
    - latency: 983.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 3.02683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:02:10Z"
    - latency: 993.111µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 2.110229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:01:10Z"
    - latency: 1.642555ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T01:00:10Z"
    - latency: 2.299325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T01:00:10Z"
kind: List
metadata:
  resourceVersion: ""