apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "15333"
    uid: fc882046-efe4-4f58-b77e-410c203f2ed0
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:06:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.26µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:20Z"
    - latency: 948.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 820µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 1.188806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 947.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 846.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 704.063µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "14973"
    uid: eb88069c-4c14-43dd-bef5-2e56d55a6cc8
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:05:20Z"
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.307938ms
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 6.494136ms
      message: 'load-balancer-api-external: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 4.908633ms
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 7.210225ms
      message: 'load-balancer-api-external: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 4.606972ms
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 6.702702ms
      message: 'load-balancer-api-external: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 5.115073ms
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 7.104298ms
      message: 'load-balancer-api-external: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 5.989836ms
      message: 'load-balancer-api-external: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 5.943868ms
      message: 'load-balancer-api-external: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "14972"
    uid: 35de08cb-d7f3-4514-a32f-95ecbe56dce1
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:05:20Z"
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.443916ms
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 6.564534ms
      message: 'load-balancer-api-internal: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 4.950386ms
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 7.21021ms
      message: 'load-balancer-api-internal: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 4.469918ms
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 6.737515ms
      message: 'load-balancer-api-internal: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 5.079135ms
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 7.129391ms
      message: 'load-balancer-api-internal: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 6.700277ms
      message: 'load-balancer-api-internal: tcp connection to a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 5.974252ms
      message: 'load-balancer-api-internal: resolved host name a4d2dc7b8c7b44d0cacbc24f332cd946-ca8e7ee02188e180.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-network-check-target-ip-10-0-130-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "15330"
    uid: f68cb18e-ef46-4ce0-8ad8-2aad6dbd5b0d
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:06:20Z"
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.584µs
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:20Z"
    - latency: 1.074633ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 810.096µs
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 868.477µs
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 1.141487ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 1.271667ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 1.51566ms
      message: 'network-check-target-ip-10-0-130-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-network-check-target-ip-10-0-137-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "15331"
    uid: 0a0d00cf-8200-47f9-97e4-b9d3d25618e1
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:06:20Z"
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.120397ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:20Z"
    - latency: 2.331705ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 1.849254ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 1.873155ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 2.019418ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 2.014221ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 2.084186ms
      message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-network-check-target-ip-10-0-137-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "15332"
    uid: a76dd036-b5ef-4daf-924a-f61f9abb6eaa
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:06:20Z"
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.774008ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:20Z"
    - latency: 1.856399ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 1.870313ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 1.884064ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 1.951362ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 1.723091ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 2.046538ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:59:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-64.ec2.internal
      uid: b0d76cd1-2a9b-47d8-a754-6ab52769bec6
    resourceVersion: "14971"
    uid: 82d3d91f-0af1-40f3-908e-fe85512c9b3c
  spec:
    sourcePod: network-check-source-869dcfcdcd-dc6m6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:05:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 1.580515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:20Z"
    - latency: 792.557µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 2.158647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:20Z"
    - latency: 889.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 1.801049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:20Z"
    - latency: 615.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 2.079144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:02:20Z"
    - latency: 935.152µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:20Z"
    - latency: 1.688998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:20Z"
kind: List
metadata:
  resourceVersion: ""