apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "23941"
    uid: 1b593885-a87d-465b-b8bc-c1f99f76b108
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:47:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.882µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:47:40Z"
    - latency: 1.209924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 1.201662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 824.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 809.288µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 750.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 1.070225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "22496"
    uid: 1015c5a0-b392-48c8-9894-35bbc69c9289
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:46:40Z"
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.866059ms
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 8.714441ms
      message: 'load-balancer-api-external: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 4.184908ms
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 7.109672ms
      message: 'load-balancer-api-external: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 6.129052ms
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 10.064684ms
      message: 'load-balancer-api-external: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 4.962424ms
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 7.264146ms
      message: 'load-balancer-api-external: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 5.163442ms
      message: 'load-balancer-api-external: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 6.782567ms
      message: 'load-balancer-api-external: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:42:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "22497"
    uid: 3abb1b0b-06de-4037-96d4-3e8ba1011cfd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:46:40Z"
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.910713ms
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 8.630307ms
      message: 'load-balancer-api-internal: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 4.237677ms
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 7.128378ms
      message: 'load-balancer-api-internal: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 7.361657ms
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 10.125739ms
      message: 'load-balancer-api-internal: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 4.976578ms
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 7.312806ms
      message: 'load-balancer-api-internal: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 4.068148ms
      message: 'load-balancer-api-internal: tcp connection to ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 6.828356ms
      message: 'load-balancer-api-internal: resolved host name ae52c2326341c440fb5608b19803bcb5-a674eb23e4e6c9e6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:42:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-network-check-target-ip-10-0-133-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "23939"
    uid: 7aa8de8d-7287-4c70-b862-c3c94f85513b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:47:40Z"
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.154909ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:47:40Z"
    - latency: 2.699877ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 2.328999ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 2.423658ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 2.271802ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 2.033046ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 2.651502ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-network-check-target-ip-10-0-135-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "23940"
    uid: 19e81324-03f8-4d5c-81b4-9a623d2d2093
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:47:40Z"
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205614ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:47:40Z"
    - latency: 2.275007ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 2.880775ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 2.408384ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 1.943558ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 1.786861ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 2.607672ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-network-check-target-ip-10-0-136-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "23938"
    uid: 2d8ea50d-733d-41f2-9090-01bc30cb78bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:47:40Z"
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.348266ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:47:40Z"
    - latency: 1.310862ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 1.263209ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 968.94µs
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 776.725µs
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 869.747µs
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 1.083881ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T23:40:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-188.ec2.internal
      uid: 6649e757-1bbd-4e09-9f31-e576e457a918
    resourceVersion: "22495"
    uid: f8eb1a7b-a78a-4172-bd19-a0bf43d2e9ad
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nzdnj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T23:46:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.482µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 2.044087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:46:40Z"
    - latency: 868.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 1.68459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:45:40Z"
    - latency: 803.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 2.407728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:44:40Z"
    - latency: 864.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 1.810523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:43:40Z"
    - latency: 844.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T23:42:40Z"
    - latency: 1.748171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T23:42:40Z"
kind: List
metadata:
  resourceVersion: ""