apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "11099"
    uid: 02b30b78-2305-4fd0-bcb6-93b30c10ac35
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "14566"
    uid: 4ae54dd0-eb77-48fe-a09e-5258bf21d9f9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:37:40Z"
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.560028ms
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 8.751054ms
      message: 'load-balancer-api-external: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 4.945892ms
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 7.827114ms
      message: 'load-balancer-api-external: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 5.081684ms
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 8.441304ms
      message: 'load-balancer-api-external: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 5.168369ms
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 7.101672ms
      message: 'load-balancer-api-external: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 6.886882ms
      message: 'load-balancer-api-external: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:33:40Z"
    - latency: 8.704188ms
      message: 'load-balancer-api-external: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "14567"
    uid: c5189e23-7a63-4767-ba2a-51abb86d95c4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:37:40Z"
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.316791ms
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 8.673566ms
      message: 'load-balancer-api-internal: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 4.15514ms
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 7.860752ms
      message: 'load-balancer-api-internal: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 4.759028ms
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 8.366626ms
      message: 'load-balancer-api-internal: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 5.185524ms
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 7.181278ms
      message: 'load-balancer-api-internal: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 6.883814ms
      message: 'load-balancer-api-internal: tcp connection to a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:33:40Z"
    - latency: 8.727673ms
      message: 'load-balancer-api-internal: resolved host name a30176f66effb43989dc6fc4f9ccccb8-e6c207c21dccdb35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-131-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "11106"
    uid: 10687be5-2609-4571-968a-a1e15ffc106d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-135-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "11104"
    uid: fb1c4fb2-4b36-4469-b1e0-420cfc5556b7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-142-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "11105"
    uid: 643b9629-2648-4646-a2f9-2053d2f7bf3e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T13:31:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 035e83fa-47c5-48f7-809a-e6c6846061cc
    resourceVersion: "14565"
    uid: 554e6c33-44fb-4455-8a4f-fe524c60ce54
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h5tv8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T13:37:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 2.068266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:37:40Z"
    - latency: 820.88µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 1.721092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:36:40Z"
    - latency: 926.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 1.726989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:35:40Z"
    - latency: 766.883µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 1.740327ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:34:40Z"
    - latency: 866.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T13:33:40Z"
    - latency: 2.790222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T13:33:40Z"
kind: List
metadata:
  resourceVersion: ""