apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "21171"
    uid: 04d8bb41-0bec-4dfc-9697-904c6154a8dc
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:01:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.093058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:01:15Z"
    - latency: 864.452µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 1.209253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 1.517656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 897.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 937.242µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 947.265µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "20577"
    uid: fba83771-7a1a-470b-a73f-2871994cb412
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:00:15Z"
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.344816ms
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 7.637065ms
      message: 'load-balancer-api-external: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 6.090968ms
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 8.236709ms
      message: 'load-balancer-api-external: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 4.827833ms
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 8.251457ms
      message: 'load-balancer-api-external: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 5.683096ms
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 8.281234ms
      message: 'load-balancer-api-external: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 5.242899ms
      message: 'load-balancer-api-external: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 8.57917ms
      message: 'load-balancer-api-external: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "20576"
    uid: fa402dfa-e13b-420b-a535-69c7186f2447
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:00:15Z"
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.864725ms
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 7.622663ms
      message: 'load-balancer-api-internal: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 6.053518ms
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 8.207053ms
      message: 'load-balancer-api-internal: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 4.860679ms
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 8.194571ms
      message: 'load-balancer-api-internal: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 5.669388ms
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 8.259128ms
      message: 'load-balancer-api-internal: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 5.256107ms
      message: 'load-balancer-api-internal: tcp connection to aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 8.484075ms
      message: 'load-balancer-api-internal: resolved host name aa2f9a0dc6b6a466d9705b952f4be41b-eada0536e9d10afc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:56:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-128-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "21170"
    uid: 2bac98cc-acc6-4cf8-b4b7-a02d06ae2c86
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:01:15Z"
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.942404ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:01:15Z"
    - latency: 1.766077ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 1.761593ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 1.886712ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 1.694453ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 1.826498ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 1.874165ms
      message: 'network-check-target-ip-10-0-128-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-135-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "21168"
    uid: 291aecd2-d4c3-4142-8764-1dcf2eb52eef
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:01:15Z"
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.485µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:01:15Z"
    - latency: 810.105µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 1.225053ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 1.172488ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 871.077µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 786.097µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 1.521988ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-138-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "21169"
    uid: c1b6dbf6-6c56-4366-9119-4752dc7d0443
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:01:15Z"
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.524764ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:01:15Z"
    - latency: 2.39017ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 2.358197ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 2.291069ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 2.23304ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 2.114821ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 2.421975ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:55:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: 1cc6fa79-c12c-41c3-82f7-f62277e79fcd
    resourceVersion: "20575"
    uid: 46492ffd-2bd8-4c9c-bef3-b5ff489334ab
  spec:
    sourcePod: network-check-source-6f8b768455-pqxbk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:00:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.866µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 1.757165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T15:00:15Z"
    - latency: 897.947µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 1.793651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:59:15Z"
    - latency: 794.895µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 1.860728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:58:15Z"
    - latency: 840.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 1.731224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:57:15Z"
    - latency: 785.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:56:15Z"
    - latency: 2.296469ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:56:15Z"
kind: List
metadata:
  resourceVersion: ""