apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "11088"
    uid: 21937581-67b6-41f8-94ee-dfb5d24c9bda
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "14474"
    uid: 3c8c9f1c-d729-4eb1-abb2-f1632622eaad
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:45:45Z"
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.396731ms
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 7.39948ms
      message: 'load-balancer-api-external: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 5.23159ms
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 7.933047ms
      message: 'load-balancer-api-external: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 4.432656ms
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 8.224823ms
      message: 'load-balancer-api-external: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 5.097306ms
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 9.065677ms
      message: 'load-balancer-api-external: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 4.297111ms
      message: 'load-balancer-api-external: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:41:45Z"
    - latency: 7.425048ms
      message: 'load-balancer-api-external: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:41:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "14475"
    uid: b6b9ca54-eb07-41af-81e3-1de05c3bc905
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:45:45Z"
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.441041ms
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 7.505214ms
      message: 'load-balancer-api-internal: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 5.233791ms
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 8.027826ms
      message: 'load-balancer-api-internal: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 4.123809ms
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 8.245449ms
      message: 'load-balancer-api-internal: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 5.065628ms
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 9.01178ms
      message: 'load-balancer-api-internal: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 4.32002ms
      message: 'load-balancer-api-internal: tcp connection to a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:41:45Z"
    - latency: 7.406098ms
      message: 'load-balancer-api-internal: resolved host name a80cd0c7ca02f4976b037986acda81ad-b9e39098aabeeb39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:41:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-129-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "11093"
    uid: 2da0b7cb-5379-464d-88c6-3890b459b02f
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-135-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "11095"
    uid: 624c7b11-66cb-4a35-b4d4-bee35cdc38b1
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-136-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "11094"
    uid: 4e976ad6-59cb-461e-b4e3-daf9a0525ce0
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: e9167df3-3683-4a30-8b1c-dee192c9ac24
    resourceVersion: "14473"
    uid: be16aad4-ef83-4aae-8c06-6f2de8d09ddf
  spec:
    sourcePod: network-check-source-6f8b768455-vm465
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:45:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 1.537012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:45Z"
    - latency: 766.43µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 1.476557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:44:45Z"
    - latency: 1.122565ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 1.826633ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:43:45Z"
    - latency: 1.028794ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 1.8636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:42:45Z"
    - latency: 1.00184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:41:45Z"
    - latency: 1.633747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:41:45Z"
kind: List
metadata:
  resourceVersion: ""