apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "10937"
    uid: c1f9bbb2-6134-4f67-a0dd-a42fa7af9357
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "14362"
    uid: 6bba23ae-5b71-4349-82f6-f973bf66eda2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:24:03Z"
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.574086ms
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 9.293667ms
      message: 'load-balancer-api-external: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 4.933436ms
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 9.924504ms
      message: 'load-balancer-api-external: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 4.926213ms
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 10.152851ms
      message: 'load-balancer-api-external: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 4.147307ms
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 7.658378ms
      message: 'load-balancer-api-external: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 5.457247ms
      message: 'load-balancer-api-external: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:20:03Z"
    - latency: 8.809426ms
      message: 'load-balancer-api-external: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:20:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "14361"
    uid: 0ee255c1-8278-4837-ba11-04e5fa0b8b5e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:24:03Z"
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.326297ms
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 9.360944ms
      message: 'load-balancer-api-internal: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 4.951814ms
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 9.872895ms
      message: 'load-balancer-api-internal: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 4.877293ms
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 10.204531ms
      message: 'load-balancer-api-internal: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 5.196589ms
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 7.732341ms
      message: 'load-balancer-api-internal: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 5.071302ms
      message: 'load-balancer-api-internal: tcp connection to a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:20:03Z"
    - latency: 8.85415ms
      message: 'load-balancer-api-internal: resolved host name a37ed0fa4913d4f349ba96a06a144ef6-9947d95f5b4cb444.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:20:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-network-check-target-ip-10-0-130-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "10944"
    uid: 74780bf5-88b0-443a-afaa-2e438d8227f4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-network-check-target-ip-10-0-133-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "10942"
    uid: 0529b982-1aa5-497f-855f-44a6adc3b440
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-network-check-target-ip-10-0-135-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "10943"
    uid: 99539352-bf87-4973-b82f-0ecc06f22bf1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T19:18:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-155.ec2.internal
      uid: 412c7130-fa72-4cd5-b76c-e6d51a5945af
    resourceVersion: "14360"
    uid: 5e717d4a-a271-48a6-94ab-f28ee5ed59cc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-r99bq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T19:24:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 1.761487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:24:03Z"
    - latency: 1.026028ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 1.697791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:23:03Z"
    - latency: 889.163µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 1.802346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:22:03Z"
    - latency: 921.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 1.602399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:21:03Z"
    - latency: 839.263µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:20:03Z"
    - latency: 1.520594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:20:03Z"
kind: List
metadata:
  resourceVersion: ""