apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "11727"
    uid: 0fd8bf4b-89a9-4076-988c-c93e8366f123
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "15266"
    uid: c5fcdde9-1f9f-4822-97a1-b5925c8b92c1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:18:51Z"
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.646048ms
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 12.189215ms
      message: 'load-balancer-api-external: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 5.918902ms
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 10.273932ms
      message: 'load-balancer-api-external: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 4.881391ms
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 8.689457ms
      message: 'load-balancer-api-external: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 4.224116ms
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 8.270895ms
      message: 'load-balancer-api-external: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 4.022715ms
      message: 'load-balancer-api-external: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:14:51Z"
    - latency: 7.987551ms
      message: 'load-balancer-api-external: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:14:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "15265"
    uid: 23fafecb-f22d-437d-80aa-099ac676f580
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:18:51Z"
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.599872ms
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 12.300041ms
      message: 'load-balancer-api-internal: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 6.007212ms
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 10.438167ms
      message: 'load-balancer-api-internal: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 4.801482ms
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 8.658568ms
      message: 'load-balancer-api-internal: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 4.502127ms
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 8.306438ms
      message: 'load-balancer-api-internal: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 3.995198ms
      message: 'load-balancer-api-internal: tcp connection to a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:14:51Z"
    - latency: 8.069412ms
      message: 'load-balancer-api-internal: resolved host name a44dd8755babc4b1684b234e3799ca16-6d1338b48b09b43d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:14:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-128-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "11734"
    uid: 4c63cf90-fab9-499a-b6ee-8b1f961dc1a2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-129-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "11733"
    uid: 1961bc05-a4ff-40a0-ad17-44beb5b7fb52
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-ip-10-0-135-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "11732"
    uid: 0ef8ceeb-dcfe-44c1-a759-8a3f0fd7f402
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:12:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-200.ec2.internal
      uid: 6044a8cd-c77c-467b-a91b-b70cc9caf23d
    resourceVersion: "15264"
    uid: c71b52ec-1ca8-4993-ac3c-069656b977c6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-75xcm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:18:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.903648ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 3.058475ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:18:51Z"
    - latency: 1.009615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 2.6184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:17:51Z"
    - latency: 772.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 1.856215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:16:51Z"
    - latency: 924.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 1.619494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:15:51Z"
    - latency: 950.034µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:14:51Z"
    - latency: 1.707143ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:14:51Z"
kind: List
metadata:
  resourceVersion: ""