apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "23231"
    uid: c9dabb95-5ab2-4aee-aa88-7751d8af2688
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:51:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:02Z"
    - latency: 1.203975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 862.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 872.677µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 857.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 1.248537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 1.096884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "22076"
    uid: b6b69af0-3ef7-418b-b59b-1307eb55ee53
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:50:02Z"
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.333039ms
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 7.879184ms
      message: 'load-balancer-api-external: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 3.281288ms
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 7.814441ms
      message: 'load-balancer-api-external: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 3.194355ms
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 7.997749ms
      message: 'load-balancer-api-external: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 4.149606ms
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 8.998071ms
      message: 'load-balancer-api-external: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 4.261909ms
      message: 'load-balancer-api-external: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 8.055885ms
      message: 'load-balancer-api-external: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:46:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "22077"
    uid: 32105f83-fd9e-4644-9ad6-3ba0c8b3428b
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:50:02Z"
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.723607ms
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 7.845901ms
      message: 'load-balancer-api-internal: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 3.865609ms
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 7.780553ms
      message: 'load-balancer-api-internal: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 3.28663ms
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 7.932343ms
      message: 'load-balancer-api-internal: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 4.841296ms
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 8.940592ms
      message: 'load-balancer-api-internal: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 4.698687ms
      message: 'load-balancer-api-internal: tcp connection to a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 7.923513ms
      message: 'load-balancer-api-internal: resolved host name a750a2fe9cb6049728668949458e2659-8d6608b50264e3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:46:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-128-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "23229"
    uid: dca8c17a-f8eb-41de-8cc4-e1beaecb0b06
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:51:02Z"
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.93592ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:02Z"
    - latency: 2.110234ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 1.949482ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 1.753758ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 1.727055ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 2.017653ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 2.093257ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-137-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "23230"
    uid: 22b17395-d93a-4e48-b297-fc33cf4720ac
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:51:02Z"
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.324139ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:02Z"
    - latency: 2.546777ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 2.086848ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 1.828386ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 1.778758ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 2.918368ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 2.298869ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-139-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "23228"
    uid: 7dbf39e9-fdf0-4762-a0a0-044f143ffd13
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:51:02Z"
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.68µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:51:02Z"
    - latency: 1.520644ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 1.291313ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 913.805µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 774.907µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 1.488872ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 1.203696ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:45:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T01:44:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 0e5b53ad-3b08-46e2-ab23-7bedabdb77d4
    resourceVersion: "22075"
    uid: 9e60a00f-b83a-48b6-a2ba-d59305eac9af
  spec:
    sourcePod: network-check-source-7cbc45fddc-wvbjc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T01:50:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.27713ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 1.942082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:50:02Z"
    - latency: 878.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 1.848588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:49:02Z"
    - latency: 947.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 1.979415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:48:02Z"
    - latency: 1.03856ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 1.776244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:47:02Z"
    - latency: 1.829928ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T01:46:02Z"
    - latency: 1.977281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T01:46:02Z"
kind: List
metadata:
  resourceVersion: ""