apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "23117"
    uid: e63e9e35-b9ab-48e6-a399-61704af0efed
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:35:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.332834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:07Z"
    - latency: 1.196322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 1.209327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 1.355871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 1.232962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 1.735076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 1.059112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "21534"
    uid: e2f0a5f8-8a9a-4e27-b5c5-85f6283f75e5
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:34:07Z"
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.609578ms
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 6.835628ms
      message: 'load-balancer-api-external: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 4.246406ms
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 7.886973ms
      message: 'load-balancer-api-external: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 4.80337ms
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 8.623295ms
      message: 'load-balancer-api-external: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 4.083281ms
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 7.511269ms
      message: 'load-balancer-api-external: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 6.07214ms
      message: 'load-balancer-api-external: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 7.989503ms
      message: 'load-balancer-api-external: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "21535"
    uid: 6705313f-3255-41a1-ab5b-d969eb0479ad
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:34:07Z"
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.684245ms
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 6.680972ms
      message: 'load-balancer-api-internal: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 6.157363ms
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 7.809637ms
      message: 'load-balancer-api-internal: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 4.753466ms
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 8.66019ms
      message: 'load-balancer-api-internal: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 4.057433ms
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 7.55401ms
      message: 'load-balancer-api-internal: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 6.859004ms
      message: 'load-balancer-api-internal: tcp connection to aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 7.875908ms
      message: 'load-balancer-api-internal: resolved host name aa2eaf941d25f4a4fa43eaa5cfe8e4b1-d7653b50fa16f596.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-128-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "23116"
    uid: 6d726659-37e7-4a67-baa8-05445e7b32d8
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:35:07Z"
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.378436ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:07Z"
    - latency: 2.41862ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 2.189019ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 2.293739ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 2.197831ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 2.394249ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 2.293715ms
      message: 'network-check-target-ip-10-0-128-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-136-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "23114"
    uid: 73de532a-1c69-45a3-be07-e7254d1bf006
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:35:07Z"
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109717ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:07Z"
    - latency: 1.036982ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 1.044606ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 1.098637ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 1.036241ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 1.326421ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 1.757194ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-138-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "23115"
    uid: 3a2a8b4d-9aac-44e4-8ec4-e5154c7bc732
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:35:07Z"
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.945773ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:35:07Z"
    - latency: 2.283316ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 2.124409ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 2.245952ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 2.141096ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 2.156287ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 2.243221ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:28:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: e198fc92-7ace-4054-be97-d09a71d44b11
    resourceVersion: "21533"
    uid: 7c719c19-6993-469c-899c-78b29e59e322
  spec:
    sourcePod: network-check-source-65bdbbff45-qndgm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:34:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014979ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 1.731364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:34:07Z"
    - latency: 953.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 1.973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:33:07Z"
    - latency: 980.598µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 2.337639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:32:07Z"
    - latency: 986.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 1.716602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:31:07Z"
    - latency: 1.028722ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:30:07Z"
    - latency: 1.944521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:30:07Z"
kind: List
metadata:
  resourceVersion: ""