apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "22241"
    uid: 93965f17-eafd-46f6-b590-02d309e079d4
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:03Z"
    - latency: 1.126423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 1.171067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 1.059512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 1.132984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 1.241086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 1.105008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "21213"
    uid: 751e04b7-8ea3-41ac-b1b3-c2ed1e6762ab
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:05:03Z"
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.91037ms
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 8.18327ms
      message: 'load-balancer-api-external: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 6.935122ms
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 17.22728ms
      message: 'load-balancer-api-external: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 3.956038ms
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 8.985693ms
      message: 'load-balancer-api-external: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 5.334216ms
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 9.422297ms
      message: 'load-balancer-api-external: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 5.393306ms
      message: 'load-balancer-api-external: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 9.066281ms
      message: 'load-balancer-api-external: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "21214"
    uid: 6fc43c02-929d-4c8f-9422-6d335abcacce
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:05:03Z"
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.950433ms
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 8.080549ms
      message: 'load-balancer-api-internal: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 6.915162ms
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 17.122739ms
      message: 'load-balancer-api-internal: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 3.998303ms
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 8.90483ms
      message: 'load-balancer-api-internal: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 5.346331ms
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 9.340271ms
      message: 'load-balancer-api-internal: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 5.407753ms
      message: 'load-balancer-api-internal: tcp connection to a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 8.943693ms
      message: 'load-balancer-api-internal: resolved host name a5c87c80936974062a780fd1c721f960-6e6eccc7a87d1ca6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:01:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-128-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "22238"
    uid: 161f951b-e49d-4a0b-9b69-da5bd61856af
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:03Z"
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.701189ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:03Z"
    - latency: 2.338246ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 2.157521ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 2.467939ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 2.235568ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 2.242496ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 2.362618ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-129-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "22240"
    uid: 21aae5ea-966e-41fb-9ad4-b173ec622c00
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:03Z"
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.65258ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:03Z"
    - latency: 1.402029ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 990.741µs
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 969.742µs
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 1.04483ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 1.039893ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 1.25039ms
      message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-138-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "22239"
    uid: fbf103b9-4006-476e-a23a-86da1909a90d
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:06:03Z"
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.958517ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:06:03Z"
    - latency: 1.925645ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 1.930808ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 1.951913ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 1.930541ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 2.045216ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 2.106095ms
      message: 'network-check-target-ip-10-0-138-59: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:00:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T15:59:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-170-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-170.ec2.internal
      uid: 7c679eae-5807-451d-a594-80b7117ca8f3
    resourceVersion: "21212"
    uid: fd4c4b20-db54-4f93-ab14-8e17dfea2b0c
  spec:
    sourcePod: network-check-source-989f8b8dc-m66kb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:05:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087122ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 1.726515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:05:03Z"
    - latency: 1.19555ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 1.570793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:04:03Z"
    - latency: 959.297µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 1.795122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:03:03Z"
    - latency: 830.604µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 1.990116ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:02:03Z"
    - latency: 902.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:01:03Z"
    - latency: 1.940938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:01:03Z"
kind: List
metadata:
  resourceVersion: ""