apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "15329"
    uid: 79febc1e-6192-4710-af96-c98f2d6956dd
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:33:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:33:54Z"
    - latency: 845.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 1.5728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 1.058893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 930.054µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 1.058041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 976.859µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "14868"
    uid: cceb3d6d-0332-427a-876c-e06fa0d2c86c
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:32:54Z"
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.670887ms
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 7.906093ms
      message: 'load-balancer-api-external: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 5.562315ms
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 7.788058ms
      message: 'load-balancer-api-external: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 5.478575ms
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 7.292054ms
      message: 'load-balancer-api-external: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 4.387181ms
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 8.13652ms
      message: 'load-balancer-api-external: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 5.062997ms
      message: 'load-balancer-api-external: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 9.787492ms
      message: 'load-balancer-api-external: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "14867"
    uid: 48fe4bcd-c6c3-4a1b-ae6e-0c9880da1c38
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:32:54Z"
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.221381ms
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 7.889076ms
      message: 'load-balancer-api-internal: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 5.556474ms
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 7.892676ms
      message: 'load-balancer-api-internal: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 5.482606ms
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 7.234049ms
      message: 'load-balancer-api-internal: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 4.032525ms
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 8.099883ms
      message: 'load-balancer-api-internal: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 5.034307ms
      message: 'load-balancer-api-internal: tcp connection to ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 9.846707ms
      message: 'load-balancer-api-internal: resolved host name ad41fe27a69c04ed5af6f255225d17e5-30865bcb83b19fda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-136-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "15328"
    uid: 1a809ca4-eb8b-446a-ba10-c5e3b786eebd
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:33:54Z"
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.641045ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:33:54Z"
    - latency: 2.099486ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 2.658369ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 2.214474ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 2.234414ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 2.581827ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 2.86814ms
      message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-142-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "15326"
    uid: 1cdc731c-cf5f-4129-9aa6-45b61ac40204
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:33:54Z"
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.155µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:33:54Z"
    - latency: 1.183574ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 1.413874ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 988.778µs
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 1.787523ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 1.079721ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 1.64937ms
      message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-ip-10-0-143-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "15327"
    uid: f1aa900b-5cfd-4bca-b676-380d5b7f3d3d
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:33:54Z"
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212812ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:33:54Z"
    - latency: 2.147796ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 2.434326ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 2.399157ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 2.570616ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 5.762844ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 2.455808ms
      message: 'network-check-target-ip-10-0-143-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:27:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T08:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-2.ec2.internal
      uid: aafb69eb-713a-473e-92e9-52987cc61d1f
    resourceVersion: "14866"
    uid: 98c07a68-2167-4c46-83bf-dd70c5815422
  spec:
    sourcePod: network-check-source-6f8b768455-8ssdx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T08:32:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.021724ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 1.924476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:32:54Z"
    - latency: 997.39µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 1.94913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:31:54Z"
    - latency: 905.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 1.827463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:30:54Z"
    - latency: 924.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 2.489464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:29:54Z"
    - latency: 3.596368ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:28:54Z"
    - latency: 2.419319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:28:54Z"
kind: List
metadata:
  resourceVersion: ""