apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "11110"
    uid: f0e8e051-fc86-4b24-85ab-66dd4eae5f40
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "14653"
    uid: 56fc41d5-3bd0-429f-852e-28ca904c1bb2
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T11:32:28Z"
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.13291ms
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 6.404741ms
      message: 'load-balancer-api-external: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 5.3237ms
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 8.652077ms
      message: 'load-balancer-api-external: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 4.891821ms
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 6.722551ms
      message: 'load-balancer-api-external: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 4.574534ms
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 7.053342ms
      message: 'load-balancer-api-external: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 5.469887ms
      message: 'load-balancer-api-external: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:28:28Z"
    - latency: 6.086757ms
      message: 'load-balancer-api-external: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "14652"
    uid: c4feb9e9-7aa2-4da2-84c3-42ace9a61e1c
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T11:32:28Z"
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.091975ms
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 6.47725ms
      message: 'load-balancer-api-internal: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 5.344995ms
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 8.603831ms
      message: 'load-balancer-api-internal: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 4.920951ms
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 6.8094ms
      message: 'load-balancer-api-internal: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 4.604241ms
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 6.955057ms
      message: 'load-balancer-api-internal: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 3.86014ms
      message: 'load-balancer-api-internal: tcp connection to a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:28:28Z"
    - latency: 6.172866ms
      message: 'load-balancer-api-internal: resolved host name a3d86b31c73a342ef876863342885441-240c3dec4a45598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:28:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-131-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "11106"
    uid: 4ed59a4e-ff34-481b-9b6a-3f53667169d6
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-133-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "11107"
    uid: 87e671e3-132c-4804-8669-669ec5dc7080
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-137-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "11109"
    uid: 8d1ee65b-8357-4436-8745-fa8c0646c20d
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T11:26:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: 62ed2494-2c02-426f-bc04-8f59f305e2a1
    resourceVersion: "14651"
    uid: 8daf8cf4-b99e-4da2-a3e2-e0b8c50754dd
  spec:
    sourcePod: network-check-source-7d88cb55d8-qx2c8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T11:32:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 1.682074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:32:28Z"
    - latency: 820.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 1.778141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:31:28Z"
    - latency: 830.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 1.500584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:30:28Z"
    - latency: 840.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 1.603227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:29:28Z"
    - latency: 835.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T11:28:28Z"
    - latency: 1.45623ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T11:28:28Z"
kind: List
metadata:
  resourceVersion: ""