apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "11060"
    uid: e3bfc23b-34be-430d-a8be-81e0d6cdd896
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "21811"
    uid: 27d030df-2e23-4f59-9e42-92610031cbb7
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:46:53Z"
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.675492ms
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 6.869926ms
      message: 'load-balancer-api-external: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 4.23314ms
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 7.743239ms
      message: 'load-balancer-api-external: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 5.418608ms
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 10.159868ms
      message: 'load-balancer-api-external: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 4.49418ms
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 9.985235ms
      message: 'load-balancer-api-external: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 5.021904ms
      message: 'load-balancer-api-external: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:42:53Z"
    - latency: 8.531818ms
      message: 'load-balancer-api-external: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "21812"
    uid: 7264390d-9d5e-4e8f-98f6-2dfe1fb9f9fb
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:46:53Z"
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.39156ms
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 6.824248ms
      message: 'load-balancer-api-internal: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 6.516719ms
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 7.558342ms
      message: 'load-balancer-api-internal: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 5.234606ms
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 9.984966ms
      message: 'load-balancer-api-internal: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 4.545138ms
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 9.787307ms
      message: 'load-balancer-api-internal: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 5.154253ms
      message: 'load-balancer-api-internal: tcp connection to a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:42:53Z"
    - latency: 8.310192ms
      message: 'load-balancer-api-internal: resolved host name a70799d1ef1a74103871c61a0b1b81b4-b6215bb5cf04417b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:42:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-132-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "11065"
    uid: 6cd099c4-1e24-487b-9ac2-749a412824af
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-132-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "11068"
    uid: 3d206512-81c1-4fe2-ab90-30cb9b4fbccd
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-network-check-target-ip-10-0-140-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "11067"
    uid: 0bb716b8-299a-4b42-9409-c885ee31dee6
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:40:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-181-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-181.ec2.internal
      uid: 37ac90ec-992d-4337-affc-61033e41bb22
    resourceVersion: "21810"
    uid: 9db05ba9-936f-4255-acf0-9c6480336e79
  spec:
    sourcePod: network-check-source-989f8b8dc-n6vz2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:46:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.308749ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 1.644181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:46:53Z"
    - latency: 917.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 2.035109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:45:53Z"
    - latency: 1.11515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 2.597771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:44:53Z"
    - latency: 769.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 2.504232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:43:53Z"
    - latency: 956.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:42:53Z"
    - latency: 1.881302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:42:53Z"
kind: List
metadata:
  resourceVersion: ""