apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "11291"
    uid: bc7dbbc6-c86f-479d-98eb-0e8aad9415c8
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "14801"
    uid: b5bcbc8d-0abe-4fef-8a3e-ef23372973f7
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T07:44:43Z"
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.086463ms
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 7.315798ms
      message: 'load-balancer-api-external: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 6.005571ms
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 7.547858ms
      message: 'load-balancer-api-external: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 5.379698ms
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 8.529768ms
      message: 'load-balancer-api-external: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 4.979617ms
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 7.524924ms
      message: 'load-balancer-api-external: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 4.79378ms
      message: 'load-balancer-api-external: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:40:43Z"
    - latency: 6.891402ms
      message: 'load-balancer-api-external: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "14802"
    uid: 3a2a2069-1511-44af-8396-28029e5f15b7
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T07:44:43Z"
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.658885ms
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 7.283328ms
      message: 'load-balancer-api-internal: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 6.001956ms
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 7.462808ms
      message: 'load-balancer-api-internal: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 5.358266ms
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 8.492536ms
      message: 'load-balancer-api-internal: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 4.895746ms
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 7.467255ms
      message: 'load-balancer-api-internal: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 4.812162ms
      message: 'load-balancer-api-internal: tcp connection to a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:40:43Z"
    - latency: 6.797148ms
      message: 'load-balancer-api-internal: resolved host name a2a648b73db5241d183e68a6f8df310b-ad26a95f14c130fd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:40:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-network-check-target-ip-10-0-130-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "11295"
    uid: 06169b67-a54f-48ed-b994-557350ed1434
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-network-check-target-ip-10-0-131-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "11297"
    uid: 4d07b84e-184d-495a-925b-645fe9ad4b6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-network-check-target-ip-10-0-141-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "11298"
    uid: 441e82b7-f933-4b9f-af6e-d50d03b7ade3
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T07:38:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-196.ec2.internal
      uid: 7143c71f-c88d-445e-bd21-e91147dd3279
    resourceVersion: "14800"
    uid: a0d31e2b-d402-4d1c-85fe-4b78ea75a364
  spec:
    sourcePod: network-check-source-869dcfcdcd-gjd7l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T07:44:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.001µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 1.9724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:44:43Z"
    - latency: 860.599µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 1.679604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:43:43Z"
    - latency: 1.112572ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 1.73787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:42:43Z"
    - latency: 883.381µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 1.745721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:41:43Z"
    - latency: 820.626µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T07:40:43Z"
    - latency: 2.404742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T07:40:43Z"
kind: List
metadata:
  resourceVersion: ""