apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "22941"
    uid: a1e42116-28b4-4508-b60e-a8e11e54eb6d
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:05:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:49Z"
    - latency: 1.470899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 1.505985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 1.014929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 1.025034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 944.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 1.13673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "21934"
    uid: 987342c3-7b71-4611-9930-01b2984f83bf
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:04:49Z"
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.296341ms
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 9.401433ms
      message: 'load-balancer-api-external: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 4.358304ms
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 8.402261ms
      message: 'load-balancer-api-external: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 8.035132ms
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 10.140473ms
      message: 'load-balancer-api-external: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 5.249376ms
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 7.266171ms
      message: 'load-balancer-api-external: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 5.198976ms
      message: 'load-balancer-api-external: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 8.653483ms
      message: 'load-balancer-api-external: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:00:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "21933"
    uid: 7f630bbf-0e9c-494a-8c1b-775b17bd4430
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:04:49Z"
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.617089ms
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 9.301259ms
      message: 'load-balancer-api-internal: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 4.935817ms
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 8.276653ms
      message: 'load-balancer-api-internal: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 7.988305ms
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 10.241144ms
      message: 'load-balancer-api-internal: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 5.177501ms
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 7.336868ms
      message: 'load-balancer-api-internal: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 4.278985ms
      message: 'load-balancer-api-internal: tcp connection to ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 8.627713ms
      message: 'load-balancer-api-internal: resolved host name ae82b285227354edd93053e872fbe067-af13088d1ed6f90b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:00:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-network-check-target-ip-10-0-132-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "22940"
    uid: ec7b59dd-f7c9-4e95-9f06-1a74525fd81b
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:05:49Z"
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.539577ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:49Z"
    - latency: 2.73484ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 2.361057ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 2.296569ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 2.12437ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 3.009716ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 2.383734ms
      message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-network-check-target-ip-10-0-134-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "22939"
    uid: f7f14779-1e80-45e0-a9f2-ca12299be80e
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:05:49Z"
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159026ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:49Z"
    - latency: 1.011684ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 1.013937ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 1.118919ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 1.263562ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 1.115066ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 1.29587ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-network-check-target-ip-10-0-135-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "22938"
    uid: c6001b59-0627-49a5-ac0b-98d6454668da
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:05:49Z"
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047612ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:05:49Z"
    - latency: 3.373854ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 2.837683ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 2.247196ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 2.091368ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 2.67609ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 2.428189ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T17:59:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T17:58:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-6.ec2.internal
      uid: 912a9549-268a-4dcc-8563-e3a10e8c85a2
    resourceVersion: "21932"
    uid: c47344c7-e6c4-4611-abcd-8676b3808b86
  spec:
    sourcePod: network-check-source-56499946bc-hzngp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:04:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 2.250795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:04:49Z"
    - latency: 1.288594ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 2.016872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:03:49Z"
    - latency: 878.806µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 2.293555ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:02:49Z"
    - latency: 822.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 1.818247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:01:49Z"
    - latency: 968.679µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:00:49Z"
    - latency: 3.082414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:00:49Z"
kind: List
metadata:
  resourceVersion: ""