apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "23684"
    uid: f7dde30a-533e-4d2a-a678-90189c5c1be3
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:52:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:04Z"
    - latency: 911.268µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 874.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 1.048749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 1.024409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 989.845µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 1.70019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "22251"
    uid: 0e86b501-18db-496e-a508-bd573df8162e
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:51:04Z"
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.500741ms
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 8.268384ms
      message: 'load-balancer-api-external: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 4.811238ms
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 7.886197ms
      message: 'load-balancer-api-external: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 13.288379ms
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 7.95677ms
      message: 'load-balancer-api-external: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 4.589966ms
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 8.628121ms
      message: 'load-balancer-api-external: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 6.534056ms
      message: 'load-balancer-api-external: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 7.485993ms
      message: 'load-balancer-api-external: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "22252"
    uid: 6414d348-c640-4ca5-a381-867c4decb83d
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:51:04Z"
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.62411ms
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 8.350972ms
      message: 'load-balancer-api-internal: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 3.898531ms
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 7.979661ms
      message: 'load-balancer-api-internal: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 4.870627ms
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 7.994058ms
      message: 'load-balancer-api-internal: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 4.565383ms
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 8.570808ms
      message: 'load-balancer-api-internal: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 6.516748ms
      message: 'load-balancer-api-internal: tcp connection to a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 7.535764ms
      message: 'load-balancer-api-internal: resolved host name a133b73da6d4c470584ec157066f3d36-f93bce0be34e24d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-network-check-target-ip-10-0-129-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "23681"
    uid: 1a551bda-5e36-45ca-aec9-53f8306513f8
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:52:04Z"
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.14µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:04Z"
    - latency: 857.776µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 858.182µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 911.509µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 752.922µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 828.986µs
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 1.254167ms
      message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-network-check-target-ip-10-0-130-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "23682"
    uid: e3b70160-ab4a-4453-9ce7-f63488e2fd94
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:52:04Z"
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.403667ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:04Z"
    - latency: 1.89878ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 2.160429ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 2.776003ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 2.317857ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 2.134742ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 2.064831ms
      message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-network-check-target-ip-10-0-143-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "23683"
    uid: 244711e9-9402-4bb0-84e2-07c447333c7d
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:52:04Z"
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272234ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:52:04Z"
    - latency: 1.685417ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 1.954903ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 2.01997ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 1.965504ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 1.976136ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 2.121587ms
      message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:46:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:45:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-36.ec2.internal
      uid: 21b2887b-0e34-4c9e-b83b-d9edd175dafe
    resourceVersion: "22250"
    uid: aa2402ac-1bbd-4409-8232-2f15eaebebb3
  spec:
    sourcePod: network-check-source-685456655f-fd99q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:51:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 1.714408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:51:04Z"
    - latency: 788.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 1.876369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:50:04Z"
    - latency: 1.335939ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 1.748484ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:49:04Z"
    - latency: 1.098437ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 1.95319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:48:04Z"
    - latency: 1.130087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:47:04Z"
    - latency: 1.929949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T17:47:04Z"
kind: List
metadata:
  resourceVersion: ""