apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "23080"
    uid: 20f00110-ac6e-49a4-8640-3af677082d7d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:09:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:09:32Z"
    - latency: 1.051178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 1.330842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 1.17662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 1.125668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 988.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 1.129839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "21875"
    uid: 33a3460e-c826-46e2-a9f5-0f15250e15d7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:08:32Z"
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.590171ms
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 8.820561ms
      message: 'load-balancer-api-external: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 6.100171ms
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 9.54792ms
      message: 'load-balancer-api-external: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 4.294375ms
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 9.420857ms
      message: 'load-balancer-api-external: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 4.916687ms
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 8.68936ms
      message: 'load-balancer-api-external: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 5.082974ms
      message: 'load-balancer-api-external: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 8.769745ms
      message: 'load-balancer-api-external: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "21876"
    uid: e5243a94-ccf7-4c9c-9d5f-48d8039712b6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:08:32Z"
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.554509ms
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 8.896138ms
      message: 'load-balancer-api-internal: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 6.045745ms
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 9.628444ms
      message: 'load-balancer-api-internal: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 4.991856ms
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 9.495954ms
      message: 'load-balancer-api-internal: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 4.907115ms
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 8.742267ms
      message: 'load-balancer-api-internal: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 5.167892ms
      message: 'load-balancer-api-internal: tcp connection to aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 8.689057ms
      message: 'load-balancer-api-internal: resolved host name aa276547ccd794da3af27aece0aafb5e-83dbcd350ee293b8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:04:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-network-check-target-ip-10-0-128-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "23078"
    uid: 792397f4-271a-4a79-8f51-a5879ff80ec0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:09:32Z"
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.415773ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:09:32Z"
    - latency: 2.084556ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 2.470308ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 2.17933ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 2.286592ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 2.279056ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 2.324239ms
      message: 'network-check-target-ip-10-0-128-156: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-network-check-target-ip-10-0-129-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "23077"
    uid: ce032534-3370-41d7-b0c7-4d54f35372ef
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:09:32Z"
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107789ms
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:09:32Z"
    - latency: 965.419µs
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 1.40868ms
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 1.400679ms
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 928.631µs
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 1.071073ms
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 1.553255ms
      message: 'network-check-target-ip-10-0-129-43: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-network-check-target-ip-10-0-139-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "23079"
    uid: 4fa0ee80-8102-4477-9631-38ee674661cf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:09:32Z"
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.370206ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:09:32Z"
    - latency: 1.740973ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 2.268909ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 2.065441ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 2.053045ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 1.894313ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 2.279132ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:02:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-43.ec2.internal
      uid: 7ef99d41-40d1-4f6e-89d9-a65c5363bd26
    resourceVersion: "21874"
    uid: 4bc49f06-1396-4206-a67a-772fcb9f8e1d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-zm8xj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T21:08:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 1.951231ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:08:32Z"
    - latency: 970.206µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 2.403302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:07:32Z"
    - latency: 847.568µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 1.749603ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:06:32Z"
    - latency: 1.105061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 1.842605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:05:32Z"
    - latency: 1.034056ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T21:04:32Z"
    - latency: 1.78279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T21:04:32Z"
kind: List
metadata:
  resourceVersion: ""