apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "14069"
    uid: 69e410b0-b340-42d0-a3a5-bfcc7c52571b
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:45:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.632426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:45:12Z"
    - latency: 836.554µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:44:12Z"
    - latency: 940.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:43:12Z"
    - latency: 743.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:42:12Z"
    - latency: 936.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:41:12Z"
    - latency: 653.66µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:40:12Z"
    - latency: 1.429344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "16357"
    uid: 60d2f0c9-cc82-445a-8e50-ef2a6405c423
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:44:12Z"
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.129643ms
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 6.261429ms
      message: 'load-balancer-api-external: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 5.28086ms
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 7.58433ms
      message: 'load-balancer-api-external: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 4.620312ms
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 6.793618ms
      message: 'load-balancer-api-external: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 5.496439ms
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 7.98493ms
      message: 'load-balancer-api-external: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 5.023557ms
      message: 'load-balancer-api-external: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:46:12Z"
    - latency: 5.938985ms
      message: 'load-balancer-api-external: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "16356"
    uid: 62002b38-8fec-4598-af73-4af4303fe34b
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:44:12Z"
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.623589ms
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 6.319721ms
      message: 'load-balancer-api-internal: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 5.345341ms
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 7.400334ms
      message: 'load-balancer-api-internal: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 5.478366ms
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 6.890025ms
      message: 'load-balancer-api-internal: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 4.677872ms
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 8.028936ms
      message: 'load-balancer-api-internal: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 5.033708ms
      message: 'load-balancer-api-internal: tcp connection to ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:46:12Z"
    - latency: 5.879308ms
      message: 'load-balancer-api-internal: resolved host name ae6051c52d200495d9b11829e5cfae6d-0c339a13b7867018.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:46:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-128-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "14068"
    uid: 1fc1f734-2b06-4798-be96-c98ea2275749
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:45:12Z"
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.166643ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:45:12Z"
    - latency: 2.252487ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:44:12Z"
    - latency: 2.450917ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:43:12Z"
    - latency: 2.163552ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:42:12Z"
    - latency: 2.120759ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:41:12Z"
    - latency: 2.036061ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:40:12Z"
    - latency: 15.217645ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-129-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "14066"
    uid: e7ab8d9e-3e25-42a2-8000-0f5d2af09834
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:45:12Z"
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.996µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:45:12Z"
    - latency: 1.329979ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:44:12Z"
    - latency: 1.042195ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:43:12Z"
    - latency: 1.206228ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:42:12Z"
    - latency: 1.091373ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:41:12Z"
    - latency: 761.058µs
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:40:12Z"
    - latency: 2.778443ms
      message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-136-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "14067"
    uid: e7beedb4-d127-4d0f-b7aa-4dcb0657c9d2
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:45:12Z"
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.72139ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:45:12Z"
    - latency: 2.435994ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:44:12Z"
    - latency: 1.97939ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:43:12Z"
    - latency: 1.8102ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:42:12Z"
    - latency: 1.747506ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:41:12Z"
    - latency: 1.688187ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:40:12Z"
    - latency: 2.719411ms
      message: 'network-check-target-ip-10-0-136-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:39:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-203-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-203.ec2.internal
      uid: 08d44ebb-dcf3-4e9c-a1ee-13af740cbd0e
    resourceVersion: "16355"
    uid: d4296ee8-66fc-41ec-9d0c-ccddd3622998
  spec:
    sourcePod: network-check-source-989f8b8dc-bmnzb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:44:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.453µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 1.533167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:50:12Z"
    - latency: 849.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 1.983095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:49:12Z"
    - latency: 832.654µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 1.644338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:48:12Z"
    - latency: 904.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 2.228892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:47:12Z"
    - latency: 800.01µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:46:12Z"
    - latency: 1.743214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:46:12Z"
kind: List
metadata:
  resourceVersion: ""