apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "11328"
    uid: a6210359-4d73-4f4e-a289-57e6eac45ecd
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "14883"
    uid: 96a24313-c7e8-41e6-a4ca-109f311e1630
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T07:10:23Z"
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.623801ms
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 7.445911ms
      message: 'load-balancer-api-external: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 5.421127ms
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 6.378847ms
      message: 'load-balancer-api-external: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 4.554685ms
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 7.025512ms
      message: 'load-balancer-api-external: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 5.009236ms
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 8.064201ms
      message: 'load-balancer-api-external: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 5.169687ms
      message: 'load-balancer-api-external: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:06:23Z"
    - latency: 9.560532ms
      message: 'load-balancer-api-external: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "14884"
    uid: f46f460c-63dd-432e-9eab-4fe503347ead
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T07:10:23Z"
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.685478ms
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 7.390287ms
      message: 'load-balancer-api-internal: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 4.939587ms
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 6.307222ms
      message: 'load-balancer-api-internal: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 4.991738ms
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 7.10424ms
      message: 'load-balancer-api-internal: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 6.500247ms
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 8.016696ms
      message: 'load-balancer-api-internal: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 5.215724ms
      message: 'load-balancer-api-internal: tcp connection to a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:06:23Z"
    - latency: 9.525907ms
      message: 'load-balancer-api-internal: resolved host name a7b3055fe9e344b639b3562352a6846c-653b74b40598295f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-128-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "11333"
    uid: 0cb5509c-e9e4-4cf7-abc8-888ecbb24c92
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-135-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "11334"
    uid: 9c32a493-bf20-4cb2-a515-2d79cc7f0cb9
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-network-check-target-ip-10-0-138-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "11335"
    uid: 782b1a3b-5235-4126-85fd-843bcc03c5f0
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T07:04:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-250.ec2.internal
      uid: 8441947d-b555-400f-90ba-5a71ec2f3a15
    resourceVersion: "14882"
    uid: b6622780-8658-426c-9196-05a36623225e
  spec:
    sourcePod: network-check-source-7d88cb55d8-j5hvl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T07:10:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 1.666422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:10:23Z"
    - latency: 884.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 1.594942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:09:23Z"
    - latency: 1.097922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 1.727598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:08:23Z"
    - latency: 764.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 1.587393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:07:23Z"
    - latency: 859.181µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T07:06:23Z"
    - latency: 1.585953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T07:06:23Z"
kind: List
metadata:
  resourceVersion: ""