apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22721"
    uid: 08580c34-57a2-4e45-bf0d-d6f14a038eeb
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:06:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.457µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:06:45Z"
    - latency: 1.237903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 1.431147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 1.060822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 932.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 1.116798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 1.104434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22131"
    uid: 4496f593-0406-4ae0-8356-2e84db165b4a
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:05:45Z"
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.957502ms
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 6.792438ms
      message: 'load-balancer-api-external: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 4.689287ms
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 6.645377ms
      message: 'load-balancer-api-external: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 5.000048ms
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 8.6637ms
      message: 'load-balancer-api-external: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 4.727332ms
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 6.268194ms
      message: 'load-balancer-api-external: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 5.730334ms
      message: 'load-balancer-api-external: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 10.195002ms
      message: 'load-balancer-api-external: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:01:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22130"
    uid: 7e7c60d7-c977-4781-a55e-010b079a4bc3
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:05:45Z"
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.709628ms
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 6.827606ms
      message: 'load-balancer-api-internal: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 4.648005ms
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 6.549993ms
      message: 'load-balancer-api-internal: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 5.09531ms
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 8.618325ms
      message: 'load-balancer-api-internal: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 4.730355ms
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 6.336538ms
      message: 'load-balancer-api-internal: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 5.729859ms
      message: 'load-balancer-api-internal: tcp connection to adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 10.151753ms
      message: 'load-balancer-api-internal: resolved host name adfa306fdb90c492d928c67e05fa881e-737a4bad2bee7fcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:01:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-network-check-target-ip-10-0-128-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22719"
    uid: 45791fec-e2c4-4cea-b05d-4989327c1cd4
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:06:45Z"
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.40806ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:06:45Z"
    - latency: 2.260542ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 2.328995ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 2.042498ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 2.176275ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 2.07907ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 2.317797ms
      message: 'network-check-target-ip-10-0-128-154: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-network-check-target-ip-10-0-138-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22718"
    uid: 221bb002-2ddd-45c1-9b92-be1102b383ed
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:06:45Z"
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.15µs
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:06:45Z"
    - latency: 890.643µs
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 1.61958ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 1.114707ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 1.306224ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 741.842µs
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 1.680762ms
      message: 'network-check-target-ip-10-0-138-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-network-check-target-ip-10-0-140-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22720"
    uid: 45782914-944a-4dc1-a8bd-079e64e98c69
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:06:45Z"
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.298123ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:06:45Z"
    - latency: 2.363031ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 2.334111ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 2.343553ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 1.996847ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 2.194968ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 2.469533ms
      message: 'network-check-target-ip-10-0-140-38: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:00:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T14:59:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-137.ec2.internal
      uid: d59d8e14-2404-4166-bf24-3ac892ef40b3
    resourceVersion: "22129"
    uid: bb4146c5-ab50-4ad2-a7b9-65f55e43cbda
  spec:
    sourcePod: network-check-source-989f8b8dc-xpzpd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T15:05:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.378826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 1.795657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:05:45Z"
    - latency: 1.342813ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 1.832309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:04:45Z"
    - latency: 1.037847ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 1.932985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:03:45Z"
    - latency: 967.515µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 1.935089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:02:45Z"
    - latency: 935.225µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T15:01:45Z"
    - latency: 1.647213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T15:01:45Z"
kind: List
metadata:
  resourceVersion: ""