apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14661"
    uid: 32bc807e-08bb-4726-b95a-4eb99ddd902c
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:19:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.94µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:56Z"
    - latency: 1.001837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 1.368838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 850.251µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 841.023µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 802.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 777.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14230"
    uid: 73bd8b47-74f8-4904-89d5-ff96352bd601
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:18:56Z"
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810165ms
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 13.359829ms
      message: 'load-balancer-api-external: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 5.121294ms
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 16.374855ms
      message: 'load-balancer-api-external: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 4.671765ms
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 8.182131ms
      message: 'load-balancer-api-external: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 3.885102ms
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 9.777167ms
      message: 'load-balancer-api-external: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 5.187386ms
      message: 'load-balancer-api-external: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 8.807035ms
      message: 'load-balancer-api-external: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:14:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14231"
    uid: 925c7e47-59d9-4f4f-983b-b1de12715c4c
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:18:56Z"
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.892586ms
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 13.384654ms
      message: 'load-balancer-api-internal: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 5.106665ms
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 16.852349ms
      message: 'load-balancer-api-internal: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 5.374213ms
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 8.122819ms
      message: 'load-balancer-api-internal: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 3.873029ms
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 9.836783ms
      message: 'load-balancer-api-internal: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 5.220824ms
      message: 'load-balancer-api-internal: tcp connection to aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 8.733327ms
      message: 'load-balancer-api-internal: resolved host name aa093558dcc3c4e7f929083bed0e2b08-39323cb79eb2ab57.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:14:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-130-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14659"
    uid: 5411fcd2-a754-43f9-bcea-982d8091ed10
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:19:56Z"
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.032943ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:56Z"
    - latency: 2.244129ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 2.191748ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 2.105993ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 1.983776ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 2.35165ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 2.165177ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-133-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14658"
    uid: ce16a912-43cf-4978-b0ca-7d52f48274f9
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:19:56Z"
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.33µs
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:56Z"
    - latency: 872.052µs
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 1.544077ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 776.501µs
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 745.15µs
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 822.194µs
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 1.745441ms
      message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-network-check-target-ip-10-0-134-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14660"
    uid: a73a2cb5-95d6-4247-bf1d-79a076321d4a
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:19:56Z"
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.163899ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:19:56Z"
    - latency: 2.591374ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 2.538016ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 1.915186ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 2.573932ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 2.017837ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 2.268977ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:13:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:12:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-190-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-190.ec2.internal
      uid: 279019c4-8982-48e8-b400-e7dda4d38dfa
    resourceVersion: "14229"
    uid: bc1b04d5-5576-4d06-b8a0-d801bbbdf61c
  spec:
    sourcePod: network-check-source-685456655f-qhfdn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:18:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.226µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 2.333756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:18:56Z"
    - latency: 1.15599ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 2.106993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:17:56Z"
    - latency: 1.092501ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 1.778027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:16:56Z"
    - latency: 844.576µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 1.963126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:15:56Z"
    - latency: 850.314µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:14:56Z"
    - latency: 1.698336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:14:56Z"
kind: List
metadata:
  resourceVersion: ""