apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14689"
    uid: bd9e72c8-19e9-46be-b56b-5cf34d4d5515
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:46: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.239149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:46:43Z"
    - latency: 694.782µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 1.156104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 886.392µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 915.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 752.643µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 935.055µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14359"
    uid: c659df3c-be90-4a2b-81f2-22d714d1a8d3
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:45:43Z"
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.971436ms
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 6.298728ms
      message: 'load-balancer-api-external: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 5.540808ms
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 7.930135ms
      message: 'load-balancer-api-external: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 4.308353ms
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 6.633174ms
      message: 'load-balancer-api-external: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 4.741004ms
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 6.850226ms
      message: 'load-balancer-api-external: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 5.152092ms
      message: 'load-balancer-api-external: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 7.004261ms
      message: 'load-balancer-api-external: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:41:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14358"
    uid: f0b302d4-adbd-475d-b83d-6d932501e307
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:45:43Z"
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.033444ms
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 6.336385ms
      message: 'load-balancer-api-internal: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 4.687608ms
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 7.891459ms
      message: 'load-balancer-api-internal: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 4.590439ms
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 6.551274ms
      message: 'load-balancer-api-internal: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 4.717859ms
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 6.907341ms
      message: 'load-balancer-api-internal: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 5.138861ms
      message: 'load-balancer-api-internal: tcp connection to a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 6.928286ms
      message: 'load-balancer-api-internal: resolved host name a543740a3b64943c79aec6ec12f9e8cd-eb0e85265ad6ce84.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:41:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-130-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14687"
    uid: 80d88a32-966b-4a57-8195-4ea2f4d880bb
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:46:43Z"
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376946ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:46:43Z"
    - latency: 2.122698ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 1.843391ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 1.807749ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 1.879122ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 1.915563ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 1.966761ms
      message: 'network-check-target-ip-10-0-130-124: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-136-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14688"
    uid: 6dbafa76-9835-4eb4-b21c-fc6fdce2f397
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:46:43Z"
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315508ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:46:43Z"
    - latency: 1.684519ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 1.920049ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 1.979073ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 1.754566ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 1.798993ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 2.378343ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-ip-10-0-136-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14686"
    uid: 1b503d7c-3e48-401c-9174-ed3cdbb7e15a
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:46:43Z"
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.457912ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:46:43Z"
    - latency: 751.698µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 1.163067ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 1.180688ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 1.065439ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 918.895µs
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 1.662805ms
      message: 'network-check-target-ip-10-0-136-213: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T13:39:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-213.ec2.internal
      uid: f69bfca9-d615-4320-9fe9-f3ce4378e53b
    resourceVersion: "14356"
    uid: 2c5e3343-98ef-4227-940e-a5ef962fa1dc
  spec:
    sourcePod: network-check-source-56d84b9f44-bvx4q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T13:45:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 1.860193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:45:43Z"
    - latency: 890.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 1.80902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:44:43Z"
    - latency: 907.687µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 1.879698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:43:43Z"
    - latency: 866.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 1.629562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:42:43Z"
    - latency: 1.138417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T13:41:43Z"
    - latency: 1.505554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T13:41:43Z"
kind: List
metadata:
  resourceVersion: ""