apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "12062"
    uid: a876bdcb-160e-4588-87c3-f9987518ec2e
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:03:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:12Z"
    - latency: 935.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 1.050771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 827.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 917.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 940.778µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 1.020697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "11813"
    uid: 03eefce6-d537-49d4-8c93-7905aae0f901
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:02:12Z"
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.967005ms
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 8.376584ms
      message: 'load-balancer-api-external: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 5.47432ms
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 8.380778ms
      message: 'load-balancer-api-external: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 7.732103ms
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 8.874372ms
      message: 'load-balancer-api-external: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 5.885731ms
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 8.028638ms
      message: 'load-balancer-api-external: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 6.27284ms
      message: 'load-balancer-api-external: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 7.620789ms
      message: 'load-balancer-api-external: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "11814"
    uid: d8be0b05-f3de-4573-81f5-4cf1e9379aec
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:02:12Z"
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.53677ms
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 8.27422ms
      message: 'load-balancer-api-internal: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 5.192348ms
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 8.461662ms
      message: 'load-balancer-api-internal: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 5.931127ms
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 8.776443ms
      message: 'load-balancer-api-internal: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 5.884915ms
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 8.098746ms
      message: 'load-balancer-api-internal: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 6.284737ms
      message: 'load-balancer-api-internal: tcp connection to a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 7.700458ms
      message: 'load-balancer-api-internal: resolved host name a73d50bd21f754fd29cb102587fb58e2-6a601b6f396e7661.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-network-check-target-ip-10-0-128-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "12061"
    uid: 0d20aed6-e376-4e1f-b67b-fbf5aa6df704
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:03:12Z"
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.207304ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:12Z"
    - latency: 2.204344ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 2.077994ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 2.426419ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 2.311425ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 2.411886ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 2.417819ms
      message: 'network-check-target-ip-10-0-128-242: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-network-check-target-ip-10-0-129-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "12060"
    uid: cd282c11-75a8-4389-bc81-539b984bd29d
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:03:12Z"
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.895974ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:12Z"
    - latency: 1.874621ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 1.787425ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 1.795315ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 1.967021ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 1.955147ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 2.063981ms
      message: 'network-check-target-ip-10-0-129-92: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-network-check-target-ip-10-0-134-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "12059"
    uid: 83f9116a-3ab6-4cab-b43f-84152769177c
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:03:12Z"
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.309461ms
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:03:12Z"
    - latency: 862.822µs
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 1.183345ms
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 972µs
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 1.282977ms
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 988.672µs
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 1.170687ms
      message: 'network-check-target-ip-10-0-134-213: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:57:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:56:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-213.ec2.internal
      uid: 01cd3265-e21a-423e-84cd-c4ebc72a8ea1
    resourceVersion: "11812"
    uid: be3e687a-18a5-4a6c-96d3-6eb535624d0a
  spec:
    sourcePod: network-check-source-56499946bc-6468w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T19:02:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 1.600229ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:02:12Z"
    - latency: 1.02408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 1.85095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:01:12Z"
    - latency: 943.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 1.773834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T19:00:12Z"
    - latency: 1.238591ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 1.64145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:59:12Z"
    - latency: 851.67µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:58:12Z"
    - latency: 1.587851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:58:12Z"
kind: List
metadata:
  resourceVersion: ""