apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "11221"
    uid: e96b4ac0-f3d7-4149-b8cf-9a1227069b3b
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "14724"
    uid: d18a1378-ae93-4343-bfce-bf68473ae222
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:05:20Z"
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.039624ms
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 9.482676ms
      message: 'load-balancer-api-external: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 5.199534ms
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 10.863372ms
      message: 'load-balancer-api-external: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 6.264242ms
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 12.328492ms
      message: 'load-balancer-api-external: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 4.08358ms
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 8.919362ms
      message: 'load-balancer-api-external: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 3.407529ms
      message: 'load-balancer-api-external: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:01:20Z"
    - latency: 7.74754ms
      message: 'load-balancer-api-external: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "14723"
    uid: 18a01587-7a07-462d-b541-fa8ac75d6583
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:05:20Z"
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.004313ms
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 9.598881ms
      message: 'load-balancer-api-internal: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 3.705967ms
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 10.920724ms
      message: 'load-balancer-api-internal: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 5.525897ms
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 12.515008ms
      message: 'load-balancer-api-internal: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 5.285463ms
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 8.87184ms
      message: 'load-balancer-api-internal: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 12.837402ms
      message: 'load-balancer-api-internal: tcp connection to a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:01:20Z"
    - latency: 7.886399ms
      message: 'load-balancer-api-internal: resolved host name a0a5253916bbf4b9893f44387ccbbd2e-3283f14fe274a7fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-network-check-target-ip-10-0-131-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "11220"
    uid: c048c247-8b09-48df-ab6a-318c1b4e8918
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-network-check-target-ip-10-0-133-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "11218"
    uid: e578082f-8493-47e2-a822-a4442b8bae13
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-network-check-target-ip-10-0-136-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "11219"
    uid: cb56b29e-4705-4475-861b-09749b737b6d
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T09:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-92.ec2.internal
      uid: fea859fd-9463-44d1-8bda-022857ac2d71
    resourceVersion: "14722"
    uid: 999f742e-10f3-458c-abde-12fa4c8b63a4
  spec:
    sourcePod: network-check-source-65bdbbff45-2k7l2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:05:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 1.705023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:20Z"
    - latency: 821.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 1.776258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:20Z"
    - latency: 1.091921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 1.650971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:03:20Z"
    - latency: 722.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 2.6172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:02:20Z"
    - latency: 819.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:01:20Z"
    - latency: 1.769727ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:01:20Z"
kind: List
metadata:
  resourceVersion: ""