apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "11222"
    uid: e5a3baf8-679e-4755-a1e2-8b6c67ae49f5
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "14563"
    uid: f804904b-14d8-4c6f-a159-483304d669e8
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:45:25Z"
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.536813ms
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 6.776893ms
      message: 'load-balancer-api-external: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 5.429327ms
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 6.979822ms
      message: 'load-balancer-api-external: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 4.932945ms
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 7.404114ms
      message: 'load-balancer-api-external: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 4.374488ms
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 8.095171ms
      message: 'load-balancer-api-external: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 7.54064ms
      message: 'load-balancer-api-external: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:41:25Z"
    - latency: 7.181747ms
      message: 'load-balancer-api-external: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:41:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "14562"
    uid: 983298a2-4bd4-4940-97e0-e05da2de15f3
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:45:25Z"
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.644511ms
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 6.753358ms
      message: 'load-balancer-api-internal: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 6.676137ms
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 6.948704ms
      message: 'load-balancer-api-internal: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 5.223625ms
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 7.361945ms
      message: 'load-balancer-api-internal: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 4.368088ms
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 8.052648ms
      message: 'load-balancer-api-internal: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 7.57421ms
      message: 'load-balancer-api-internal: tcp connection to a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:41:25Z"
    - latency: 7.118201ms
      message: 'load-balancer-api-internal: resolved host name a9745eb19e23d48d499a98de5f8fa5c5-afe8ba4497fc09d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:41:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-133-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "11228"
    uid: fc4c0201-ca50-4c6b-bed5-b07b26a70cee
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-137-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "11227"
    uid: a7d68790-51ab-45f7-a43d-952f3772b1e1
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-network-check-target-ip-10-0-139-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "11229"
    uid: ff5f14d6-3193-4170-abb6-b6a909f1440e
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:39:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-63.ec2.internal
      uid: 4accdc12-dc3e-4e16-8636-d1beee530d4d
    resourceVersion: "14561"
    uid: 98e30cf1-e7f4-4311-a34c-a9f8c49ed300
  spec:
    sourcePod: network-check-source-685456655f-dgjzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:45:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.792µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 2.177919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:45:25Z"
    - latency: 1.363395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 1.736455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:44:25Z"
    - latency: 900.775µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 2.332441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:43:25Z"
    - latency: 753.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 1.640217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:42:25Z"
    - latency: 979.798µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:41:25Z"
    - latency: 2.182974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:41:25Z"
kind: List
metadata:
  resourceVersion: ""