apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "22773"
    uid: 7e3cc446-5539-4b30-8abc-b5bc1962a959
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:28:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:28:52Z"
    - latency: 1.00867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 954.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 952.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 1.222052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 1.470069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 955.171µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "21814"
    uid: 2592d5b4-8177-48b4-934a-b11ad1c883c1
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:27:52Z"
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.790093ms
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 9.484614ms
      message: 'load-balancer-api-external: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 4.873147ms
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 6.83637ms
      message: 'load-balancer-api-external: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 4.676441ms
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 8.630622ms
      message: 'load-balancer-api-external: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 4.835634ms
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 8.310998ms
      message: 'load-balancer-api-external: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 5.717371ms
      message: 'load-balancer-api-external: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 6.593082ms
      message: 'load-balancer-api-external: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "21813"
    uid: 7b1417a1-0c85-490c-b46c-2d0f19c4ad9b
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:27:52Z"
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.301081ms
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 9.587113ms
      message: 'load-balancer-api-internal: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 4.190119ms
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 6.869349ms
      message: 'load-balancer-api-internal: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 4.09365ms
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 8.648183ms
      message: 'load-balancer-api-internal: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 4.161256ms
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 8.345143ms
      message: 'load-balancer-api-internal: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 5.832435ms
      message: 'load-balancer-api-internal: tcp connection to ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 6.620464ms
      message: 'load-balancer-api-internal: resolved host name ab0257d06801949b780194fe6adefc53-6bf5ab80998add94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-135-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "22770"
    uid: 1d2cfdd3-f7e8-40ed-bac5-c371e5a07302
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:28:52Z"
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250394ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:28:52Z"
    - latency: 2.233111ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 2.349647ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 2.609801ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 2.28059ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 2.426751ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 2.394582ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-139-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "22772"
    uid: dfa361f3-0db6-4800-8d73-bbad81788fca
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:28:52Z"
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.33764ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:28:52Z"
    - latency: 916.642µs
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 909.182µs
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 909.531µs
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 1.26407ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 1.154529ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 1.596636ms
      message: 'network-check-target-ip-10-0-139-77: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-ip-10-0-143-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "22771"
    uid: fef24af3-9582-403b-b53a-d4bc3a4fde58
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:28:52Z"
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.384476ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:28:52Z"
    - latency: 2.485508ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 2.34766ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 2.817334ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 2.478182ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 2.319507ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 2.457346ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T19:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-77.ec2.internal
      uid: 1c1ebbd5-79c5-4427-8e7b-2263f7e538ed
    resourceVersion: "21812"
    uid: a0d5173f-8c35-4717-bd81-105aa8559a45
  spec:
    sourcePod: network-check-source-56499946bc-wdstj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:27:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.234µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 1.849027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:27:52Z"
    - latency: 1.01361ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 1.803305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:26:52Z"
    - latency: 900.342µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 1.83062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:25:52Z"
    - latency: 852.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 1.767962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:24:52Z"
    - latency: 1.337784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:23:52Z"
    - latency: 2.047392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:23:52Z"
kind: List
metadata:
  resourceVersion: ""