apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14948"
    uid: 136c87ec-d35c-4d56-96d4-59dc0bcc7a00
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:02:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.409194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:02:35Z"
    - latency: 818.317µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 1.067814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 862.682µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 1.037341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 1.026124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 1.106579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:56:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14507"
    uid: 5a31c92b-79f4-49f3-8efb-2919dc55ecb7
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:01:35Z"
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.200112ms
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 8.993156ms
      message: 'load-balancer-api-external: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 4.890754ms
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 7.664924ms
      message: 'load-balancer-api-external: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 4.770711ms
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 5.697639ms
      message: 'load-balancer-api-external: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 8.233679ms
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 7.978701ms
      message: 'load-balancer-api-external: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 3.888238ms
      message: 'load-balancer-api-external: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 8.298701ms
      message: 'load-balancer-api-external: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14508"
    uid: 49ee4cca-61e5-4eda-a2f0-6dd484dff238
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:01:35Z"
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.16122ms
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 9.037463ms
      message: 'load-balancer-api-internal: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 4.860023ms
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 7.607925ms
      message: 'load-balancer-api-internal: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 3.985554ms
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 5.796262ms
      message: 'load-balancer-api-internal: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 8.20328ms
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 8.051333ms
      message: 'load-balancer-api-internal: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 3.946469ms
      message: 'load-balancer-api-internal: tcp connection to a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 8.333666ms
      message: 'load-balancer-api-internal: resolved host name a7a70b42d008e4757bb0581d57506de0-77483f63b6e12ce8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-network-check-target-ip-10-0-131-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14947"
    uid: 8ee56932-6a09-4903-85e1-b322ff1f2f81
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:02:35Z"
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.512378ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:02:35Z"
    - latency: 2.141884ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 2.280392ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 2.18021ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 2.162218ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 2.171833ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 3.253265ms
      message: 'network-check-target-ip-10-0-131-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:56:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-network-check-target-ip-10-0-134-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14945"
    uid: 76c3eb73-103a-4cb3-bf04-1dd011fe88d5
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:02:35Z"
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.114µs
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:02:35Z"
    - latency: 1.492914ms
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 723.886µs
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 987.134µs
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 871.199µs
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 849.283µs
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 1.379955ms
      message: 'network-check-target-ip-10-0-134-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:56:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-network-check-target-ip-10-0-139-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14946"
    uid: a7310cc9-c707-4e52-aa2a-b94c243222ff
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:02:35Z"
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.911638ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:02:35Z"
    - latency: 1.81142ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 1.828242ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 2.095074ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 1.811814ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 1.833787ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 2.4316ms
      message: 'network-check-target-ip-10-0-139-194: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:56:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:55:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-11.ec2.internal
      uid: 4d460c61-4a34-4a89-9920-ecbfe0f6c54a
    resourceVersion: "14506"
    uid: c100b9a2-3c20-46d9-87ba-fd7149febaba
  spec:
    sourcePod: network-check-source-685456655f-lj9jw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T03:01:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069462ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 1.665502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:01:35Z"
    - latency: 908.546µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 1.775294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T03:00:35Z"
    - latency: 1.425074ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 1.645248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:59:35Z"
    - latency: 896.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 1.855765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:58:35Z"
    - latency: 1.215184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:57:35Z"
    - latency: 1.780235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:57:35Z"
kind: List
metadata:
  resourceVersion: ""