apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14488"
    uid: 6e1e2ee7-04bc-41c4-93b0-61939fe436d7
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:27:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:27:43Z"
    - latency: 893.529µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 1.107262ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 1.062024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 1.124704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 1.009228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 1.016861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14076"
    uid: 561141ed-7dbb-41b3-8207-c0bcd8b4bbc0
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:26:43Z"
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.17544ms
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 8.407929ms
      message: 'load-balancer-api-external: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 4.284015ms
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 13.920276ms
      message: 'load-balancer-api-external: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 4.811911ms
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 7.886887ms
      message: 'load-balancer-api-external: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 5.815103ms
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 8.953502ms
      message: 'load-balancer-api-external: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 4.748321ms
      message: 'load-balancer-api-external: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 8.072337ms
      message: 'load-balancer-api-external: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:22:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14075"
    uid: 628d287d-600e-4517-9e22-c68df4f7f13d
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:26:43Z"
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.525128ms
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 8.4298ms
      message: 'load-balancer-api-internal: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 6.021788ms
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 13.953221ms
      message: 'load-balancer-api-internal: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 6.481868ms
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 7.937979ms
      message: 'load-balancer-api-internal: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 5.610776ms
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 8.967488ms
      message: 'load-balancer-api-internal: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 5.747309ms
      message: 'load-balancer-api-internal: tcp connection to ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 8.091271ms
      message: 'load-balancer-api-internal: resolved host name ae996a2b98cb74ff68aae569b51533cb-2986da764c573486.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:22:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-network-check-target-ip-10-0-129-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14485"
    uid: e52639c0-887f-4f84-9a32-a5f2df35e4b0
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:27:43Z"
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.617055ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:27:43Z"
    - latency: 1.630386ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 1.503462ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 1.598576ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 1.551616ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 1.525998ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 1.594867ms
      message: 'network-check-target-ip-10-0-129-231: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-network-check-target-ip-10-0-136-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14487"
    uid: cef88242-952b-4b68-8283-8fb426546c98
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:27:43Z"
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.762093ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:27:43Z"
    - latency: 914.864µs
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 1.553225ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 825.12µs
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 1.399418ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 1.00728ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 1.317027ms
      message: 'network-check-target-ip-10-0-136-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-network-check-target-ip-10-0-138-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14486"
    uid: 2923d3b2-bc8b-4920-b941-1c0db8ce145d
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:27:43Z"
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.090172ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:27:43Z"
    - latency: 2.170064ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 2.210676ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 2.257325ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 2.298991ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 2.297177ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 2.562829ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-221-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-221.ec2.internal
      uid: ffa45008-6208-460e-a2f9-74c60c5b38ed
    resourceVersion: "14073"
    uid: a15c122f-967d-4ad2-933b-721671ce6966
  spec:
    sourcePod: network-check-source-65bdbbff45-k8dfj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:26:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.731035ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 1.665743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:26:43Z"
    - latency: 825.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 1.906224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:25:43Z"
    - latency: 892.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 1.939818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:24:43Z"
    - latency: 1.350832ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 1.815487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:23:43Z"
    - latency: 848.662µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T16:22:43Z"
    - latency: 1.669917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T16:22:43Z"
kind: List
metadata:
  resourceVersion: ""