apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "23014"
    uid: 7b7da65d-5f52-4a40-8068-520d23f2aa36
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:15:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:15:41Z"
    - latency: 2.758893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 1.219363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 1.316919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 851.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 2.055313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 1.091232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:09:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "22017"
    uid: 28c497d4-f3a9-4ea0-a12f-3fee90ea1b0a
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:14:41Z"
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.308697ms
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 11.427696ms
      message: 'load-balancer-api-external: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 5.787639ms
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 8.656971ms
      message: 'load-balancer-api-external: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 4.277301ms
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 8.309831ms
      message: 'load-balancer-api-external: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 5.309138ms
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 8.90318ms
      message: 'load-balancer-api-external: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 5.559927ms
      message: 'load-balancer-api-external: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 9.256527ms
      message: 'load-balancer-api-external: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:10:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "22016"
    uid: 72bce48a-ad26-4f17-b82a-23df9b4b6a61
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:14:41Z"
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.281496ms
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 9.638534ms
      message: 'load-balancer-api-internal: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 5.798207ms
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 8.585784ms
      message: 'load-balancer-api-internal: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 3.444675ms
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 8.193882ms
      message: 'load-balancer-api-internal: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 3.627196ms
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 8.858711ms
      message: 'load-balancer-api-internal: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 5.398778ms
      message: 'load-balancer-api-internal: tcp connection to a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 9.208323ms
      message: 'load-balancer-api-internal: resolved host name a2f25b6c2002a4e5b887a1b808d44487-f2b40fc74564307c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:10:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-network-check-target-ip-10-0-129-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "23011"
    uid: e5001250-90cb-4e8d-8c94-bf9bdddd500d
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:15:41Z"
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.087µs
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:15:41Z"
    - latency: 1.305149ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 1.361032ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 723.712µs
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 1.49631ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 1.524117ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 1.210425ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:09:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-network-check-target-ip-10-0-131-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "23012"
    uid: 8f72b019-b702-43a0-bee2-84d1de968438
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:15:41Z"
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.897046ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:15:41Z"
    - latency: 2.167569ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 2.100259ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 2.047646ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 1.850579ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 2.66894ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 1.746614ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:09:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-network-check-target-ip-10-0-141-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "23013"
    uid: d311aa85-4c1e-4b20-aacd-a75ac278ecec
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:15:41Z"
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.454154ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:15:41Z"
    - latency: 2.362007ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 2.124853ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 2.342044ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 2.240826ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 2.612758ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 2.5179ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:09:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T23:08:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-230.ec2.internal
      uid: 1a2e72d5-2184-4729-be78-eba0df7633d7
    resourceVersion: "22015"
    uid: 2bc918e2-aaba-44be-9df2-ba9def53f3ba
  spec:
    sourcePod: network-check-source-56499946bc-2z582
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T23:14:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.088µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 2.41286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:14:41Z"
    - latency: 899.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 2.062644ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:13:41Z"
    - latency: 936.845µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 1.823405ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:12:41Z"
    - latency: 1.007864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 1.709067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:11:41Z"
    - latency: 1.900892ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T23:10:41Z"
    - latency: 1.870147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T23:10:41Z"
kind: List
metadata:
  resourceVersion: ""