apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "23647"
    uid: 8831f39b-57cc-4551-8a1f-14cfe6b7bedd
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:02:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 798.528µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:12Z"
    - latency: 1.083182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:12Z"
    - latency: 1.171416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:12Z"
    - latency: 993.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:12Z"
    - latency: 858.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:58:12Z"
    - latency: 1.374429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:57:12Z"
    - latency: 1.024792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:56:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "27518"
    uid: 401ea798-7bbc-4b50-ad8c-3b93ac913ecf
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:12Z"
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.587397ms
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 8.88095ms
      message: 'load-balancer-api-external: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 5.025612ms
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 9.670856ms
      message: 'load-balancer-api-external: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 5.375649ms
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 8.411172ms
      message: 'load-balancer-api-external: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 3.72434ms
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 8.0396ms
      message: 'load-balancer-api-external: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 4.714164ms
      message: 'load-balancer-api-external: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:12Z"
    - latency: 8.725604ms
      message: 'load-balancer-api-external: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:03:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "27517"
    uid: 361c761d-5e15-47c7-8ee3-5704172a9f5c
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:12Z"
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.627221ms
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 8.849369ms
      message: 'load-balancer-api-internal: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 5.021351ms
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 9.635191ms
      message: 'load-balancer-api-internal: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 5.373148ms
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 8.376332ms
      message: 'load-balancer-api-internal: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 3.688932ms
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 8.005884ms
      message: 'load-balancer-api-internal: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 4.745031ms
      message: 'load-balancer-api-internal: tcp connection to a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:12Z"
    - latency: 8.733401ms
      message: 'load-balancer-api-internal: resolved host name a884ed79bec504af4a6c5d7d60078b0b-c5cbc1e5aca9d57c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:03:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-network-check-target-ip-10-0-131-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "23646"
    uid: 9227ffb3-9226-4424-bea1-4edaf1e9eac8
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:02:12Z"
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175081ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:12Z"
    - latency: 5.38756ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:12Z"
    - latency: 2.193971ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:12Z"
    - latency: 2.19708ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:12Z"
    - latency: 2.171019ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:58:12Z"
    - latency: 2.171783ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:57:12Z"
    - latency: 2.318143ms
      message: 'network-check-target-ip-10-0-131-100: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:56:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-network-check-target-ip-10-0-133-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "23645"
    uid: 912c3d33-6725-46fd-b85b-60926ba65e23
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:02:12Z"
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211994ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:12Z"
    - latency: 2.27201ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:12Z"
    - latency: 2.310307ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:12Z"
    - latency: 2.115189ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:12Z"
    - latency: 2.311711ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:58:12Z"
    - latency: 2.449227ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:57:12Z"
    - latency: 2.332548ms
      message: 'network-check-target-ip-10-0-133-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:56:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-network-check-target-ip-10-0-138-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "23644"
    uid: 6a920452-6849-4bc3-8ff8-028e14b4de53
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:02:12Z"
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 755.309µs
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:02:12Z"
    - latency: 975.463µs
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:01:12Z"
    - latency: 960.844µs
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:00:12Z"
    - latency: 868.43µs
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:59:12Z"
    - latency: 1.367831ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:58:12Z"
    - latency: 1.849034ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:57:12Z"
    - latency: 1.279024ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:56:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T14:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-28.ec2.internal
      uid: 2369380e-e7a2-45e7-82dd-614e7be64581
    resourceVersion: "27516"
    uid: 1a0155c9-0282-4e1c-b2da-bef14725f452
  spec:
    sourcePod: network-check-source-7cbc45fddc-2kqb8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:01:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 2.004122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:07:12Z"
    - latency: 946.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 1.993744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:06:12Z"
    - latency: 806.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 1.750991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:05:12Z"
    - latency: 831.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 1.748987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:04:12Z"
    - latency: 1.211142ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T15:03:12Z"
    - latency: 1.807108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T15:03:12Z"
kind: List
metadata:
  resourceVersion: ""