apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "21017"
    uid: be6c80a5-f422-4a2a-b943-8973418c42c8
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:31:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.184227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:39Z"
    - latency: 844.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:39Z"
    - latency: 1.072614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:39Z"
    - latency: 1.153491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:39Z"
    - latency: 1.632303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:39Z"
    - latency: 1.502319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:39Z"
    - latency: 890.121µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "24043"
    uid: 97341ea9-11ca-4d47-82d3-a4a98ccae98c
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:30:39Z"
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.68568ms
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 8.440677ms
      message: 'load-balancer-api-external: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 4.998383ms
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 13.923129ms
      message: 'load-balancer-api-external: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 3.668735ms
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 15.025201ms
      message: 'load-balancer-api-external: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 4.646274ms
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 8.98898ms
      message: 'load-balancer-api-external: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 5.674675ms
      message: 'load-balancer-api-external: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:39Z"
    - latency: 8.67401ms
      message: 'load-balancer-api-external: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "24042"
    uid: ac0e3957-ecd0-4cc7-8ea5-633cb4701a0d
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:30:39Z"
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.384151ms
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 8.532611ms
      message: 'load-balancer-api-internal: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 5.04895ms
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 13.870721ms
      message: 'load-balancer-api-internal: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 6.283707ms
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 15.082631ms
      message: 'load-balancer-api-internal: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 4.693286ms
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 8.920826ms
      message: 'load-balancer-api-internal: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 5.938843ms
      message: 'load-balancer-api-internal: tcp connection to a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:39Z"
    - latency: 8.749904ms
      message: 'load-balancer-api-internal: resolved host name a932673fce7324b448e863f7af500c8d-07a8468204471400.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-129-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "21016"
    uid: 57e8c002-5d99-4766-9805-4fcbe81bf1bd
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:31:39Z"
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.046459ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:39Z"
    - latency: 2.346045ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:39Z"
    - latency: 1.974303ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:39Z"
    - latency: 2.295953ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:39Z"
    - latency: 2.247608ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:39Z"
    - latency: 2.698679ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:39Z"
    - latency: 2.368458ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-133-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "21014"
    uid: a09d4046-0e0e-45ef-94a5-6002d89ef525
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:31:39Z"
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.138933ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:39Z"
    - latency: 2.581409ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:39Z"
    - latency: 2.46062ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:39Z"
    - latency: 2.137355ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:39Z"
    - latency: 2.597529ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:39Z"
    - latency: 2.798742ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:39Z"
    - latency: 2.574228ms
      message: 'network-check-target-ip-10-0-133-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-ip-10-0-136-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "21015"
    uid: b6c14807-94af-45d2-8656-5f9f4d6e9fa9
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:31:39Z"
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131708ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:39Z"
    - latency: 956.427µs
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:39Z"
    - latency: 853.561µs
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:39Z"
    - latency: 980.799µs
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:39Z"
    - latency: 821.152µs
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:39Z"
    - latency: 1.096521ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:39Z"
    - latency: 1.282537ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:24:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-40.ec2.internal
      uid: 011035ca-8e32-4947-983f-fbd3b5b63458
    resourceVersion: "24041"
    uid: 0d03f714-54b3-4639-94a1-6f42acc9547f
  spec:
    sourcePod: network-check-source-7cbc45fddc-gzr85
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:30:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.510872ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 1.703774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:36:39Z"
    - latency: 1.004254ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 1.967588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:35:39Z"
    - latency: 994.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 1.68221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:34:39Z"
    - latency: 844.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 1.807067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:39Z"
    - latency: 1.400634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:39Z"
    - latency: 1.679298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:39Z"
kind: List
metadata:
  resourceVersion: ""