apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "24331"
    uid: 203213ca-efc9-4c73-a7f2-128acfc9393a
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:18:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.606049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:18:46Z"
    - latency: 1.196107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 1.252966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 1.254759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 1.256347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 1.182357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 1.004181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "23127"
    uid: 5d6f33c6-178f-4add-b075-cb3415efc3df
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:17:46Z"
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.308261ms
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 7.047802ms
      message: 'load-balancer-api-external: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 4.207476ms
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 7.658871ms
      message: 'load-balancer-api-external: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 4.575988ms
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 6.842162ms
      message: 'load-balancer-api-external: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 3.695945ms
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 6.49372ms
      message: 'load-balancer-api-external: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 3.760238ms
      message: 'load-balancer-api-external: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 11.667064ms
      message: 'load-balancer-api-external: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "23128"
    uid: 0ebb4221-0d6e-4c46-894e-50abafd2ec56
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:17:46Z"
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.977021ms
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 7.092159ms
      message: 'load-balancer-api-internal: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 4.159612ms
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 7.735305ms
      message: 'load-balancer-api-internal: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 5.046165ms
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 6.933438ms
      message: 'load-balancer-api-internal: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 5.029353ms
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 6.540648ms
      message: 'load-balancer-api-internal: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 4.172727ms
      message: 'load-balancer-api-internal: tcp connection to a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 11.715557ms
      message: 'load-balancer-api-internal: resolved host name a17d0062bfe1e4275ad7a4d419c6b1ea-25d9e6e8b0d0fd96.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-network-check-target-ip-10-0-129-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "24328"
    uid: 0a349279-f497-43bd-bf95-046af26dbc10
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:18:46Z"
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.162447ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:18:46Z"
    - latency: 842.518µs
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 1.261663ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 1.384576ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 1.533192ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 2.174692ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 1.409144ms
      message: 'network-check-target-ip-10-0-129-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-network-check-target-ip-10-0-129-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "24329"
    uid: 7501f6fc-1680-4d73-8c96-731f73a23d47
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:18:46Z"
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.671413ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:18:46Z"
    - latency: 2.078773ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 2.175043ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 2.192259ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 6.875987ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 2.958631ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 2.475675ms
      message: 'network-check-target-ip-10-0-129-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-network-check-target-ip-10-0-137-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "24330"
    uid: d419b488-7109-4008-a12e-d0721216817c
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:18:46Z"
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.692727ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:18:46Z"
    - latency: 1.92662ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 2.034227ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 2.026815ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 2.077064ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 2.90708ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 2.144486ms
      message: 'network-check-target-ip-10-0-137-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-13T19:11:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-160.ec2.internal
      uid: 60e157f5-998d-4b89-ae97-16119784f010
    resourceVersion: "23126"
    uid: ce3eb5ae-2888-40ce-80c7-39801ac7ba55
  spec:
    sourcePod: network-check-source-6f8b768455-q48gb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-13T19:17:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.851µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 2.13631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:17:46Z"
    - latency: 858.684µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 1.912219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:16:46Z"
    - latency: 1.26398ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 1.743581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:15:46Z"
    - latency: 819.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 1.744648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:14:46Z"
    - latency: 828.069µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-13T19:13:46Z"
    - latency: 2.746109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-13T19:13:46Z"
kind: List
metadata:
  resourceVersion: ""