apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12298"
    uid: c311b665-931a-4285-8ed0-4908a2794c8f
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:31:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.52µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:31:27Z"
    - latency: 1.062143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 1.015361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 1.81177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 1.373309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 1.182082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 1.478963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12142"
    uid: 81080a06-7321-4e14-8998-bf1d266fb73e
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:30:27Z"
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 59.668958ms
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 8.409076ms
      message: 'load-balancer-api-external: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 58.57565ms
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 7.449896ms
      message: 'load-balancer-api-external: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 69.842221ms
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 10.936461ms
      message: 'load-balancer-api-external: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 56.751358ms
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 7.917224ms
      message: 'load-balancer-api-external: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 57.116946ms
      message: 'load-balancer-api-external: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 9.905244ms
      message: 'load-balancer-api-external: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12141"
    uid: cb21bc7c-c263-4e7a-afcf-0898fc6a12d3
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:30:27Z"
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 58.318777ms
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 8.347226ms
      message: 'load-balancer-api-internal: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 58.602916ms
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 7.376332ms
      message: 'load-balancer-api-internal: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 59.314373ms
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 10.780147ms
      message: 'load-balancer-api-internal: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 56.23751ms
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 7.851804ms
      message: 'load-balancer-api-internal: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 57.159065ms
      message: 'load-balancer-api-internal: tcp connection to a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 9.851882ms
      message: 'load-balancer-api-internal: resolved host name a833aef6fcce34b3382a1ceb8002cf40-39a6703b7698ae02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-network-check-target-ip-10-0-130-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12294"
    uid: 0e906827-8f9b-43f6-b37d-f123a0f45a96
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:31:27Z"
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.604205ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:31:27Z"
    - latency: 2.140679ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 1.95794ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 2.4238ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 1.870254ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 2.559627ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 2.796966ms
      message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-network-check-target-ip-10-0-135-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12295"
    uid: b6704a5b-3f4e-428e-b59b-adf2a745303d
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:31:27Z"
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.662567ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:31:27Z"
    - latency: 1.992469ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 2.153996ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 2.439269ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 2.174438ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 2.522637ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 2.434859ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-network-check-target-ip-10-0-136-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12296"
    uid: 644f87da-0e3d-41de-835d-5b58168e932a
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:31:27Z"
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.697109ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:31:27Z"
    - latency: 1.262512ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 1.193441ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 1.08522ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 1.665579ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 1.502535ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 1.621657ms
      message: 'network-check-target-ip-10-0-136-49: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:24:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-49-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-49.us-west-1.compute.internal
      uid: 709cdcde-435c-4a15-8b88-8d45f856ffdb
    resourceVersion: "12140"
    uid: d429cb5c-c9b0-4da6-8507-5e9b7d57e7ce
  spec:
    sourcePod: network-check-source-6f78d59f99-5kppb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:30:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.278µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 2.151768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:30:27Z"
    - latency: 742.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 1.936359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 1.569341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 3.103884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 1.008152ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 1.895066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 826.47µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 2.659356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:27Z"
kind: List
metadata:
  resourceVersion: ""