apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "23099"
    uid: 727a0be2-920e-4e2e-8808-765735420819
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:02:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:02:54Z"
    - latency: 1.343781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 903.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 1.720804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 1.181925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 896.004µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 1.033853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "21762"
    uid: 35a29a36-d6ae-4ce4-a994-5c3bc7c943c8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:01:54Z"
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.902818ms
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 8.588719ms
      message: 'load-balancer-api-external: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 5.219887ms
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 8.879877ms
      message: 'load-balancer-api-external: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 3.300578ms
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 7.091681ms
      message: 'load-balancer-api-external: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 3.004329ms
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 9.160355ms
      message: 'load-balancer-api-external: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 4.975444ms
      message: 'load-balancer-api-external: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 8.507748ms
      message: 'load-balancer-api-external: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:57:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "21761"
    uid: 498b7292-0caf-4bae-b119-bbcd0c42b428
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:01:54Z"
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.169482ms
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 8.6125ms
      message: 'load-balancer-api-internal: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 3.608719ms
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 8.82012ms
      message: 'load-balancer-api-internal: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 4.679985ms
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 6.974622ms
      message: 'load-balancer-api-internal: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 2.996834ms
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 9.041836ms
      message: 'load-balancer-api-internal: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 4.520701ms
      message: 'load-balancer-api-internal: tcp connection to a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 8.447945ms
      message: 'load-balancer-api-internal: resolved host name a947f9b93343e4cd1b6e11a8b67353ad-f73b2bac811563bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:57:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-130-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "23097"
    uid: d51f6437-e294-4a51-9b29-bacd31b316ce
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:02:54Z"
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.062562ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:02:54Z"
    - latency: 2.281781ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 2.342079ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 2.474294ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 2.528546ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 2.693108ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 2.569171ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-134-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "23096"
    uid: 53f78594-4071-4549-b135-b93b74dbe69f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:02:54Z"
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043657ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:02:54Z"
    - latency: 1.273389ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 984.782µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 1.036424ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 993.404µs
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 1.143438ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 2.132381ms
      message: 'network-check-target-ip-10-0-134-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-ip-10-0-140-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "23098"
    uid: 18d88e2c-6bd3-439d-94d5-830a8b6020f7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:02:54Z"
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122667ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:02:54Z"
    - latency: 2.308274ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 2.078881ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 2.810641ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 2.531698ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 2.474911ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 2.813224ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:56:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T02:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-207.ec2.internal
      uid: 61601ef5-f913-44fc-912f-2198236e75e3
    resourceVersion: "21760"
    uid: dec14cb0-144e-422d-a8f5-8ac6e6d95bb7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-2j7c4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T03:01:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100867ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 2.134291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:01:54Z"
    - latency: 829.889µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 2.611244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:00:54Z"
    - latency: 1.016394ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 2.208608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:59:54Z"
    - latency: 869.083µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 2.089839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:58:54Z"
    - latency: 1.069527ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:57:54Z"
    - latency: 1.822131ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:57:54Z"
kind: List
metadata:
  resourceVersion: ""