apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12503"
    uid: e8f1e44c-8516-4c05-af1a-bbf7aa6ed967
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:29:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.166734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:19Z"
    - latency: 944.078µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 1.344985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 1.009453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 1.102109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 1.125327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:19Z"
    - latency: 1.430689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:23:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12280"
    uid: 8c5ae520-7fa7-4495-9d68-8d4580659654
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:28:19Z"
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 23.429357ms
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 15.766527ms
      message: 'load-balancer-api-external: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 15.100179ms
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 8.849042ms
      message: 'load-balancer-api-external: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 17.049685ms
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 6.289331ms
      message: 'load-balancer-api-external: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 16.340617ms
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 9.90647ms
      message: 'load-balancer-api-external: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 17.357846ms
      message: 'load-balancer-api-external: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:19Z"
    - latency: 8.623971ms
      message: 'load-balancer-api-external: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:24:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12279"
    uid: 31231cb1-7935-4737-a130-3881c3c606de
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:28:19Z"
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.2789ms
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 15.916146ms
      message: 'load-balancer-api-internal: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 15.545705ms
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 8.906769ms
      message: 'load-balancer-api-internal: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 17.032853ms
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 6.349127ms
      message: 'load-balancer-api-internal: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 17.148625ms
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 10.175103ms
      message: 'load-balancer-api-internal: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 19.293362ms
      message: 'load-balancer-api-internal: tcp connection to a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:19Z"
    - latency: 8.670969ms
      message: 'load-balancer-api-internal: resolved host name a5fe97f4d33ef42f29c47eb8015112c5-f138e4b8749b9bd4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:24:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-network-check-target-ip-10-0-129-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12605"
    uid: 076b65ea-64df-4fc0-8885-b115d023d92a
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:29:51Z"
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.141847ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:51Z"
    - latency: 2.707538ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:51Z"
    - latency: 2.295916ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:51Z"
    - latency: 2.492068ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:51Z"
    - latency: 2.416266ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:51Z"
    - latency: 2.363829ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:51Z"
    - latency: 2.238586ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-network-check-target-ip-10-0-135-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12536"
    uid: 856a8f57-4b2b-4dd6-ae5d-01d4930684f7
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:29:27Z"
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089819ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:27Z"
    - latency: 1.182131ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:27Z"
    - latency: 924.757µs
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:27Z"
    - latency: 883.358µs
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:27Z"
    - latency: 1.220881ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:27Z"
    - latency: 963.046µs
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:27Z"
    - latency: 1.43289ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:23:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-network-check-target-ip-10-0-135-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12527"
    uid: 59a7430a-5b75-4733-b1fc-5d25bf034a9a
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:29:26Z"
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.163005ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:29:26Z"
    - latency: 2.45314ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:26Z"
    - latency: 1.024666ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:26Z"
    - latency: 2.537343ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:26Z"
    - latency: 2.324889ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:26Z"
    - latency: 1.318397ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:26Z"
    - latency: 1.080166ms
      message: 'network-check-target-ip-10-0-135-180: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:23:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T08:22:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-138.ec2.internal
      uid: d4ec01b5-0d23-4b3a-bdcc-89e9a603860a
    resourceVersion: "12278"
    uid: 0f6cce97-2eb1-4f8d-983d-6bfacf9ccbe3
  spec:
    sourcePod: network-check-source-6f78d59f99-prcdt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T08:28:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.217443ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 1.615834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:28:19Z"
    - latency: 1.820852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 1.747852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:27:19Z"
    - latency: 988.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 1.644104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:26:19Z"
    - latency: 2.28748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 2.172179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:25:19Z"
    - latency: 1.91553ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T08:24:19Z"
    - latency: 1.613291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T08:24:19Z"
kind: List
metadata:
  resourceVersion: ""