apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "24231"
    uid: d7ac8fa1-981d-4239-9930-cd1f70b1591a
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:35:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:35:56Z"
    - latency: 1.166455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 1.400307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 1.161543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 1.575052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 849.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 1.162006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "23180"
    uid: 35752607-a6a6-488d-af95-3ddb8095057c
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:34:56Z"
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.340463ms
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 6.846618ms
      message: 'load-balancer-api-external: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 4.104138ms
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 7.581658ms
      message: 'load-balancer-api-external: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 4.279008ms
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 6.492863ms
      message: 'load-balancer-api-external: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 5.079913ms
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 9.247797ms
      message: 'load-balancer-api-external: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 4.995776ms
      message: 'load-balancer-api-external: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 7.128881ms
      message: 'load-balancer-api-external: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:30:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "23181"
    uid: f10c27ba-4e32-4d11-8384-62cec3332f2e
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:34:56Z"
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.111932ms
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 6.82121ms
      message: 'load-balancer-api-internal: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 3.993544ms
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 7.512994ms
      message: 'load-balancer-api-internal: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 5.485418ms
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 6.459493ms
      message: 'load-balancer-api-internal: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 5.477518ms
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 9.307184ms
      message: 'load-balancer-api-internal: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 5.003262ms
      message: 'load-balancer-api-internal: tcp connection to ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 7.047318ms
      message: 'load-balancer-api-internal: resolved host name ab39379058c204b488a35a4e03cb30ea-58f4279e57765e0e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:30:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-network-check-target-ip-10-0-133-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "24230"
    uid: 3cd6e31f-07b3-422f-87d3-8dc3996a6e39
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:35:56Z"
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.092978ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:35:56Z"
    - latency: 2.141128ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 2.172162ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 1.986432ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 2.700593ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 2.086556ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 2.206765ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-network-check-target-ip-10-0-142-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "24228"
    uid: 71b02565-eefd-4927-b6f9-ff3f8b25a849
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:35:56Z"
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.648µs
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:35:56Z"
    - latency: 789.301µs
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 1.078427ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 972.867µs
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 2.542397ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 937.91µs
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 1.299945ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-network-check-target-ip-10-0-143-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "24229"
    uid: 5da0068f-a8c4-469c-9d3b-47a5acda2c95
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:35:56Z"
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.950706ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:35:56Z"
    - latency: 1.825368ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 1.955985ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 1.730344ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 2.360918ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 1.703562ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 1.970639ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T08:28:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-79.ec2.internal
      uid: 66523578-2705-4fe1-8222-19ffeda96541
    resourceVersion: "23179"
    uid: 75f5c55a-8841-4d97-b872-95016bf95d6a
  spec:
    sourcePod: network-check-source-dbd9cf844-jvjnh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T08:34:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.328µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 1.543987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:34:56Z"
    - latency: 1.073532ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 1.818779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:33:56Z"
    - latency: 945.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 1.814999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:32:56Z"
    - latency: 1.47884ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 3.007029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:31:56Z"
    - latency: 837.53µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T08:30:56Z"
    - latency: 2.008081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T08:30:56Z"
kind: List
metadata:
  resourceVersion: ""